Thinking Out Loud

March 25, 2017

RAC Attack Vagrant FAILED

Filed under: Vagrant,VirtualBox — mdinh @ 10:34 pm

If anyone has successfully configured RAC Attack using Vagrant, I really would love to know how you did it.

First, instructions are all over the place and I finally followed the one below.

https://en.wikibooks.org/wiki/RAC_Attack_-_Oracle_Cluster_Database_at_Home/RAC_Attack_Automation

Does anyone know what the vagrant password is?

E:\vagrantfile\OracleLinux\racattack12cR1>vagrant up

collabn2 eth1 lanip  :192.168.78.52
collabn2 eth2 privip :172.16.100.52
collabn2 dns server role is slave
on first boot shared disks will be created, this will take some time

collabn1 eth1 lanip  :192.168.78.51
collabn1 eth2 privip :172.16.100.51
collabn1 dns server role is master
Bringing machine 'collabn2' up with 'virtualbox' provider...
Bringing machine 'collabn1' up with 'virtualbox' provider...
==> collabn2: Importing base box 'racattack/oracle65'...
==> collabn2: Matching MAC address for NAT networking...
==> collabn2: Checking if box 'racattack/oracle65' is up to date...
==> collabn2: Setting the name of the VM: collabn2.1703251454
==> collabn2: Fixed port collision for 22 => 2222. Now on port 2200.
==> collabn2: Clearing any previously set network interfaces...
==> collabn2: Preparing network interfaces based on configuration...
    collabn2: Adapter 1: nat
    collabn2: Adapter 2: hostonly
    collabn2: Adapter 3: hostonly
==> collabn2: Forwarding ports...
    collabn2: 22 (guest) => 2200 (host) (adapter 1)
==> collabn2: Running 'pre-boot' VM customizations...
==> collabn2: Booting VM...
==> collabn2: Waiting for machine to boot. This may take a few minutes...
    collabn2: SSH address: 127.0.0.1:2200
    collabn2: SSH username: vagrant
    collabn2: SSH auth method: private key
    collabn2:
    collabn2: Vagrant insecure key detected. Vagrant will automatically replace
    collabn2: this with a newly generated keypair for better security.
    collabn2:
    collabn2: Inserting generated public key within guest...
    collabn2: Removing insecure key from the guest if it's present...
    collabn2: Key inserted! Disconnecting and reconnecting using new SSH key...
    collabn2: Warning: Authentication failure. Retrying...
..........	
    collabn2: Warning: Authentication failure. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

E:\vagrantfile\OracleLinux\racattack12cR1>

++++++++++++++++++++++++++++

E:\vagrantfile\OracleLinux\racattack12cR1>vagrant plugin install vagrant-rekey-ssh
Installing the 'vagrant-rekey-ssh' plugin. This can take a few minutes...
Fetching: sshkey-1.9.0.gem (100%)
Fetching: vagrant-rekey-ssh-0.1.9.gem (100%)
Installed the plugin 'vagrant-rekey-ssh (0.1.9)'!

E:\vagrantfile\OracleLinux\racattack12cR1>vagrant box list
racattack/oracle65 (virtualbox, 16.01.01)
ubuntu/trusty64    (virtualbox, 20170313.0.7)

E:\vagrantfile\OracleLinux\racattack12cR1>vagrant reload

collabn2 eth1 lanip  :192.168.78.52
collabn2 eth2 privip :172.16.100.52
collabn2 dns server role is slave

collabn1 eth1 lanip  :192.168.78.51
collabn1 eth2 privip :172.16.100.51
collabn1 dns server role is master
==> collabn2: Less insecure SSH key not found, generating key
==> collabn2: Less insecure SSH key generated and stored at C:/Users/falcon/.vagrant.d/less_insecure_private_key
==> collabn2: Attempting graceful shutdown of VM...
    collabn2: Guest communication could not be established! This is usually because
    collabn2: SSH is not running, the authentication information was changed,
    collabn2: or some other networking issue. Vagrant will force halt, if
    collabn2: capable.
