You are correct, I saw both of those listed, so I kept: 'root 23941 1 0 Apr08 ? 00:00:00 /usr/sbin/dhcpd vmnet1 vmnet1' and I killed the other one. The messages log doesn't seem to be of much use (or maybe the lack there of tells us something?) I tried reseting the VMs and even just powered them down and tried a new reservation and I still get the same not responding to ssh message and this is the output in the /var/log/messages:
Apr 12 12:40:44 vcl kernel: device eth0 left promiscuous mode Apr 12 12:40:44 vcl kernel: bridge-eth0: disabled promiscuous mode Apr 12 12:44:29 vcl /usr/lib/vmware/bin/vmware-hostd[1533]: Accepted password for user root from 127.0.0.1 Apr 12 12:45:00 vcl last message repeated 13 times Apr 12 12:45:04 vcl last message repeated 2 times Apr 12 12:45:05 vcl kernel: device eth0 entered promiscuous mode Apr 12 12:45:05 vcl kernel: bridge-eth0: enabled promiscuous mode Apr 12 12:45:06 vcl /usr/lib/vmware/bin/vmware-hostd[1533]: Accepted password for user root from 127.0.0.1 Apr 12 12:45:10 vcl last message repeated 2 times Apr 12 12:45:12 vcl kernel: device eth0 left promiscuous mode Apr 12 12:45:12 vcl kernel: bridge-eth0: disabled promiscuous mode Apr 12 12:45:12 vcl kernel: device eth0 entered promiscuous mode Apr 12 12:45:12 vcl kernel: bridge-eth0: enabled promiscuous mode -Tyler On Tue, Apr 12, 2011 at 11:54 AM, Andy Kurth <[email protected]> wrote: > It looks like you're close. DHCP on the private host-only network isn't > working. The VM that VCL created was assigned the correct MAC addresses: > |15920|53:53|reload| : "ethernet0.address" => "00:50:56:1a:01:01", > |15920|53:53|reload| : "ethernet1.address" => "00:50:56:1a:01:02", > > I think it may be failing because VMware installed and started its own DHCP > service when the host-only network was configured. Run this command: > ps -ef | grep dhcp > > Do you see 2 processes that look like this?: > /usr/sbin/dhcpd vmnet1 > > /usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet1/dhcpd/dhcpd.conf -lf > /etc/vmware/vmnet1/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet1.pid > vmnet1 > > If you do see the vmnet-dhcpd process along with dhcpd, try killing the > vmnet-dhcpd process. Hopefully this allows the normal dhcpd process to > respond to the VM's DHCP request. > > The main way to debug DHCP problems is to look at /var/log/messages. Try > running the following command: > tail -f /var/log/messages | grep -i dhcp > > Then reboot the VM that VCL created. If the VM's DHCP request is getting > to the dhcpd service running on the management node then you should see > output containing the private MAC address: 00:50:56:1a:01:01. > > The public IP address isn't necessarily a problem. Once the private > interface gets an IP address and responds to SSH, vcld will SSH in and > configure the public interface with a static address if you have configured > the management node and IP address for the VM in the VCL database > accordingly. > > -Andy > > > On 4/11/2011 1:41 PM, Tyler Hardesty wrote: > >> Ok, sorry to be such a bug with the same problem but I've done >> everything exactly how it is in the link that you provided and after >> this image is created, it still fails to be reserved saying it's not >> responding to ssh. Here are some of my configs: >> >> [root@vcl ~]# ifconfig >> eth0 Link encap:Ethernet HWaddr 00:1B:63:99:DA:B6 >> inet addr:144.38.205.200 <tel:144.38.205.200> >> Bcast:144.38.205.255 <tel:144.38.205.255> Mask:255.255.255.128 >> >> inet6 addr: fe80::21b:63ff:fe99:dab6/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:26728797 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:14037294 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:3637195452 (3.3 GiB) TX bytes:2717331485 (2.5 GiB) >> Interrupt:185 >> >> lo Link encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> inet6 addr: ::1/128 Scope:Host >> UP LOOPBACK RUNNING MTU:16436 Metric:1 >> RX packets:714243376 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:714243376 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:2461321418 (2.2 GiB) TX bytes:2461321418 (2.2 GiB) >> >> vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01 >> inet addr:192.168.0.1 Bcast:192.168.255.255 Mask:255.255.0.0 >> inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:4237 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:6875 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> [root@vcl ~]# cat /etc/dhcpd.conf >> # >> # DHCP Server Configuration file. >> # see /usr/share/doc/dhcp*/dhcpd.conf.sample >> # >> ddns-update-style none; shared-network vmnet1 { >> subnet 192.168.0.0 netmask 255.255.0.0 { >> ignore unknown-clients; >> option routers 192.168.0.1; >> host vm-1 { >> option host-name "vm-1"; >> hardware ethernet 00:50:56:1a:01:01; >> fixed-address 192.168.1.1; >> filename "/tftpboot/pxelinux.0"; >> option dhcp-server-identifier 127.0.0.1; >> next-server 127.0.0.1; >> } >> >> host vm-2 { >> option host-name "vm-2"; >> hardware ethernet 00:50:56:1a:01:03; >> fixed-address 192.168.1.2; >> filename "/tftpboot/pxelinux.0"; >> option dhcp-server-identifier 127.0.0.1; >> next-server 127.0.0.1; >> } >> >> host vm-3 { >> option host-name "vm-3"; >> hardware ethernet 00:50:56:1a:01:05; >> fixed-address 192.168.1.3; >> filename "/tftpboot/pxelinux.0"; >> option dhcp-server-identifier 127.0.0.1; >> next-server 127.0.0.1; >> } >> ......... >> ......... >> >> } >> } >> >> When I set up the VM Base machines, I followed the instructions on the >> site with network adapter 1 set to HostOnly and network adapter 2 set to >> Bridged... the host only network gets automatically configured with a >> 192.168.128.x ip so I statically set it to 192.168.1.x to match what's >> in the database and I statically set network adapter 2 with >> 144.38.205.201 <tel:144.38.205.201> ..... after the image is captured >> >> and it tries to make a reservation I notice that the network adapter 1 >> has an IP of 169.254.212.140 (or 169.254.xxx.xxx) and adapter 2 has an >> IP of 0.0.0.0 ... Does that even matter? Here are some snippets of my >> log file (my full log file can be found here - >> http://tylerhardesty.info/it4600/reslog.txt and again, sorry for being >> so troublesome but thanks for all the help!!!!): >> >> 2011-04-11 >> 01:58:11|15920|53:53|reload|VMware.pm:prepare_vmx(1699)|created >> temporary vmx file: /tmp/vm-1_34-v0.vmx >> 2011-04-11 >> 01:58:12|15920|53:53|reload|Linux.pm:create_directory(1502)|directory >> already exists on localvmhost: '/var/lib/vmware/Virtual >> Machines/vm-1_34-v0' >> 2011-04-11 >> 01:58:12|15920|53:53|reload|utils.pm:run_scp_command(5584)|attempting to >> copy file via SCP: '/tmp/vm-1_34-v0.vmx' --> >> 'localvmhost:"/var/lib/vmware/Virtual\ >> Machines/vm-1_34-v0/vm-1_34-v0.vmx"' >> 2011-04-11 >> 01:58:12|15920|53:53|reload|utils.pm:run_scp_command(5620)|copied file >> via SCP: '/tmp/vm-1_34-v0.vmx' --> >> 'localvmhost:"/var/lib/vmware/Virtual\ >> Machines/vm-1_34-v0/vm-1_34-v0.vmx"' >> 2011-04-11 >> 01:58:12|15920|53:53|reload|Linux.pm:copy_file_to(1837)|copied file from >> management node to localvmhost: '/tmp/vm-1_34-v0.vmx' --> >> localvmhost:'/var/lib/vmware/Virtual Machines/vm-1_34-v0/vm-1_34-v0.vmx' >> 2011-04-11 >> 01:58:12|15920|53:53|reload|VMware.pm:prepare_vmx(1711)|created vmx file >> on VM host: /var/lib/vmware/Virtual Machines/vm-1_34-v0/vm-1_34-v0.vmx >> 2011-04-11 >> 01:58:12|15920|53:53|reload|VMware.pm:prepare_vmx(1714)|deleted >> temporary vmx file: /tmp/vm-1_34-v0.vmx >> 2011-04-11 >> 01:58:12|15920|53:53|reload|utils.pm:insertloadlog(3875)|inserted >> computer=8, vmsetupconfig, prepared vmx file >> 2011-04-11 >> 01:58:12|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call >> count: 6 (vmsvc/getallvms) >> 2011-04-11 01:58:13|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 01:58:13 >> 2011-04-11 >> 01:58:14|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(208)|executed >> command on VM host localvmhost: vmware-vim-cmd vmsvc/getallvms >> 2011-04-11 >> 01:58:14|15920|53:53|reload|VIM_SSH.pm:get_registered_vms(835)|found 0 >> registered VMs >> 2011-04-11 >> 01:58:14|15920|53:53|reload|VMware.pm:is_vm_registered(3738)|VM is not >> registered: '/var/lib/vmware/Virtual Machines/vm-1_34-v0/vm-1_34-v0.vmx' >> 2011-04-11 >> 01:58:14|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call >> count: 7 (solo/registervm "/var/lib/vmware/Virtual\ >> Machines/vm-1_34-v0/vm-1_34-v0.vmx") >> 2011-04-11 >> 01:58:16|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(208)|executed >> command on VM host localvmhost: vmware-vim-cmd solo/registervm >> "/var/lib/vmware/Virtual\ Machines/vm-1_34-v0/vm-1_34-v0.vmx" >> 2011-04-11 >> 01:58:16|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call >> count: 8 (vmsvc/getallvms) >> 2011-04-11 >> 01:58:18|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(208)|executed >> command on VM host localvmhost: vmware-vim-cmd vmsvc/getallvms >> 2011-04-11 >> 01:58:18|15920|53:53|reload|VIM_SSH.pm:get_registered_vms(835)|found 1 >> registered VMs >> 2011-04-11 >> 01:58:18|15920|53:53|reload|VMware.pm:is_vm_registered(3733)|VM is >> registered: /var/lib/vmware/Virtual Machines/vm-1_34-v0/vm-1_34-v0.vmx >> 2011-04-11 >> 01:58:18|15920|53:53|reload|VIM_SSH.pm:vm_register(1105)|registered VM: >> '/var/lib/vmware/Virtual\ Machines/vm-1_34-v0/vm-1_34-v0.vmx' >> 2011-04-11 >> 01:58:18|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call >> count: 9 (vmsvc/getallvms) >> 2011-04-11 01:58:18|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 01:58:18 >> 2011-04-11 >> 01:58:20|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(208)|executed >> command on VM host localvmhost: vmware-vim-cmd vmsvc/getallvms >> 2011-04-11 >> 01:58:20|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call >> count: 10 (vmsvc/power.on 336) >> 2011-04-11 >> 01:58:21|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(208)|executed >> command on VM host localvmhost: vmware-vim-cmd vmsvc/power.on 336 >> 2011-04-11 >> 01:58:21|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call >> count: 11 (vmsvc/getallvms) >> 2011-04-11 01:58:23|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 01:58:23 >> 2011-04-11 >> 01:58:24|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(208)|executed >> command on VM host localvmhost: vmware-vim-cmd vmsvc/getallvms >> 2011-04-11 >> 01:58:24|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call >> count: 12 (vmsvc/get.tasklist 336) >> 2011-04-11 >> 01:58:26|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(208)|executed >> command on VM host localvmhost: vmware-vim-cmd vmsvc/get.tasklist 336 >> 2011-04-11 >> 01:58:26|15920|53:53|reload|VIM_SSH.pm:_wait_for_task(748)|checking >> status of task: haTask-336-vim.VirtualMachine.powerOn-66587404 >> 2011-04-11 >> 01:58:26|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call >> count: 13 (vimsvc/task_info >> haTask-336-vim.VirtualMachine.powerOn-66587404) >> 2011-04-11 >> 01:58:27|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(208)|executed >> command on VM host localvmhost: vmware-vim-cmd vimsvc/task_info >> haTask-336-vim.VirtualMachine.powerOn-66587404 >> 2011-04-11 >> 01:58:27|15920|53:53|reload|VIM_SSH.pm:_wait_for_task(771)|task >> completed successfully: haTask-336-vim.VirtualMachine.powerOn-66587404 >> 2011-04-11 >> 01:58:27|15920|53:53|reload|VIM_SSH.pm:vm_power_on(970)|powered on VM: >> /var/lib/vmware/Virtual Machines/vm-1_34-v0/vm-1_34-v0.vmx >> 2011-04-11 >> 01:58:27|15920|53:53|reload|utils.pm:insertloadlog(3875)|inserted >> computer=8, startvm, registered and powered on vm-1 >> 2011-04-11 >> 01:58:27|15920|53:53|reload|Windows.pm:post_load(583)|beginning Windows >> post-load tasks on vm-1 >> 2011-04-11 01:58:28|15920|53:53|reload|OS.pm:is_ssh_responding(386)|vm-1 >> is NOT responding to SSH, ports 22 or 24 are both closed >> 2011-04-11 >> 01:58:28|15920|53:53|reload|OS.pm:wait_for_response(457)|waiting 15 >> seconds for vm-1 to boot >> 2011-04-11 01:58:28|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 01:58:28 >> 2011-04-11 01:58:33|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 01:58:33 >> 2011-04-11 01:58:38|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 01:58:38 >> 2011-04-11 >> 01:58:43|15920|53:53|reload|OS.pm:wait_for_response(459)|waited 15 >> seconds for vm-1 to boot >> 2011-04-11 >> 01:58:43|15920|53:53|reload|OS.pm:wait_for_response(463)|waiting for >> vm-1 to respond to SSH, maximum of 900 seconds >> 2011-04-11 >> 01:58:43|15920|53:53|reload|Module.pm:code_loop_timeout(711)|waiting for >> vm-1 to respond to SSH, maximum of 900 seconds >> 2011-04-11 >> 01:58:43|15920|53:53|reload|Module.pm:code_loop_timeout(728)|attempt 1: >> waiting for vm-1 to respond to SSH >> 2011-04-11 01:58:43|15920|53:53|reload|OS.pm:is_ssh_responding(386)|vm-1 >> is NOT responding to SSH, ports 22 or 24 are both closed >> 2011-04-11 >> 01:58:43|15920|53:53|reload|Module.pm:code_loop_timeout(724)|attempt 1: >> code returned false, seconds elapsed/remaining: 0/900, sleeping for 8 >> seconds >> 2011-04-11 01:58:43|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 01:58:43 >> 2011-04-11 01:58:49|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 01:58:48 >> 2011-04-11 >> 01:58:51|15920|53:53|reload|Module.pm:code_loop_timeout(728)|attempt 2: >> waiting for vm-1 to respond to SSH >> 2011-04-11 01:58:52|15920|53:53|reload|OS.pm:is_ssh_responding(386)|vm-1 >> is NOT responding to SSH, ports 22 or 24 are both closed >> 2011-04-11 >> 01:58:52|15920|53:53|reload|Module.pm:code_loop_timeout(724)|attempt 2: >> code returned false, seconds elapsed/remaining: 9/891, sleeping for 8 >> seconds >> 2011-04-11 01:58:54|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 01:58:54 >> 2011-04-11 01:58:59|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 01:58:59 >> 2011-04-11 >> 01:59:00|15920|53:53|reload|Module.pm:code_loop_timeout(728)|attempt 3: >> waiting for vm-1 to respond to SSH >> 2011-04-11 01:59:00|15920|53:53|reload|OS.pm:is_ssh_responding(386)|vm-1 >> is NOT responding to SSH, ports 22 or 24 are both closed >> 2011-04-11 >> 01:59:00|15920|53:53|reload|Module.pm:code_loop_timeout(724)|attempt 3: >> code returned false, seconds elapsed/remaining: 17/883, sleeping for 8 >> seconds >> 2011-04-11 01:59:04|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 01:59:04 >> 2011-04-11 >> 01:59:08|15920|53:53|reload|Module.pm:code_loop_timeout(728)|attempt 4: >> waiting for vm-1 to respond to SSH >> 2011-04-11 01:59:09|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 01:59:09 >> ............................. >> ............................. >> 2011-04-11 >> 02:13:41|15920|53:53|reload|Module.pm:code_loop_timeout(728)|attempt >> 107: waiting for vm-1 to respond to SSH >> 2011-04-11 02:13:41|15920|53:53|reload|OS.pm:is_ssh_responding(386)|vm-1 >> is NOT responding to SSH, ports 22 or 24 are both closed >> 2011-04-11 >> 02:13:41|15920|53:53|reload|Module.pm:code_loop_timeout(724)|attempt >> 107: code returned false, seconds elapsed/remaining: 898/2, sleeping for >> 8 seconds >> 2011-04-11 02:13:44|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 02:13:44 >> 2011-04-11 02:13:49|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 02:13:49 >> 2011-04-11 >> 02:13:49|15920|53:53|reload|Module.pm:code_loop_timeout(728)|attempt >> 108: waiting for vm-1 to respond to SSH >> 2011-04-11 02:13:50|15920|53:53|reload|OS.pm:is_ssh_responding(386)|vm-1 >> is NOT responding to SSH, ports 22 or 24 are both closed >> 2011-04-11 >> 02:13:50|15920|53:53|reload|Module.pm:code_loop_timeout(736)|waiting for >> vm-1 to respond to SSH, code did not return true after waiting 900 seconds >> >> |15920|53:53|reload| ---- WARNING ---- >> |15920|53:53|reload| 2011-04-11 >> 02:13:50|15920|53:53|reload|OS.pm:wait_for_response(465)|failed to >> connect to vm-1 via SSH after 900 seconds >> |15920|53:53|reload| ( 0) OS.pm, wait_for_response (line: 465) >> |15920|53:53|reload| (-1) Windows.pm, post_load (line: 591) >> |15920|53:53|reload| (-2) VMware.pm, load (line: 415) >> |15920|53:53|reload| (-3) new.pm <http://new.pm>, reload_image (line: >> 687) >> |15920|53:53|reload| (-4) new.pm <http://new.pm>, process (line: 282) >> >> |15920|53:53|reload| (-5) vcld, make_new_child (line: 568) >> >> >> |15920|53:53|reload| ---- WARNING ---- >> |15920|53:53|reload| 2011-04-11 >> 02:13:50|15920|53:53|reload|Windows.pm:post_load(592)|vm-1 never >> responded to SSH >> |15920|53:53|reload| ( 0) Windows.pm, post_load (line: 592) >> |15920|53:53|reload| (-1) VMware.pm, load (line: 415) >> |15920|53:53|reload| (-2) new.pm <http://new.pm>, reload_image (line: >> 687) >> |15920|53:53|reload| (-3) new.pm <http://new.pm>, process (line: 282) >> >> |15920|53:53|reload| (-4) vcld, make_new_child (line: 568) >> |15920|53:53|reload| (-5) vcld, main (line: 346) >> >> >> |15920|53:53|reload| ---- WARNING ---- >> |15920|53:53|reload| 2011-04-11 >> 02:13:50|15920|53:53|reload|VMware.pm:load(419)|failed to perform OS >> post-load tasks on VM vm-1 on VM host: localvmhost >> |15920|53:53|reload| ( 0) VMware.pm, load (line: 419) >> |15920|53:53|reload| (-1) new.pm <http://new.pm>, reload_image (line: >> 687) >> |15920|53:53|reload| (-2) new.pm <http://new.pm>, process (line: 282) >> >> |15920|53:53|reload| (-3) vcld, make_new_child (line: 568) >> |15920|53:53|reload| (-4) vcld, main (line: 346) >> >> >> |15920|53:53|reload| ---- WARNING ---- >> |15920|53:53|reload| 2011-04-11 >> 02:13:50|15920|53:53|reload|new.pm:reload_image(692)|vmwarewinxp-xp134-v0 >> failed >> to load on vm-1, returning >> |15920|53:53|reload| ( 0) new.pm <http://new.pm>, reload_image (line: >> 692) >> |15920|53:53|reload| (-1) new.pm <http://new.pm>, process (line: 282) >> >> |15920|53:53|reload| (-2) vcld, make_new_child (line: 568) >> |15920|53:53|reload| (-3) vcld, main (line: 346) >> >> 2011-04-11 >> 02:13:50|15920|53:53|reload|utils.pm:insertloadlog(3875)|inserted >> computer=8, loadimagefailed, vmwarewinxp-xp134-v0 failed to load on vm-1 >> >> |15920|53:53|reload| ---- WARNING ---- >> |15920|53:53|reload| 2011-04-11 >> 02:13:50|15920|53:53|reload|new.pm:process(329)|failed to load vm-1 with >> vmwarewinxp-xp134-v0 >> |15920|53:53|reload| ( 0) new.pm <http://new.pm>, process (line: 329) >> >> |15920|53:53|reload| (-1) vcld, make_new_child (line: 568) >> |15920|53:53|reload| (-2) vcld, main (line: 346) >> >> 2011-04-11 >> >> 02:13:50|15920|53:53|reload|DataStructure.pm:get_computer_state_name(2299)|attempting >> to retrieve current state of computer vm-1 from the database >> 2011-04-11 >> >> 02:13:50|15920|53:53|reload|DataStructure.pm:get_computer_state_name(2330)|retrieved >> current state of computer vm-1 from the database: reloading >> 2011-04-11 >> 02:13:50|15920|53:53|reload|DataStructure.pm:_automethod(835)|data >> structure updated: >> $self->request_data->{reservation}{53}{computer}{state}{name} >> |15920|53:53|reload| computer_state_name = reloading >> 2011-04-11 >> >> 02:13:50|15920|53:53|reload|DataStructure.pm:get_computer_private_ip_address(1582)|attempting >> to retrieve private IP address for computer: vm-1 >> 2011-04-11 >> >> 02:13:50|15920|53:53|reload|DataStructure.pm:get_computer_private_ip_address(1586)|retrieved >> contents of /etc/hosts on this management node, contains 16 lines >> 2011-04-11 >> >> 02:13:50|15920|53:53|reload|DataStructure.pm:get_computer_private_ip_address(1639)|returning >> IP address from /etc/hosts file: 192.168.1.1 >> 2011-04-11 >> 02:13:50|15920|53:53|reload|utils.pm:is_inblockrequest(6147)|zero rows >> were returned from database select >> 2011-04-11 >> >> 02:13:50|15920|53:53|reload|DataStructure.pm:get_image_affiliation_name(2029)|image >> owner id: 1 >> 2011-04-11 02:13:50|15920|53:53|reload|utils.pm:getnewdbh(2709)|database >> requested (information_schema) does not match handle stored in $ENV{dbh} >> (vcl:127.0.0.1) >> 2011-04-11 02:13:50|15920|53:53|reload|utils.pm:getnewdbh(2760)|database >> handle stored in $ENV{dbh} >> 2011-04-11 >> >> 02:13:50|15920|53:53|reload|DataStructure.pm:retrieve_user_data(1353)|attempting >> to retrieve and store data for user: user.id <http://user.id> = '1' >> >> 2011-04-11 02:13:50|15920|53:53|reload|utils.pm:getnewdbh(2709)|database >> requested (vcl) does not match handle stored in $ENV{dbh} >> (information_schema:127.0.0.1) >> 2011-04-11 02:13:50|15920|53:53|reload|utils.pm:getnewdbh(2760)|database >> handle stored in $ENV{dbh} >> 2011-04-11 >> 02:13:50|15920|53:53|reload|DataStructure.pm:retrieve_user_data(1416)|data >> has been retrieved for user: admin (id: 1) >> /etc/mail/submit.cf <http://submit.cf>: line 544: fileclass: cannot open >> >> '/etc/mail/trusted-users': Group writable directory >> 2011-04-11 02:13:50|15920|53:53|reload|utils.pm:mail(1268)|SUCCESS -- >> Sending mail To: [email protected] >> <mailto:[email protected]>, PROBLEM -- >> >> 53:53|reload|State.pm|vm-1>localvmhost|vmwarewinxp-xp134-v0|vclreload >> >> |15920|53:53|reload| ---- CRITICAL ---- >> |15920|53:53|reload| 2011-04-11 >> 02:13:50|15920|53:53|reload|State.pm:reservation_failed(223)|reservation >> failed on vm-1: process failed after trying to load or make available >> |15920|53:53|reload| ( 0) State.pm, reservation_failed (line: 223) >> |15920|53:53|reload| (-1) new.pm <http://new.pm>, process (line: 332) >> >> |15920|53:53|reload| (-2) vcld, make_new_child (line: 568) >> |15920|53:53|reload| (-3) vcld, main (line: 346) >> >> 2011-04-11 >> 02:13:50|15920|53:53|reload|utils.pm:insertloadlog(3875)|inserted >> computer=8, failed, process failed after trying to load or make available >> 2011-04-11 >> 02:13:50|15920|53:53|reload|State.pm:reservation_failed(226)|inserted >> computerloadlog entry >> 2011-04-11 >> 02:13:50|15920|53:53|reload|utils.pm:update_computer_state(2033)|computer >> 8 >> state updated to: failed >> 2011-04-11 >> 02:13:50|15920|53:53|reload|State.pm:reservation_failed(245)|computer >> vm-1 (8) state set to failed >> 2011-04-11 >> 02:13:50|15920|53:53|reload|utils.pm:update_request_state(1991)|request >> 53 state updated to: failed, laststate to: image >> 2011-04-11 >> 02:13:50|15920|53:53|reload|State.pm:reservation_failed(258)|set request >> state to 'failed'/'image' >> 2011-04-11 >> 02:13:50|15920|53:53|reload|utils.pm:is_inblockrequest(6147)|zero rows >> were returned from database select >> 2011-04-11 >> 02:13:50|15920|53:53|reload|State.pm:reservation_failed(276)|vm-1 is NOT >> in blockcomputers table >> 2011-04-11 >> 02:13:50|15920|53:53|reload|State.pm:reservation_failed(279)|exiting 1 >> 2011-04-11 02:13:50|15920|53:53|reload|State.pm:DESTROY(839)|VCL::new >> destructor called, address: 9eacb6c >> 2011-04-11 >> 02:13:50|15920|53:53|reload|utils.pm: >> delete_computerloadlog_reservation(6726)|removing >> computerloadlog entries matching loadstate = begin >> 2011-04-11 >> 02:13:50|15920|53:53|reload|utils.pm: >> delete_computerloadlog_reservation(6773)|deleted >> rows from computerloadlog for reservation id=53 >> 2011-04-11 02:13:50|15920|53:53|reload|State.pm:DESTROY(858)|number of >> database handles state process created: 3 >> 2011-04-11 02:13:50|15920|53:53|reload|State.pm:DESTROY(886)|VCL::new >> process duration: 957 seconds >> 2011-04-11 02:13:50|15920|53:53|reload|VIM_SSH.pm:DESTROY(1685)|vim-cmd >> call count: 13 >> 2011-04-11 02:13:50|30717|vcld:REAPER(718)|VCL process exited for >> reservation 53, PID: 15920, signal: CHLD >> 2011-04-11 02:13:50|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 02:13:50 >> 2011-04-11 02:13:50|30717|53:53|failed|vcld:main(252)|request deleted >> 2011-04-11 02:13:55|30717|vcld:main(167)|lastcheckin time updated for >> management node 1: 2011-04-11 02:13:55 >> >> >> >> On Thu, Apr 7, 2011 at 2:24 PM, Andy Kurth <[email protected] >> <mailto:[email protected]>> wrote: >> >> DHCP is a requirement for the private interface but you should still >> be able to get it to work. I have configured similar installations >> before. For the private network, you'll want to configure a VMware >> host-only network, not a bridged network. >> >> I created updated instructions to configure a standalone environment >> using VMware Server 2.0: >> >> https://cwiki.apache.org/confluence/display/VCL/Configuring+a+Standalone+VCL+Environment+using+VMware+Server+2.0 >> >> The instructions haven't been tested and there are probably a couple >> errors but this will hopefully point you in the right direction. >> >> To use static public addresses, you just need to define them when >> you add new computers and configure the management node to use >> static addresses and specify the correct subnet mask, gateway, and >> DNS servers under Management Nodes > Edit. >> >> -Andy >> >> >>
