Re: Reservation Problem
Thanks for that vmprofile tip. That fixed the network naming issue I was seeing. Good news is that it got farther in the process, but still failed. Here's the new logs: 2009-03-25 19:29:33|28031|149:16|new|esx.pm:load(235)|SSHing to copy vmdk-flat file 2009-03-25 19:29:43|2421|vcld:main(166)|lastcheckin time updated for management node 1: 2009-03-25 19:29:43 2009-03-25 19:29:55|2421|vcld:main(166)|lastcheckin time updated for management node 1: 2009-03-25 19:29:55 2009-03-25 19:29:57|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:29:57|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:29:57|28031|149:16|new|esx.pm:load(258)|adapter= lsilogic 2009-03-25 19:29:57|28031|149:16|new|esx.pm:load(300)|wrote vmxarray to /mnt/vcl/inuse/esx3-lamp-v0-bl3/esx3-lamp-v0.vmx 2009-03-25 19:30:00|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:30:00|28031|149:16|new|esx.pm:load(321)|Registered: |28031|149:16|new| Register of VM 'esx3-lamp-v0-bl3' successfully completed under host esxibl3.preloads.private 2009-03-25 19:30:00|28031|149:16|new|esx.pm:load(330)|Power on command: /usr/lib/vmware-viperl/apps/vm/vmcontrol.pl --server 'esxibl3.preloads.private' --vmname esx3-lamp-v0-bl3 --operation poweron --username vcl --password 'd834jfhd734jgfhf7' 2009-03-25 19:30:04|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:30:04|28031|149:16|new|esx.pm:load(333)|Powered on: |28031|149:16|new| virtual machine 'esx3-lamp-v0-bl3' under host esxibl3.preloads.private powered on 2009-03-25 19:30:05|28031|149:16|new|esx.pm:load(349)|deviceinfo-summary: VirtualPCNet32=HASH(0xbdd3d64)-deviceinfo-summary 2009-03-25 19:30:05|28031|149:16|new|esx.pm:load(350)|virtualswitch0: Management 2009-03-25 19:30:05|28031|149:16|new|esx.pm:load(349)|deviceinfo-summary: VirtualPCNet32=HASH(0xacbce1c)-deviceinfo-summary 2009-03-25 19:30:05|28031|149:16|new|esx.pm:load(350)|virtualswitch0: Management 2009-03-25 19:30:05|28031|149:16|new|esx.pm:load(360)|Queried MAC address is 00:0c:29:46:1d:c7 2009-03-25 19:30:05|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:30:05|28031|149:16|new|esx.pm:load(381)|going to sleep 5 seconds, waiting for computer to DHCP. Try 1 2009-03-25 19:30:07|2421|vcld:main(166)|lastcheckin time updated for management node 1: 2009-03-25 19:30:07 2009-03-25 19:30:10|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:30:10|28031|149:16|new|esx.pm:load(381)|going to sleep 5 seconds, waiting for computer to DHCP. Try 2 2009-03-25 19:30:15|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:30:15|28031|149:16|new|esx.pm:load(381)|going to sleep 5 seconds, waiting for computer to DHCP. Try 3 2009-03-25 19:30:19|2421|vcld:main(166)|lastcheckin time updated for management node 1: 2009-03-25 19:30:19 2009-03-25 19:30:20|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:30:20|28031|149:16|new|esx.pm:load(381)|going to sleep 5 seconds, waiting for computer to DHCP. Try 4 2009-03-25 19:30:25|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:30:25|28031|149:16|new|esx.pm:load(381)|going to sleep 5 seconds, waiting for computer to DHCP. Try 5 2009-03-25 19:30:30|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:30:30|28031|149:16|new|esx.pm:load(372)|esx3-lamp-v0-bl3 now has ip 10.0.4.101 2009-03-25 19:30:30|28031|149:16|new|esx.pm:load(388)|Found IP address 10.0.4.101 2009-03-25 19:30:30|28031|149:16|new|esx.pm:load(391)|Removing old hosts entry 2009-03-25 19:30:30|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:30:30|28031|149:16|new|esx.pm:load(393)| 2009-03-25 19:30:30|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:30:30|28031|149:16|new|esx.pm:load(402)|Waiting for ssh to come up on esx3-lamp-v0-bl3 2009-03-25 19:30:31|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:30:31|28031|149:16|new|esx.pm:load(419)|going to sleep 5 seconds, waiting for computer to start SSH. Try 1 2009-03-25 19:30:31|2421|vcld:main(166)|lastcheckin time updated for management node 1: 2009-03-25 19:30:31 2009-03-25 19:30:36|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:30:36|28031|149:16|new|utils.pm:run_ssh_command(6672)|executing SSH command on esx3-lamp-v0-bl3: uname -s 2009-03-25 19:30:43|2421|vcld:main(166)|lastcheckin time updated for management node 1: 2009-03-25 19:30:43 2009-03-25 19:30:47|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-25 19:30:47|28031|149:16|new|utils.pm:run_ssh_command(6753)|run_ssh_command output: Linux 2009-03-25 19:30:47|28031|149:16|new|utils.pm:run_ssh_command(6756)|SSH command executed on
Re: Reservation Problem
The failed reservation problem that we were experiencing was related to our
configuration.
We are currently running our VCL installation in an isolated lab, so we have
the public network on a 10.138.x.x subnet and the private management
network on 10.0.x.x utils.pm in looking for the dynamic address finds the
private IP address, but skips our public IP address on the 10.138 subnet.
From the utils.pm linux path:
elsif ($image_os_type =~ /linux/) {
$identity = $IDENTITY_bladerhel;
undef @sshcmd;
@sshcmd = run_ssh_command($node, $identity, /sbin/ifconfig \|grep inet,
root);
for my $l (@{$sshcmd[1]}) {
# skip class a,b,c private addresses
next if ($l =~ /inet addr:$privateIP/);
next if ($l =~ /inet addr:10.([.0-9]*)/); --- removing this
line made our configuration work.
next if ($l =~ /inet addr:127([.0-9]*)/);
next if ($l =~ /inet addr:172([.0-9]*)/);
next if ($l =~ /inet addr:192.168([.0-9]*)/);
if ($l =~ /inet addr:([.0-9]*)/) {
if ($l !~ /inet addr:$privateIP/) {
#to cover sites using eth0 as public
$dynaIPaddress = $1;
}
}
} ## end for my $l (@{$sshcmd[1]})
--Melba
On Wed, Mar 25, 2009 at 2:37 PM, Melba Lopez milo...@gmail.com wrote:
Thanks for that vmprofile tip. That fixed the network naming issue I was
seeing.
Good news is that it got farther in the process, but still failed. Here's
the new logs:
2009-03-25 19:29:33|28031|149:16|new|esx.pm:load(235)|SSHing to copy
vmdk-flat file
2009-03-25 19:29:43|2421|vcld:main(166)|lastcheckin time updated for
management node 1: 2009-03-25 19:29:43
2009-03-25 19:29:55|2421|vcld:main(166)|lastcheckin time updated for
management node 1: 2009-03-25 19:29:55
2009-03-25 19:29:57|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit
status: 0
2009-03-25 19:29:57|28031|149:16|new|vcld:REAPER(770)|setting $? to 0,
exit status: 0
2009-03-25 19:29:57|28031|149:16|new|esx.pm:load(258)|adapter= lsilogic
2009-03-25 19:29:57|28031|149:16|new|esx.pm:load(300)|wrote vmxarray to
/mnt/vcl/inuse/esx3-lamp-v0-bl3/esx3-lamp-v0.vmx
2009-03-25 19:30:00|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit
status: 0
2009-03-25 19:30:00|28031|149:16|new|esx.pm:load(321)|Registered:
|28031|149:16|new| Register of VM 'esx3-lamp-v0-bl3' successfully completed
under host esxibl3.preloads.private
2009-03-25 19:30:00|28031|149:16|new|esx.pm:load(330)|Power on command:
/usr/lib/vmware-viperl/apps/vm/vmcontrol.pl --server
'esxibl3.preloads.private' --vmname esx3-lamp-v0-bl3 --operation poweron
--username vcl --password 'd834jfhd734jgfhf7'
2009-03-25 19:30:04|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit
status: 0
2009-03-25 19:30:04|28031|149:16|new|esx.pm:load(333)|Powered on:
|28031|149:16|new| virtual machine 'esx3-lamp-v0-bl3' under host
esxibl3.preloads.private powered on
2009-03-25 19:30:05|28031|149:16|new|esx.pm:load(349)|deviceinfo-summary:
VirtualPCNet32=HASH(0xbdd3d64)-deviceinfo-summary
2009-03-25 19:30:05|28031|149:16|new|esx.pm:load(350)|virtualswitch0:
Management
2009-03-25 19:30:05|28031|149:16|new|esx.pm:load(349)|deviceinfo-summary:
VirtualPCNet32=HASH(0xacbce1c)-deviceinfo-summary
2009-03-25 19:30:05|28031|149:16|new|esx.pm:load(350)|virtualswitch0:
Management
2009-03-25 19:30:05|28031|149:16|new|esx.pm:load(360)|Queried MAC address
is 00:0c:29:46:1d:c7
2009-03-25 19:30:05|28031|149:16|new|vcld:REAPER(770)|setting $? to 0,
exit status: 0
2009-03-25 19:30:05|28031|149:16|new|esx.pm:load(381)|going to sleep 5
seconds, waiting for computer to DHCP. Try 1
2009-03-25 19:30:07|2421|vcld:main(166)|lastcheckin time updated for
management node 1: 2009-03-25 19:30:07
2009-03-25 19:30:10|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit
status: 0
2009-03-25 19:30:10|28031|149:16|new|esx.pm:load(381)|going to sleep 5
seconds, waiting for computer to DHCP. Try 2
2009-03-25 19:30:15|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit
status: 0
2009-03-25 19:30:15|28031|149:16|new|esx.pm:load(381)|going to sleep 5
seconds, waiting for computer to DHCP. Try 3
2009-03-25 19:30:19|2421|vcld:main(166)|lastcheckin time updated for
management node 1: 2009-03-25 19:30:19
2009-03-25 19:30:20|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit
status: 0
2009-03-25 19:30:20|28031|149:16|new|esx.pm:load(381)|going to sleep 5
seconds, waiting for computer to DHCP. Try 4
2009-03-25 19:30:25|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit
status: 0
2009-03-25 19:30:25|28031|149:16|new|esx.pm:load(381)|going to sleep 5
seconds, waiting for computer to DHCP. Try 5
2009-03-25 19:30:30|28031|149:16|new|vcld:REAPER(770)|setting $? to 0, exit
status: 0
2009-03-25 19:30:30|28031|149:16|new|esx.pm:load(372)|esx3-lamp-v0-bl3
now has ip 10.0.4.101
2009-03-25 19:30:30|28031|149:16|new|esx.pm:load(388)|Found IP address
10.0.4.101
2009-03-25
Re: Reservation Problem
I'm still suspicious of your DNS resolution and configuration. In addition to creating the DNS entries in your lab's DNS server, did you connect VCL to that DNS by creating an entry similar to the one below in the /etc/resolv.conf on your VCL management node? nameserver ip_of_your_DNS_here Can you connect with virtual center to the blade you're trying to provision to when referencing it strictly by it's hostname? If you want to remove DNS resolution from the list of possible culprits, you can create an entry in /etc/hosts of your VCL management node similar to the line below. I think that should work. IP Address of esxib1esxibl1. Remember to restart networking (or the whole VCL management node) when testing these configuration changes. Best, Brian Brian Bouterse Secure Open Systems Initiative 919.698.8796 On Mar 23, 2009, at 9:13 PM, Melba Lopez wrote: Ok, our lab already had DNS capabilities, so I've set esxibl1-3* *to be valid hostnames*. *However, it is still saying it can't find esxibl1. I've pinged that hostname from another machine on the same network and it works just fine. Also because it kept saying it couldn't load the VM, I've found another problem. The vmdk file successfully copies over into the inuse folder. When I manually add that VM to a blade, I'm noticing that the VM does not keep the network setings. I watched someone actually create this VM and I redid it myself, and the settings do not stay when its copied over. Not sure if it's related, but thought I might mention it. * 2009-03-24 04:28:57|24815|143:10|new|esx.pm:load(300)|wrote vmxarray to /mnt/vcl/inuse/esx3-lamp-v0-bl1/esx3-lamp-v0.vmx 2009-03-24 04:28:59|24815|143:10|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-24 04:28:59|24815|143:10|new|esx.pm:load(321)|Registered: |24815|143:10|new| No host found with name esxibl1. 2009-03-24 04:28:59|24815|143:10|new|esx.pm:load(330)|Power on command: /usr/lib/vmware-viperl/apps/vm/vmcontrol.pl --server 'esxibl1' -- vmname esx3-lamp-v0-bl1 --operation poweron --username vcl --password 'd834jfhd734jgfhf7' 2009-03-24 04:29:00|24815|143:10|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-24 04:29:00|24815|143:10|new|esx.pm:load(333)|Powered on: Virtual Machine esx3-lamp-v0-bl1 not found. 2009-03-24 04:29:01|24815|143:10|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-24 04:29:01|24815|143:10|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-24 04:29:01|24815|143:10|new|utils.pm:mail(1281)|SUCCESS -- Sending mail To: r...@localhost, PROBLEM -- esx.pm |24815|143:10|new| CRITICAL |24815|143:10|new| 2009-03-24 04:29:01|24815|143:10|new| esx.pm:load(341)|Could not query for VM in VI PERL API |24815|143:10|new| ( 0) utils.pm, notify (line: 683) |24815|143:10|new| (-1) esx.pm, load (line: 341) |24815|143:10|new| (-2) new.pm, reload_image (line: 664) |24815|143:10|new| (-3) new.pm, process (line: 266) |24815|143:10|new| (-4) vcld, make_new_child (line: 606) |24815|143:10|new| (-5) vcld, main (line: 353) |24815|143:10|new| WARNING |24815|143:10|new| 2009-03-24 04:29:01|24815|143:10|new|new.pm:reload_image(669)|esx3-lamp-v0 failed to load on esx3-lamp-v0-bl1, returning |24815|143:10|new| ( 0) utils.pm, notify (line: 683)* On Thu, Mar 19, 2009 at 7:12 PM, Josh Thompson josh_thomp...@ncsu.eduwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu March 19 2009 5:45:40 pm Brian Bouterse wrote: always fake the DNS resolution by placing an entry /etc/resolv.conf That would be /etc/hosts :) Josh - -- - --- Josh Thompson Systems Programmer Virtual Computing Lab (VCL) North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at www.keyserver.net -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iD8DBQFJwt9xV/LQcNdtPQMRAiekAJ9Sna6on6gIZC8fO/1wKWFw9W3zIQCffxLj nKgBCGnhdhToNQ0EtzLhRC8= =Yjph -END PGP SIGNATURE-
Re: Reservation Problem
Actually everything you've mentioned has been put into place. The nameserver entry is in /etc/resolv.conf and all the esxibl1-3 hostnames are in the /etc/hosts. I can connect to the blades by putting esxibl1-3 into VIClient without a problem. Note: /etc/resolv.conf is generated by /sbin/dhclient-script; once network/vm is rebooted it restores original. I also restarted the networking and went as far as to reboot the VCL VM and still it gives me the same error. --Melba On Tue, Mar 24, 2009 at 9:34 AM, Brian Bouterse bmbou...@ncsu.edu wrote: I'm still suspicious of your DNS resolution and configuration. In addition to creating the DNS entries in your lab's DNS server, did you connect VCL to that DNS by creating an entry similar to the one below in the /etc/resolv.conf on your VCL management node? nameserver ip_of_your_DNS_here Can you connect with virtual center to the blade you're trying to provision to when referencing it strictly by it's hostname? If you want to remove DNS resolution from the list of possible culprits, you can create an entry in /etc/hosts of your VCL management node similar to the line below. I think that should work. IP Address of esxib1 esxibl1. Remember to restart networking (or the whole VCL management node) when testing these configuration changes. Best, Brian Brian Bouterse Secure Open Systems Initiative 919.698.8796 On Mar 23, 2009, at 9:13 PM, Melba Lopez wrote: Ok, our lab already had DNS capabilities, so I've set esxibl1-3* *to be valid hostnames*. *However, it is still saying it can't find esxibl1. I've pinged that hostname from another machine on the same network and it works just fine. Also because it kept saying it couldn't load the VM, I've found another problem. The vmdk file successfully copies over into the inuse folder. When I manually add that VM to a blade, I'm noticing that the VM does not keep the network setings. I watched someone actually create this VM and I redid it myself, and the settings do not stay when its copied over. Not sure if it's related, but thought I might mention it. * 2009-03-24 04:28:57|24815|143:10|new|esx.pm:load(300)|wrote vmxarray to /mnt/vcl/inuse/esx3-lamp-v0-bl1/esx3-lamp-v0.vmx 2009-03-24 04:28:59|24815|143:10|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-24 04:28:59|24815|143:10|new|esx.pm:load(321)|Registered: |24815|143:10|new| No host found with name esxibl1. 2009-03-24 04:28:59|24815|143:10|new|esx.pm:load(330)|Power on command: /usr/lib/vmware-viperl/apps/vm/vmcontrol.pl --server 'esxibl1' --vmname esx3-lamp-v0-bl1 --operation poweron --username vcl --password 'd834jfhd734jgfhf7' 2009-03-24 04:29:00|24815|143:10|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-24 04:29:00|24815|143:10|new|esx.pm:load(333)|Powered on: Virtual Machine esx3-lamp-v0-bl1 not found. 2009-03-24 04:29:01|24815|143:10|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-24 04:29:01|24815|143:10|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-24 04:29:01|24815|143:10|new|utils.pm:mail(1281)|SUCCESS -- Sending mail To: r...@localhost, PROBLEM -- esx.pm |24815|143:10|new| CRITICAL |24815|143:10|new| 2009-03-24 04:29:01|24815|143:10|new|esx.pm: load(341)|Could not query for VM in VI PERL API |24815|143:10|new| ( 0) utils.pm, notify (line: 683) |24815|143:10|new| (-1) esx.pm, load (line: 341) |24815|143:10|new| (-2) new.pm, reload_image (line: 664) |24815|143:10|new| (-3) new.pm, process (line: 266) |24815|143:10|new| (-4) vcld, make_new_child (line: 606) |24815|143:10|new| (-5) vcld, main (line: 353) |24815|143:10|new| WARNING |24815|143:10|new| 2009-03-24 04:29:01|24815|143:10|new|new.pm:reload_image(669)|esx3-lamp-v0 failed to load on esx3-lamp-v0-bl1, returning |24815|143:10|new| ( 0) utils.pm, notify (line: 683)* On Thu, Mar 19, 2009 at 7:12 PM, Josh Thompson josh_thomp...@ncsu.edu wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu March 19 2009 5:45:40 pm Brian Bouterse wrote: always fake the DNS resolution by placing an entry /etc/resolv.conf That would be /etc/hosts :) Josh - -- - --- Josh Thompson Systems Programmer Virtual Computing Lab (VCL) North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at www.keyserver.net -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iD8DBQFJwt9xV/LQcNdtPQMRAiekAJ9Sna6on6gIZC8fO/1wKWFw9W3zIQCffxLj nKgBCGnhdhToNQ0EtzLhRC8= =Yjph -END PGP SIGNATURE-
Re: Reservation Problem
Ok, our lab already had DNS capabilities, so I've set esxibl1-3* *to be valid hostnames*. *However, it is still saying it can't find esxibl1. I've pinged that hostname from another machine on the same network and it works just fine. Also because it kept saying it couldn't load the VM, I've found another problem. The vmdk file successfully copies over into the inuse folder. When I manually add that VM to a blade, I'm noticing that the VM does not keep the network setings. I watched someone actually create this VM and I redid it myself, and the settings do not stay when its copied over. Not sure if it's related, but thought I might mention it. * 2009-03-24 04:28:57|24815|143:10|new|esx.pm:load(300)|wrote vmxarray to /mnt/vcl/inuse/esx3-lamp-v0-bl1/esx3-lamp-v0.vmx 2009-03-24 04:28:59|24815|143:10|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-24 04:28:59|24815|143:10|new|esx.pm:load(321)|Registered: |24815|143:10|new| No host found with name esxibl1. 2009-03-24 04:28:59|24815|143:10|new|esx.pm:load(330)|Power on command: /usr/lib/vmware-viperl/apps/vm/vmcontrol.pl --server 'esxibl1' --vmname esx3-lamp-v0-bl1 --operation poweron --username vcl --password 'd834jfhd734jgfhf7' 2009-03-24 04:29:00|24815|143:10|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-24 04:29:00|24815|143:10|new|esx.pm:load(333)|Powered on: Virtual Machine esx3-lamp-v0-bl1 not found. 2009-03-24 04:29:01|24815|143:10|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-24 04:29:01|24815|143:10|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-24 04:29:01|24815|143:10|new|utils.pm:mail(1281)|SUCCESS -- Sending mail To: r...@localhost, PROBLEM -- esx.pm |24815|143:10|new| CRITICAL |24815|143:10|new| 2009-03-24 04:29:01|24815|143:10|new|esx.pm:load(341)|Could not query for VM in VI PERL API |24815|143:10|new| ( 0) utils.pm, notify (line: 683) |24815|143:10|new| (-1) esx.pm, load (line: 341) |24815|143:10|new| (-2) new.pm, reload_image (line: 664) |24815|143:10|new| (-3) new.pm, process (line: 266) |24815|143:10|new| (-4) vcld, make_new_child (line: 606) |24815|143:10|new| (-5) vcld, main (line: 353) |24815|143:10|new| WARNING |24815|143:10|new| 2009-03-24 04:29:01|24815|143:10|new|new.pm:reload_image(669)|esx3-lamp-v0 failed to load on esx3-lamp-v0-bl1, returning |24815|143:10|new| ( 0) utils.pm, notify (line: 683)* On Thu, Mar 19, 2009 at 7:12 PM, Josh Thompson josh_thomp...@ncsu.eduwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu March 19 2009 5:45:40 pm Brian Bouterse wrote: always fake the DNS resolution by placing an entry /etc/resolv.conf That would be /etc/hosts :) Josh - -- - --- Josh Thompson Systems Programmer Virtual Computing Lab (VCL) North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at www.keyserver.net -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iD8DBQFJwt9xV/LQcNdtPQMRAiekAJ9Sna6on6gIZC8fO/1wKWFw9W3zIQCffxLj nKgBCGnhdhToNQ0EtzLhRC8= =Yjph -END PGP SIGNATURE-
Re: Reservation Problem
I've verified and tried everything you have mentioned. I also followed the steps in esx.README to make sure I configured everything ok, but I still get a failure. Good news is that the reservation doesn't stay stuck in Pending and actually returns as Failed. I also do not see it complaining about the host name, but rather that it cannot load the VM. Do you have any other suggestions on what other configurations I'm missing? *Log of Reservation:* *2009-03-19 23:04:02|4359|137:4|new|esx.pm:load(166)|Entered ESX module, loading esx3-lamp-v0 on esx3-lamp-v0_blade1 (on vclblade1) for reservation 4 2009-03-19 23:04:02|4359|137:4|new|esx.pm:load(176)|VM info command: /usr/lib/vmware-viperl/apps/vm/vminfo.pl --server 'vclblade1' --vmname esx3-lamp-v0_blade1 --username vcl --password 'd834jfhd734jgfhf7' 2009-03-19 23:04:04|4359|137:4|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-19 23:04:04|4359|137:4|new|esx.pm:load(179)|VM info output: Virtual Machine esx3-lamp-v0_blade1 not found. 2009-03-19 23:04:04|4359|137:4|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-19 23:04:04|4359|137:4|new|esx.pm:load(212)|Output from remove command is: 2009-03-19 23:04:04|4359|137:4|new|esx.pm:load(227)|COPIED VMDK SUCCESSFULLY 2009-03-19 23:04:04|4359|137:4|new|esx.pm:load(235)|SSHing to copy vmdk-flat file 2009-03-19 23:04:14|2420|vcld:main(166)|lastcheckin time updated for management node 1: 2009-03-19 23:04:14 2009-03-19 23:04:26|2420|vcld:main(166)|lastcheckin time updated for management node 1: 2009-03-19 23:04:26 2009-03-19 23:04:28|4359|137:4|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-19 23:04:28|4359|137:4|new|vcld:REAPER(751)|process reaped: pid: 4374, $?: 0, exit status: 0 2009-03-19 23:04:28|4359|137:4|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-19 23:04:28|4359|137:4|new|esx.pm:load(258)|adapter= lsilogic 2009-03-19 23:04:28|4359|137:4|new|esx.pm:load(300)|wrote vmxarray to /mnt/vcl/inuse/esx3-lamp-v0_blade1/esx3-lamp-v0.vmx 2009-03-19 23:04:29|4359|137:4|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-19 23:04:29|4359|137:4|new|esx.pm:load(321)|Registered: |4359|137:4|new| No host found with name vclblade1. 2009-03-19 23:04:29|4359|137:4|new|esx.pm:load(330)|Power on command: /usr/lib/vmware-viperl/apps/vm/vmcontrol.pl --server 'vclblade1' --vmname esx3-lamp-v0_blade1 --operation poweron --username vcl --password 'd834jfhd734jgfhf7' 2009-03-19 23:04:31|4359|137:4|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-19 23:04:31|4359|137:4|new|esx.pm:load(333)|Powered on: Virtual Machine esx3-lamp-v0_blade1 not found. 2009-03-19 23:04:32|4359|137:4|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-19 23:04:32|4359|137:4|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-19 23:04:32|4359|137:4|new|utils.pm:mail(1281)|SUCCESS -- Sending mail To: r...@localhost, PROBLEM -- esx.pm |4359|137:4|new| CRITICAL |4359|137:4|new| 2009-03-19 23:04:32|4359|137:4|new|esx.pm:load(341)|Could not query for VM in VI PERL API |4359|137:4|new| ( 0) utils.pm, notify (line: 683) |4359|137:4|new| (-1) esx.pm, load (line: 341) |4359|137:4|new| (-2) new.pm, reload_image (line: 664) |4359|137:4|new| (-3) new.pm, process (line: 266) |4359|137:4|new| (-4) vcld, make_new_child (line: 606) |4359|137:4|new| (-5) vcld, main (line: 353) |4359|137:4|new| WARNING |4359|137:4|new| 2009-03-19 23:04:32|4359|137:4|new|new.pm:reload_image(669)|esx3-lamp-v0 failed to load on esx3-lamp-v0_blade1, returning |4359|137:4|new| ( 0) utils.pm, notify (line: 683) |4359|137:4|new| (-1) new.pm, reload_image (line: 669) |4359|137:4|new| (-2) new.pm, process (line: 266) |4359|137:4|new| (-3) vcld, make_new_child (line: 606) |4359|137:4|new| (-4) vcld, main (line: 353) 2009-03-19 23:04:32|4359|137:4|new|utils.pm:insertloadlog(5300)|inserted computer=11, loadimagefailed, esx3-lamp-v0 failed to load on esx3-lamp-v0_blade1 |4359|137:4|new| WARNING |4359|137:4|new| 2009-03-19 23:04:32|4359|137:4|new|new.pm:process(313)|failed to load esx3-lamp-v0_blade1 with esx3-lamp-v0 |4359|137:4|new| ( 0) utils.pm, notify (line: 683) |4359|137:4|new| (-1) new.pm, process (line: 313) |4359|137:4|new| (-2) vcld, make_new_child (line: 606) |4359|137:4|new| (-3) vcld, main (line: 353) 2009-03-19 23:04:32|4359|137:4|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-19 23:04:32|4359|137:4|new|vcld:REAPER(770)|setting $? to 0, exit status: 0 2009-03-19 23:04:32|4359|137:4|new|utils.pm:mail(1281)|SUCCESS -- Sending mail To: r...@localhost, PROBLEM -- State.pm |4359|137:4|new| CRITICAL |4359|137:4|new| 2009-03-19 23:04:32|4359|137:4|new|State.pm:reservation_failed(285)|reservation failed on esx3-lamp-v0_blade1: process failed after trying to load or make available |4359|137:4|new| ( 0) utils.pm, notify (line: 683) |4359|137:4|new| (-1)
Re: Reservation Problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu March 19 2009 5:45:40 pm Brian Bouterse wrote: always fake the DNS resolution by placing an entry /etc/resolv.conf That would be /etc/hosts :) Josh - -- - --- Josh Thompson Systems Programmer Virtual Computing Lab (VCL) North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at www.keyserver.net -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iD8DBQFJwt9xV/LQcNdtPQMRAiekAJ9Sna6on6gIZC8fO/1wKWFw9W3zIQCffxLj nKgBCGnhdhToNQ0EtzLhRC8= =Yjph -END PGP SIGNATURE-