==> collabn2: Forcing shutdown of VM...
==> collabn2: Checking if box 'racattack/oracle65' is up to date...
==> collabn2: Setting the name of the VM: collabn2.1703251507
==> collabn2: Clearing any previously set forwarded ports...
==> collabn2: Fixed port collision for 22 => 2222. Now on port 2200.
==> collabn2: Clearing any previously set network interfaces...
==> collabn2: Preparing network interfaces based on configuration...
    collabn2: Adapter 1: nat
    collabn2: Adapter 2: hostonly
    collabn2: Adapter 3: hostonly
==> collabn2: Forwarding ports...
    collabn2: 22 (guest) => 2200 (host) (adapter 1)
==> collabn2: Running 'pre-boot' VM customizations...
==> collabn2: Booting VM...
==> collabn2: Waiting for machine to boot. This may take a few minutes...
    collabn2: SSH address: 127.0.0.1:2200
    collabn2: SSH username: vagrant
    collabn2: SSH auth method: private key
    collabn2: Warning: Authentication failure. Retrying...
..........	
    collabn2: Warning: Authentication failure. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

E:\vagrantfile\OracleLinux\racattack12cR1>

++++++++++++++++++++++++++++++

E:\vagrantfile\OracleLinux\racattack12cR1>vagrant ssh

collabn2 eth1 lanip  :192.168.78.52
collabn2 eth2 privip :172.16.100.52
collabn2 dns server role is slave

collabn1 eth1 lanip  :192.168.78.51
collabn1 eth2 privip :172.16.100.51
collabn1 dns server role is master
This command requires a specific VM name to target in a multi-VM environment.

E:\vagrantfile\OracleLinux\racattack12cR1>vagrant box list
racattack/oracle65 (virtualbox, 16.01.01)
ubuntu/trusty64    (virtualbox, 20170313.0.7)


E:\vagrantfile\OracleLinux\racattack12cR1>vagrant ssh collabn1

collabn1 eth1 lanip  :192.168.78.51
collabn1 eth2 privip :172.16.100.51
collabn1 dns server role is master
VM must be created before running this command. Run `vagrant up` first.

E:\vagrantfile\OracleLinux\racattack12cR1>vboxmanage list runningvms
"ubuntu_default_1490460698004_34177" {78574166-49a6-433f-af6a-f3d03146a5f4}
"collabn2.1703251507" {ef37e131-f44a-49f8-ae2a-7eed423c1c7e}

E:\vagrantfile\OracleLinux\racattack12cR1>vagrant ssh collabn2

collabn2 eth1 lanip  :192.168.78.52
collabn2 eth2 privip :172.16.100.52
collabn2 dns server role is slave
vagrant@127.0.0.1's password:
vagrant@127.0.0.1's password:
vagrant@127.0.0.1's password:
Connection to 127.0.0.1 closed by remote host.
Connection to 127.0.0.1 closed.

E:\vagrantfile\OracleLinux\racattack12cR1>vagrant ssh collabn2

collabn2 eth1 lanip  :192.168.78.52
collabn2 eth2 privip :172.16.100.52
collabn2 dns server role is slave
vagrant@127.0.0.1's password:
vagrant@127.0.0.1's password:

E:\vagrantfile\OracleLinux\racattack12cR1>

++++++++++++++++++++++++++++++

E:\vagrantfile>vagrant box list
racattack/oracle65 (virtualbox, 16.01.01)
ubuntu/trusty64    (virtualbox, 20170313.0.7)

E:\vagrantfile>vagrant box remove racattack/oracle65

collabn2 eth1 lanip  :192.168.78.52
collabn2 eth2 privip :172.16.100.52
collabn2 dns server role is slave
on first boot shared disks will be created, this will take some time
Removing box 'racattack/oracle65' (v16.01.01) with provider 'virtualbox'...

E:\vagrantfile>vagrant box list
ubuntu/trusty64 (virtualbox, 20170313.0.7)

E:\vagrantfile>

Advertisements

1 Comment »

  1. Hi,

    Have you tried this: https://github.com/racattack/racattack-ansible-oracle?

    I just tried it and it works. If all you want is to have the machines created, just skip the ‘vagrant provision’ part.

    regards
    /M

    Comment by oravirt — March 25, 2017 @ 11:19 pm | Reply


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a free website or blog at WordPress.com.

%d bloggers like this: