Hello,

since I upgrade to last version of VCL I’m unable to do a new image
capture. Any clues ?

Thanks.

---------- Mensagem encaminhada ---------
De: <[email protected]>
Data: sex, 6/10/2017 às 18:46
Assunto: PROBLEM -- vclnode1|844:844|image|image.pm
|vm14>servidor12|vmwarewin7-WIN7_20171006126-v0|admin
Para: <[email protected]>


vmwarewin7-WIN7_20171006126-v0 Image Capture Failed
------------------------------------------------------------------------
time: 2017-10-06 18:45:18
caller: image.pm:reservation_failed(334)
( 0) image.pm, reservation_failed (line: 334)
(-1) image.pm, process (line: 169)
(-2) vcld, make_new_child (line: 601)
(-3) vcld, main (line: 353)
------------------------------------------------------------------------
management node: vclnode1.apachevcl.di.uminho.pt
reservation PID: 5405
parent vcld PID: 2049

request ID: 844
reservation ID: 844
request state/laststate: image/inuse
request start time: 2017-10-06 15:45:00
request end time: 2017-10-07 00:00:00
for imaging: yes
log ID: 569

computer: vm14.apachevcl.di.uminho.pt
computer id: 18
computer type: virtualmachine
computer eth0 MAC address: 00:50:56:00:00:1a
computer eth1 MAC address: 00:50:56:00:00:1b
computer private IP address: 10.100.0.114
computer public IP address: 192.168.93.114
computer in block allocation: no
provisioning module: VCL::Module::Provisioning::VMware::VMware

vm host: servidor12.di.uminho.pt
vm host ID: 3
vm host computer ID: 57
vm profile: vmhostprofile1
vm profile VM path: /vmfs/volumes/datastore1/
vm profile repository path: /vmfs/volumes/vcl_images/
vm profile datastore path: /vmfs/volumes/datastore1/
vm profile disk type: shared

image: vmwarewin7-WIN7_20171006126-v0
image display name: WIN7_20171006
image ID: 126
image revision ID: 126
image size: 0 MB
use Sysprep: no
root access: yes
image owner ID: 1
image owner affiliation: Local
image revision date created: 2017-10-06 16:11:33
image revision production: yes
OS module: VCL::Module::OS::Windows::Version_6::7

