Hello,

Been having an issue with our system. We just added a few new blades
and had our network team move over files to clone our blades so they
work correct.

I can't create images anymore. Normal operation works, but I can't
update or create images currently.

Here is the error code I am getting.

I think that vmkfstools was deleted (I can't find it anywhere), but I
only see that tool for ESX? Do we have this tool on the VCL web site?
Or am I missing something else that is needed to make images?


2010-09-08 08:50:40|6294|9915:9651|new|utils.pm:run_ssh_command(6276)|SSH
command executed on vclesx05, returning (0, "none")
2010-09-08 08:50:40|6294|9915:9651|new|vmware.pm:_vmwareclone(1426)|srcDisk
is exists /virtualmachines/vmwarewinxp-build97-v1/vmwarewinxp-build97-v1.vmdk
2010-09-08 08:50:40|6294|9915:9651|new|vmware.pm:_vmwareclone(1427)|starting
clone process vmkfstools -d thin -i
/virtualmachines/vmwarewinxp-build97-v1/vmwarewinxp-build97-v1.vmdk
/virtualmachines/9651vmguest-104/vmwarewinxp-build97-v1.vmdk
2010-09-08 08:50:40|6294|9915:9651|new|utils.pm:run_ssh_command(6180)|executing
SSH command on vclesx05:
|6294|9915:9651|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22
-x vclesx05 'ls -1
/virtualmachines/9651vmguest-104/vmwarewinxp-build97-v1.vmdk' 2>&1
2010-09-08 
08:50:40|6294|9915:9651|new|utils.pm:run_ssh_command(6262)|run_ssh_command
output:
|6294|9915:9651|new| ls:
/virtualmachines/9651vmguest-104/vmwarewinxp-build97-v1.vmdk: No such
file or directory
2010-09-08 08:50:40|6294|9915:9651|new|utils.pm:run_ssh_command(6272)|SSH
command executed on vclesx05, command:
|6294|9915:9651|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22
-x vclesx05 'ls -1
/virtualmachines/9651vmguest-104/vmwarewinxp-build97-v1.vmdk' 2>&1
|6294|9915:9651|new| returning (2, "ls: /virtualmachines/9651vmgue...")

|6294|9915:9651|new| ---- WARNING ----
|6294|9915:9651|new| 2010-09-08
08:50:40|6294|9915:9651|new|vmware.pm:_vmwareclone(1457)|clone process
failed dstDisk /virtualmachines/9651vmguest-104/vmwarewinxp-build97-v1.vmdk
does not exist
|6294|9915:9651|new| ( 0) utils.pm, notify (line: 737)
|6294|9915:9651|new| (-1) vmware.pm, _vmwareclone (line: 1457)
|6294|9915:9651|new| (-2) vmware.pm, load (line: 502)
|6294|9915:9651|new| (-3) new.pm, reload_image (line: 665)
|6294|9915:9651|new| (-4) new.pm, process (line: 266)
|6294|9915:9651|new| (-5) vcld, make_new_child (line: 594)
|6294|9915:9651|new| (-6) vcld, main (line: 341)

2010-09-08 08:50:40|6294|9915:9651|new|utils.pm:insertloadlog(4710)|inserted
computer=107, failed, cloning base image failed
No recipient addresses found in header
2010-09-08 08:50:40|6294|9915:9651|new|utils.pm:mail(1348)|SUCCESS --
Sending mail To: , PROBLEM -- vmware.pm

|6294|9915:9651|new| ---- CRITICAL ----
|6294|9915:9651|new| 2010-09-08
08:50:40|6294|9915:9651|new|vmware.pm:load(508)|problem cloning failed
/virtualmachines/vmwarewinxp-build97-v1/vmwarewinxp-build97-v1.vmdk to
/virtualmachines/9651vmguest-104/vmwarewinxp-build97-v1.vmdk
|6294|9915:9651|new| ( 0) utils.pm, notify (line: 737)
|6294|9915:9651|new| (-1) vmware.pm, load (line: 508)
|6294|9915:9651|new| (-2) new.pm, reload_image (line: 665)
|6294|9915:9651|new| (-3) new.pm, process (line: 266)
|6294|9915:9651|new| (-4) vcld, make_new_child (line: 594)
|6294|9915:9651|new| (-5) vcld, main (line: 341)


|6294|9915:9651|new| ---- WARNING ----
|6294|9915:9651|new| 2010-09-08
08:50:40|6294|9915:9651|new|new.pm:reload_image(670)|vmwarewinxp-build97-v1
failed to load on vmguest-104, returning
|6294|9915:9651|new| ( 0) utils.pm, notify (line: 737)
|6294|9915:9651|new| (-1) new.pm, reload_image (line: 670)
|6294|9915:9651|new| (-2) new.pm, process (line: 266)
|6294|9915:9651|new| (-3) vcld, make_new_child (line: 594)
|6294|9915:9651|new| (-4) vcld, main (line: 341)

2010-09-08 08:50:40|6294|9915:9651|new|utils.pm:insertloadlog(4710)|inserted
computer=107, loadimagefailed, vmwarewinxp-build97-v1 failed to load
on vmguest-104

|6294|9915:9651|new| ---- WARNING ----
|6294|9915:9651|new| 2010-09-08
08:50:40|6294|9915:9651|new|new.pm:process(313)|failed to load
vmguest-104 with vmwarewinxp-build97-v1
|6294|9915:9651|new| ( 0) utils.pm, notify (line: 737)
|6294|9915:9651|new| (-1) new.pm, process (line: 313)
|6294|9915:9651|new| (-2) vcld, make_new_child (line: 594)
|6294|9915:9651|new| (-3) vcld, main (line: 341)

2010-09-08 
08:50:40|6294|9915:9651|new|DataStructure.pm:get_computer_state_name(1946)|attempting
to retrieve current state of computer vmguest-104 from the database
2010-09-08 
08:50:40|6294|9915:9651|new|DataStructure.pm:get_computer_state_name(1977)|retrieved
current state of computer vmguest-104 from the database: reloading
2010-09-08 08:50:40|6294|9915:9651|new|DataStructure.pm:_automethod(697)|data
structure updated:
$self->request_data->{reservation}{9651}{computer}{state}{name}
|6294|9915:9651|new| computer_state_name = reloading
No recipient addresses found in header
2010-09-08 08:50:40|6294|9915:9651|new|utils.pm:mail(1348)|SUCCESS --
Sending mail To: , PROBLEM -- State.pm

|6294|9915:9651|new| ---- CRITICAL ----
|6294|9915:9651|new| 2010-09-08
08:50:40|6294|9915:9651|new|State.pm:reservation_failed(290)|reservation
failed on vmguest-104: process failed after trying to load or make
available
|6294|9915:9651|new| ( 0) utils.pm, notify (line: 737)
|6294|9915:9651|new| (-1) State.pm, reservation_failed (line: 290)
|6294|9915:9651|new| (-2) new.pm, process (line: 316)
|6294|9915:9651|new| (-3) vcld, make_new_child (line: 594)
|6294|9915:9651|new| (-4) vcld, main (line: 341)

2010-09-08 08:50:40|6294|9915:9651|new|utils.pm:insertloadlog(4710)|inserted
computer=107, failed, process failed after trying to load or make
available
2010-09-08 08:50:40|6294|9915:9651|new|State.pm:reservation_failed(293)|inserted
computerloadlog entry
2010-09-08 08:50:40|6294|9915:9651|new|State.pm:reservation_failed(301)|updated
log ending value to 'failed', logid=3483
2010-09-08 
08:50:40|6294|9915:9651|new|utils.pm:update_computer_state(2228)|computer
107 state updated to: failed
2010-09-08 08:50:40|6294|9915:9651|new|State.pm:reservation_failed(312)|computer
vmguest-104 (107) state set to failed
2010-09-08 
08:50:40|6294|9915:9651|new|utils.pm:update_request_state(2186)|request
9915 state updated to: failed, laststate to: new
2010-09-08 08:50:40|6294|9915:9651|new|State.pm:reservation_failed(325)|set
request state to 'failed'/'new'
2010-09-08 08:50:40|6294|9915:9651|new|utils.pm:is_inblockrequest(6972)|zero
rows were returned from database select
2010-09-08 
08:50:40|6294|9915:9651|new|State.pm:reservation_failed(343)|vmguest-104
is NOT in blockcomputers table
2010-09-08 08:50:40|6294|9915:9651|new|State.pm:reservation_failed(346)|exiting
1
2010-09-08 08:50:40|6294|9915:9651|new|State.pm:DESTROY(905)|destructor
called, ref($self)=VCL::new
2010-09-08 
08:50:40|6294|9915:9651|new|utils.pm:delete_computerloadlog_reservation(7551)|removing
computerloadlog entries matching loadstate = begin
2010-09-08 
08:50:40|6294|9915:9651|new|utils.pm:delete_computerloadlog_reservation(7598)|deleted
rows from computerloadlog for reservation id=9651
2010-09-08 08:50:40|6294|9915:9651|new|State.pm:DESTROY(912)|removed
computerloadlog rows with loadstate=begin for reservation
2010-09-08 08:50:40|6294|9915:9651|new|State.pm:DESTROY(924)|number of
database handles state process created: 1
2010-09-08 08:50:40|6294|9915:9651|new|State.pm:DESTROY(933)|process
has a database handle stored in $ENV{dbh}, attempting disconnect
2010-09-08 08:50:40|6294|9915:9651|new|State.pm:DESTROY(935)|$ENV{dbh}:
database disconnect successful
2010-09-08 08:50:40|6294|9915:9651|new|State.pm:DESTROY(949)|VCL::new
process 6294 exiting
2010-09-08 08:50:40|4994|vcld:REAPER(744)|VCL process exited for
reservation 9651
2010-09-08 08:50:40|4994|vcld:main(165)|lastcheckin time updated for
management node 1: 2010-09-08 08:50:40


-- 
Thanks,
Alex  Patterson
User Support Services
Operating System Analyst
California State University, East Bay

Reply via email to