Yes, that was the issue,

Resolved.

On 18 May 2017 8:20 pm, "[email protected]" <[email protected]> wrote:

> Try the vboxmanage poweroff commands to kill running VMs.  There's also a
> command to list all running VMs which is currently escaping me.  Then try
> starting again
>
> Jon
>
> On Wed, May 17, 2017, 9:15 PM Kevin Waterson <[email protected]>
> wrote:
>
>> Installing full dev environment,
>> Everything seems to be building, however, it is reporting that the host
>> is already in use.
>> I can see nothing in /etc/hosts
>>
>> Any ideas on this on?
>>
>> Thanks
>> Kevin
>>
>> Bringing up enviroment
>>  Running with ansible-skip-tags: ["sensors", "quick_dev"]
>> Bringing machine 'node1' up with 'virtualbox' provider...
>> ==> node1: Importing base box 'metron/centos_base'...
>> ==> node1: Matching MAC address for NAT networking...
>> ==> node1: Checking if box 'metron/centos_base' is up to date...
>> ==> node1: Setting the name of the VM: full-dev-platform_node1_149506
>> 0344605_46112
>> ==> node1: Fixed port collision for 22 => 2222. Now on port 2200.
>> ==> node1: Clearing any previously set network interfaces...
>> ==> node1: Preparing network interfaces based on configuration...
>>     node1: Adapter 1: nat
>>     node1: Adapter 2: hostonly
>> ==> node1: Forwarding ports...
>>     node1: 22 (guest) => 2200 (host) (adapter 1)
>> ==> node1: Running 'pre-boot' VM customizations...
>> ==> node1: Booting VM...
>> ==> node1: Waiting for machine to boot. This may take a few minutes...
>>     node1: SSH address: 127.0.0.1:2200
>>     node1: SSH username: vagrant
>>     node1: SSH auth method: private key
>>     node1:
>>     node1: Vagrant insecure key detected. Vagrant will automatically
>> replace
>>     node1: this with a newly generated keypair for better security.
>>     node1:
>>     node1: Inserting generated public key within guest...
>>     node1: Removing insecure key from the guest if it's present...
>>     node1: Key inserted! Disconnecting and reconnecting using new SSH
>> key...
>> ==> node1: Machine booted and ready!
>> ==> node1: Checking for guest additions in VM...
>> ==> node1: Setting hostname...
>> The following SSH command responded with a non-zero exit status.
>> Vagrant assumes that this means the command failed!
>>
>> # Update sysconfig
>> sed -i 's/\(HOSTNAME=\).*/\1node1/' /etc/sysconfig/network
>>
>> # Update DNS
>> sed -i 's/\(DHCP_HOSTNAME=\).*/\1"node1"/' /etc/sysconfig/network-scripts
>> /ifcfg-*
>>
>> # Set the hostname - use hostnamectl if available
>> echo 'node1' > /etc/hostname
>> if command -v hostnamectl; then
>>   hostnamectl set-hostname --static 'node1'
>>   hostnamectl set-hostname --transient 'node1'
>> else
>>   hostname -F /etc/hostname
>> fi
>>
>> # Remove comments and blank lines from /etc/hosts
>> sed -i'' -e 's/#.*$//' -e '/^$/d' /etc/hosts
>>
>> # Prepend ourselves to /etc/hosts
>> grep -w 'node1' /etc/hosts || {
>>   sed -i'' '1i 127.0.0.1\tnode1\tnode1' /etc/hosts
>> }
>>
>> # Restart network
>> service network restart
>>
>>
>> Stdout from the command:
>>
>> Shutting down interface eth0:  [  OK  ]
>> Shutting down interface eth1:  [  OK  ]
>> Shutting down loopback interface:  [  OK  ]
>> Bringing up loopback interface:  [  OK  ]
>> Bringing up interface eth0:
>> Determining IP information for eth0... done.
>> [  OK  ]
>> Bringing up interface eth1:  Determining if ip address 192.168.66.121 is
>> already in use for device eth1...
>> Error, some other host (08:00:27:1E:21:07) already uses address
>> 192.168.66.121.
>> [FAILED]
>>
>>
>> Stderr from the command:
>>
>>
>> id       name   provider   state   directory
>>
>> ------------------------------------------------------------
>> ------------------------------------------------------------
>> bd930da  node1  virtualbox running /home/kevin/metron/docs/incuba
>> tor-metron/metron-deployment/vagrant/full-dev-platform
>>
>> The above shows information about all known Vagrant environments
>> on this machine. This data is cached and may not be completely
>> up-to-date. To interact with any of the machines, you can go to
>> that directory and run Vagrant, or you can use the ID directly
>> with Vagrant commands from any directory. For example:
>> "vagrant destroy 1a2b3c4d"
>>  Running with ansible-skip-tags: ["sensors", "quick_dev"]
>> #########################################
>> ##         Accessing Vagrant           ##
>> #########################################
>> ssh: connect to host 127.0.0.1 port 2201: Connection refused
>> done
>> kevin@sirius:~/metron/docs$ more /etc/hosts
>>
>> 127.0.0.1    localhost
>> 127.0.0.1    leap.dev
>> 127.0.0.1    azgovbiz.dev
>> 127.0.0.1    kirtan.dev
>> 127.0.0.1    sias.dev
>> 127.0.0.1    skf.dev
>> 127.0.0.1    digitalfortress.dev
>> 127.0.1.1    sirius
>>
>> # The following lines are desirable for IPv6 capable hosts
>> ::1     ip6-localhost ip6-loopback
>> fe00::0 ip6-localnet
>> ff00::0 ip6-mcastprefix
>> ff02::1 ip6-allnodes
>> ff02::2 ip6-allrouters
>>
>> --
>
> Jon
>

Reply via email to