user: admin
user name: vcl admin
user ID: 1
user affiliation: Local
------------------------------------------------------------------------
RECENT LOG ENTRIES FOR THIS PROCESS:
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s014.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s086.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s049.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s091.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s023.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s016.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s024.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s005.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s080.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s004.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s064.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s022.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s095.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s026.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s060.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s073.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s085.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s072.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s077.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s033.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s025.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s081.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s035.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s074.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s068.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s098.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s044.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s036.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s030.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s066.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s034.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s011.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s029.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s042.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s083.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s100.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s007.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s002.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s003.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s021.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s071.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s043.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s047.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s059.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s079.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s018.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s040.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s037.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s101.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s038.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0-s045.vmdk':
Device or resource busy
|5405|844|844|image|Linux.pm:delete_file|1766| rm: can't remove
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0': Directory not
empty
|5405|844|844|image|Linux.pm:delete_file|1766| ( 0) Linux.pm, delete_file
(line: 1766)
|5405|844|844|image|Linux.pm:delete_file|1766| (-1) VMware.pm, copy_vmdk
(line: 6357)
|5405|844|844|image|Linux.pm:delete_file|1766| (-2) VMware.pm, capture
(line: 1003)
|5405|844|844|image|Linux.pm:delete_file|1766| (-3) image.pm, process
(line: 164)
|5405|844|844|image|Linux.pm:delete_file|1766| (-4) vcld, make_new_child
(line: 601)
|5405|844|844|image|Linux.pm:delete_file|1766| (-5) vcld, main (line: 353)
|5405|844|844|image|Linux.pm:delete_file|1787| ---- WARNING ----
|5405|844|844|image|Linux.pm:delete_file|1787| 2017-10-06
18:45:11|5405|844|844|image|Linux.pm:delete_file|1787|file was not deleted,
it still exists on servidor12:
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0'
|5405|844|844|image|Linux.pm:delete_file|1787| ( 0) Linux.pm, delete_file
(line: 1787)
|5405|844|844|image|Linux.pm:delete_file|1787| (-1) VMware.pm, copy_vmdk
(line: 6357)
|5405|844|844|image|Linux.pm:delete_file|1787| (-2) VMware.pm, capture
(line: 1003)
|5405|844|844|image|Linux.pm:delete_file|1787| (-3) image.pm, process
(line: 164)
|5405|844|844|image|Linux.pm:delete_file|1787| (-4) vcld, make_new_child
(line: 601)
|5405|844|844|image|Linux.pm:delete_file|1787| (-5) vcld, main (line: 353)
|5405|844|844|image|VMware.pm:copy_vmdk|6357| ---- WARNING ----
|5405|844|844|image|VMware.pm:copy_vmdk|6357| 2017-10-06
18:45:11|5405|844|844|image|VMware.pm:copy_vmdk|6357|failed to delete
destination directory after failing to copy virtual disk on VM host
servidor12: /vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0
|5405|844|844|image|VMware.pm:copy_vmdk|6357| ( 0) VMware.pm, copy_vmdk
(line: 6357)
|5405|844|844|image|VMware.pm:copy_vmdk|6357| (-1) VMware.pm, capture
(line: 1003)
|5405|844|844|image|VMware.pm:copy_vmdk|6357| (-2) image.pm, process (line:
164)
|5405|844|844|image|VMware.pm:copy_vmdk|6357| (-3) vcld, make_new_child
(line: 601)
|5405|844|844|image|VMware.pm:copy_vmdk|6357| (-4) vcld, main (line: 353)
|5405|844|844|image|VMware.pm:capture|1007| ---- WARNING ----
|5405|844|844|image|VMware.pm:capture|1007| 2017-10-06
18:45:11|5405|844|844|image|VMware.pm:capture|1007|failed to copy the vmdk
files to the repository mounted on the VM host after the VM was powered
off:
'/vmfs/volumes/datastore1/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0.vmdk'
-->
'/vmfs/volumes/vcl_images/vmwarewin7-WIN7_20171006126-v0/vmwarewin7-WIN7_20171006126-v0.vmdk'
|5405|844|844|image|VMware.pm:capture|1007| ( 0) VMware.pm, capture (line:
1007)
|5405|844|844|image|VMware.pm:capture|1007| (-1) image.pm, process (line:
164)
|5405|844|844|image|VMware.pm:capture|1007| (-2) vcld, make_new_child
(line: 601)
|5405|844|844|image|VMware.pm:capture|1007| (-3) vcld, main (line: 353)
2017-10-06 18:45:11|5405|844|844|image|VMware.pm:capture|1099|attempting to
delete directory where moved vmdk resided before reverting the name back to
the original: /vmfs/volumes/datastore1/vmwarewin7-WIN7_20171006126-v0
2017-10-06 18:45:11|5405|844|844|image|utils.pm:run_ssh_command|4243|executing
SSH command on 192.168.85.22 (servidor12): '/usr/bin/ssh -i
/etc/vcl/vcl.key  -o StrictHostKeyChecking=no -o
UserKnownHostsFile=/dev/null -o ConnectionAttempts=1 -o ConnectTimeout=30
-o BatchMode=no -o PasswordAuthentication=no -l root -p 22 -x 192.168.85.22
'rm -rfv /vmfs/volumes/datastore1/vmwarewin7\-WIN7_20171006126\-v0' 2>&1'
2017-10-06 18:45:12|5405|844|844|image|utils.pm:run_ssh_command|4392|command:
'rm -rfv /vmfs/volumes/datastore1/vmwarewin7\-WIN7_20171006126\-v0',
exit_status: 0, output:
2017-10-06 18:45:12|5405|844|844|image|Linux.pm:delete_file|1777|deleted
'/vmfs/volumes/datastore1/vmwarewin7-WIN7_20171006126-v0' on servidor12
2017-10-06 18:45:12|5405|844|844|image|VMware.pm:capture|1105|attempting to
power the VM back on so that it can be captured again
2017-10-06 18:45:16|5405|844|844|image|VIM_SSH.pm:_run_vim_cmd|303|executed
command on VM host servidor12: vim-cmd vmsvc/power.on 278, exit status: 0
2017-10-06 18:45:17|5405|844|844|image|VIM_SSH.pm:_run_vim_cmd|303|executed
command on VM host servidor12: vim-cmd vmsvc/get.tasklist 278, exit status:
0
2017-10-06
18:45:17|5405|844|844|image|VIM_SSH.pm:_wait_for_task|1029|checking status
of task: haTask-278-vim.VirtualMachine.powerOn-406454855
2017-10-06 18:45:18|5405|844|844|image|VIM_SSH.pm:_run_vim_cmd|303|executed
command on VM host servidor12: vim-cmd vimsvc/task_info
haTask-278-vim.VirtualMachine.powerOn-406454855, exit status: 0
2017-10-06 18:45:18|5405|844|844|image|VIM_SSH.pm:_wait_for_task|1053|task
completed successfully: haTask-278-vim.VirtualMachine.powerOn-406454855
2017-10-06 18:45:18|5405|844|844|image|VIM_SSH.pm:vm_power_on|1277|powered
on VM: /vmfs/volumes/datastore1/vm14_120-v0/vm14_120-v0.vmx
|5405|844|844|image|image.pm:process|168| ---- WARNING ----
|5405|844|844|image|image.pm:process|168| 2017-10-06
18:45:18|5405|844|844|image|image.pm:process|168|vmwarewin7-WIN7_20171006126-v0
image failed to be captured by provisioning module
|5405|844|844|image|image.pm:process|168| ( 0) image.pm, process (line: 168)
|5405|844|844|image|image.pm:process|168| (-1) vcld, make_new_child (line:
601)
|5405|844|844|image|image.pm:process|168| (-2) vcld, main (line: 353)
2017-10-06
18:45:18|5405|844|844|image|DataStructure.pm:get_computer_private_ip_address|1580|private
IP address for vm14.apachevcl.di.uminho.pt (18) stored in this object
matches IP address stored in %ENV: 10.100.0.114
2017-10-06 18:45:18|5405|844|844|image|utils.pm:is_inblockrequest|4933|zero
rows were returned from database select
2017-10-06
18:45:18|5405|844|844|image|DataStructure.pm:get_image_affiliation_name|1703|image
owner id: 1
2017-10-06 18:45:18|5405|844|844|image|utils.pm:get_user_info|6568|retrieving
current user info for '1' from database, cached data is stale: 9234 seconds
old
2017-10-06 18:45:18|5405|844|844|image|utils.pm:get_user_info|6696|management
node's 'Affiliations Using Federated Authentication for Linux Images' list
is empty, setting FEDERATED_LINUX_AUTHENTICATION=0
-- 
António Aragão
(Especialista de Informática)
Universidade do Minho
Departamento de Informática
Edificio 7 - 1.07 (DI-1.03)
Campus de Gualtar
Braga
Telefone: +351 253 6044 86

Reply via email to