RE: Reservation Error:
Hi Ryan, Thank you for your quick response. I just realized the part with giving hostname rather than just the IP for VMhost by looking at the regular expression parsing for hostname. I didn't know that we need to have the same name for Vmguest and the base image. Now that you mentioned it makes sense why the code is looking for vmguest name. I will give this a try. Thank you!!! Amit > -Original Message- > From: Ryan Johnson [mailto:rjoh...@gwmail.gwu.edu] > Sent: Tuesday, March 23, 2010 12:50 PM > To: vcl-dev@incubator.apache.org > Subject: Re: Reservation Error: > > I believe when you are creating a base image, the vmguest name should be the > same as the name of the image you are creating it should be in a format like > vmwarewinxp-base7-v1. Note that the vm you are imaging should have this > name as well as the vmdk file. Your other problem with the hostname is that > you need to use the hostname of the esxi server in the hostname column of > the computer table entry you have for your esxi server (rather than the IP > address). Because VCL just uses the hostname and not the fully qualified > name, make sure you have an entry for the hostname in your /etc/hosts file > on the management node. > > On Tue, Mar 23, 2010 at 11:01 AM, Kumar, Amit H. wrote: > > > Hi All, > > > > Looking closely it looks like there is an issue when, the esx.pm picks all > > the parameters to initiate a poweroff command on the VMguest using the > > VMware Perl toolkit API > > > > Please advise ...if my understanding below is right or wrong? > > > > 2010-03-22 16:51:09|15553|2:2|image|esx.pm:capture(646)|found previous > > name= > > 2010-03-22 16:51:09|15553|2:2|image|esx.pm:capture(648)|SSHing to node to > > configure currentimage.txt > > 2010-03-22 16:51:09|15553|2:2|image|utils.pm:run_ssh_command(6180)|executing > > SSH command on resxi000: > > |15553|2:2|image| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x > > resxi000 'echo esx3-basewinxp-v0 > /root/currentimage.txt' 2>&1 > > 2010-03-22 > 16:51:10|15553|2:2|image|utils.pm:run_ssh_command(6262)|run_ssh_command > > output: > > |15553|2:2|image| bash: /root/currentimage.txt: No such file or directory > > 2010-03-22 16:51:10|15553|2:2|image|utils.pm:run_ssh_command(6272)|SSH > > command executed on resxi000, command: > > |15553|2:2|image| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x > > resxi000 'echo esx3-basewinxp-v0 > /root/currentimage.txt' 2>&1 > > |15553|2:2|image| returning (1, "bash: /root/currentimage.txt: ...") > > 2010-03-22 16:51:10|15553|2:2|image|esx.pm:capture(658)|Power off command: > > /usr/lib/vmware-vcli/apps/vm/vmcontrol.pl --server '128' --vmname resxi000 > > --operation poweroff --username 0 --password 'xxx' > > > > #>>>> > >1. Here the server info seems to be wrong. > >2. --vmname should actually be " esx3-basewinxp-v0" and not the > > VMguest name; > >3. NOT sure if the username 0 is associated with "root" ??? if > > yes then that seems right. > > > > When I corrected the above info and executed on command line it powered off > > the VMguest. > > > > I am still looking into where the above incorrect info is pulled from so > > that I can correct it. Any idea ?? Any database tables ?? > > I am also curious to know if we are supposed to name our Vmguest based on > > the vmnames? Just for imaging purpose? > > > > Thank you, > > Amit > > > >
Re: Reservation Error:
I believe when you are creating a base image, the vmguest name should be the same as the name of the image you are creating it should be in a format like vmwarewinxp-base7-v1. Note that the vm you are imaging should have this name as well as the vmdk file. Your other problem with the hostname is that you need to use the hostname of the esxi server in the hostname column of the computer table entry you have for your esxi server (rather than the IP address). Because VCL just uses the hostname and not the fully qualified name, make sure you have an entry for the hostname in your /etc/hosts file on the management node. On Tue, Mar 23, 2010 at 11:01 AM, Kumar, Amit H. wrote: > Hi All, > > Looking closely it looks like there is an issue when, the esx.pm picks all > the parameters to initiate a poweroff command on the VMguest using the > VMware Perl toolkit API > > Please advise ...if my understanding below is right or wrong? > > 2010-03-22 16:51:09|15553|2:2|image|esx.pm:capture(646)|found previous > name= > 2010-03-22 16:51:09|15553|2:2|image|esx.pm:capture(648)|SSHing to node to > configure currentimage.txt > 2010-03-22 16:51:09|15553|2:2|image|utils.pm:run_ssh_command(6180)|executing > SSH command on resxi000: > |15553|2:2|image| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x > resxi000 'echo esx3-basewinxp-v0 > /root/currentimage.txt' 2>&1 > 2010-03-22 > 16:51:10|15553|2:2|image|utils.pm:run_ssh_command(6262)|run_ssh_command > output: > |15553|2:2|image| bash: /root/currentimage.txt: No such file or directory > 2010-03-22 16:51:10|15553|2:2|image|utils.pm:run_ssh_command(6272)|SSH > command executed on resxi000, command: > |15553|2:2|image| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x > resxi000 'echo esx3-basewinxp-v0 > /root/currentimage.txt' 2>&1 > |15553|2:2|image| returning (1, "bash: /root/currentimage.txt: ...") > 2010-03-22 16:51:10|15553|2:2|image|esx.pm:capture(658)|Power off command: > /usr/lib/vmware-vcli/apps/vm/vmcontrol.pl --server '128' --vmname resxi000 > --operation poweroff --username 0 --password 'xxx' > > # >1. Here the server info seems to be wrong. >2. --vmname should actually be " esx3-basewinxp-v0" and not the > VMguest name; >3. NOT sure if the username 0 is associated with "root" ??? if > yes then that seems right. > > When I corrected the above info and executed on command line it powered off > the VMguest. > > I am still looking into where the above incorrect info is pulled from so > that I can correct it. Any idea ?? Any database tables ?? > I am also curious to know if we are supposed to name our Vmguest based on > the vmnames? Just for imaging purpose? > > Thank you, > Amit > >
RE: Reservation Error:
Hi All, Looking closely it looks like there is an issue when, the esx.pm picks all the parameters to initiate a poweroff command on the VMguest using the VMware Perl toolkit API Please advise ...if my understanding below is right or wrong? 2010-03-22 16:51:09|15553|2:2|image|esx.pm:capture(646)|found previous name= 2010-03-22 16:51:09|15553|2:2|image|esx.pm:capture(648)|SSHing to node to configure currentimage.txt 2010-03-22 16:51:09|15553|2:2|image|utils.pm:run_ssh_command(6180)|executing SSH command on resxi000: |15553|2:2|image| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x resxi000 'echo esx3-basewinxp-v0 > /root/currentimage.txt' 2>&1 2010-03-22 16:51:10|15553|2:2|image|utils.pm:run_ssh_command(6262)|run_ssh_command output: |15553|2:2|image| bash: /root/currentimage.txt: No such file or directory 2010-03-22 16:51:10|15553|2:2|image|utils.pm:run_ssh_command(6272)|SSH command executed on resxi000, command: |15553|2:2|image| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x resxi000 'echo esx3-basewinxp-v0 > /root/currentimage.txt' 2>&1 |15553|2:2|image| returning (1, "bash: /root/currentimage.txt: ...") 2010-03-22 16:51:10|15553|2:2|image|esx.pm:capture(658)|Power off command: /usr/lib/vmware-vcli/apps/vm/vmcontrol.pl --server '128' --vmname resxi000 --operation poweroff --username 0 --password 'xxx' # 1. Here the server info seems to be wrong. 2. --vmname should actually be " esx3-basewinxp-v0" and not the VMguest name; 3. NOT sure if the username 0 is associated with "root" ??? if yes then that seems right. When I corrected the above info and executed on command line it powered off the VMguest. I am still looking into where the above incorrect info is pulled from so that I can correct it. Any idea ?? Any database tables ?? I am also curious to know if we are supposed to name our Vmguest based on the vmnames? Just for imaging purpose? Thank you, Amit
RE: Reservation Error:
Hi Ryan, you are great! I made quite a bit of progress with your suggestion.
I hope you can help me with this next step error: Seems like image creation was
successful but upon realod/poweron VMware perl toolkit looks for server '128'
instead of the full ip.
Something seems to be missing: Hope you can shed some more light on this!!!
2010-03-22 16:50:28|14912|vcld:main(165)|lastcheckin time updated for
management node 1: 2010-03-22 16:50:28
2010-03-22 16:50:33|14912|vcld:main(165)|lastcheckin time updated for
management node 1: 2010-03-22 16:50:33
===
OUTPUT for vcld run on 2010-03-22 16:51:04
===
2010-03-22 16:51:04|15551|vcld:main(116)|vcld environment variable set to 1 for
this process
2010-03-22 16:51:04|15551|utils.pm:rename_vcld_process(7901)|renamed process to
'vcld vcld'
2010-03-22 16:51:04|15551|utils.pm:get_management_node_info(6815)|management
node info retrieved from database for colbert
2010-03-22 16:51:04|15551|vcld:main(127)|retrieved management node information
from database
2010-03-22 16:51:04|15551|vcld:main(140)|management_node_id environment
variable set: 1
2010-03-22 16:51:04|15551|vcld:main(148)|management node checkin interval is 5
seconds
2010-03-22 16:51:04|15551|vcld:main(149)|vcld started on
colbert.vcls.priv.odu.edu
2010-03-22 16:51:09|15551|vcld:main(165)|lastcheckin time updated for
management node 1: 2010-03-22 16:51:09
2010-03-22
16:51:09|15551|2:2|image|utils.pm:reservation_being_processed(9634)|computerloadlog
'begin' entry does NOT exist for reservation 2
2010-03-22
16:51:09|15551|2:2|image|utils.pm:reservation_being_processed(9686)|reservation
is NOT currently being processed
2010-03-22 16:51:09|15551|2:2|image|vcld:main(276)|reservation 2 is NOT already
being processed
|15551|2:2|image| WARNING
|15551|2:2|image| 2010-03-22
16:51:09|15551|2:2|image|utils.pm:get_request_info(5218)|preferredimageid is
not set for computer id=3
|15551|2:2|image| ( 0) utils.pm, notify (line: 737)
|15551|2:2|image| (-1) utils.pm, get_request_info (line: 5218)
|15551|2:2|image| (-2) vcld, main (line: 280)
2010-03-22 16:51:09|15551|2:2|image|utils.pm:get_request_info(5354)|standalone
affiliation found: Local
2010-03-22
16:51:09|15551|2:2|image|utils.pm:get_management_node_info(6815)|management
node info retrieved from database for colbert
2010-03-22 16:51:09|15551|2:2|image|vcld:main(281)|retrieved request
information from database
2010-03-22
16:51:09|15551|2:2|image|utils.pm:get_management_node_info(6815)|management
node info retrieved from database for colbert
2010-03-22
16:51:09|15551|2:2|image|DataStructure.pm:is_parent_reservation(854)|returning
true: parent reservation ID for this request: 2
2010-03-22 16:51:09|15551|2:2|image|utils.pm:update_request_state(2186)|request
2 state updated to: pending, laststate to: image
2010-03-22 16:51:09|15551|2:2|image|utils.pm:insertloadlog(4710)|inserted
computer=3, begin, beginning to process, state is image
2010-03-22 16:51:09|15551|2:2|image|vcld:make_new_child(509)|loaded VCL::image
module
2010-03-22 16:51:09|15553|2:2|image|vcld:make_new_child(582)|vcld environment
variable set to 0 for this process
2010-03-22 16:51:09|15553|2:2|image|Module.pm:new(132)|constructor called,
class=VCL::image
2010-03-22 16:51:09|15553|2:2|image|Module.pm:new(154)|VCL::image object created
2010-03-22 16:51:09|15551|2:2|image|vcld:make_new_child(566)|current number of
forked kids: 1
2010-03-22 16:51:09|15553|2:2|image|State.pm:initialize(85)|obtained a database
handle for this state process, stored as $ENV{dbh}
2010-03-22 16:51:09|15553|2:2|image|State.pm:check_image_os(839)|no corrections
need to be made to image OS: esx35
2010-03-22
16:51:09|15553|2:2|image|DataStructure.pm:is_parent_reservation(854)|returning
true: parent reservation ID for this request: 2
2010-03-22
16:51:09|15553|2:2|image|utils.pm:rename_vcld_process(7863)|reservation count: 1
2010-03-22
16:51:09|15553|2:2|image|utils.pm:rename_vcld_process(7882)|PARENTIMAGE: 1
2010-03-22
16:51:09|15553|2:2|image|utils.pm:rename_vcld_process(7883)|SUBIMAGE: 0
2010-03-22 16:51:09|15553|2:2|image|utils.pm:rename_vcld_process(7901)|renamed
process to 'vcld VCL::image 2:2 image imaging'
2010-03-22
16:51:09|15553|2:2|image|DataStructure.pm:is_parent_reservation(854)|returning
true: parent reservation ID for this request: 2
2010-03-22
16:51:09|15553|2:2|image|DataStructure.pm:is_parent_reservation(854)|returning
true: parent reservation ID for this request: 2
2010-03-22 16:51:09|15553|2:2|image|State.pm:initialize(121)|attempting to load
provisioning module: VCL::Module::Provisioning::esx
2010-03-22 16:51:09|15553|2:2|image|esx.pm:initialize(138)|esx vmware toolkit
root path found: /usr/lib/vmware-vcli/apps
2010-03-22 16:51:09|15553|2:2|image|esx.pm:initialize(140)|vmware ESX module
initialized
2010-03-22
16:51:09|15553|2:2|image|State.pm:initia
Re: Reservation Error:
No what I did was avoid running ssh commands on the Esxi entirely by specifying the IP of a remote server which is hosting a network file system as the datastorepath column in the vmprofile table. On Mon, Mar 22, 2010 at 3:59 PM, Kumar, Amit H. wrote: > Hi Ryan, > > Well I am using the free version as well. I don't seem to understand your > workaround. > Do you mean that: Instead of specifying the IP:path_to_images for Data > store path, I would rather benefit from specifying just the IP: ? > > Thank you for your feedback, > Amit > > > > -Original Message- > > From: Ryan Johnson [mailto:rjoh...@gwmail.gwu.edu] > > Sent: Monday, March 22, 2010 3:55 PM > > To: vcl-dev@incubator.apache.org > > Subject: Re: Reservation Error: > > > > I ran into this as well using the free version of Esxi, I'm not sure what > > version you are using. It has to do with the exit status returned from > the > > Esx server. Try running the ssh command that VCL runs from the command > > line, but add the -v option to print out more information. The > work-around > > I came up with was just to specify the server that was actually exporting > > the NFS. > > > > 14061|2:3|image| WARNING > > |14061|2:3|image| 2010-03-22 > > 13:55:12|14061|2:3|image|utils.pm:run_ssh_command(6252)|attempt > > 1/3: failed to execute SSH command on 128.82.128.252: ls -1 > > /vmfs/volumes/15a5e041-86bf33de//golden 2>&1, exit status: 255, SSH exits > > with the exit status of the remote command or with 255 if an error > occurred, > > output: > > |14061|2:3|image| ssh output (ls -1 /vmf...): esx3-basewinxp-v0 > #>>> > > notice that the command returns the correct output > > > > #>>> Here it sees the image But I don't understand why it fails to create > > it. > > > > |14061|2:3|image| ( 0) utils.pm, notify (line: 737) > > |14061|2:3|image| (-1) utils.pm, run_ssh_command (line: 6252) > > |14061|2:3|image| (-2) esx.pm, does_image_exist (line: 910) > > |14061|2:3|image| (-3) image.pm, process (line: 135) > > |14061|2:3|image| (-4) vcld, make_new_child (line: 594) > > |14061|2:3|image| (-5) vcld, main (line: 341) > > > > > > On Mon, Mar 22, 2010 at 2:08 PM, Kumar, Amit H. wrote: > > > > > Hi Andy, > > > > > > I followed through every step in esx.README and still not successful in > > > capturing an image: > > > > > > I can SSH to the hypervisor and the VMhost through the management node > with > > > the/etc/vcl/vcl.key etc etc ..everything else looks okay; below I also > have > > > the query's that I used to create this image and reservation. > > > > > > Please advise. > > > > > > 2010-03-22 13:55:11|14001|vcld:main(165)|lastcheckin time updated for > > > management node 1: 2010-03-22 13:55:11 > > > 2010-03-22 > > 13:55:11|14001|2:3|image|utils.pm: > reservation_being_processed(9634)|computerloadlog > > > 'begin' entry does NOT exist for reservation 3 > > > 2010-03-22 > > 13:55:11|14001|2:3|image|utils.pm: > reservation_being_processed(9686)|reservation > > > is NOT currently being processed > > > 2010-03-22 13:55:11|14001|2:3|image|vcld:main(276)|reservation 3 is NOT > > > already being processed > > > > > > |14001|2:3|image| WARNING > > > |14001|2:3|image| 2010-03-22 > > 13:55:11|14001|2:3|image|utils.pm: > get_request_info(5218)|preferredimageid > > > is not set for computer id=3 > > > |14001|2:3|image| ( 0) utils.pm, notify (line: 737) > > > |14001|2:3|image| (-1) utils.pm, get_request_info (line: 5218) > > > |14001|2:3|image| (-2) vcld, main (line: 280) > > > > > > 2010-03-22 13:55:11|14001|2:3|image|utils.pm: > get_request_info(5354)|standalone > > > affiliation found: Local > > > 2010-03-22 > > 13:55:11|14001|2:3|image|utils.pm: > get_management_node_info(6815)|management > > > node info retrieved from database for colbert > > > 2010-03-22 13:55:11|14001|2:3|image|vcld:main(281)|retrieved request > > > information from database > > > 2010-03-22 > > > > 13:55:11|14001|2:3|image|DataStructure.pm:is_parent_reservation(854)|returning > > > true: parent reservation ID for this request: 3 > > > 2010-03-22 13:55:11|14001|2:3|image|utils.pm: > update_request_state(2186)|request > > > 2 state updated to: pending, laststate to: image > > > 2010-03-22 13:55:11|14001|2:3|image|utils.pm: > insertloadlog(4710)|inserted &g
RE: Reservation Error:
Hi Ryan, Well I am using the free version as well. I don't seem to understand your workaround. Do you mean that: Instead of specifying the IP:path_to_images for Data store path, I would rather benefit from specifying just the IP: ? Thank you for your feedback, Amit > -Original Message- > From: Ryan Johnson [mailto:rjoh...@gwmail.gwu.edu] > Sent: Monday, March 22, 2010 3:55 PM > To: vcl-dev@incubator.apache.org > Subject: Re: Reservation Error: > > I ran into this as well using the free version of Esxi, I'm not sure what > version you are using. It has to do with the exit status returned from the > Esx server. Try running the ssh command that VCL runs from the command > line, but add the -v option to print out more information. The work-around > I came up with was just to specify the server that was actually exporting > the NFS. > > 14061|2:3|image| WARNING > |14061|2:3|image| 2010-03-22 > 13:55:12|14061|2:3|image|utils.pm:run_ssh_command(6252)|attempt > 1/3: failed to execute SSH command on 128.82.128.252: ls -1 > /vmfs/volumes/15a5e041-86bf33de//golden 2>&1, exit status: 255, SSH exits > with the exit status of the remote command or with 255 if an error occurred, > output: > |14061|2:3|image| ssh output (ls -1 /vmf...): esx3-basewinxp-v0 #>>> > notice that the command returns the correct output > > #>>> Here it sees the image But I don't understand why it fails to create > it. > > |14061|2:3|image| ( 0) utils.pm, notify (line: 737) > |14061|2:3|image| (-1) utils.pm, run_ssh_command (line: 6252) > |14061|2:3|image| (-2) esx.pm, does_image_exist (line: 910) > |14061|2:3|image| (-3) image.pm, process (line: 135) > |14061|2:3|image| (-4) vcld, make_new_child (line: 594) > |14061|2:3|image| (-5) vcld, main (line: 341) > > > On Mon, Mar 22, 2010 at 2:08 PM, Kumar, Amit H. wrote: > > > Hi Andy, > > > > I followed through every step in esx.README and still not successful in > > capturing an image: > > > > I can SSH to the hypervisor and the VMhost through the management node with > > the/etc/vcl/vcl.key etc etc ..everything else looks okay; below I also have > > the query's that I used to create this image and reservation. > > > > Please advise. > > > > 2010-03-22 13:55:11|14001|vcld:main(165)|lastcheckin time updated for > > management node 1: 2010-03-22 13:55:11 > > 2010-03-22 > 13:55:11|14001|2:3|image|utils.pm:reservation_being_processed(9634)|computerloadlog > > 'begin' entry does NOT exist for reservation 3 > > 2010-03-22 > 13:55:11|14001|2:3|image|utils.pm:reservation_being_processed(9686)|reservation > > is NOT currently being processed > > 2010-03-22 13:55:11|14001|2:3|image|vcld:main(276)|reservation 3 is NOT > > already being processed > > > > |14001|2:3|image| WARNING > > |14001|2:3|image| 2010-03-22 > 13:55:11|14001|2:3|image|utils.pm:get_request_info(5218)|preferredimageid > > is not set for computer id=3 > > |14001|2:3|image| ( 0) utils.pm, notify (line: 737) > > |14001|2:3|image| (-1) utils.pm, get_request_info (line: 5218) > > |14001|2:3|image| (-2) vcld, main (line: 280) > > > > 2010-03-22 > > 13:55:11|14001|2:3|image|utils.pm:get_request_info(5354)|standalone > > affiliation found: Local > > 2010-03-22 > 13:55:11|14001|2:3|image|utils.pm:get_management_node_info(6815)|management > > node info retrieved from database for colbert > > 2010-03-22 13:55:11|14001|2:3|image|vcld:main(281)|retrieved request > > information from database > > 2010-03-22 > > 13:55:11|14001|2:3|image|DataStructure.pm:is_parent_reservation(854)|returning > > true: parent reservation ID for this request: 3 > > 2010-03-22 > > 13:55:11|14001|2:3|image|utils.pm:update_request_state(2186)|request > > 2 state updated to: pending, laststate to: image > > 2010-03-22 13:55:11|14001|2:3|image|utils.pm:insertloadlog(4710)|inserted > > computer=3, begin, beginning to process, state is image > > 2010-03-22 13:55:11|14001|2:3|image|vcld:make_new_child(509)|loaded > > VCL::image module > > 2010-03-22 13:55:11|14061|2:3|image|vcld:make_new_child(582)|vcld > > environment variable set to 0 for this process > > 2010-03-22 13:55:11|14061|2:3|image|Module.pm:new(132)|constructor called, > > class=VCL::image > > 2010-03-22 13:55:11|14061|2:3|image|Module.pm:new(154)|VCL::image object > > created > > 2010-03-22 13:55:11|14001|2:3|image|vcld:make_new_child(566)|current number > > of forked kids: 1 > > 2010-03-22 13:55:11|14061|2:3|image|State.pm:initialize(85)|obtained a > > database handl
Re: Reservation Error:
I ran into this as well using the free version of Esxi, I'm not sure what
version you are using. It has to do with the exit status returned from the
Esx server. Try running the ssh command that VCL runs from the command
line, but add the -v option to print out more information. The work-around
I came up with was just to specify the server that was actually exporting
the NFS.
14061|2:3|image| WARNING
|14061|2:3|image| 2010-03-22
13:55:12|14061|2:3|image|utils.pm:run_ssh_command(6252)|attempt
1/3: failed to execute SSH command on 128.82.128.252: ls -1
/vmfs/volumes/15a5e041-86bf33de//golden 2>&1, exit status: 255, SSH exits
with the exit status of the remote command or with 255 if an error occurred,
output:
|14061|2:3|image| ssh output (ls -1 /vmf...): esx3-basewinxp-v0 #>>>
notice that the command returns the correct output
#>>> Here it sees the image But I don't understand why it fails to create
it.
|14061|2:3|image| ( 0) utils.pm, notify (line: 737)
|14061|2:3|image| (-1) utils.pm, run_ssh_command (line: 6252)
|14061|2:3|image| (-2) esx.pm, does_image_exist (line: 910)
|14061|2:3|image| (-3) image.pm, process (line: 135)
|14061|2:3|image| (-4) vcld, make_new_child (line: 594)
|14061|2:3|image| (-5) vcld, main (line: 341)
On Mon, Mar 22, 2010 at 2:08 PM, Kumar, Amit H. wrote:
> Hi Andy,
>
> I followed through every step in esx.README and still not successful in
> capturing an image:
>
> I can SSH to the hypervisor and the VMhost through the management node with
> the/etc/vcl/vcl.key etc etc ..everything else looks okay; below I also have
> the query's that I used to create this image and reservation.
>
> Please advise.
>
> 2010-03-22 13:55:11|14001|vcld:main(165)|lastcheckin time updated for
> management node 1: 2010-03-22 13:55:11
> 2010-03-22
> 13:55:11|14001|2:3|image|utils.pm:reservation_being_processed(9634)|computerloadlog
> 'begin' entry does NOT exist for reservation 3
> 2010-03-22
> 13:55:11|14001|2:3|image|utils.pm:reservation_being_processed(9686)|reservation
> is NOT currently being processed
> 2010-03-22 13:55:11|14001|2:3|image|vcld:main(276)|reservation 3 is NOT
> already being processed
>
> |14001|2:3|image| WARNING
> |14001|2:3|image| 2010-03-22
> 13:55:11|14001|2:3|image|utils.pm:get_request_info(5218)|preferredimageid
> is not set for computer id=3
> |14001|2:3|image| ( 0) utils.pm, notify (line: 737)
> |14001|2:3|image| (-1) utils.pm, get_request_info (line: 5218)
> |14001|2:3|image| (-2) vcld, main (line: 280)
>
> 2010-03-22 13:55:11|14001|2:3|image|utils.pm:get_request_info(5354)|standalone
> affiliation found: Local
> 2010-03-22
> 13:55:11|14001|2:3|image|utils.pm:get_management_node_info(6815)|management
> node info retrieved from database for colbert
> 2010-03-22 13:55:11|14001|2:3|image|vcld:main(281)|retrieved request
> information from database
> 2010-03-22
> 13:55:11|14001|2:3|image|DataStructure.pm:is_parent_reservation(854)|returning
> true: parent reservation ID for this request: 3
> 2010-03-22
> 13:55:11|14001|2:3|image|utils.pm:update_request_state(2186)|request
> 2 state updated to: pending, laststate to: image
> 2010-03-22 13:55:11|14001|2:3|image|utils.pm:insertloadlog(4710)|inserted
> computer=3, begin, beginning to process, state is image
> 2010-03-22 13:55:11|14001|2:3|image|vcld:make_new_child(509)|loaded
> VCL::image module
> 2010-03-22 13:55:11|14061|2:3|image|vcld:make_new_child(582)|vcld
> environment variable set to 0 for this process
> 2010-03-22 13:55:11|14061|2:3|image|Module.pm:new(132)|constructor called,
> class=VCL::image
> 2010-03-22 13:55:11|14061|2:3|image|Module.pm:new(154)|VCL::image object
> created
> 2010-03-22 13:55:11|14001|2:3|image|vcld:make_new_child(566)|current number
> of forked kids: 1
> 2010-03-22 13:55:11|14061|2:3|image|State.pm:initialize(85)|obtained a
> database handle for this state process, stored as $ENV{dbh}
> 2010-03-22 13:55:11|14061|2:3|image|State.pm:check_image_os(839)|no
> corrections need to be made to image OS: esx35
> 2010-03-22
> 13:55:11|14061|2:3|image|DataStructure.pm:is_parent_reservation(854)|returning
> true: parent reservation ID for this request: 3
> 2010-03-22
> 13:55:11|14061|2:3|image|utils.pm:rename_vcld_process(7863)|reservation
> count: 1
> 2010-03-22
> 13:55:11|14061|2:3|image|utils.pm:rename_vcld_process(7882)|PARENTIMAGE:
> 1
> 2010-03-22
> 13:55:11|14061|2:3|image|utils.pm:rename_vcld_process(7883)|SUBIMAGE:
> 0
> 2010-03-22 13:55:11|14061|2:3|image|utils.pm:rename_vcld_process(7901)|renamed
> process to 'vcld VCL::image 2:3 image imaging'
> 2010-03-22
> 13:55:11|14061|2:3|image|DataStructure.pm:is_parent_reservation(854)|returning
> true: parent reservation ID for this request: 3
> 2010-03-22
> 13:55:11|14061|2:3|image|DataStructure.pm:is_parent_reservation(854)|returning
> true: parent reservation ID for this request: 3
> 2010-03-22 13:55:11|14061|2:3|image|State.pm:initialize(121)|attempting to
> load provisioning module: VCL::Module::Provisioning::
RE: Reservation Error:
Hi Andy,
I followed through every step in esx.README and still not successful in
capturing an image:
I can SSH to the hypervisor and the VMhost through the management node with
the/etc/vcl/vcl.key etc etc ..everything else looks okay; below I also have the
query's that I used to create this image and reservation.
Please advise.
2010-03-22 13:55:11|14001|vcld:main(165)|lastcheckin time updated for
management node 1: 2010-03-22 13:55:11
2010-03-22
13:55:11|14001|2:3|image|utils.pm:reservation_being_processed(9634)|computerloadlog
'begin' entry does NOT exist for reservation 3
2010-03-22
13:55:11|14001|2:3|image|utils.pm:reservation_being_processed(9686)|reservation
is NOT currently being processed
2010-03-22 13:55:11|14001|2:3|image|vcld:main(276)|reservation 3 is NOT already
being processed
|14001|2:3|image| WARNING
|14001|2:3|image| 2010-03-22
13:55:11|14001|2:3|image|utils.pm:get_request_info(5218)|preferredimageid is
not set for computer id=3
|14001|2:3|image| ( 0) utils.pm, notify (line: 737)
|14001|2:3|image| (-1) utils.pm, get_request_info (line: 5218)
|14001|2:3|image| (-2) vcld, main (line: 280)
2010-03-22 13:55:11|14001|2:3|image|utils.pm:get_request_info(5354)|standalone
affiliation found: Local
2010-03-22
13:55:11|14001|2:3|image|utils.pm:get_management_node_info(6815)|management
node info retrieved from database for colbert
2010-03-22 13:55:11|14001|2:3|image|vcld:main(281)|retrieved request
information from database
2010-03-22
13:55:11|14001|2:3|image|DataStructure.pm:is_parent_reservation(854)|returning
true: parent reservation ID for this request: 3
2010-03-22 13:55:11|14001|2:3|image|utils.pm:update_request_state(2186)|request
2 state updated to: pending, laststate to: image
2010-03-22 13:55:11|14001|2:3|image|utils.pm:insertloadlog(4710)|inserted
computer=3, begin, beginning to process, state is image
2010-03-22 13:55:11|14001|2:3|image|vcld:make_new_child(509)|loaded VCL::image
module
2010-03-22 13:55:11|14061|2:3|image|vcld:make_new_child(582)|vcld environment
variable set to 0 for this process
2010-03-22 13:55:11|14061|2:3|image|Module.pm:new(132)|constructor called,
class=VCL::image
2010-03-22 13:55:11|14061|2:3|image|Module.pm:new(154)|VCL::image object created
2010-03-22 13:55:11|14001|2:3|image|vcld:make_new_child(566)|current number of
forked kids: 1
2010-03-22 13:55:11|14061|2:3|image|State.pm:initialize(85)|obtained a database
handle for this state process, stored as $ENV{dbh}
2010-03-22 13:55:11|14061|2:3|image|State.pm:check_image_os(839)|no corrections
need to be made to image OS: esx35
2010-03-22
13:55:11|14061|2:3|image|DataStructure.pm:is_parent_reservation(854)|returning
true: parent reservation ID for this request: 3
2010-03-22
13:55:11|14061|2:3|image|utils.pm:rename_vcld_process(7863)|reservation count: 1
2010-03-22
13:55:11|14061|2:3|image|utils.pm:rename_vcld_process(7882)|PARENTIMAGE: 1
2010-03-22
13:55:11|14061|2:3|image|utils.pm:rename_vcld_process(7883)|SUBIMAGE: 0
2010-03-22 13:55:11|14061|2:3|image|utils.pm:rename_vcld_process(7901)|renamed
process to 'vcld VCL::image 2:3 image imaging'
2010-03-22
13:55:11|14061|2:3|image|DataStructure.pm:is_parent_reservation(854)|returning
true: parent reservation ID for this request: 3
2010-03-22
13:55:11|14061|2:3|image|DataStructure.pm:is_parent_reservation(854)|returning
true: parent reservation ID for this request: 3
2010-03-22 13:55:11|14061|2:3|image|State.pm:initialize(121)|attempting to load
provisioning module: VCL::Module::Provisioning::esx
2010-03-22 13:55:11|14061|2:3|image|esx.pm:initialize(138)|esx vmware toolkit
root path found: /usr/lib/vmware-vcli/apps
2010-03-22 13:55:11|14061|2:3|image|esx.pm:initialize(140)|vmware ESX module
initialized
2010-03-22
13:55:11|14061|2:3|image|State.pm:initialize(127)|VCL::Module::Provisioning::esx
module loaded
2010-03-22 13:55:11|14061|2:3|image|Module.pm:new(132)|constructor called,
class=VCL::Module::Provisioning::esx
2010-03-22
13:55:11|14061|2:3|image|Module.pm:new(154)|VCL::Module::Provisioning::esx
object created
2010-03-22 13:55:11|14061|2:3|image|esx.pm:initialize(138)|esx vmware toolkit
root path found: /usr/lib/vmware-vcli/apps
2010-03-22 13:55:11|14061|2:3|image|esx.pm:initialize(140)|vmware ESX module
initialized
2010-03-22
13:55:11|14061|2:3|image|State.pm:initialize(131)|VCL::Module::Provisioning::esx
provisioner object created
2010-03-22 13:55:11|14061|2:3|image|State.pm:initialize(145)|attempting to load
OS module: VCL::Module::OS::Linux
2010-03-22
13:55:11|14061|2:3|image|State.pm:initialize(151)|VCL::Module::OS::Linux module
loaded
2010-03-22 13:55:11|14061|2:3|image|Module.pm:new(132)|constructor called,
class=VCL::Module::OS::Linux
2010-03-22 13:55:11|14061|2:3|image|Module.pm:new(154)|VCL::Module::OS::Linux
object created
2010-03-22
13:55:11|14061|2:3|image|State.pm:initialize(154)|VCL::Module::OS::Linux OS
object created
2010-03-22 13:55:11|14061|2:3|image|State.pm:initialize(169)|r
RE: Reservation Error:
18 15:06:27|20986|1:1|image|image.pm:reservation_failed(450)|resxi-2
state set to maintenance
2010-03-18 15:06:27|20986|1:1|image|image.pm:reservation_failed(457)|exiting
2010-03-18 15:06:27|20986|1:1|image|State.pm:DESTROY(905)|destructor called,
ref($self)=VCL::image
2010-03-18
15:06:27|20986|1:1|image|utils.pm:delete_computerloadlog_reservation(7551)|removing
computerloadlog entries matching loadstate = begin
2010-03-18
15:06:27|20986|1:1|image|utils.pm:delete_computerloadlog_reservation(7598)|deleted
rows from computerloadlog for reservation id=1
2010-03-18 15:06:27|20986|1:1|image|State.pm:DESTROY(912)|removed
computerloadlog rows with loadstate=begin for reservation
2010-03-18 15:06:27|20986|1:1|image|State.pm:DESTROY(924)|number of database
handles state process created: 1
2010-03-18 15:06:27|20986|1:1|image|State.pm:DESTROY(933)|process has a
database handle stored in $ENV{dbh}, attempting disconnect
2010-03-18 15:06:27|20986|1:1|image|State.pm:DESTROY(935)|$ENV{dbh}: database
disconnect successful
2010-03-18 15:06:27|20986|1:1|image|State.pm:DESTROY(949)|VCL::image process
20986 exiting
2010-03-18 15:06:27|20858|vcld:REAPER(744)|VCL process exited for reservation 1
2010-03-18 15:06:27|20858|vcld:main(165)|lastcheckin time updated for
management node 1: 2010-03-18 15:06:27
2010-03-18 15:06:32|20858|vcld:main(165)|lastcheckin time updated for
management node 1: 2010-03-18 15:06:32
You have new mail in /var/spool/mail/root
[r...@colbert vcl-debug]# exit
Script done, file is vclamit03.18.a.2010.log
You have new mail in /var/spool/mail/root
[r...@colbert vcl-debug]# /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x
128.82.128.252 'ls -1 /vmfs/volumes/15a5e041-86bf33de/golden
>
[r...@colbert vcl-debug]# /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x
128.82.128.252 'ls -1 /vmfs/volumes/15a5e041-86bf33de/golden'
/vmfs/volumes/15a5e041-86bf33de/golden
[r...@colbert vcl-debug]# /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x
128.82.128.252 'ls -1 /vmfs/volumes/15a5e041-86bf33de/golden/' <- Note forward
slash
thrash
vmwarewinxp-base7-v0
Thank you,
Amit
> -Original Message-
> From: Andy Kurth [mailto:andy_ku...@ncsu.edu]
> Sent: Thursday, March 18, 2010 12:22 PM
> To: vcl-dev@incubator.apache.org
> Subject: Re: Reservation Error:
>
> Yes, the management node needs to be be able to SSH to the VM hosts before
> attempting the image capture, or any other VM operations. Assuming password
> authentication is still enabled on the VM hosts, you can run "gen-node-key.sh
> " for each of them. I wouldn't try the VCL image capture process until
> this
> works:
> ssh -i /etc/vcl/vcl.key -l root -p 22
>
> -Andy
>
> Kumar, Amit H. wrote:
> > Ah! .. I see. Seems like I started with a wrong assumption.
> >
> > I didn't not do the capture image process yet. I wanted to see if I can
> > make a reservation
> for the already existing VM, that I built with the name
> 'vmwarewinxp-base7-v0' and placed
> it under the Data-Store-Path on the VMhost that built it.
> >
> > Yes you were right I was missing the IP address in the Data-Store Path: I
> > will put in the
> VMhost IP here.
> > In that case shouldn't I generate-node-key's for all the VMhost's because
> > it will try to
> SSH to it to get to the Data-Store-Path?
> >
> >
> > Thank you Andy for the help ... I will give image capture a try first.
> > Amit
Re: Reservation Error:
Yes, the management node needs to be be able to SSH to the VM hosts before attempting the image capture, or any other VM operations. Assuming password authentication is still enabled on the VM hosts, you can run "gen-node-key.sh " for each of them. I wouldn't try the VCL image capture process until this works: ssh -i /etc/vcl/vcl.key -l root -p 22 -Andy Kumar, Amit H. wrote: Ah! .. I see. Seems like I started with a wrong assumption. I didn't not do the capture image process yet. I wanted to see if I can make a reservation for the already existing VM, that I built with the name 'vmwarewinxp-base7-v0' and placed it under the Data-Store-Path on the VMhost that built it. Yes you were right I was missing the IP address in the Data-Store Path: I will put in the VMhost IP here. In that case shouldn't I generate-node-key's for all the VMhost's because it will try to SSH to it to get to the Data-Store-Path? Thank you Andy for the help ... I will give image capture a try first. Amit
RE: Reservation Error:
Ah! .. I see. Seems like I started with a wrong assumption.
I didn't not do the capture image process yet. I wanted to see if I can make a
reservation for the already existing VM, that I built with the name
'vmwarewinxp-base7-v0' and placed it under the Data-Store-Path on the VMhost
that built it.
Yes you were right I was missing the IP address in the Data-Store Path: I will
put in the VMhost IP here.
In that case shouldn't I generate-node-key's for all the VMhost's because it
will try to SSH to it to get to the Data-Store-Path?
Thank you Andy for the help ... I will give image capture a try first.
Amit
> -Original Message-
> From: Andy Kurth [mailto:andy_ku...@ncsu.edu]
> Sent: Thursday, March 18, 2010 10:56 AM
> To: vcl-dev@incubator.apache.org
> Subject: Re: Reservation Error:
>
> > 376 |16651|5:5|new| WARNING ^M
> > 377 |16651|5:5|new| 2010-03-17
> 13:02:45|16651|5:5|new|DataStructure.pm:_automethod(675)|corresponding data
> has not
> been initialized for get_computer_preferredimage_id:
> $self->request_data-
> >{reservation}{5}{computer}{preferredimage}{id}^M
> > 378 |16651|5:5|new| ( 0) utils.pm, notify (line: 737)^M
> > 379 |16651|5:5|new| (-1) DataStructure.pm, _automethod (line: 675)^M
> > 380 |16651|5:5|new| (-2) Autoload.pm, __ANON__ (line: 80)^M
> > 381 |16651|5:5|new| (-3) new.pm, process (line: 106)^M
> > 382 |16651|5:5|new| (-4) vcld, make_new_child (line: 594)^M
> > 383 |16651|5:5|new| (-5) vcld, main (line: 341)^M
> >
> > #>>> Not sure if I am missing something here.
>
> This isn't a problem. It occurs because computer.preferredimageid isn't set
> in
> the database. It should get set automatically after a successful reservation
> is
> made on the computer.
>
> > 475 2010-03-17
> > 13:02:46|16651|5:5|new|utils.pm:run_ssh_command(6180)|executing
> SSH command on resxi-2:^M
> > 476 |16651|5:5|new| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x
> > resxi-2 'cat
> currentimage.txt' 2>&1^M
> > 477 2010-03-17
> 13:02:47|16651|5:5|new|utils.pm:run_ssh_command(6262)|run_ssh_command
> output:^M
> > 478 |16651|5:5|new| cat: currentimage.txt: No such file or directory^M
> >
> > #>>> currentimage.txt : Is this something that we have to create at
> > anytime? I am
> thinking it is created automatically when a image is loaded for the first
> time.
>
> This appears to be a problem. You never have to manually create/alter
> currentimage.txt. It should be created automatically during the image capture
> process and saved within the image. This file is used when a reservation is
> made to determine if the correct image is loaded on the computer in order to
> know if the computer needs to be reloaded or not. The computer will be
> reloaded
> every time a reservation is made if the file is missing or incorrect, even if
> the correct image is loaded.
>
> Check if currentimage.txt exists in root's home directory on that computer.
> You
> should be able to shell into it from the management node via:
> ssh -i /etc/vcl/vcl.key -l root -p 22 -x resxi-2
>
> Then run "ls -l ~". What do you see?
>
> If you still have the vcld.log output from the image capture process, search
> it
> for "currentimage.txt" to see if anything went wrong.
>
> > 516 2010-03-17
> > 13:02:47|16651|5:5|new|utils.pm:run_ssh_command(6180)|executing
> SSH command on /install/image/nfs1:^M
> > 517 |16651|5:5|new| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x
> > /install/image/nfs1
> 'ls -1 /golden 2>&1' 2>&1^M
> >
> > #>>> This is where my real issues are: I realized reading the README for
> > esx and
> esxthin, that I need to have a VCL mount point and a subdirectory /golden for
> my images
> > But what I am missing here is why is it trying to ssh -x
> > /install/image/nfs1 which is
> actually the Data Store path. Isn't it supposed to ssh to my VMhost machine.
> > Also when does VCL code use the esxthin.pm, as opposed to esx.pm?
>
> The previous two questions are related. I'm not too familiar with the esx.pm
> module but you cannot ignore this. From looking at the code, the warning is
> being displayed because there's a problem with your VM host profile's data
> store
> path value. It's looking for this setting to be in the format:
> :
>
> Check this setting:
> Virtual Hosts > VM Host Profiles > Configure Profile > Data Store Path
>
> I'm guessing it doesn't include
Re: Reservation Error:
376 |16651|5:5|new| WARNING ^M
377 |16651|5:5|new| 2010-03-17
13:02:45|16651|5:5|new|DataStructure.pm:_automethod(675)|corresponding data has not
been initialized for get_computer_preferredimage_id:
$self->request_data->{reservation}{5}{computer}{preferredimage}{id}^M
378 |16651|5:5|new| ( 0) utils.pm, notify (line: 737)^M
379 |16651|5:5|new| (-1) DataStructure.pm, _automethod (line: 675)^M
380 |16651|5:5|new| (-2) Autoload.pm, __ANON__ (line: 80)^M
381 |16651|5:5|new| (-3) new.pm, process (line: 106)^M
382 |16651|5:5|new| (-4) vcld, make_new_child (line: 594)^M
383 |16651|5:5|new| (-5) vcld, main (line: 341)^M
#>>> Not sure if I am missing something here.
This isn't a problem. It occurs because computer.preferredimageid isn't set in
the database. It should get set automatically after a successful reservation is
made on the computer.
475 2010-03-17
13:02:46|16651|5:5|new|utils.pm:run_ssh_command(6180)|executing SSH command on
resxi-2:^M
476 |16651|5:5|new| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x resxi-2
'cat currentimage.txt' 2>&1^M
477 2010-03-17
13:02:47|16651|5:5|new|utils.pm:run_ssh_command(6262)|run_ssh_command output:^M
478 |16651|5:5|new| cat: currentimage.txt: No such file or directory^M
#>>> currentimage.txt : Is this something that we have to create at anytime? I
am thinking it is created automatically when a image is loaded for the first time.
This appears to be a problem. You never have to manually create/alter
currentimage.txt. It should be created automatically during the image capture
process and saved within the image. This file is used when a reservation is
made to determine if the correct image is loaded on the computer in order to
know if the computer needs to be reloaded or not. The computer will be reloaded
every time a reservation is made if the file is missing or incorrect, even if
the correct image is loaded.
Check if currentimage.txt exists in root's home directory on that computer. You
should be able to shell into it from the management node via:
ssh -i /etc/vcl/vcl.key -l root -p 22 -x resxi-2
Then run "ls -l ~". What do you see?
If you still have the vcld.log output from the image capture process, search it
for "currentimage.txt" to see if anything went wrong.
489 2010-03-17 13:02:47|16651|5:5|new|utils.pm:insertloadlog(4710)|inserted
computer=3, loadimageblade, resxi-2 must be reloaded with vmwarewinxp-base7-v
0^M
490 2010-03-17 13:02:47|16651|5:5|new|new.pm:reload_image(616)|calling
VCL::Module::Provisioning::esx->does_image_exist()^M
491 Use of uninitialized value in concatenation (.) or string at^M
492 /usr/local/vcl/bin/../lib/VCL/Module/Provisioning/esx.pm line
907 (#1)^M
493 (W uninitialized) An undefined value was used as if it were
already^M
494 defined. It was interpreted as a "" or a 0, but maybe it was a
mistake.^M
495 To suppress this warning assign a defined value to your variables.^M
496 ^M
497 To help you figure out what was undefined, perl tells you what
operation^M
498 you used the undefined value in. Note, however, that perl
optimizes your^M
499 program and the operation displayed in the warning may not
necessarily^M
500 appear literally in your program. For example, "that $foo" is^M
501 usually optimized into "that " . $foo, and the warning will refer
to^M
502 the concatenation (.) operator, even though there is no . in your^M
503 program.^M
#>>> Can we ignore this?
504 ^M
505 ^M
506 |16651|5:5|new| WARNING ^M
507 |16651|5:5|new| 2010-03-17
13:02:47|16651|5:5|new|vcld:warning_handler(636)|Use of uninitialized value in
concatenation (.) or string at /usr/local/v
cl/bin/../lib/VCL/Module/Provisioning/esx.pm line 907.^M
508 |16651|5:5|new| ( 0) utils.pm, notify (line: 737)^M
509 |16651|5:5|new| (-1) vcld, warning_handler (line: 636)^M
510 |16651|5:5|new| (-2) esx.pm, does_image_exist (line: 907)^M
511 |16651|5:5|new| (-3) new.pm, reload_image (line: 618)^M
512 |16651|5:5|new| (-4) new.pm, process (line: 266)^M
513 |16651|5:5|new| (-5) vcld, make_new_child (line: 594)^M
514 |16651|5:5|new| (-6) vcld, main (line: 341)^M
515 ^M
516 2010-03-17
13:02:47|16651|5:5|new|utils.pm:run_ssh_command(6180)|executing SSH command on
/install/image/nfs1:^M
517 |16651|5:5|new| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x
/install/image/nfs1 'ls -1 /golden 2>&1' 2>&1^M
#>>> This is where my real issues are: I realized reading the README for esx
and esxthin, that I need to have a VCL mount point and a subdirectory /golden for my
images
But what I am missing here is why is it trying to ssh -x /install/image/nfs1
which is actually the Data Store path. Isn't it supposed to ssh to my VMhost
machine.
Also when does VCL code use the esxthin.pm,
