You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@vcl.apache.org by Evelio Quiros <ev...@fiu.edu> on 2011/10/25 17:30:12 UTC

Re: Base Image creation error - Continued

OK, 

After adding the missing javascript, I am able to get the Virtual Hosts
page to display.

I added 10 VMs which have been added to the database, as well as the base
image I want to capture, so 11 in all.

Does VCL require the Vsphere module to add a virtual machine computer ?

Also, I am using a free version of ESXi. Is there a licensing issue ?


I tried once again to capture the base image, and I got this error:


VCL::image object could not be created and initialized
------------------------------------------------------------------------
time: 2011-10-25 11:38:43
caller: vcld:make_new_child(571)
( 0) vcld, make_new_child (line: 571)
(-1) vcld, main (line: 346)
------------------------------------------------------------------------
management node: vcltst.fiu.edu
reservation PID: 5327
parent vcld PID: 15838

request ID: 5
reservation ID: 5
request state/laststate: image/image
request start time: 2011-10-25 11:38:35
request end time: 2011-10-25 12:38:35
for imaging: no
log ID: none

computer: redhat64base
computer id: 12
computer type: virtualmachine
computer eth0 MAC address: <undefined>
computer eth1 MAC address: <undefined>
computer private IP address: 10.0.0.2
computer public IP address: 10.106.128.53
computer in block allocation: no
provisioning module: VCL::Module::Provisioning::VMware::VMware

vm host: vcldell_01
vm host ID: 2
vm host computer ID: 13
vm profile: VMware ESX - local storage
vm profile VM path: /vmfs/volumes/local-datastore
vm profile repository path: 0
vm profile datastore path: /vmfs/volumes/local-datastore
vm profile disk type: localdisk

image: vmwarelinux-redhat_linux16-v0
image display name: redhat_linux
image ID: 16
image revision ID: 9
image size: 1450 MB
use Sysprep: yes
root access: yes
image owner ID: 1
image owner affiliation: Local
image revision date created: 2011-10-25 11:38:35
image revision production: yes
OS module: VCL::Module::OS::Linux

user: admin
user name: vcl admin
user ID: 1
user affiliation: Local
------------------------------------------------------------------------
RECENT LOG ENTRIES FOR THIS PROCESS:
2011-10-25 11:38:41|5327|5:5|image|vSphere_SDK.pm:initialize(1826)|vSphere
SDK for Perl does not appear to be installed on this managment node,
unable to load VMware vSphere SDK Perl modules
2011-10-25 
11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1313)|API object
could not be created: VCL::Module::Provisioning::VMware::vSphere_SDK
2011-10-25 
11:38:41|5327|5:5|image|DataStructure.pm:_initialize(613)|computer ID
argument was specified, retrieving data for computer ID: 13
2011-10-25 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(643)|image
ID argument was specified: 4, DataStructure object will contain image
information for the production imagerevision of this image
2011-10-25 
11:38:41|5327|5:5|image|DataStructure.pm:_initialize(660)|retrieved data
for imagerevision ID: 4
2011-10-25 
11:38:41|5327|5:5|image|DataStructure.pm:_initialize(676)|retrieved data
for image ID: 4
2011-10-25 
11:38:41|5327|5:5|image|VMware.pm:get_vmhost_datastructure(1190)|created
DataStructure object for VM host: vcldell_01
2011-10-25 
11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1293)|attempting
to load VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
2011-10-25 
11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1299)|loaded
VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
2011-10-25 11:38:41|5327|5:5|image|Module.pm:new(172)|set 'vmhost_data'
key for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
2011-10-25 11:38:41|5327|5:5|image|Module.pm:new(172)|set 'vmhost_os' key
for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
2011-10-25 
11:38:41|5327|5:5|image|Module.pm:create_mn_os_object(335)|management node
OS object has already been created, address: 219ab58, returning 1
2011-10-25 
11:38:41|5327|5:5|image|Module.pm:new(200)|VCL::Module::Provisioning::VMwar
e::VIM_SSH object created for computer redhat64base, address: 1fd9588
2011-10-25 11:38:42|5327|5:5|image|VIM_SSH.pm:initialize(138)|VIM
executable available on VM host: vim-cmd
2011-10-25 
11:38:42|5327|5:5|image|VIM_SSH.pm:initialize(140)|VCL::Module::Provisionin
g::VMware::VIM_SSH object initialized
2011-10-25 
11:38:42|5327|5:5|image|VMware.pm:get_vmhost_api_object(1320)|created API
object: VCL::Module::Provisioning::VMware::VIM_SSH
2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(278)|VMware on VM
host vcldell_01 will be controlled using vim-cmd via SSH
2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(293)|VMware OS and
API objects created for VM host vcldell_01:
|5327|5:5|image| VM host OS object type: VCL::Module::OS::Linux::UnixLab
|5327|5:5|image| VMware API object type:
VCL::Module::Provisioning::VMware::VIM_SSH
2011-10-25 
11:38:42|5327|5:5|image|VMware.pm:get_vmhost_product_name(5405)|VMware
product being used on VM host vcldell_01: 'VMware ESXi 5.0.0 build-469512'
2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(307)|product:
VMware ESXi 5.0.0 build-469512, OS object: VCL::Module::OS::Linux::UnixLab
2011-10-25 11:38:42|5327|5:5|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd
call count: 1 (hostsvc/datastore/listsummary)
2011-10-25 11:38:43|5327|5:5|image|VIM_SSH.pm:_run_vim_cmd(208)|executed
command on VM host vcldell_01: vim-cmd hostsvc/datastore/listsummary
2011-10-25 
11:38:43|5327|5:5|image|VMware.pm:get_datastore_info(5531)|retrieved
datastore info from VM host:
|5327|5:5|image| datastore1
|5327|5:5|image| ---- WARNING ----
|5327|5:5|image| 2011-10-25
11:38:43|5327|5:5|image|VMware.pm:_get_datastore_name(5848)|unable to
determine datastore name from path: '/vmfs/volumes/local-datastore', path
does not begin with any of the datastore paths:
|5327|5:5|image| '[datastore1]'
|5327|5:5|image| '/vmfs/volumes/datastore1'
|5327|5:5|image| '/vmfs/volumes/4e96b3e5-a6562886-638a-00188be54b59'
|5327|5:5|image| ( 0) VMware.pm, _get_datastore_name (line: 5848)
|5327|5:5|image| (-1) VMware.pm, _get_datastore_root_normal_path (line:
5685)
|5327|5:5|image| (-2) VMware.pm, _get_normal_path (line: 5775)
|5327|5:5|image| (-3) VMware.pm, get_vmx_base_directory_path (line: 2743)
|5327|5:5|image| (-4) VMware.pm, initialize (line: 313)
|5327|5:5|image| (-5) Module.pm, new (line: 207)
|5327|5:5|image| ---- WARNING ----
|5327|5:5|image| 2011-10-25
11:38:43|5327|5:5|image|VMware.pm:_get_datastore_root_normal_path(5687)|fai
led to determine datastore root normal path, unable to determine datastore
name: /vmfs/volumes/local-datastore
|5327|5:5|image| ( 0) VMware.pm, _get_datastore_root_normal_path (line:
5687)
|5327|5:5|image| (-1) VMware.pm, _get_normal_path (line: 5775)
|5327|5:5|image| (-2) VMware.pm, get_vmx_base_directory_path (line: 2743)
|5327|5:5|image| (-3) VMware.pm, initialize (line: 313)
|5327|5:5|image| (-4) Module.pm, new (line: 207)
|5327|5:5|image| (-5) Module.pm, create_provisioning_object (line: 423)
|5327|5:5|image| ---- WARNING ----
|5327|5:5|image| 2011-10-25
11:38:43|5327|5:5|image|VMware.pm:_get_normal_path(5777)|unable to
determine normal path, failed to determine datastore root normal path:
/vmfs/volumes/local-datastore
|5327|5:5|image| ( 0) VMware.pm, _get_normal_path (line: 5777)
|5327|5:5|image| (-1) VMware.pm, get_vmx_base_directory_path (line: 2743)
|5327|5:5|image| (-2) VMware.pm, initialize (line: 313)
|5327|5:5|image| (-3) Module.pm, new (line: 207)
|5327|5:5|image| (-4) Module.pm, create_provisioning_object (line: 423)
|5327|5:5|image| (-5) State.pm, initialize (line: 117)
|5327|5:5|image| ---- WARNING ----
|5327|5:5|image| 2011-10-25
11:38:43|5327|5:5|image|VMware.pm:get_vmx_base_directory_path(2749)|unable
to determine the vmx base directory path, failed to convert path
configured in the VM profile to a normal path:
/vmfs/volumes/local-datastore
|5327|5:5|image| ( 0) VMware.pm, get_vmx_base_directory_path (line: 2749)
|5327|5:5|image| (-1) VMware.pm, initialize (line: 313)
|5327|5:5|image| (-2) Module.pm, new (line: 207)
|5327|5:5|image| (-3) Module.pm, create_provisioning_object (line: 423)
|5327|5:5|image| (-4) State.pm, initialize (line: 117)
|5327|5:5|image| (-5) Module.pm, new (line: 207)
|5327|5:5|image| ---- WARNING ----
|5327|5:5|image| 2011-10-25
11:38:43|5327|5:5|image|VMware.pm:initialize(315)|unable to determine vmx
base directory path on VM host vcldell_01
|5327|5:5|image| ( 0) VMware.pm, initialize (line: 315)
|5327|5:5|image| (-1) Module.pm, new (line: 207)
|5327|5:5|image| (-2) Module.pm, create_provisioning_object (line: 423)
|5327|5:5|image| (-3) State.pm, initialize (line: 117)
|5327|5:5|image| (-4) Module.pm, new (line: 207)
|5327|5:5|image| (-5) vcld, make_new_child (line: 564)
|5327|5:5|image| ---- WARNING ----
|5327|5:5|image| 2011-10-25
11:38:43|5327|5:5|image|Module.pm:create_provisioning_object(431)|provision
ing object could not be created, returning 0
|5327|5:5|image| ( 0) Module.pm, create_provisioning_object (line: 431)
|5327|5:5|image| (-1) State.pm, initialize (line: 117)
|5327|5:5|image| (-2) Module.pm, new (line: 207)
|5327|5:5|image| (-3) vcld, make_new_child (line: 564)
|5327|5:5|image| (-4) vcld, main (line: 346)
|5327|5:5|image| ---- WARNING ----
|5327|5:5|image| 2011-10-25
11:38:43|5327|5:5|image|State.pm:initialize(118)|failed to create
provisioning object
|5327|5:5|image| ( 0) State.pm, initialize (line: 118)
|5327|5:5|image| (-1) Module.pm, new (line: 207)
|5327|5:5|image| (-2) vcld, make_new_child (line: 564)
|5327|5:5|image| (-3) vcld, main (line: 346)
2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(829)|VCL::image
destructor called, address: 1e47a28
2011-10-25 
11:38:43|5327|5:5|image|utils.pm:delete_computerloadlog_reservation(6742)|r
emoving computerloadlog entries matching loadstate = begin
2011-10-25 
11:38:43|5327|5:5|image|utils.pm:delete_computerloadlog_reservation(6789)|d
eleted rows from computerloadlog for reservation id=5
2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(848)|number of
database handles state process created: 1
2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(876)|VCL::image
process duration: 4 seconds
2011-10-25 
11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address(15
81)|attempting to retrieve private IP address for computer: redhat64base
2011-10-25 
11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address(15
85)|retrieved contents of /etc/hosts on this management node, contains 10
lines
2011-10-25 
11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address(16
45)|returning IP address from /etc/hosts file: 10.0.0.2
2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2703)|unable to use
database handle stored in $ENV{dbh}
2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
handle stored in $ENV{dbh}
2011-10-25 11:38:43|5327|5:5|image|utils.pm:is_inblockrequest(6163)|zero
rows were returned from database select
2011-10-25 
11:38:43|5327|5:5|image|DataStructure.pm:get_image_affiliation_name(2035)|i
mage owner id: 1
2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2709)|database
requested (information_schema) does not match handle stored in $ENV{dbh}
(vcl:localhost)
2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
handle stored in $ENV{dbh}
2011-10-25 
11:38:43|5327|5:5|image|DataStructure.pm:retrieve_user_data(1352)|attemptin
g to retrieve and store data for user: user.id = '1'
2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2709)|database
requested (vcl) does not match handle stored in $ENV{dbh}
(information_schema:localhost)
2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
handle stored in $ENV{dbh}
2011-10-25 
11:38:43|5327|5:5|image|DataStructure.pm:retrieve_user_data(1415)|data has
been retrieved for user: admin (id: 1)







On 10/25/11 10:26 AM, "Aaron Coburn" <ac...@amherst.edu> wrote:

>Al,
>if you plan to use the vSphere API, then you will need to install the
>vSphere SDK for Perl separately. The perl modules are available here --
>just make sure that you download the release that matches your vCenter
>version.
>
>http://www.vmware.com/support/developer/viperltoolkit/
>
>Aaron Coburn
>
>
>On Oct 25, 2011, at 10:03 AM, Evelio Quiros wrote:
>
>> Thanks again Aaron. It seems we are taking baby steps here.
>> 
>> Ok, next issue: When I click "Configure Host" in the vcl web interface,
>> nothing happens.
>> 
>> My Vmware server is listed there. It is in "vmhostinuse" state.
>> 
>> I noticed some complaints below about the Vsphere perl module not being
>> installed.
>> I thought that was done in the "install_perl_libraries script.
>> 
>> Thanks again for all your help.
>> 
>> Al Quiros
>> 
>> 
>> On 10/25/11 9:43 AM, "Aaron Peeler" <fa...@ncsu.edu> wrote:
>> 
>>> In the log output your missing the vmhost information.
>>> 
>>> Make sure your vm host server have a correctly configured vmhost
>>> profile and you have assigned your vms to the virtual host server by
>>> using the Virtual Host interface.
>>> 
>>> 
>>>https://cwiki.apache.org/confluence/display/VCL/VCL+2.2.1+-+Further+Step
>>>s+
>>> if+Using+VMware
>>> https://cwiki.apache.org/confluence/display/VCL/VMware+Configuration
>>> 
>>> I'm not seeing the virtual host interface mentioned directly in the
>>> vcl 2.2.1 install guide. I'll added that to the first link.
>>> 
>>> Here is a link from a bootcamp that you can review this morning while
>>> I work on adding the content to Apache VCL:
>>> 
>>>https://sites.google.com/a/ncsu.edu/vcl-bootcamp/exercises/assign-a-vm-t
>>>o-
>>> a-virtual-host
>>> 
>>> Aaron
>>> 
>>> 
>>> On Tue, Oct 25, 2011 at 9:19 AM, Evelio Quiros <ev...@fiu.edu> wrote:
>>>> Thank you Aaron.
>>>> 
>>>> Ok, now it can resolve the name redhat64base to the private IP address
>>>> 10.0.0.2.
>>>> I tried to add the base image as the name linux64.
>>>> It resides in the database as redhat64base, with the public IP of
>>>> 10.106.128.53, and set as available.
>>>> I'm not sure what this error message is telling meŠ
>>>> 
>>>> VCL::image object could not be created and initialized
>>>> 
>>>>-----------------------------------------------------------------------
>>>>-
>>>> time: 2011-10-25 09:30:44
>>>> caller: vcld:make_new_child(571)
>>>> ( 0) vcld, make_new_child (line: 571)
>>>> (-1) vcld, main (line: 346)
>>>> 
>>>>-----------------------------------------------------------------------
>>>>-
>>>> management node: vcltst.fiu.edu
>>>> reservation PID: 31318
>>>> parent vcld PID: 15838
>>>> 
>>>> request ID: 4
>>>> reservation ID: 4
>>>> request state/laststate: image/image
>>>> request start time: 2011-10-25 09:30:37
>>>> request end time: 2011-10-25 10:30:37
>>>> for imaging: no
>>>> log ID: none
>>>> 
>>>> computer: redhat64base
>>>> computer id: 12
>>>> computer type: blade
>>>> computer eth0 MAC address: <undefined>
>>>> computer eth1 MAC address: <undefined>
>>>> computer private IP address: 10.0.0.2
>>>> computer public IP address: 10.106.128.53
>>>> computer in block allocation: no
>>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>> 
>>>> image: vmwarelinux-linux6414-v0
>>>> image display name: linux64
>>>> image ID: 14
>>>> image revision ID: 8
>>>> image size: 1450 MB
>>>> use Sysprep: yes
>>>> root access: yes
>>>> image owner ID: 1
>>>> image owner affiliation: Local
>>>> image revision date created: 2011-10-25 09:30:37
>>>> image revision production: yes
>>>> OS module: VCL::Module::OS::Linux
>>>> 
>>>> user: admin
>>>> user name: vcl admin
>>>> user ID: 1
>>>> user affiliation: Local
>>>> 
>>>>-----------------------------------------------------------------------
>>>>-
>>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attempti
>>>>ng
>>>> to load VMware control module:
>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>> 2011-10-25
>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>> VMware control module: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>'vmhost_data'
>>>> key for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>> arguments
>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set 'vmhost_os'
>>>> key
>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>arguments
>>>> 2011-10-25
>>>> 09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|management
>>>> node OS object has already been created, address: 21956b8, returning 1
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioning::
>>>>VM
>>>> wa
>>>> re::vSphere_SDK object created for computer redhat64base, address:
>>>> 21e6980
>>>> 2011-10-25
>>>> 09:30:43|31318|4:4|image|vSphere_SDK.pm:initialize(1826)|vSphere SDK
>>>>for
>>>> Perl does not appear to be installed on this managment node, unable to
>>>> load VMware vSphere SDK Perl modules
>>>> 2011-10-25
>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>> object
>>>> could not be created: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>> |31318|4:4|image| ---- WARNING ----
>>>> |31318|4:4|image| 2011-10-25
>>>> 
>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspondin
>>>>g
>>>> data has not been initialized for get_vmhost_computer_id:
>>>> $self->request_data->{reservation}{4}{computer}{vmhost}{computerid}
>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>1161)
>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>> |31318|4:4|image| ---- WARNING ----
>>>> |31318|4:4|image| 2011-10-25
>>>> 
>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspondin
>>>>g
>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>> 
>>>> 
>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{vmprofile}{imag
>>>>ei
>>>> d}
>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>1162)
>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_datastructure(1190)|creat
>>>>ed
>>>> DataStructure object for VM host: redhat64base
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attempti
>>>>ng
>>>> to load VMware control module:
>>>> VCL::Module::Provisioning::VMware::VIM_SSH
>>>> 2011-10-25
>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>> VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>'vmhost_data'
>>>> key for VCL::Module::Provisioning::VMware::VIM_SSH object from
>>>>arguments
>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set 'vmhost_os'
>>>> key
>>>> for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
>>>> 2011-10-25
>>>> 09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|management
>>>> node OS object has already been created, address: 21956b8, returning 1
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioning::
>>>>VM
>>>> wa
>>>> re::VIM_SSH object created for computer redhat64base, address: 24f7888
>>>> 2011-10-25 09:30:43|31318|4:4|image|VIM_SSH.pm:initialize(126)|VIM
>>>> executable is not available on the VM host, output:
>>>> |31318|4:4|image| bash: vim-cmd: command not found
>>>> |31318|4:4|image| bash: vmware-vim-cmd: command not found
>>>> 2011-10-25
>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>> object
>>>> could not be created: VCL::Module::Provisioning::VMware::VIM_SSH
>>>> |31318|4:4|image| ---- WARNING ----
>>>> |31318|4:4|image| 2011-10-25
>>>> 
>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspondin
>>>>g
>>>> data has not been initialized for get_vmhost_computer_id:
>>>> $self->request_data->{reservation}{4}{computer}{vmhost}{computerid}
>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>1161)
>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>> |31318|4:4|image| ---- WARNING ----
>>>> |31318|4:4|image| 2011-10-25
>>>> 
>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspondin
>>>>g
>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>> 
>>>> 
>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{vmprofile}{imag
>>>>ei
>>>> d}
>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>1162)
>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_datastructure(1190)|creat
>>>>ed
>>>> DataStructure object for VM host: redhat64base
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attempti
>>>>ng
>>>> to load VMware control module:
>>>> VCL::Module::Provisioning::VMware::vmware_cmd
>>>> 2011-10-25
>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>> VMware control module: VCL::Module::Provisioning::VMware::vmware_cmd
>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>'vmhost_data'
>>>> key for VCL::Module::Provisioning::VMware::vmware_cmd object from
>>>> arguments
>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set 'vmhost_os'
>>>> key
>>>> for VCL::Module::Provisioning::VMware::vmware_cmd object from
>>>>arguments
>>>> 2011-10-25
>>>> 09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|management
>>>> node OS object has already been created, address: 21956b8, returning 1
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioning::
>>>>VM
>>>> wa
>>>> re::vmware_cmd object created for computer redhat64base, address:
>>>> 251d1e0
>>>> 2011-10-25
>>>> 09:30:44|31318|4:4|image|vmware_cmd.pm:initialize(107)|vmware-cmd is
>>>>not
>>>> available on the VM host, output:
>>>> |31318|4:4|image| bash: vmware-cmd: command not found
>>>> 2011-10-25
>>>> 09:30:44|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>> object
>>>> could not be created: VCL::Module::Provisioning::VMware::vmware_cmd
>>>> |31318|4:4|image| ---- WARNING ----
>>>> |31318|4:4|image| 2011-10-25
>>>> 09:30:44|31318|4:4|image|VMware.pm:initialize(285)|failed to create an
>>>> object to control VMware on VM host: redhat64base
>>>> |31318|4:4|image| ( 0) VMware.pm, initialize (line: 285)
>>>> |31318|4:4|image| (-1) Module.pm, new (line: 207)
>>>> |31318|4:4|image| (-2) Module.pm, create_provisioning_object (line:
>>>>423)
>>>> |31318|4:4|image| (-3) State.pm, initialize (line: 117)
>>>> |31318|4:4|image| (-4) Module.pm, new (line: 207)
>>>> |31318|4:4|image| (-5) vcld, make_new_child (line: 564)
>>>> |31318|4:4|image| ---- WARNING ----
>>>> |31318|4:4|image| 2011-10-25
>>>> 
>>>> 
>>>>09:30:44|31318|4:4|image|Module.pm:create_provisioning_object(431)|prov
>>>>is
>>>> io
>>>> ning object could not be created, returning 0
>>>> |31318|4:4|image| ( 0) Module.pm, create_provisioning_object (line:
>>>>431)
>>>> |31318|4:4|image| (-1) State.pm, initialize (line: 117)
>>>> |31318|4:4|image| (-2) Module.pm, new (line: 207)
>>>> |31318|4:4|image| (-3) vcld, make_new_child (line: 564)
>>>> |31318|4:4|image| (-4) vcld, main (line: 346)
>>>> |31318|4:4|image| ---- WARNING ----
>>>> |31318|4:4|image| 2011-10-25
>>>> 09:30:44|31318|4:4|image|State.pm:initialize(118)|failed to create
>>>> provisioning object
>>>> |31318|4:4|image| ( 0) State.pm, initialize (line: 118)
>>>> |31318|4:4|image| (-1) Module.pm, new (line: 207)
>>>> |31318|4:4|image| (-2) vcld, make_new_child (line: 564)
>>>> |31318|4:4|image| (-3) vcld, main (line: 346)
>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(829)|VCL::image
>>>> destructor called, address: 1e47818
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:44|31318|4:4|image|utils.pm:delete_computerloadlog_reservation(67
>>>>42
>>>> )|
>>>> removing computerloadlog entries matching loadstate = begin
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:44|31318|4:4|image|utils.pm:delete_computerloadlog_reservation(67
>>>>89
>>>> )|
>>>> deleted rows from computerloadlog for reservation id=4
>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(848)|number of
>>>> database handles state process created: 1
>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(876)|VCL::image
>>>> process duration: 2 seconds
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_addre
>>>>ss
>>>> (1
>>>> 581)|attempting to retrieve private IP address for computer:
>>>> redhat64base
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_addre
>>>>ss
>>>> (1
>>>> 585)|retrieved contents of /etc/hosts on this management node,
>>>>contains
>>>> 9
>>>> lines
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_addre
>>>>ss
>>>> (1
>>>> 645)|returning IP address from /etc/hosts file: 10.0.0.2
>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2703)|unable to
>>>> use
>>>> database handle stored in $ENV{dbh}
>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>> handle stored in $ENV{dbh}
>>>> 2011-10-25 
>>>> 09:30:44|31318|4:4|image|utils.pm:is_inblockrequest(6163)|zero
>>>> rows were returned from database select
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_image_affiliation_name(20
>>>>35
>>>> )|
>>>> image owner id: 1
>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2709)|database
>>>> requested (information_schema) does not match handle stored in
>>>>$ENV{dbh}
>>>> (vcl:localhost)
>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>> handle stored in $ENV{dbh}
>>>> 2011-10-25
>>>> 
>>>> 
>>>>09:30:44|31318|4:4|image|DataStructure.pm:retrieve_user_data(1352)|atte
>>>>mp
>>>> ti
>>>> ng to retrieve and store data for user: user.id = '1'
>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2709)|database
>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>> (information_schema:localhost)
>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>> handle stored in $ENV{dbh}
>>>> 2011-10-25
>>>> 
>>>>09:30:44|31318|4:4|image|DataStructure.pm:retrieve_user_data(1415)|data
>>>> has been retrieved for user: admin (id: 1)
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On 10/25/11 9:04 AM, "Aaron Peeler" <aa...@ncsu.edu> wrote:
>>>> 
>>>>> Al,
>>>>> 
>>>>> The hostname has to resolve.
>>>>> 
>>>>> Put an entry in your /etc/hosts file.
>>>>> 
>>>>> Aaron
>>>>> 
>>>>> On Tue, Oct 25, 2011 at 8:52 AM, Evelio Quiros <ev...@fiu.edu>
>>>>>wrote:
>>>>>> Hello,
>>>>>> I am getting an error when I try to capture a linux base image in
>>>>>>vcl.
>>>>>> I am
>>>>>> following the instructions, but perhaps some parts of these may have
>>>>>> been
>>>>>> misinterpreted.
>>>>>> My VCL server is at 10.0.0.1. My Vmware based virtual machine is at
>>>>>> 10.0.0.2. I can ssh without passwords using keys from the vcl server
>>>>>> to
>>>>>> the
>>>>>> VM.
>>>>>> The computer has been added to the database as hostname
>>>>>>redhat64base,
>>>>>> although I have no DNS entry to resolve that name, so I use it's
>>>>>> private IP
>>>>>> of 10.0.0.2.
>>>>>> Below is the result of vcld trying to capture the computer to
>>>>>>create a
>>>>>> new
>>>>>> base imageŠ.Any ideas about what could be wrong ?
>>>>>> Thanks,
>>>>>> Al Quiros
>>>>>> 
>>>>>> VCL::image object could not be created and initialized
>>>>>> 
>>>>>> 
>>>>>>---------------------------------------------------------------------
>>>>>>--
>>>>>> -
>>>>>> time: 2011-10-25 08:58:38
>>>>>> caller: vcld:make_new_child(571)
>>>>>> ( 0) vcld, make_new_child (line: 571)
>>>>>> (-1) vcld, main (line: 346)
>>>>>> 
>>>>>> 
>>>>>>---------------------------------------------------------------------
>>>>>>--
>>>>>> -
>>>>>> management node: vcltst.fiu.edu
>>>>>> reservation PID: 29609
>>>>>> parent vcld PID: 15838
>>>>>> request ID: 2
>>>>>> reservation ID: 2
>>>>>> request state/laststate: image/image
>>>>>> request start time: 2011-10-25 08:58:37
>>>>>> request end time: 2011-10-25 09:58:37
>>>>>> for imaging: no
>>>>>> log ID: none
>>>>>> computer: redhat64base
>>>>>> computer id: 12
>>>>>> computer type: blade
>>>>>> computer eth0 MAC address: <undefined>
>>>>>> computer eth1 MAC address: <undefined>
>>>>>> computer private IP address: <undefined>
>>>>>> computer public IP address: 10.0.0.2
>>>>>> computer in block allocation: no
>>>>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>>>> image: vmwarelinux-redhat64linux8-v0
>>>>>> image display name: redhat64linux
>>>>>> image ID: 8
>>>>>> image revision ID: 6
>>>>>> image size: 1450 MB
>>>>>> use Sysprep: yes
>>>>>> root access: yes
>>>>>> image owner ID: 1
>>>>>> image owner affiliation: Local
>>>>>> image revision date created: 2011-10-25 08:58:37
>>>>>> image revision production: yes
>>>>>> OS module: VCL::Module::OS::Linux
>>>>>> user: admin
>>>>>> user name: vcl admin
>>>>>> user ID: 1
>>>>>> user affiliation: Local
>>>>>> 
>>>>>> 
>>>>>>---------------------------------------------------------------------
>>>>>>--
>>>>>> -
>>>>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>>>>> 2011-10-25
>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_os_object(1238)|VM
>>>>>> host OS module loaded: VCL::Module::OS::Linux
>>>>>> 2011-10-25
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|Module.pm:create_mn_os_object(335)|managemen
>>>>>>t
>>>>>> node
>>>>>> OS object has already been created, address: 1fbe730, returning 1
>>>>>> 2011-10-25
>>>>>> 08:58:38|29609|2:2|image|Module.pm:new(196)|VCL::Module::OS::Linux
>>>>>> object
>>>>>> created for image vmwarelinux-redhat64linux8-v0, address: 24f12f0
>>>>>> 2011-10-25
>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_os_object(1244)|VM
>>>>>> host OS object created: VCL::Module::OS::Linux
>>>>>> 2011-10-25 08:58:38|29609|2:2|image|utils.pm:run_command(8998)|$? is
>>>>>> set to
>>>>>> -1, setting exit status to 0, Perl bug likely encountered
>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>> |29609|2:2|image| 2011-10-25
>>>>>> 08:58:38|29609|2:2|image|utils.pm:nmap_port(2645)|error occurred
>>>>>> running
>>>>>> nmap command: '/usr/bin/nmap redhat64base -P0 -p 22 -T Aggressive',
>>>>>> output:
>>>>>> |29609|2:2|image| Starting Nmap 5.21 ( http://nmap.org ) at
>>>>>>2011-10-25
>>>>>> 08:58
>>>>>> EDT
>>>>>> |29609|2:2|image| Failed to resolve given hostname/IP: redhat64base.
>>>>>> Note
>>>>>> that you can't use '/mask' AND '1-4,7,100-' style IP ranges
>>>>>> |29609|2:2|image| WARNING: No targets were specified, so 0 hosts
>>>>>> scanned.
>>>>>> |29609|2:2|image| Nmap done: 0 IP addresses (0 hosts up) scanned in
>>>>>> 0.05
>>>>>> seconds
>>>>>> |29609|2:2|image| ( 0) utils.pm, nmap_port (line: 2645)
>>>>>> |29609|2:2|image| (-1) OS.pm, is_ssh_responding (line: 383)
>>>>>> |29609|2:2|image| (-2) VMware.pm, initialize (line: 252)
>>>>>> |29609|2:2|image| (-3) Module.pm, new (line: 207)
>>>>>> |29609|2:2|image| (-4) Module.pm, create_provisioning_object (line:
>>>>>> 423)
>>>>>> |29609|2:2|image| (-5) State.pm, initialize (line: 117)
>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>> |29609|2:2|image| 2011-10-25
>>>>>> 08:58:38|29609|2:2|image|utils.pm:nmap_port(2645)|error occurred
>>>>>> running
>>>>>> nmap command: '/usr/bin/nmap redhat64base -P0 -p 24 -T Aggressive',
>>>>>> output:
>>>>>> |29609|2:2|image| Starting Nmap 5.21 ( http://nmap.org ) at
>>>>>>2011-10-25
>>>>>> 08:58
>>>>>> EDT
>>>>>> |29609|2:2|image| Failed to resolve given hostname/IP: redhat64base.
>>>>>> Note
>>>>>> that you can't use '/mask' AND '1-4,7,100-' style IP ranges
>>>>>> |29609|2:2|image| WARNING: No targets were specified, so 0 hosts
>>>>>> scanned.
>>>>>> |29609|2:2|image| Nmap done: 0 IP addresses (0 hosts up) scanned in
>>>>>> 0.05
>>>>>> seconds
>>>>>> |29609|2:2|image| ( 0) utils.pm, nmap_port (line: 2645)
>>>>>> |29609|2:2|image| (-1) OS.pm, is_ssh_responding (line: 384)
>>>>>> |29609|2:2|image| (-2) VMware.pm, initialize (line: 252)
>>>>>> |29609|2:2|image| (-3) Module.pm, new (line: 207)
>>>>>> |29609|2:2|image| (-4) Module.pm, create_provisioning_object (line:
>>>>>> 423)
>>>>>> |29609|2:2|image| (-5) State.pm, initialize (line: 117)
>>>>>> 2011-10-25
>>>>>> 08:58:38|29609|2:2|image|OS.pm:is_ssh_responding(386)|redhat64base 
>>>>>>is
>>>>>> NOT
>>>>>> responding to SSH, ports 22 or 24 are both closed
>>>>>> 2011-10-25 08:58:38|29609|2:2|image|VMware.pm:initialize(257)|unable
>>>>>> to
>>>>>> control OS of VM host redhat64base using VCL::Module::OS::Linux OS
>>>>>> object
>>>>>> because VM host is not responding to SSH
>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>> |29609|2:2|image| 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:_automethod(812)|correspond
>>>>>>in
>>>>>> g
>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>> $self->request_data->{reservation}{2}{computer}{vmhost}{computerid}
>>>>>> |29609|2:2|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>> |29609|2:2|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>> |29609|2:2|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>> 1161)
>>>>>> |29609|2:2|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>>> |29609|2:2|image| (-4) VMware.pm, initialize (line: 265)
>>>>>> |29609|2:2|image| (-5) Module.pm, new (line: 207)
>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>> |29609|2:2|image| 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:_automethod(812)|correspond
>>>>>>in
>>>>>> g
>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>> 
>>>>>> 
>>>>>>$self->request_data->{reservation}{2}{computer}{vmhost}{vmprofile}{im
>>>>>>ag
>>>>>> ei
>>>>>> d}
>>>>>> |29609|2:2|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>> |29609|2:2|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>> |29609|2:2|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>> 1162)
>>>>>> |29609|2:2|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>>> |29609|2:2|image| (-4) VMware.pm, initialize (line: 265)
>>>>>> |29609|2:2|image| (-5) Module.pm, new (line: 207)
>>>>>> 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_datastructure(1190)|cre
>>>>>>at
>>>>>> ed
>>>>>> DataStructure object for VM host: redhat64base
>>>>>> 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1293)|attemp
>>>>>>ti
>>>>>> ng
>>>>>> to
>>>>>> load VMware control module:
>>>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>> 2011-10-25
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>>>> VMware
>>>>>> control module: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>> 2011-10-25 08:58:38|29609|2:2|image|Module.pm:new(172)|set
>>>>>> 'vmhost_data' key
>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>> arguments
>>>>>> 2011-10-25 08:58:38|29609|2:2|image|Module.pm:new(172)|set 
>>>>>>'vmhost_os'
>>>>>> key
>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>> arguments
>>>>>> 2011-10-25
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|Module.pm:create_mn_os_object(335)|managemen
>>>>>>t
>>>>>> node
>>>>>> OS object has already been created, address: 1fbe730, returning 1
>>>>>> 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|Module.pm:new(200)|VCL::Module::Provisioning
>>>>>>::
>>>>>> VM
>>>>>> ware::vSphere_SDK
>>>>>> object created for computer redhat64base, address: 2508cf8
>>>>>> 2011-10-25
>>>>>> 08:58:38|29609|2:2|image|vSphere_SDK.pm:initialize(1826)|vSphere
>>>>>> SDK for Perl does not appear to be installed on this managment node,
>>>>>> unable
>>>>>> to load VMware vSphere SDK Perl modules
>>>>>> 2011-10-25
>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>> object
>>>>>> could not be created: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>> |29609|2:2|image| 2011-10-25
>>>>>> 08:58:38|29609|2:2|image|VMware.pm:initialize(273)|no methods are
>>>>>> available
>>>>>> to control VM host redhat64base, the vSphere SDK cannot be used to
>>>>>> control
>>>>>> the VM host and the host OS cannot be controlled via SSH
>>>>>> |29609|2:2|image| ( 0) VMware.pm, initialize (line: 273)
>>>>>> |29609|2:2|image| (-1) Module.pm, new (line: 207)
>>>>>> |29609|2:2|image| (-2) Module.pm, create_provisioning_object (line:
>>>>>> 423)
>>>>>> |29609|2:2|image| (-3) State.pm, initialize (line: 117)
>>>>>> |29609|2:2|image| (-4) Module.pm, new (line: 207)
>>>>>> |29609|2:2|image| (-5) vcld, make_new_child (line: 564)
>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>> |29609|2:2|image| 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|Module.pm:create_provisioning_object(431)|pr
>>>>>>ov
>>>>>> is
>>>>>> ioning
>>>>>> object could not be created, returning 0
>>>>>> |29609|2:2|image| ( 0) Module.pm, create_provisioning_object (line:
>>>>>> 431)
>>>>>> |29609|2:2|image| (-1) State.pm, initialize (line: 117)
>>>>>> |29609|2:2|image| (-2) Module.pm, new (line: 207)
>>>>>> |29609|2:2|image| (-3) vcld, make_new_child (line: 564)
>>>>>> |29609|2:2|image| (-4) vcld, main (line: 346)
>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>> |29609|2:2|image| 2011-10-25
>>>>>> 08:58:38|29609|2:2|image|State.pm:initialize(118)|failed to create
>>>>>> provisioning object
>>>>>> |29609|2:2|image| ( 0) State.pm, initialize (line: 118)
>>>>>> |29609|2:2|image| (-1) Module.pm, new (line: 207)
>>>>>> |29609|2:2|image| (-2) vcld, make_new_child (line: 564)
>>>>>> |29609|2:2|image| (-3) vcld, main (line: 346)
>>>>>> 2011-10-25 08:58:38|29609|2:2|image|State.pm:DESTROY(829)|VCL::image
>>>>>> destructor called, address: 1e52a60
>>>>>> 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|utils.pm:delete_computerloadlog_reservation(
>>>>>>67
>>>>>> 42
>>>>>> )|removing
>>>>>> computerloadlog entries matching loadstate = begin
>>>>>> 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|utils.pm:delete_computerloadlog_reservation(
>>>>>>67
>>>>>> 89
>>>>>> )|deleted
>>>>>> rows from computerloadlog for reservation id=2
>>>>>> 2011-10-25 08:58:38|29609|2:2|image|State.pm:DESTROY(848)|number of
>>>>>> database
>>>>>> handles state process created: 1
>>>>>> 2011-10-25 08:58:38|29609|2:2|image|State.pm:DESTROY(876)|VCL::image
>>>>>> process
>>>>>> duration: 0 seconds
>>>>>> 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_add
>>>>>>re
>>>>>> ss
>>>>>> (1581)|attempting
>>>>>> to retrieve private IP address for computer: redhat64base
>>>>>> 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_add
>>>>>>re
>>>>>> ss
>>>>>> (1585)|retrieved
>>>>>> contents of /etc/hosts on this management node, contains 8 lines
>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>> |29609|2:2|image| 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_add
>>>>>>re
>>>>>> ss
>>>>>> (1629)|did
>>>>>> not find any lines in /etc/hosts containing 'redhat64base' and the
>>>>>> private
>>>>>> IP address is not defined in the database
>>>>>> |29609|2:2|image| ( 0) DataStructure.pm,
>>>>>> get_computer_private_ip_address
>>>>>> (line: 1629)
>>>>>> |29609|2:2|image| (-1) DataStructure.pm, get_reservation_info_string
>>>>>> (line:
>>>>>> 2419)
>>>>>> |29609|2:2|image| (-3) vcld, make_new_child (line: 571)
>>>>>> |29609|2:2|image| (-4) vcld, main (line: 346)
>>>>>> 2011-10-25 08:58:38|29609|2:2|image|utils.pm:getnewdbh(2703)|unable 
>>>>>>to
>>>>>> use
>>>>>> database handle stored in $ENV{dbh}
>>>>>> 2011-10-25 
>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>> handle
>>>>>> stored in $ENV{dbh}
>>>>>> 2011-10-25
>>>>>> 08:58:38|29609|2:2|image|utils.pm:is_inblockrequest(6163)|zero
>>>>>> rows were returned from database select
>>>>>> 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_image_affiliation_name(
>>>>>>20
>>>>>> 35
>>>>>> )|image
>>>>>> owner id: 1
>>>>>> 2011-10-25 
>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2709)|database
>>>>>> requested (information_schema) does not match handle stored in
>>>>>> $ENV{dbh}
>>>>>> (vcl:localhost)
>>>>>> 2011-10-25 
>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>> handle
>>>>>> stored in $ENV{dbh}
>>>>>> 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:retrieve_user_data(1352)|at
>>>>>>te
>>>>>> mp
>>>>>> ting
>>>>>> to retrieve and store data for user: user.id = '1'
>>>>>> 2011-10-25 
>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2709)|database
>>>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>>>> (information_schema:localhost)
>>>>>> 2011-10-25 
>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>> handle
>>>>>> stored in $ENV{dbh}
>>>>>> 2011-10-25
>>>>>> 
>>>>>> 
>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:retrieve_user_data(1415)|da
>>>>>>ta
>>>>>> has
>>>>>> been retrieved for user: admin (id: 1)
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Aaron Peeler
>>>>> Program Manager
>>>>> Virtual Computing Lab
>>>>> NC State University
>>>>> 
>>>>> All electronic mail messages in connection with State business which
>>>>> are sent to or received by this account are subject to the NC Public
>>>>> Records Law and may be disclosed to third parties.
>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Aaron Peeler
>>> Program Manager
>>> Virtual Computing Lab
>>> NC State University
>>> 
>>> All electronic mail messages in connection with State business which
>>> are sent to or received by this account are subject to the NC Public
>>> Records Law and may be disclosed to third parties.
>> 
>


Re: another problem for image reservation

Posted by "Huang,Lei" <lh...@PVAMU.EDU>.
Aaron,

   I tested it again using the two modules. However, both of reservations
worked this time. I will do more tests to see in what situation the
failure happens. I am still attaching the log to let you see the
differences. The blade name is CSB303, and the vmguest is vmguest-3.

Thanks,
Lei




On 11/2/11 2:17 PM, "Aaron Peeler" <aa...@ncsu.edu> wrote:

>Can you send log output of a reservation flow working with the old
>module and a 2nd reservation flow of it not working using the
>recommended vmware module?
>
>I'd have to trace through it to see what is going on. We want to move
>away from the older GSX module.
>
>It's also strange that is works for one and not the other. Both
>modules using ssh <nodename> to get on the node.
>
>Thanks,
>Aaron
>
>
>On Wed, Nov 2, 2011 at 3:10 PM, Huang,Lei <lh...@pvamu.edu> wrote:
>> Aaron,
>>
>>  Thanks. The question is why the old module using Vmware Server GSX
>>works.
>> If I switch back to Vmware server GSX, windows image works fine.In this
>> case, ssh can log into the image. Do I need to switch back?
>>
>> Thanks,
>> Lei
>>
>> On 11/2/11 1:37 PM, "Aaron Peeler" <fa...@ncsu.edu> wrote:
>>
>>>Hi Lei,
>>>
>>>The issue in the log output is related to ssh is not responding.
>>>
>>>Double check that you can log into vmguest-1 or vmguest-3 via ssh (you
>>>have a couple of different reservations in your log output).
>>>
>>>Things to check are to;
>>>make sure your vmguest-X machines are getting the correct dhcp IP
>>>address.
>>>make sure cygwin sshd service is started.
>>>
>>>Aaron
>>>
>>>
>>>
>>>On Wed, Nov 2, 2011 at 2:22 PM, Huang,Lei <lh...@pvamu.edu> wrote:
>>>> Hi All,
>>>>
>>>>  I have encountered another problem after upgraded to 2.2.1. Per
>>>>Aaron's
>>>> suggestion, I changed my Vmguests provisioning engine to Vmware from
>>>> Vmware Server GSX. However, my Windows XP image failed to reserve
>>>>after
>>>> the change. From the log, I found that it looks for
>>>> 'C:/Windows/System32/qwinsta.exe' and 'C:/Windows/System32/sc.exe
>>>>config
>>>> sshd start= auto'. However, both them are not found on my XP image.
>>>>Do I
>>>> need to update my XP image? The image works fine on Vmware Server GSX
>>>> provision engine. The following is the log.
>>>>
>>>> Thanks,
>>>> Lei
>>>>
>>>> ======================
>>>>
>>>> |15314|780:780|new| ---- WARNING ----
>>>> |15314|780:780|new| 2011-11-02
>>>> 12:58:21|15314|780:780|new|Windows.pm:is_64_bit(8095)|unable to find
>>>> registry value line in reg.exe output:
>>>> |15314|780:780|new| bash: reg.exe: command not found
>>>> |15314|780:780|new| ( 0) Windows.pm, is_64_bit (line: 8095)
>>>> |15314|780:780|new| (-1) Windows.pm, get_system32_path (line: 8146)
>>>> |15314|780:780|new| (-2) Windows.pm, user_logged_in (line: 8342)
>>>> |15314|780:780|new| (-3) Windows.pm, wait_for_logoff (line: 8440)
>>>> |15314|780:780|new| (-4) Windows.pm, post_load (line: 602)
>>>> |15314|780:780|new| (-5) VMware.pm, load (line: 415)
>>>>
>>>> 2011-11-02
>>>> 12:58:21|15314|780:780|new|Windows.pm:get_system32_path(8152)|32-bit
>>>> Windows OS installed on vmguest-3, using C:/Windows/System32
>>>> 2011-11-02
>>>> 12:58:21|15314|780:780|new|Windows.pm:user_logged_in(8356)|checking if
>>>> root is logged in to vmguest-3
>>>> 2011-11-02
>>>> 12:58:21|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing
>>>>SSH
>>>> command on vmguest-3:
>>>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>>>> 'C:/Windows/System32/qwinsta.exe' 2>&1
>>>> 2011-11-02
>>>> 12:58:25|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 5:
>>>> waiting for vmguest-1 to respond to SSH
>>>> 2011-11-02
>>>> 12:58:25|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is
>>>>NOT
>>>> responding to SSH, ports 22 or 24 are both closed
>>>> 2011-11-02
>>>> 12:58:25|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 5:
>>>> code returned false, seconds elapsed/remaining: 34/866, sleeping for 8
>>>> seconds
>>>> 2011-11-02 12:58:26|12831|vcld:main(167)|lastcheckin time updated for
>>>> management node 1: 2011-11-02 12:58:26
>>>> 2011-11-02
>>>>
>>>>12:58:26|15410|778:778|reserved|DataStructure.pm:get_reservation_remote
>>>>_i
>>>>p(
>>>> 1093)|reservation remote IP is not defined
>>>> 2011-11-02
>>>>
>>>>12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_comma
>>>>nd
>>>> output:
>>>> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such
>>>>file
>>>>or
>>>> directory
>>>> 2011-11-02
>>>>12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
>>>> command executed on vmguest-3, command:
>>>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>>>> 'C:/Windows/System32/qwinsta.exe' 2>&1
>>>> |15314|780:780|new| returning (127, "bash:
>>>>C:/Windows/System32/qwin...")
>>>>
>>>> |15314|780:780|new| ---- WARNING ----
>>>> |15314|780:780|new| 2011-11-02
>>>> 12:58:27|15314|780:780|new|Windows.pm:user_logged_in(8361)|failed to
>>>>run
>>>> qwinsta.exe on vmguest-3, exit status: 127, output:
>>>> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such
>>>>file
>>>>or
>>>> directory
>>>> |15314|780:780|new| ( 0) Windows.pm, user_logged_in (line: 8361)
>>>> |15314|780:780|new| (-1) Windows.pm, wait_for_logoff (line: 8440)
>>>> |15314|780:780|new| (-2) Windows.pm, post_load (line: 602)
>>>> |15314|780:780|new| (-3) VMware.pm, load (line: 415)
>>>> |15314|780:780|new| (-4) new.pm, reload_image (line: 618)
>>>> |15314|780:780|new| (-5) new.pm, process (line: 248)
>>>>
>>>> 2011-11-02
>>>> 12:58:27|15314|780:780|new|Windows.pm:wait_for_logoff(8441)|root is
>>>>NOT
>>>> logged in to vmguest-3, returning 1
>>>> 2011-11-02
>>>> 12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing
>>>>SSH
>>>> command on vmguest-3:
>>>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>>>> 'C:/Windows/System32/qwinsta.exe' 2>&1
>>>> 2011-11-02 12:58:31|12831|vcld:main(167)|lastcheckin time updated for
>>>> management node 1: 2011-11-02 12:58:31
>>>> 2011-11-02
>>>>
>>>>12:58:31|15410|778:778|reserved|DataStructure.pm:get_reservation_remote
>>>>_i
>>>>p(
>>>> 1093)|reservation remote IP is not defined
>>>> 2011-11-02
>>>>
>>>>12:58:32|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_comma
>>>>nd
>>>> output:
>>>> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such
>>>>file
>>>>or
>>>> directory
>>>> 2011-11-02
>>>>12:58:32|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
>>>> command executed on vmguest-3, command:
>>>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>>>> 'C:/Windows/System32/qwinsta.exe' 2>&1
>>>> |15314|780:780|new| returning (127, "bash:
>>>>C:/Windows/System32/qwin...")
>>>>
>>>> |15314|780:780|new| ---- WARNING ----
>>>> |15314|780:780|new| 2011-11-02
>>>> 12:58:32|15314|780:780|new|Windows.pm:logoff_users(1437)|failed to run
>>>> qwinsta.exe on vmguest-3, exit status: 127, output:
>>>> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such
>>>>file
>>>>or
>>>> directory
>>>> |15314|780:780|new| ( 0) Windows.pm, logoff_users (line: 1437)
>>>> |15314|780:780|new| (-1) Windows.pm, post_load (line: 615)
>>>> |15314|780:780|new| (-2) VMware.pm, load (line: 415)
>>>> |15314|780:780|new| (-3) new.pm, reload_image (line: 618)
>>>> |15314|780:780|new| (-4) new.pm, process (line: 248)
>>>> |15314|780:780|new| (-5) vcld, make_new_child (line: 568)
>>>>
>>>>
>>>> |15314|780:780|new| ---- WARNING ----
>>>> |15314|780:780|new| 2011-11-02
>>>> 12:58:32|15314|780:780|new|Windows.pm:post_load(615)|failed to log off
>>>>all
>>>> currently logged in users
>>>> |15314|780:780|new| ( 0) Windows.pm, post_load (line: 615)
>>>> |15314|780:780|new| (-1) VMware.pm, load (line: 415)
>>>> |15314|780:780|new| (-2) new.pm, reload_image (line: 618)
>>>> |15314|780:780|new| (-3) new.pm, process (line: 248)
>>>> |15314|780:780|new| (-4) vcld, make_new_child (line: 568)
>>>> |15314|780:780|new| (-5) vcld, main (line: 346)
>>>>
>>>> 2011-11-02
>>>> 12:58:33|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 6:
>>>> waiting for vmguest-1 to respond to SSH
>>>> 2011-11-02
>>>> 12:58:34|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is
>>>>NOT
>>>> responding to SSH, ports 22 or 24 are both closed
>>>> 2011-11-02
>>>> 12:58:34|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 6:
>>>> code returned false, seconds elapsed/remaining: 43/857, sleeping for 8
>>>> seconds
>>>> 2011-11-02 12:58:36|12831|vcld:main(167)|lastcheckin time updated for
>>>> management node 1: 2011-11-02 12:58:36
>>>> 2011-11-02
>>>>
>>>>12:58:36|15410|778:778|reserved|DataStructure.pm:get_reservation_remote
>>>>_i
>>>>p(
>>>> 1093)|reservation remote IP is not defined
>>>>
>>>> |15314|780:780|new| ---- WARNING ----
>>>> |15314|780:780|new| 2011-11-02
>>>> 12:58:37|15314|780:780|new|Windows.pm:set_file_owner(1398)|error
>>>>occurred
>>>> setting root as the owner of /home/root, error output:
>>>> |15314|780:780|new| bash: /usr/bin/chown.exe: No such file or
>>>>directory
>>>> |15314|780:780|new| ( 0) Windows.pm, set_file_owner (line: 1398)
>>>> |15314|780:780|new| (-1) Windows.pm, post_load (line: 625)
>>>> |15314|780:780|new| (-2) VMware.pm, load (line: 415)
>>>> |15314|780:780|new| (-3) new.pm, reload_image (line: 618)
>>>> |15314|780:780|new| (-4) new.pm, process (line: 248)
>>>> |15314|780:780|new| (-5) vcld, make_new_child (line: 568)
>>>>
>>>>
>>>> |15314|780:780|new| ---- WARNING ----
>>>> |15314|780:780|new| 2011-11-02
>>>> 12:58:37|15314|780:780|new|Windows.pm:post_load(625)|unable to set
>>>>root
>>>>as
>>>> the owner of /home/root
>>>> |15314|780:780|new| ( 0) Windows.pm, post_load (line: 625)
>>>> |15314|780:780|new| (-1) VMware.pm, load (line: 415)
>>>> |15314|780:780|new| (-2) new.pm, reload_image (line: 618)
>>>> |15314|780:780|new| (-3) new.pm, process (line: 248)
>>>> |15314|780:780|new| (-4) vcld, make_new_child (line: 568)
>>>> |15314|780:780|new| (-5) vcld, main (line: 346)
>>>>
>>>> 2011-11-02
>>>> 12:58:37|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing
>>>>SSH
>>>> command on vmguest-3:
>>>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>>>> 'C:/Windows/System32/sc.exe config sshd start= auto' 2>&1
>>>> 2011-11-02 12:58:41|12831|vcld:main(167)|lastcheckin time updated for
>>>> management node 1: 2011-11-02 12:58:41
>>>> 2011-11-02
>>>>
>>>>12:58:41|15410|778:778|reserved|DataStructure.pm:get_reservation_remote
>>>>_i
>>>>p(
>>>> 1093)|reservation remote IP is not defined
>>>> 2011-11-02
>>>> 12:58:42|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 7:
>>>> waiting for vmguest-1 to respond to SSH
>>>> 2011-11-02
>>>> 12:58:42|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is
>>>>NOT
>>>> responding to SSH, ports 22 or 24 are both closed
>>>> 2011-11-02
>>>> 12:58:42|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 7:
>>>> code returned false, seconds elapsed/remaining: 51/849, sleeping for 8
>>>> seconds
>>>> 2011-11-02
>>>>
>>>>12:58:43|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_comma
>>>>nd
>>>> output:
>>>> |15314|780:780|new| bash: C:/Windows/System32/sc.exe: No such file or
>>>> directory
>>>> 2011-11-02
>>>>12:58:43|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
>>>> command executed on vmguest-3, command:
>>>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>>>> 'C:/Windows/System32/sc.exe config sshd start= auto' 2>&1
>>>> |15314|780:780|new| returning (127, "bash:
>>>>C:/Windows/System32/sc.e...")
>>>>
>>>> |15314|780:780|new| ---- WARNING ----
>>>> |15314|780:780|new| 2011-11-02
>>>>
>>>>12:58:43|15314|780:780|new|Windows.pm:set_service_startup_mode(3644)|fa
>>>>il
>>>>ed
>>>>  to set sshd service startup mode to auto, exit status: 127, output:
>>>> |15314|780:780|new| bash: C:/Windows/System32/sc.exe: No such file or
>>>> directory
>>>> |15314|780:780|new| ( 0) Windows.pm, set_service_startup_mode (line:
>>>>3644)
>>>> |15314|780:780|new| (-1) Windows.pm, post_load (line: 639)
>>>> |15314|780:780|new| (-2) VMware.pm, load (line: 415)
>>>> |15314|780:780|new| (-3) new.pm, reload_image (line: 618)
>>>> |15314|780:780|new| (-4) new.pm, process (line: 248)
>>>> |15314|780:780|new| (-5) vcld, make_new_child (line: 568)
>>>>
>>>>
>>>> |15314|780:780|new| ---- WARNING ----
>>>> |15314|780:780|new| 2011-11-02
>>>> 12:58:43|15314|780:780|new|Windows.pm:post_load(640)|unable to set
>>>>sshd
>>>> service startup mode to auto
>>>> |15314|780:780|new| ( 0) Windows.pm, post_load (line: 640)
>>>> |15314|780:780|new| (-1) VMware.pm, load (line: 415)
>>>> |15314|780:780|new| (-2) new.pm, reload_image (line: 618)
>>>> |15314|780:780|new| (-3) new.pm, process (line: 248)
>>>> |15314|780:780|new| (-4) vcld, make_new_child (line: 568)
>>>> |15314|780:780|new| (-5) vcld, main (line: 346)
>>>>
>>>>
>>>> |15314|780:780|new| ---- WARNING ----
>>>> |15314|780:780|new| 2011-11-02
>>>> 12:58:43|15314|780:780|new|VMware.pm:load(419)|failed to perform OS
>>>> post-load tasks on VM vmguest-3 on VM host: CSB303
>>>> |15314|780:780|new| ( 0) VMware.pm, load (line: 419)
>>>> |15314|780:780|new| (-1) new.pm, reload_image (line: 618)
>>>> |15314|780:780|new| (-2) new.pm, process (line: 248)
>>>> |15314|780:780|new| (-3) vcld, make_new_child (line: 568)
>>>> |15314|780:780|new| (-4) vcld, main (line: 346)
>>>>
>>>>
>>>> |15314|780:780|new| ---- WARNING ----
>>>> |15314|780:780|new| 2011-11-02
>>>>
>>>>12:58:43|15314|780:780|new|new.pm:reload_image(623)|vmwarewinxp-Windows
>>>>XP
>>>>wi
>>>> thVisualStudio32-v0 failed to load on vmguest-3, returning
>>>> |15314|780:780|new| ( 0) new.pm, reload_image (line: 623)
>>>> |15314|780:780|new| (-1) new.pm, process (line: 248)
>>>> |15314|780:780|new| (-2) vcld, make_new_child (line: 568)
>>>> |15314|780:780|new| (-3) vcld, main (line: 346)
>>>>
>>>> 2011-11-02
>>>> 12:58:43|15314|780:780|new|utils.pm:insertloadlog(3875)|inserted
>>>> computer=4, loadimagefailed,
>>>>vmwarewinxp-WindowsXPwithVisualStudio32-v0
>>>> failed to load on vmguest-3
>>>>
>>>> |15314|780:780|new| ---- WARNING ----
>>>> |15314|780:780|new| 2011-11-02
>>>> 12:58:43|15314|780:780|new|new.pm:process(295)|failed to load
>>>>vmguest-3
>>>> with vmwarewinxp-WindowsXPwithVisualStudio32-v0
>>>> |15314|780:780|new| ( 0) new.pm, process (line: 295)
>>>> |15314|780:780|new| (-1) vcld, make_new_child (line: 568)
>>>> |15314|780:780|new| (-2) vcld, main (line: 346)
>>>>
>>>> 2011-11-02
>>>>
>>>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_state_name(230
>>>>5)
>>>>|a
>>>> ttempting to retrieve current state of computer vmguest-3 from the
>>>>database
>>>> 2011-11-02
>>>>
>>>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_state_name(233
>>>>6)
>>>>|r
>>>> etrieved current state of computer vmguest-3 from the database:
>>>>reloading
>>>> 2011-11-02
>>>> 12:58:43|15314|780:780|new|DataStructure.pm:_automethod(834)|data
>>>> structure updated:
>>>> $self->request_data->{reservation}{780}{computer}{state}{name}
>>>> |15314|780:780|new| computer_state_name = reloading
>>>> 2011-11-02
>>>>
>>>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_add
>>>>re
>>>>ss
>>>> (1581)|attempting to retrieve private IP address for computer:
>>>>vmguest-3
>>>> 2011-11-02
>>>>
>>>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_add
>>>>re
>>>>ss
>>>> (1585)|retrieved contents of /etc/hosts on this management node,
>>>>contains
>>>> 44 lines
>>>> 2011-11-02
>>>>
>>>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_add
>>>>re
>>>>ss
>>>> (1645)|returning IP address from /etc/hosts file: 10.10.10.4
>>>> 2011-11-02
>>>> 12:58:43|15314|780:780|new|utils.pm:is_inblockrequest(6163)|zero rows
>>>>were
>>>> returned from database select
>>>> 2011-11-02
>>>>
>>>>12:58:43|15314|780:780|new|DataStructure.pm:get_image_affiliation_name(
>>>>20
>>>>35
>>>> )|image owner id: 1
>>>> 2011-11-02
>>>>12:58:43|15314|780:780|new|utils.pm:getnewdbh(2709)|database
>>>> requested (information_schema) does not match handle stored in
>>>>$ENV{dbh}
>>>> (vcl:localhost)
>>>> 2011-11-02
>>>>12:58:43|15314|780:780|new|utils.pm:getnewdbh(2760)|database
>>>> handle stored in $ENV{dbh}
>>>> 2011-11-02
>>>>
>>>>12:58:43|15314|780:780|new|DataStructure.pm:retrieve_user_data(1352)|at
>>>>te
>>>>mp
>>>> ting to retrieve and store data for user: user.id = '1'
>>>> 2011-11-02
>>>>12:58:43|15314|780:780|new|utils.pm:getnewdbh(2709)|database
>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>> (information_schema:localhost)
>>>> 2011-11-02
>>>>12:58:43|15314|780:780|new|utils.pm:getnewdbh(2760)|database
>>>> handle stored in $ENV{dbh}
>>>> 2011-11-02
>>>>
>>>>12:58:43|15314|780:780|new|DataStructure.pm:retrieve_user_data(1415)|da
>>>>ta
>>>> has been retrieved for user: admin (id: 1)
>>>> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:mail(1268)|SUCCESS --
>>>> Sending mail To: 0, PROBLEM --
>>>>
>>>>780:780|new|State.pm|vmguest-3>CSB303|vmwarewinxp-WindowsXPwithVisualSt
>>>>ud
>>>>io
>>>> 32-v0|admin
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> |15314|780:780|new| ---- CRITICAL ----
>>>> |15314|780:780|new| 2011-11-02
>>>>
>>>>12:58:43|15314|780:780|new|State.pm:reservation_failed(213)|reservation
>>>> failed on vmguest-3: process failed after trying to load or make
>>>>available
>>>> |15314|780:780|new| ( 0) State.pm, reservation_failed (line: 213)
>>>> |15314|780:780|new| (-1) new.pm, process (line: 298)
>>>> |15314|780:780|new| (-2) vcld, make_new_child (line: 568)
>>>> |15314|780:780|new| (-3) vcld, main (line: 346)
>>>>
>>>>
>>>
>>>
>>>
>>>--
>>>Aaron Peeler
>>>Program Manager
>>>Virtual Computing Lab
>>>NC State University
>>>
>>>All electronic mail messages in connection with State business which
>>>are sent to or received by this account are subject to the NC Public
>>>Records Law and may be disclosed to third parties.
>>
>>
>
>
>
>--
>Aaron Peeler
>Program Manager
>Virtual Computing Lab
>NC State University
>
>All electronic mail messages in connection with State business which
>are sent to or received by this account are subject to the NC Public
>Records Law and may be disclosed to third parties.


Re: another problem for image reservation

Posted by Aaron Peeler <aa...@ncsu.edu>.
Can you send log output of a reservation flow working with the old
module and a 2nd reservation flow of it not working using the
recommended vmware module?

I'd have to trace through it to see what is going on. We want to move
away from the older GSX module.

It's also strange that is works for one and not the other. Both
modules using ssh <nodename> to get on the node.

Thanks,
Aaron


On Wed, Nov 2, 2011 at 3:10 PM, Huang,Lei <lh...@pvamu.edu> wrote:
> Aaron,
>
>  Thanks. The question is why the old module using Vmware Server GSX works.
> If I switch back to Vmware server GSX, windows image works fine.In this
> case, ssh can log into the image. Do I need to switch back?
>
> Thanks,
> Lei
>
> On 11/2/11 1:37 PM, "Aaron Peeler" <fa...@ncsu.edu> wrote:
>
>>Hi Lei,
>>
>>The issue in the log output is related to ssh is not responding.
>>
>>Double check that you can log into vmguest-1 or vmguest-3 via ssh (you
>>have a couple of different reservations in your log output).
>>
>>Things to check are to;
>>make sure your vmguest-X machines are getting the correct dhcp IP address.
>>make sure cygwin sshd service is started.
>>
>>Aaron
>>
>>
>>
>>On Wed, Nov 2, 2011 at 2:22 PM, Huang,Lei <lh...@pvamu.edu> wrote:
>>> Hi All,
>>>
>>>  I have encountered another problem after upgraded to 2.2.1. Per Aaron's
>>> suggestion, I changed my Vmguests provisioning engine to Vmware from
>>> Vmware Server GSX. However, my Windows XP image failed to reserve after
>>> the change. From the log, I found that it looks for
>>> 'C:/Windows/System32/qwinsta.exe' and 'C:/Windows/System32/sc.exe config
>>> sshd start= auto'. However, both them are not found on my XP image. Do I
>>> need to update my XP image? The image works fine on Vmware Server GSX
>>> provision engine. The following is the log.
>>>
>>> Thanks,
>>> Lei
>>>
>>> ======================
>>>
>>> |15314|780:780|new| ---- WARNING ----
>>> |15314|780:780|new| 2011-11-02
>>> 12:58:21|15314|780:780|new|Windows.pm:is_64_bit(8095)|unable to find
>>> registry value line in reg.exe output:
>>> |15314|780:780|new| bash: reg.exe: command not found
>>> |15314|780:780|new| ( 0) Windows.pm, is_64_bit (line: 8095)
>>> |15314|780:780|new| (-1) Windows.pm, get_system32_path (line: 8146)
>>> |15314|780:780|new| (-2) Windows.pm, user_logged_in (line: 8342)
>>> |15314|780:780|new| (-3) Windows.pm, wait_for_logoff (line: 8440)
>>> |15314|780:780|new| (-4) Windows.pm, post_load (line: 602)
>>> |15314|780:780|new| (-5) VMware.pm, load (line: 415)
>>>
>>> 2011-11-02
>>> 12:58:21|15314|780:780|new|Windows.pm:get_system32_path(8152)|32-bit
>>> Windows OS installed on vmguest-3, using C:/Windows/System32
>>> 2011-11-02
>>> 12:58:21|15314|780:780|new|Windows.pm:user_logged_in(8356)|checking if
>>> root is logged in to vmguest-3
>>> 2011-11-02
>>> 12:58:21|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing SSH
>>> command on vmguest-3:
>>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>>> 'C:/Windows/System32/qwinsta.exe' 2>&1
>>> 2011-11-02
>>> 12:58:25|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 5:
>>> waiting for vmguest-1 to respond to SSH
>>> 2011-11-02
>>> 12:58:25|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is NOT
>>> responding to SSH, ports 22 or 24 are both closed
>>> 2011-11-02
>>> 12:58:25|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 5:
>>> code returned false, seconds elapsed/remaining: 34/866, sleeping for 8
>>> seconds
>>> 2011-11-02 12:58:26|12831|vcld:main(167)|lastcheckin time updated for
>>> management node 1: 2011-11-02 12:58:26
>>> 2011-11-02
>>>
>>>12:58:26|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_i
>>>p(
>>> 1093)|reservation remote IP is not defined
>>> 2011-11-02
>>>
>>>12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_command
>>> output:
>>> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file
>>>or
>>> directory
>>> 2011-11-02 12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
>>> command executed on vmguest-3, command:
>>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>>> 'C:/Windows/System32/qwinsta.exe' 2>&1
>>> |15314|780:780|new| returning (127, "bash: C:/Windows/System32/qwin...")
>>>
>>> |15314|780:780|new| ---- WARNING ----
>>> |15314|780:780|new| 2011-11-02
>>> 12:58:27|15314|780:780|new|Windows.pm:user_logged_in(8361)|failed to run
>>> qwinsta.exe on vmguest-3, exit status: 127, output:
>>> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file
>>>or
>>> directory
>>> |15314|780:780|new| ( 0) Windows.pm, user_logged_in (line: 8361)
>>> |15314|780:780|new| (-1) Windows.pm, wait_for_logoff (line: 8440)
>>> |15314|780:780|new| (-2) Windows.pm, post_load (line: 602)
>>> |15314|780:780|new| (-3) VMware.pm, load (line: 415)
>>> |15314|780:780|new| (-4) new.pm, reload_image (line: 618)
>>> |15314|780:780|new| (-5) new.pm, process (line: 248)
>>>
>>> 2011-11-02
>>> 12:58:27|15314|780:780|new|Windows.pm:wait_for_logoff(8441)|root is NOT
>>> logged in to vmguest-3, returning 1
>>> 2011-11-02
>>> 12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing SSH
>>> command on vmguest-3:
>>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>>> 'C:/Windows/System32/qwinsta.exe' 2>&1
>>> 2011-11-02 12:58:31|12831|vcld:main(167)|lastcheckin time updated for
>>> management node 1: 2011-11-02 12:58:31
>>> 2011-11-02
>>>
>>>12:58:31|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_i
>>>p(
>>> 1093)|reservation remote IP is not defined
>>> 2011-11-02
>>>
>>>12:58:32|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_command
>>> output:
>>> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file
>>>or
>>> directory
>>> 2011-11-02 12:58:32|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
>>> command executed on vmguest-3, command:
>>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>>> 'C:/Windows/System32/qwinsta.exe' 2>&1
>>> |15314|780:780|new| returning (127, "bash: C:/Windows/System32/qwin...")
>>>
>>> |15314|780:780|new| ---- WARNING ----
>>> |15314|780:780|new| 2011-11-02
>>> 12:58:32|15314|780:780|new|Windows.pm:logoff_users(1437)|failed to run
>>> qwinsta.exe on vmguest-3, exit status: 127, output:
>>> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file
>>>or
>>> directory
>>> |15314|780:780|new| ( 0) Windows.pm, logoff_users (line: 1437)
>>> |15314|780:780|new| (-1) Windows.pm, post_load (line: 615)
>>> |15314|780:780|new| (-2) VMware.pm, load (line: 415)
>>> |15314|780:780|new| (-3) new.pm, reload_image (line: 618)
>>> |15314|780:780|new| (-4) new.pm, process (line: 248)
>>> |15314|780:780|new| (-5) vcld, make_new_child (line: 568)
>>>
>>>
>>> |15314|780:780|new| ---- WARNING ----
>>> |15314|780:780|new| 2011-11-02
>>> 12:58:32|15314|780:780|new|Windows.pm:post_load(615)|failed to log off
>>>all
>>> currently logged in users
>>> |15314|780:780|new| ( 0) Windows.pm, post_load (line: 615)
>>> |15314|780:780|new| (-1) VMware.pm, load (line: 415)
>>> |15314|780:780|new| (-2) new.pm, reload_image (line: 618)
>>> |15314|780:780|new| (-3) new.pm, process (line: 248)
>>> |15314|780:780|new| (-4) vcld, make_new_child (line: 568)
>>> |15314|780:780|new| (-5) vcld, main (line: 346)
>>>
>>> 2011-11-02
>>> 12:58:33|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 6:
>>> waiting for vmguest-1 to respond to SSH
>>> 2011-11-02
>>> 12:58:34|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is NOT
>>> responding to SSH, ports 22 or 24 are both closed
>>> 2011-11-02
>>> 12:58:34|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 6:
>>> code returned false, seconds elapsed/remaining: 43/857, sleeping for 8
>>> seconds
>>> 2011-11-02 12:58:36|12831|vcld:main(167)|lastcheckin time updated for
>>> management node 1: 2011-11-02 12:58:36
>>> 2011-11-02
>>>
>>>12:58:36|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_i
>>>p(
>>> 1093)|reservation remote IP is not defined
>>>
>>> |15314|780:780|new| ---- WARNING ----
>>> |15314|780:780|new| 2011-11-02
>>> 12:58:37|15314|780:780|new|Windows.pm:set_file_owner(1398)|error
>>>occurred
>>> setting root as the owner of /home/root, error output:
>>> |15314|780:780|new| bash: /usr/bin/chown.exe: No such file or directory
>>> |15314|780:780|new| ( 0) Windows.pm, set_file_owner (line: 1398)
>>> |15314|780:780|new| (-1) Windows.pm, post_load (line: 625)
>>> |15314|780:780|new| (-2) VMware.pm, load (line: 415)
>>> |15314|780:780|new| (-3) new.pm, reload_image (line: 618)
>>> |15314|780:780|new| (-4) new.pm, process (line: 248)
>>> |15314|780:780|new| (-5) vcld, make_new_child (line: 568)
>>>
>>>
>>> |15314|780:780|new| ---- WARNING ----
>>> |15314|780:780|new| 2011-11-02
>>> 12:58:37|15314|780:780|new|Windows.pm:post_load(625)|unable to set root
>>>as
>>> the owner of /home/root
>>> |15314|780:780|new| ( 0) Windows.pm, post_load (line: 625)
>>> |15314|780:780|new| (-1) VMware.pm, load (line: 415)
>>> |15314|780:780|new| (-2) new.pm, reload_image (line: 618)
>>> |15314|780:780|new| (-3) new.pm, process (line: 248)
>>> |15314|780:780|new| (-4) vcld, make_new_child (line: 568)
>>> |15314|780:780|new| (-5) vcld, main (line: 346)
>>>
>>> 2011-11-02
>>> 12:58:37|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing SSH
>>> command on vmguest-3:
>>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>>> 'C:/Windows/System32/sc.exe config sshd start= auto' 2>&1
>>> 2011-11-02 12:58:41|12831|vcld:main(167)|lastcheckin time updated for
>>> management node 1: 2011-11-02 12:58:41
>>> 2011-11-02
>>>
>>>12:58:41|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_i
>>>p(
>>> 1093)|reservation remote IP is not defined
>>> 2011-11-02
>>> 12:58:42|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 7:
>>> waiting for vmguest-1 to respond to SSH
>>> 2011-11-02
>>> 12:58:42|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is NOT
>>> responding to SSH, ports 22 or 24 are both closed
>>> 2011-11-02
>>> 12:58:42|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 7:
>>> code returned false, seconds elapsed/remaining: 51/849, sleeping for 8
>>> seconds
>>> 2011-11-02
>>>
>>>12:58:43|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_command
>>> output:
>>> |15314|780:780|new| bash: C:/Windows/System32/sc.exe: No such file or
>>> directory
>>> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
>>> command executed on vmguest-3, command:
>>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>>> 'C:/Windows/System32/sc.exe config sshd start= auto' 2>&1
>>> |15314|780:780|new| returning (127, "bash: C:/Windows/System32/sc.e...")
>>>
>>> |15314|780:780|new| ---- WARNING ----
>>> |15314|780:780|new| 2011-11-02
>>>
>>>12:58:43|15314|780:780|new|Windows.pm:set_service_startup_mode(3644)|fail
>>>ed
>>>  to set sshd service startup mode to auto, exit status: 127, output:
>>> |15314|780:780|new| bash: C:/Windows/System32/sc.exe: No such file or
>>> directory
>>> |15314|780:780|new| ( 0) Windows.pm, set_service_startup_mode (line:
>>>3644)
>>> |15314|780:780|new| (-1) Windows.pm, post_load (line: 639)
>>> |15314|780:780|new| (-2) VMware.pm, load (line: 415)
>>> |15314|780:780|new| (-3) new.pm, reload_image (line: 618)
>>> |15314|780:780|new| (-4) new.pm, process (line: 248)
>>> |15314|780:780|new| (-5) vcld, make_new_child (line: 568)
>>>
>>>
>>> |15314|780:780|new| ---- WARNING ----
>>> |15314|780:780|new| 2011-11-02
>>> 12:58:43|15314|780:780|new|Windows.pm:post_load(640)|unable to set sshd
>>> service startup mode to auto
>>> |15314|780:780|new| ( 0) Windows.pm, post_load (line: 640)
>>> |15314|780:780|new| (-1) VMware.pm, load (line: 415)
>>> |15314|780:780|new| (-2) new.pm, reload_image (line: 618)
>>> |15314|780:780|new| (-3) new.pm, process (line: 248)
>>> |15314|780:780|new| (-4) vcld, make_new_child (line: 568)
>>> |15314|780:780|new| (-5) vcld, main (line: 346)
>>>
>>>
>>> |15314|780:780|new| ---- WARNING ----
>>> |15314|780:780|new| 2011-11-02
>>> 12:58:43|15314|780:780|new|VMware.pm:load(419)|failed to perform OS
>>> post-load tasks on VM vmguest-3 on VM host: CSB303
>>> |15314|780:780|new| ( 0) VMware.pm, load (line: 419)
>>> |15314|780:780|new| (-1) new.pm, reload_image (line: 618)
>>> |15314|780:780|new| (-2) new.pm, process (line: 248)
>>> |15314|780:780|new| (-3) vcld, make_new_child (line: 568)
>>> |15314|780:780|new| (-4) vcld, main (line: 346)
>>>
>>>
>>> |15314|780:780|new| ---- WARNING ----
>>> |15314|780:780|new| 2011-11-02
>>>
>>>12:58:43|15314|780:780|new|new.pm:reload_image(623)|vmwarewinxp-WindowsXP
>>>wi
>>> thVisualStudio32-v0 failed to load on vmguest-3, returning
>>> |15314|780:780|new| ( 0) new.pm, reload_image (line: 623)
>>> |15314|780:780|new| (-1) new.pm, process (line: 248)
>>> |15314|780:780|new| (-2) vcld, make_new_child (line: 568)
>>> |15314|780:780|new| (-3) vcld, main (line: 346)
>>>
>>> 2011-11-02
>>> 12:58:43|15314|780:780|new|utils.pm:insertloadlog(3875)|inserted
>>> computer=4, loadimagefailed, vmwarewinxp-WindowsXPwithVisualStudio32-v0
>>> failed to load on vmguest-3
>>>
>>> |15314|780:780|new| ---- WARNING ----
>>> |15314|780:780|new| 2011-11-02
>>> 12:58:43|15314|780:780|new|new.pm:process(295)|failed to load vmguest-3
>>> with vmwarewinxp-WindowsXPwithVisualStudio32-v0
>>> |15314|780:780|new| ( 0) new.pm, process (line: 295)
>>> |15314|780:780|new| (-1) vcld, make_new_child (line: 568)
>>> |15314|780:780|new| (-2) vcld, main (line: 346)
>>>
>>> 2011-11-02
>>>
>>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_state_name(2305)
>>>|a
>>> ttempting to retrieve current state of computer vmguest-3 from the
>>>database
>>> 2011-11-02
>>>
>>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_state_name(2336)
>>>|r
>>> etrieved current state of computer vmguest-3 from the database:
>>>reloading
>>> 2011-11-02
>>> 12:58:43|15314|780:780|new|DataStructure.pm:_automethod(834)|data
>>> structure updated:
>>> $self->request_data->{reservation}{780}{computer}{state}{name}
>>> |15314|780:780|new| computer_state_name = reloading
>>> 2011-11-02
>>>
>>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_addre
>>>ss
>>> (1581)|attempting to retrieve private IP address for computer: vmguest-3
>>> 2011-11-02
>>>
>>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_addre
>>>ss
>>> (1585)|retrieved contents of /etc/hosts on this management node,
>>>contains
>>> 44 lines
>>> 2011-11-02
>>>
>>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_addre
>>>ss
>>> (1645)|returning IP address from /etc/hosts file: 10.10.10.4
>>> 2011-11-02
>>> 12:58:43|15314|780:780|new|utils.pm:is_inblockrequest(6163)|zero rows
>>>were
>>> returned from database select
>>> 2011-11-02
>>>
>>>12:58:43|15314|780:780|new|DataStructure.pm:get_image_affiliation_name(20
>>>35
>>> )|image owner id: 1
>>> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2709)|database
>>> requested (information_schema) does not match handle stored in $ENV{dbh}
>>> (vcl:localhost)
>>> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2760)|database
>>> handle stored in $ENV{dbh}
>>> 2011-11-02
>>>
>>>12:58:43|15314|780:780|new|DataStructure.pm:retrieve_user_data(1352)|atte
>>>mp
>>> ting to retrieve and store data for user: user.id = '1'
>>> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2709)|database
>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>> (information_schema:localhost)
>>> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2760)|database
>>> handle stored in $ENV{dbh}
>>> 2011-11-02
>>>
>>>12:58:43|15314|780:780|new|DataStructure.pm:retrieve_user_data(1415)|data
>>> has been retrieved for user: admin (id: 1)
>>> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:mail(1268)|SUCCESS --
>>> Sending mail To: 0, PROBLEM --
>>>
>>>780:780|new|State.pm|vmguest-3>CSB303|vmwarewinxp-WindowsXPwithVisualStud
>>>io
>>> 32-v0|admin
>>>
>>>
>>>
>>>
>>>
>>> |15314|780:780|new| ---- CRITICAL ----
>>> |15314|780:780|new| 2011-11-02
>>> 12:58:43|15314|780:780|new|State.pm:reservation_failed(213)|reservation
>>> failed on vmguest-3: process failed after trying to load or make
>>>available
>>> |15314|780:780|new| ( 0) State.pm, reservation_failed (line: 213)
>>> |15314|780:780|new| (-1) new.pm, process (line: 298)
>>> |15314|780:780|new| (-2) vcld, make_new_child (line: 568)
>>> |15314|780:780|new| (-3) vcld, main (line: 346)
>>>
>>>
>>
>>
>>
>>--
>>Aaron Peeler
>>Program Manager
>>Virtual Computing Lab
>>NC State University
>>
>>All electronic mail messages in connection with State business which
>>are sent to or received by this account are subject to the NC Public
>>Records Law and may be disclosed to third parties.
>
>



-- 
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.

Re: another problem for image reservation

Posted by "Huang,Lei" <lh...@PVAMU.EDU>.
Aaron,

 Thanks. The question is why the old module using Vmware Server GSX works.
If I switch back to Vmware server GSX, windows image works fine.In this
case, ssh can log into the image. Do I need to switch back?

Thanks,
Lei

On 11/2/11 1:37 PM, "Aaron Peeler" <fa...@ncsu.edu> wrote:

>Hi Lei,
>
>The issue in the log output is related to ssh is not responding.
>
>Double check that you can log into vmguest-1 or vmguest-3 via ssh (you
>have a couple of different reservations in your log output).
>
>Things to check are to;
>make sure your vmguest-X machines are getting the correct dhcp IP address.
>make sure cygwin sshd service is started.
>
>Aaron
>
>
>
>On Wed, Nov 2, 2011 at 2:22 PM, Huang,Lei <lh...@pvamu.edu> wrote:
>> Hi All,
>>
>>  I have encountered another problem after upgraded to 2.2.1. Per Aaron's
>> suggestion, I changed my Vmguests provisioning engine to Vmware from
>> Vmware Server GSX. However, my Windows XP image failed to reserve after
>> the change. From the log, I found that it looks for
>> 'C:/Windows/System32/qwinsta.exe' and 'C:/Windows/System32/sc.exe config
>> sshd start= auto'. However, both them are not found on my XP image. Do I
>> need to update my XP image? The image works fine on Vmware Server GSX
>> provision engine. The following is the log.
>>
>> Thanks,
>> Lei
>>
>> ======================
>>
>> |15314|780:780|new| ---- WARNING ----
>> |15314|780:780|new| 2011-11-02
>> 12:58:21|15314|780:780|new|Windows.pm:is_64_bit(8095)|unable to find
>> registry value line in reg.exe output:
>> |15314|780:780|new| bash: reg.exe: command not found
>> |15314|780:780|new| ( 0) Windows.pm, is_64_bit (line: 8095)
>> |15314|780:780|new| (-1) Windows.pm, get_system32_path (line: 8146)
>> |15314|780:780|new| (-2) Windows.pm, user_logged_in (line: 8342)
>> |15314|780:780|new| (-3) Windows.pm, wait_for_logoff (line: 8440)
>> |15314|780:780|new| (-4) Windows.pm, post_load (line: 602)
>> |15314|780:780|new| (-5) VMware.pm, load (line: 415)
>>
>> 2011-11-02
>> 12:58:21|15314|780:780|new|Windows.pm:get_system32_path(8152)|32-bit
>> Windows OS installed on vmguest-3, using C:/Windows/System32
>> 2011-11-02
>> 12:58:21|15314|780:780|new|Windows.pm:user_logged_in(8356)|checking if
>> root is logged in to vmguest-3
>> 2011-11-02
>> 12:58:21|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing SSH
>> command on vmguest-3:
>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>> 'C:/Windows/System32/qwinsta.exe' 2>&1
>> 2011-11-02
>> 12:58:25|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 5:
>> waiting for vmguest-1 to respond to SSH
>> 2011-11-02
>> 12:58:25|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is NOT
>> responding to SSH, ports 22 or 24 are both closed
>> 2011-11-02
>> 12:58:25|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 5:
>> code returned false, seconds elapsed/remaining: 34/866, sleeping for 8
>> seconds
>> 2011-11-02 12:58:26|12831|vcld:main(167)|lastcheckin time updated for
>> management node 1: 2011-11-02 12:58:26
>> 2011-11-02
>>
>>12:58:26|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_i
>>p(
>> 1093)|reservation remote IP is not defined
>> 2011-11-02
>>
>>12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_command
>> output:
>> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file
>>or
>> directory
>> 2011-11-02 12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
>> command executed on vmguest-3, command:
>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>> 'C:/Windows/System32/qwinsta.exe' 2>&1
>> |15314|780:780|new| returning (127, "bash: C:/Windows/System32/qwin...")
>>
>> |15314|780:780|new| ---- WARNING ----
>> |15314|780:780|new| 2011-11-02
>> 12:58:27|15314|780:780|new|Windows.pm:user_logged_in(8361)|failed to run
>> qwinsta.exe on vmguest-3, exit status: 127, output:
>> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file
>>or
>> directory
>> |15314|780:780|new| ( 0) Windows.pm, user_logged_in (line: 8361)
>> |15314|780:780|new| (-1) Windows.pm, wait_for_logoff (line: 8440)
>> |15314|780:780|new| (-2) Windows.pm, post_load (line: 602)
>> |15314|780:780|new| (-3) VMware.pm, load (line: 415)
>> |15314|780:780|new| (-4) new.pm, reload_image (line: 618)
>> |15314|780:780|new| (-5) new.pm, process (line: 248)
>>
>> 2011-11-02
>> 12:58:27|15314|780:780|new|Windows.pm:wait_for_logoff(8441)|root is NOT
>> logged in to vmguest-3, returning 1
>> 2011-11-02
>> 12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing SSH
>> command on vmguest-3:
>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>> 'C:/Windows/System32/qwinsta.exe' 2>&1
>> 2011-11-02 12:58:31|12831|vcld:main(167)|lastcheckin time updated for
>> management node 1: 2011-11-02 12:58:31
>> 2011-11-02
>>
>>12:58:31|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_i
>>p(
>> 1093)|reservation remote IP is not defined
>> 2011-11-02
>>
>>12:58:32|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_command
>> output:
>> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file
>>or
>> directory
>> 2011-11-02 12:58:32|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
>> command executed on vmguest-3, command:
>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>> 'C:/Windows/System32/qwinsta.exe' 2>&1
>> |15314|780:780|new| returning (127, "bash: C:/Windows/System32/qwin...")
>>
>> |15314|780:780|new| ---- WARNING ----
>> |15314|780:780|new| 2011-11-02
>> 12:58:32|15314|780:780|new|Windows.pm:logoff_users(1437)|failed to run
>> qwinsta.exe on vmguest-3, exit status: 127, output:
>> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file
>>or
>> directory
>> |15314|780:780|new| ( 0) Windows.pm, logoff_users (line: 1437)
>> |15314|780:780|new| (-1) Windows.pm, post_load (line: 615)
>> |15314|780:780|new| (-2) VMware.pm, load (line: 415)
>> |15314|780:780|new| (-3) new.pm, reload_image (line: 618)
>> |15314|780:780|new| (-4) new.pm, process (line: 248)
>> |15314|780:780|new| (-5) vcld, make_new_child (line: 568)
>>
>>
>> |15314|780:780|new| ---- WARNING ----
>> |15314|780:780|new| 2011-11-02
>> 12:58:32|15314|780:780|new|Windows.pm:post_load(615)|failed to log off
>>all
>> currently logged in users
>> |15314|780:780|new| ( 0) Windows.pm, post_load (line: 615)
>> |15314|780:780|new| (-1) VMware.pm, load (line: 415)
>> |15314|780:780|new| (-2) new.pm, reload_image (line: 618)
>> |15314|780:780|new| (-3) new.pm, process (line: 248)
>> |15314|780:780|new| (-4) vcld, make_new_child (line: 568)
>> |15314|780:780|new| (-5) vcld, main (line: 346)
>>
>> 2011-11-02
>> 12:58:33|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 6:
>> waiting for vmguest-1 to respond to SSH
>> 2011-11-02
>> 12:58:34|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is NOT
>> responding to SSH, ports 22 or 24 are both closed
>> 2011-11-02
>> 12:58:34|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 6:
>> code returned false, seconds elapsed/remaining: 43/857, sleeping for 8
>> seconds
>> 2011-11-02 12:58:36|12831|vcld:main(167)|lastcheckin time updated for
>> management node 1: 2011-11-02 12:58:36
>> 2011-11-02
>>
>>12:58:36|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_i
>>p(
>> 1093)|reservation remote IP is not defined
>>
>> |15314|780:780|new| ---- WARNING ----
>> |15314|780:780|new| 2011-11-02
>> 12:58:37|15314|780:780|new|Windows.pm:set_file_owner(1398)|error
>>occurred
>> setting root as the owner of /home/root, error output:
>> |15314|780:780|new| bash: /usr/bin/chown.exe: No such file or directory
>> |15314|780:780|new| ( 0) Windows.pm, set_file_owner (line: 1398)
>> |15314|780:780|new| (-1) Windows.pm, post_load (line: 625)
>> |15314|780:780|new| (-2) VMware.pm, load (line: 415)
>> |15314|780:780|new| (-3) new.pm, reload_image (line: 618)
>> |15314|780:780|new| (-4) new.pm, process (line: 248)
>> |15314|780:780|new| (-5) vcld, make_new_child (line: 568)
>>
>>
>> |15314|780:780|new| ---- WARNING ----
>> |15314|780:780|new| 2011-11-02
>> 12:58:37|15314|780:780|new|Windows.pm:post_load(625)|unable to set root
>>as
>> the owner of /home/root
>> |15314|780:780|new| ( 0) Windows.pm, post_load (line: 625)
>> |15314|780:780|new| (-1) VMware.pm, load (line: 415)
>> |15314|780:780|new| (-2) new.pm, reload_image (line: 618)
>> |15314|780:780|new| (-3) new.pm, process (line: 248)
>> |15314|780:780|new| (-4) vcld, make_new_child (line: 568)
>> |15314|780:780|new| (-5) vcld, main (line: 346)
>>
>> 2011-11-02
>> 12:58:37|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing SSH
>> command on vmguest-3:
>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>> 'C:/Windows/System32/sc.exe config sshd start= auto' 2>&1
>> 2011-11-02 12:58:41|12831|vcld:main(167)|lastcheckin time updated for
>> management node 1: 2011-11-02 12:58:41
>> 2011-11-02
>>
>>12:58:41|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_i
>>p(
>> 1093)|reservation remote IP is not defined
>> 2011-11-02
>> 12:58:42|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 7:
>> waiting for vmguest-1 to respond to SSH
>> 2011-11-02
>> 12:58:42|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is NOT
>> responding to SSH, ports 22 or 24 are both closed
>> 2011-11-02
>> 12:58:42|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 7:
>> code returned false, seconds elapsed/remaining: 51/849, sleeping for 8
>> seconds
>> 2011-11-02
>>
>>12:58:43|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_command
>> output:
>> |15314|780:780|new| bash: C:/Windows/System32/sc.exe: No such file or
>> directory
>> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
>> command executed on vmguest-3, command:
>> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
>> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
>> 'C:/Windows/System32/sc.exe config sshd start= auto' 2>&1
>> |15314|780:780|new| returning (127, "bash: C:/Windows/System32/sc.e...")
>>
>> |15314|780:780|new| ---- WARNING ----
>> |15314|780:780|new| 2011-11-02
>>
>>12:58:43|15314|780:780|new|Windows.pm:set_service_startup_mode(3644)|fail
>>ed
>>  to set sshd service startup mode to auto, exit status: 127, output:
>> |15314|780:780|new| bash: C:/Windows/System32/sc.exe: No such file or
>> directory
>> |15314|780:780|new| ( 0) Windows.pm, set_service_startup_mode (line:
>>3644)
>> |15314|780:780|new| (-1) Windows.pm, post_load (line: 639)
>> |15314|780:780|new| (-2) VMware.pm, load (line: 415)
>> |15314|780:780|new| (-3) new.pm, reload_image (line: 618)
>> |15314|780:780|new| (-4) new.pm, process (line: 248)
>> |15314|780:780|new| (-5) vcld, make_new_child (line: 568)
>>
>>
>> |15314|780:780|new| ---- WARNING ----
>> |15314|780:780|new| 2011-11-02
>> 12:58:43|15314|780:780|new|Windows.pm:post_load(640)|unable to set sshd
>> service startup mode to auto
>> |15314|780:780|new| ( 0) Windows.pm, post_load (line: 640)
>> |15314|780:780|new| (-1) VMware.pm, load (line: 415)
>> |15314|780:780|new| (-2) new.pm, reload_image (line: 618)
>> |15314|780:780|new| (-3) new.pm, process (line: 248)
>> |15314|780:780|new| (-4) vcld, make_new_child (line: 568)
>> |15314|780:780|new| (-5) vcld, main (line: 346)
>>
>>
>> |15314|780:780|new| ---- WARNING ----
>> |15314|780:780|new| 2011-11-02
>> 12:58:43|15314|780:780|new|VMware.pm:load(419)|failed to perform OS
>> post-load tasks on VM vmguest-3 on VM host: CSB303
>> |15314|780:780|new| ( 0) VMware.pm, load (line: 419)
>> |15314|780:780|new| (-1) new.pm, reload_image (line: 618)
>> |15314|780:780|new| (-2) new.pm, process (line: 248)
>> |15314|780:780|new| (-3) vcld, make_new_child (line: 568)
>> |15314|780:780|new| (-4) vcld, main (line: 346)
>>
>>
>> |15314|780:780|new| ---- WARNING ----
>> |15314|780:780|new| 2011-11-02
>>
>>12:58:43|15314|780:780|new|new.pm:reload_image(623)|vmwarewinxp-WindowsXP
>>wi
>> thVisualStudio32-v0 failed to load on vmguest-3, returning
>> |15314|780:780|new| ( 0) new.pm, reload_image (line: 623)
>> |15314|780:780|new| (-1) new.pm, process (line: 248)
>> |15314|780:780|new| (-2) vcld, make_new_child (line: 568)
>> |15314|780:780|new| (-3) vcld, main (line: 346)
>>
>> 2011-11-02
>> 12:58:43|15314|780:780|new|utils.pm:insertloadlog(3875)|inserted
>> computer=4, loadimagefailed, vmwarewinxp-WindowsXPwithVisualStudio32-v0
>> failed to load on vmguest-3
>>
>> |15314|780:780|new| ---- WARNING ----
>> |15314|780:780|new| 2011-11-02
>> 12:58:43|15314|780:780|new|new.pm:process(295)|failed to load vmguest-3
>> with vmwarewinxp-WindowsXPwithVisualStudio32-v0
>> |15314|780:780|new| ( 0) new.pm, process (line: 295)
>> |15314|780:780|new| (-1) vcld, make_new_child (line: 568)
>> |15314|780:780|new| (-2) vcld, main (line: 346)
>>
>> 2011-11-02
>>
>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_state_name(2305)
>>|a
>> ttempting to retrieve current state of computer vmguest-3 from the
>>database
>> 2011-11-02
>>
>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_state_name(2336)
>>|r
>> etrieved current state of computer vmguest-3 from the database:
>>reloading
>> 2011-11-02
>> 12:58:43|15314|780:780|new|DataStructure.pm:_automethod(834)|data
>> structure updated:
>> $self->request_data->{reservation}{780}{computer}{state}{name}
>> |15314|780:780|new| computer_state_name = reloading
>> 2011-11-02
>>
>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_addre
>>ss
>> (1581)|attempting to retrieve private IP address for computer: vmguest-3
>> 2011-11-02
>>
>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_addre
>>ss
>> (1585)|retrieved contents of /etc/hosts on this management node,
>>contains
>> 44 lines
>> 2011-11-02
>>
>>12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_addre
>>ss
>> (1645)|returning IP address from /etc/hosts file: 10.10.10.4
>> 2011-11-02
>> 12:58:43|15314|780:780|new|utils.pm:is_inblockrequest(6163)|zero rows
>>were
>> returned from database select
>> 2011-11-02
>>
>>12:58:43|15314|780:780|new|DataStructure.pm:get_image_affiliation_name(20
>>35
>> )|image owner id: 1
>> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2709)|database
>> requested (information_schema) does not match handle stored in $ENV{dbh}
>> (vcl:localhost)
>> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2760)|database
>> handle stored in $ENV{dbh}
>> 2011-11-02
>>
>>12:58:43|15314|780:780|new|DataStructure.pm:retrieve_user_data(1352)|atte
>>mp
>> ting to retrieve and store data for user: user.id = '1'
>> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2709)|database
>> requested (vcl) does not match handle stored in $ENV{dbh}
>> (information_schema:localhost)
>> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2760)|database
>> handle stored in $ENV{dbh}
>> 2011-11-02
>>
>>12:58:43|15314|780:780|new|DataStructure.pm:retrieve_user_data(1415)|data
>> has been retrieved for user: admin (id: 1)
>> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:mail(1268)|SUCCESS --
>> Sending mail To: 0, PROBLEM --
>>
>>780:780|new|State.pm|vmguest-3>CSB303|vmwarewinxp-WindowsXPwithVisualStud
>>io
>> 32-v0|admin
>>
>>
>>
>>
>>
>> |15314|780:780|new| ---- CRITICAL ----
>> |15314|780:780|new| 2011-11-02
>> 12:58:43|15314|780:780|new|State.pm:reservation_failed(213)|reservation
>> failed on vmguest-3: process failed after trying to load or make
>>available
>> |15314|780:780|new| ( 0) State.pm, reservation_failed (line: 213)
>> |15314|780:780|new| (-1) new.pm, process (line: 298)
>> |15314|780:780|new| (-2) vcld, make_new_child (line: 568)
>> |15314|780:780|new| (-3) vcld, main (line: 346)
>>
>>
>
>
>
>--
>Aaron Peeler
>Program Manager
>Virtual Computing Lab
>NC State University
>
>All electronic mail messages in connection with State business which
>are sent to or received by this account are subject to the NC Public
>Records Law and may be disclosed to third parties.


Re: another problem for image reservation

Posted by Aaron Peeler <fa...@ncsu.edu>.
Hi Lei,

The issue in the log output is related to ssh is not responding.

Double check that you can log into vmguest-1 or vmguest-3 via ssh (you
have a couple of different reservations in your log output).

Things to check are to;
make sure your vmguest-X machines are getting the correct dhcp IP address.
make sure cygwin sshd service is started.

Aaron



On Wed, Nov 2, 2011 at 2:22 PM, Huang,Lei <lh...@pvamu.edu> wrote:
> Hi All,
>
>  I have encountered another problem after upgraded to 2.2.1. Per Aaron's
> suggestion, I changed my Vmguests provisioning engine to Vmware from
> Vmware Server GSX. However, my Windows XP image failed to reserve after
> the change. From the log, I found that it looks for
> 'C:/Windows/System32/qwinsta.exe' and 'C:/Windows/System32/sc.exe config
> sshd start= auto'. However, both them are not found on my XP image. Do I
> need to update my XP image? The image works fine on Vmware Server GSX
> provision engine. The following is the log.
>
> Thanks,
> Lei
>
> ======================
>
> |15314|780:780|new| ---- WARNING ----
> |15314|780:780|new| 2011-11-02
> 12:58:21|15314|780:780|new|Windows.pm:is_64_bit(8095)|unable to find
> registry value line in reg.exe output:
> |15314|780:780|new| bash: reg.exe: command not found
> |15314|780:780|new| ( 0) Windows.pm, is_64_bit (line: 8095)
> |15314|780:780|new| (-1) Windows.pm, get_system32_path (line: 8146)
> |15314|780:780|new| (-2) Windows.pm, user_logged_in (line: 8342)
> |15314|780:780|new| (-3) Windows.pm, wait_for_logoff (line: 8440)
> |15314|780:780|new| (-4) Windows.pm, post_load (line: 602)
> |15314|780:780|new| (-5) VMware.pm, load (line: 415)
>
> 2011-11-02
> 12:58:21|15314|780:780|new|Windows.pm:get_system32_path(8152)|32-bit
> Windows OS installed on vmguest-3, using C:/Windows/System32
> 2011-11-02
> 12:58:21|15314|780:780|new|Windows.pm:user_logged_in(8356)|checking if
> root is logged in to vmguest-3
> 2011-11-02
> 12:58:21|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing SSH
> command on vmguest-3:
> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
> 'C:/Windows/System32/qwinsta.exe' 2>&1
> 2011-11-02
> 12:58:25|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 5:
> waiting for vmguest-1 to respond to SSH
> 2011-11-02
> 12:58:25|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is NOT
> responding to SSH, ports 22 or 24 are both closed
> 2011-11-02
> 12:58:25|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 5:
> code returned false, seconds elapsed/remaining: 34/866, sleeping for 8
> seconds
> 2011-11-02 12:58:26|12831|vcld:main(167)|lastcheckin time updated for
> management node 1: 2011-11-02 12:58:26
> 2011-11-02
> 12:58:26|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_ip(
> 1093)|reservation remote IP is not defined
> 2011-11-02
> 12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_command
> output:
> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file or
> directory
> 2011-11-02 12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
> command executed on vmguest-3, command:
> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
> 'C:/Windows/System32/qwinsta.exe' 2>&1
> |15314|780:780|new| returning (127, "bash: C:/Windows/System32/qwin...")
>
> |15314|780:780|new| ---- WARNING ----
> |15314|780:780|new| 2011-11-02
> 12:58:27|15314|780:780|new|Windows.pm:user_logged_in(8361)|failed to run
> qwinsta.exe on vmguest-3, exit status: 127, output:
> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file or
> directory
> |15314|780:780|new| ( 0) Windows.pm, user_logged_in (line: 8361)
> |15314|780:780|new| (-1) Windows.pm, wait_for_logoff (line: 8440)
> |15314|780:780|new| (-2) Windows.pm, post_load (line: 602)
> |15314|780:780|new| (-3) VMware.pm, load (line: 415)
> |15314|780:780|new| (-4) new.pm, reload_image (line: 618)
> |15314|780:780|new| (-5) new.pm, process (line: 248)
>
> 2011-11-02
> 12:58:27|15314|780:780|new|Windows.pm:wait_for_logoff(8441)|root is NOT
> logged in to vmguest-3, returning 1
> 2011-11-02
> 12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing SSH
> command on vmguest-3:
> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
> 'C:/Windows/System32/qwinsta.exe' 2>&1
> 2011-11-02 12:58:31|12831|vcld:main(167)|lastcheckin time updated for
> management node 1: 2011-11-02 12:58:31
> 2011-11-02
> 12:58:31|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_ip(
> 1093)|reservation remote IP is not defined
> 2011-11-02
> 12:58:32|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_command
> output:
> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file or
> directory
> 2011-11-02 12:58:32|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
> command executed on vmguest-3, command:
> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
> 'C:/Windows/System32/qwinsta.exe' 2>&1
> |15314|780:780|new| returning (127, "bash: C:/Windows/System32/qwin...")
>
> |15314|780:780|new| ---- WARNING ----
> |15314|780:780|new| 2011-11-02
> 12:58:32|15314|780:780|new|Windows.pm:logoff_users(1437)|failed to run
> qwinsta.exe on vmguest-3, exit status: 127, output:
> |15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file or
> directory
> |15314|780:780|new| ( 0) Windows.pm, logoff_users (line: 1437)
> |15314|780:780|new| (-1) Windows.pm, post_load (line: 615)
> |15314|780:780|new| (-2) VMware.pm, load (line: 415)
> |15314|780:780|new| (-3) new.pm, reload_image (line: 618)
> |15314|780:780|new| (-4) new.pm, process (line: 248)
> |15314|780:780|new| (-5) vcld, make_new_child (line: 568)
>
>
> |15314|780:780|new| ---- WARNING ----
> |15314|780:780|new| 2011-11-02
> 12:58:32|15314|780:780|new|Windows.pm:post_load(615)|failed to log off all
> currently logged in users
> |15314|780:780|new| ( 0) Windows.pm, post_load (line: 615)
> |15314|780:780|new| (-1) VMware.pm, load (line: 415)
> |15314|780:780|new| (-2) new.pm, reload_image (line: 618)
> |15314|780:780|new| (-3) new.pm, process (line: 248)
> |15314|780:780|new| (-4) vcld, make_new_child (line: 568)
> |15314|780:780|new| (-5) vcld, main (line: 346)
>
> 2011-11-02
> 12:58:33|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 6:
> waiting for vmguest-1 to respond to SSH
> 2011-11-02
> 12:58:34|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is NOT
> responding to SSH, ports 22 or 24 are both closed
> 2011-11-02
> 12:58:34|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 6:
> code returned false, seconds elapsed/remaining: 43/857, sleeping for 8
> seconds
> 2011-11-02 12:58:36|12831|vcld:main(167)|lastcheckin time updated for
> management node 1: 2011-11-02 12:58:36
> 2011-11-02
> 12:58:36|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_ip(
> 1093)|reservation remote IP is not defined
>
> |15314|780:780|new| ---- WARNING ----
> |15314|780:780|new| 2011-11-02
> 12:58:37|15314|780:780|new|Windows.pm:set_file_owner(1398)|error occurred
> setting root as the owner of /home/root, error output:
> |15314|780:780|new| bash: /usr/bin/chown.exe: No such file or directory
> |15314|780:780|new| ( 0) Windows.pm, set_file_owner (line: 1398)
> |15314|780:780|new| (-1) Windows.pm, post_load (line: 625)
> |15314|780:780|new| (-2) VMware.pm, load (line: 415)
> |15314|780:780|new| (-3) new.pm, reload_image (line: 618)
> |15314|780:780|new| (-4) new.pm, process (line: 248)
> |15314|780:780|new| (-5) vcld, make_new_child (line: 568)
>
>
> |15314|780:780|new| ---- WARNING ----
> |15314|780:780|new| 2011-11-02
> 12:58:37|15314|780:780|new|Windows.pm:post_load(625)|unable to set root as
> the owner of /home/root
> |15314|780:780|new| ( 0) Windows.pm, post_load (line: 625)
> |15314|780:780|new| (-1) VMware.pm, load (line: 415)
> |15314|780:780|new| (-2) new.pm, reload_image (line: 618)
> |15314|780:780|new| (-3) new.pm, process (line: 248)
> |15314|780:780|new| (-4) vcld, make_new_child (line: 568)
> |15314|780:780|new| (-5) vcld, main (line: 346)
>
> 2011-11-02
> 12:58:37|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing SSH
> command on vmguest-3:
> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
> 'C:/Windows/System32/sc.exe config sshd start= auto' 2>&1
> 2011-11-02 12:58:41|12831|vcld:main(167)|lastcheckin time updated for
> management node 1: 2011-11-02 12:58:41
> 2011-11-02
> 12:58:41|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_ip(
> 1093)|reservation remote IP is not defined
> 2011-11-02
> 12:58:42|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 7:
> waiting for vmguest-1 to respond to SSH
> 2011-11-02
> 12:58:42|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is NOT
> responding to SSH, ports 22 or 24 are both closed
> 2011-11-02
> 12:58:42|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 7:
> code returned false, seconds elapsed/remaining: 51/849, sleeping for 8
> seconds
> 2011-11-02
> 12:58:43|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_command
> output:
> |15314|780:780|new| bash: C:/Windows/System32/sc.exe: No such file or
> directory
> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
> command executed on vmguest-3, command:
> |15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
> StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
> 'C:/Windows/System32/sc.exe config sshd start= auto' 2>&1
> |15314|780:780|new| returning (127, "bash: C:/Windows/System32/sc.e...")
>
> |15314|780:780|new| ---- WARNING ----
> |15314|780:780|new| 2011-11-02
> 12:58:43|15314|780:780|new|Windows.pm:set_service_startup_mode(3644)|failed
>  to set sshd service startup mode to auto, exit status: 127, output:
> |15314|780:780|new| bash: C:/Windows/System32/sc.exe: No such file or
> directory
> |15314|780:780|new| ( 0) Windows.pm, set_service_startup_mode (line: 3644)
> |15314|780:780|new| (-1) Windows.pm, post_load (line: 639)
> |15314|780:780|new| (-2) VMware.pm, load (line: 415)
> |15314|780:780|new| (-3) new.pm, reload_image (line: 618)
> |15314|780:780|new| (-4) new.pm, process (line: 248)
> |15314|780:780|new| (-5) vcld, make_new_child (line: 568)
>
>
> |15314|780:780|new| ---- WARNING ----
> |15314|780:780|new| 2011-11-02
> 12:58:43|15314|780:780|new|Windows.pm:post_load(640)|unable to set sshd
> service startup mode to auto
> |15314|780:780|new| ( 0) Windows.pm, post_load (line: 640)
> |15314|780:780|new| (-1) VMware.pm, load (line: 415)
> |15314|780:780|new| (-2) new.pm, reload_image (line: 618)
> |15314|780:780|new| (-3) new.pm, process (line: 248)
> |15314|780:780|new| (-4) vcld, make_new_child (line: 568)
> |15314|780:780|new| (-5) vcld, main (line: 346)
>
>
> |15314|780:780|new| ---- WARNING ----
> |15314|780:780|new| 2011-11-02
> 12:58:43|15314|780:780|new|VMware.pm:load(419)|failed to perform OS
> post-load tasks on VM vmguest-3 on VM host: CSB303
> |15314|780:780|new| ( 0) VMware.pm, load (line: 419)
> |15314|780:780|new| (-1) new.pm, reload_image (line: 618)
> |15314|780:780|new| (-2) new.pm, process (line: 248)
> |15314|780:780|new| (-3) vcld, make_new_child (line: 568)
> |15314|780:780|new| (-4) vcld, main (line: 346)
>
>
> |15314|780:780|new| ---- WARNING ----
> |15314|780:780|new| 2011-11-02
> 12:58:43|15314|780:780|new|new.pm:reload_image(623)|vmwarewinxp-WindowsXPwi
> thVisualStudio32-v0 failed to load on vmguest-3, returning
> |15314|780:780|new| ( 0) new.pm, reload_image (line: 623)
> |15314|780:780|new| (-1) new.pm, process (line: 248)
> |15314|780:780|new| (-2) vcld, make_new_child (line: 568)
> |15314|780:780|new| (-3) vcld, main (line: 346)
>
> 2011-11-02
> 12:58:43|15314|780:780|new|utils.pm:insertloadlog(3875)|inserted
> computer=4, loadimagefailed, vmwarewinxp-WindowsXPwithVisualStudio32-v0
> failed to load on vmguest-3
>
> |15314|780:780|new| ---- WARNING ----
> |15314|780:780|new| 2011-11-02
> 12:58:43|15314|780:780|new|new.pm:process(295)|failed to load vmguest-3
> with vmwarewinxp-WindowsXPwithVisualStudio32-v0
> |15314|780:780|new| ( 0) new.pm, process (line: 295)
> |15314|780:780|new| (-1) vcld, make_new_child (line: 568)
> |15314|780:780|new| (-2) vcld, main (line: 346)
>
> 2011-11-02
> 12:58:43|15314|780:780|new|DataStructure.pm:get_computer_state_name(2305)|a
> ttempting to retrieve current state of computer vmguest-3 from the database
> 2011-11-02
> 12:58:43|15314|780:780|new|DataStructure.pm:get_computer_state_name(2336)|r
> etrieved current state of computer vmguest-3 from the database: reloading
> 2011-11-02
> 12:58:43|15314|780:780|new|DataStructure.pm:_automethod(834)|data
> structure updated:
> $self->request_data->{reservation}{780}{computer}{state}{name}
> |15314|780:780|new| computer_state_name = reloading
> 2011-11-02
> 12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_address
> (1581)|attempting to retrieve private IP address for computer: vmguest-3
> 2011-11-02
> 12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_address
> (1585)|retrieved contents of /etc/hosts on this management node, contains
> 44 lines
> 2011-11-02
> 12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_address
> (1645)|returning IP address from /etc/hosts file: 10.10.10.4
> 2011-11-02
> 12:58:43|15314|780:780|new|utils.pm:is_inblockrequest(6163)|zero rows were
> returned from database select
> 2011-11-02
> 12:58:43|15314|780:780|new|DataStructure.pm:get_image_affiliation_name(2035
> )|image owner id: 1
> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2709)|database
> requested (information_schema) does not match handle stored in $ENV{dbh}
> (vcl:localhost)
> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2760)|database
> handle stored in $ENV{dbh}
> 2011-11-02
> 12:58:43|15314|780:780|new|DataStructure.pm:retrieve_user_data(1352)|attemp
> ting to retrieve and store data for user: user.id = '1'
> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2709)|database
> requested (vcl) does not match handle stored in $ENV{dbh}
> (information_schema:localhost)
> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2760)|database
> handle stored in $ENV{dbh}
> 2011-11-02
> 12:58:43|15314|780:780|new|DataStructure.pm:retrieve_user_data(1415)|data
> has been retrieved for user: admin (id: 1)
> 2011-11-02 12:58:43|15314|780:780|new|utils.pm:mail(1268)|SUCCESS --
> Sending mail To: 0, PROBLEM --
> 780:780|new|State.pm|vmguest-3>CSB303|vmwarewinxp-WindowsXPwithVisualStudio
> 32-v0|admin
>
>
>
>
>
> |15314|780:780|new| ---- CRITICAL ----
> |15314|780:780|new| 2011-11-02
> 12:58:43|15314|780:780|new|State.pm:reservation_failed(213)|reservation
> failed on vmguest-3: process failed after trying to load or make available
> |15314|780:780|new| ( 0) State.pm, reservation_failed (line: 213)
> |15314|780:780|new| (-1) new.pm, process (line: 298)
> |15314|780:780|new| (-2) vcld, make_new_child (line: 568)
> |15314|780:780|new| (-3) vcld, main (line: 346)
>
>



-- 
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.

another problem for image reservation

Posted by "Huang,Lei" <lh...@PVAMU.EDU>.
Hi All, 

  I have encountered another problem after upgraded to 2.2.1. Per Aaron's
suggestion, I changed my Vmguests provisioning engine to Vmware from
Vmware Server GSX. However, my Windows XP image failed to reserve after
the change. From the log, I found that it looks for
'C:/Windows/System32/qwinsta.exe' and 'C:/Windows/System32/sc.exe config
sshd start= auto'. However, both them are not found on my XP image. Do I
need to update my XP image? The image works fine on Vmware Server GSX
provision engine. The following is the log.

Thanks,
Lei

======================

|15314|780:780|new| ---- WARNING ----
|15314|780:780|new| 2011-11-02
12:58:21|15314|780:780|new|Windows.pm:is_64_bit(8095)|unable to find
registry value line in reg.exe output:
|15314|780:780|new| bash: reg.exe: command not found
|15314|780:780|new| ( 0) Windows.pm, is_64_bit (line: 8095)
|15314|780:780|new| (-1) Windows.pm, get_system32_path (line: 8146)
|15314|780:780|new| (-2) Windows.pm, user_logged_in (line: 8342)
|15314|780:780|new| (-3) Windows.pm, wait_for_logoff (line: 8440)
|15314|780:780|new| (-4) Windows.pm, post_load (line: 602)
|15314|780:780|new| (-5) VMware.pm, load (line: 415)

2011-11-02 
12:58:21|15314|780:780|new|Windows.pm:get_system32_path(8152)|32-bit
Windows OS installed on vmguest-3, using C:/Windows/System32
2011-11-02 
12:58:21|15314|780:780|new|Windows.pm:user_logged_in(8356)|checking if
root is logged in to vmguest-3
2011-11-02 
12:58:21|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing SSH
command on vmguest-3:
|15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
'C:/Windows/System32/qwinsta.exe' 2>&1
2011-11-02 
12:58:25|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 5:
waiting for vmguest-1 to respond to SSH
2011-11-02 
12:58:25|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is NOT
responding to SSH, ports 22 or 24 are both closed
2011-11-02 
12:58:25|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 5:
code returned false, seconds elapsed/remaining: 34/866, sleeping for 8
seconds
2011-11-02 12:58:26|12831|vcld:main(167)|lastcheckin time updated for
management node 1: 2011-11-02 12:58:26
2011-11-02 
12:58:26|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_ip(
1093)|reservation remote IP is not defined
2011-11-02 
12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_command
output:
|15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file or
directory
2011-11-02 12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
command executed on vmguest-3, command:
|15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
'C:/Windows/System32/qwinsta.exe' 2>&1
|15314|780:780|new| returning (127, "bash: C:/Windows/System32/qwin...")

|15314|780:780|new| ---- WARNING ----
|15314|780:780|new| 2011-11-02
12:58:27|15314|780:780|new|Windows.pm:user_logged_in(8361)|failed to run
qwinsta.exe on vmguest-3, exit status: 127, output:
|15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file or
directory
|15314|780:780|new| ( 0) Windows.pm, user_logged_in (line: 8361)
|15314|780:780|new| (-1) Windows.pm, wait_for_logoff (line: 8440)
|15314|780:780|new| (-2) Windows.pm, post_load (line: 602)
|15314|780:780|new| (-3) VMware.pm, load (line: 415)
|15314|780:780|new| (-4) new.pm, reload_image (line: 618)
|15314|780:780|new| (-5) new.pm, process (line: 248)

2011-11-02 
12:58:27|15314|780:780|new|Windows.pm:wait_for_logoff(8441)|root is NOT
logged in to vmguest-3, returning 1
2011-11-02 
12:58:27|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing SSH
command on vmguest-3:
|15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
'C:/Windows/System32/qwinsta.exe' 2>&1
2011-11-02 12:58:31|12831|vcld:main(167)|lastcheckin time updated for
management node 1: 2011-11-02 12:58:31
2011-11-02 
12:58:31|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_ip(
1093)|reservation remote IP is not defined
2011-11-02 
12:58:32|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_command
output:
|15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file or
directory
2011-11-02 12:58:32|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
command executed on vmguest-3, command:
|15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
'C:/Windows/System32/qwinsta.exe' 2>&1
|15314|780:780|new| returning (127, "bash: C:/Windows/System32/qwin...")

|15314|780:780|new| ---- WARNING ----
|15314|780:780|new| 2011-11-02
12:58:32|15314|780:780|new|Windows.pm:logoff_users(1437)|failed to run
qwinsta.exe on vmguest-3, exit status: 127, output:
|15314|780:780|new| bash: C:/Windows/System32/qwinsta.exe: No such file or
directory
|15314|780:780|new| ( 0) Windows.pm, logoff_users (line: 1437)
|15314|780:780|new| (-1) Windows.pm, post_load (line: 615)
|15314|780:780|new| (-2) VMware.pm, load (line: 415)
|15314|780:780|new| (-3) new.pm, reload_image (line: 618)
|15314|780:780|new| (-4) new.pm, process (line: 248)
|15314|780:780|new| (-5) vcld, make_new_child (line: 568)


|15314|780:780|new| ---- WARNING ----
|15314|780:780|new| 2011-11-02
12:58:32|15314|780:780|new|Windows.pm:post_load(615)|failed to log off all
currently logged in users
|15314|780:780|new| ( 0) Windows.pm, post_load (line: 615)
|15314|780:780|new| (-1) VMware.pm, load (line: 415)
|15314|780:780|new| (-2) new.pm, reload_image (line: 618)
|15314|780:780|new| (-3) new.pm, process (line: 248)
|15314|780:780|new| (-4) vcld, make_new_child (line: 568)
|15314|780:780|new| (-5) vcld, main (line: 346)

2011-11-02 
12:58:33|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 6:
waiting for vmguest-1 to respond to SSH
2011-11-02 
12:58:34|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is NOT
responding to SSH, ports 22 or 24 are both closed
2011-11-02 
12:58:34|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 6:
code returned false, seconds elapsed/remaining: 43/857, sleeping for 8
seconds
2011-11-02 12:58:36|12831|vcld:main(167)|lastcheckin time updated for
management node 1: 2011-11-02 12:58:36
2011-11-02 
12:58:36|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_ip(
1093)|reservation remote IP is not defined

|15314|780:780|new| ---- WARNING ----
|15314|780:780|new| 2011-11-02
12:58:37|15314|780:780|new|Windows.pm:set_file_owner(1398)|error occurred
setting root as the owner of /home/root, error output:
|15314|780:780|new| bash: /usr/bin/chown.exe: No such file or directory
|15314|780:780|new| ( 0) Windows.pm, set_file_owner (line: 1398)
|15314|780:780|new| (-1) Windows.pm, post_load (line: 625)
|15314|780:780|new| (-2) VMware.pm, load (line: 415)
|15314|780:780|new| (-3) new.pm, reload_image (line: 618)
|15314|780:780|new| (-4) new.pm, process (line: 248)
|15314|780:780|new| (-5) vcld, make_new_child (line: 568)


|15314|780:780|new| ---- WARNING ----
|15314|780:780|new| 2011-11-02
12:58:37|15314|780:780|new|Windows.pm:post_load(625)|unable to set root as
the owner of /home/root
|15314|780:780|new| ( 0) Windows.pm, post_load (line: 625)
|15314|780:780|new| (-1) VMware.pm, load (line: 415)
|15314|780:780|new| (-2) new.pm, reload_image (line: 618)
|15314|780:780|new| (-3) new.pm, process (line: 248)
|15314|780:780|new| (-4) vcld, make_new_child (line: 568)
|15314|780:780|new| (-5) vcld, main (line: 346)

2011-11-02 
12:58:37|15314|780:780|new|utils.pm:run_ssh_command(5380)|executing SSH
command on vmguest-3:
|15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
'C:/Windows/System32/sc.exe config sshd start= auto' 2>&1
2011-11-02 12:58:41|12831|vcld:main(167)|lastcheckin time updated for
management node 1: 2011-11-02 12:58:41
2011-11-02 
12:58:41|15410|778:778|reserved|DataStructure.pm:get_reservation_remote_ip(
1093)|reservation remote IP is not defined
2011-11-02 
12:58:42|15241|779:779|new|Module.pm:code_loop_timeout(759)|attempt 7:
waiting for vmguest-1 to respond to SSH
2011-11-02 
12:58:42|15241|779:779|new|OS.pm:is_ssh_responding(386)|vmguest-1 is NOT
responding to SSH, ports 22 or 24 are both closed
2011-11-02 
12:58:42|15241|779:779|new|Module.pm:code_loop_timeout(755)|attempt 7:
code returned false, seconds elapsed/remaining: 51/849, sleeping for 8
seconds
2011-11-02 
12:58:43|15314|780:780|new|utils.pm:run_ssh_command(5464)|run_ssh_command
output:
|15314|780:780|new| bash: C:/Windows/System32/sc.exe: No such file or
directory
2011-11-02 12:58:43|15314|780:780|new|utils.pm:run_ssh_command(5474)|SSH
command executed on vmguest-3, command:
|15314|780:780|new| /usr/bin/ssh -i /etc/vcl/vcl.key  -o
StrictHostKeyChecking=no -l root -p 22 -x vmguest-3
'C:/Windows/System32/sc.exe config sshd start= auto' 2>&1
|15314|780:780|new| returning (127, "bash: C:/Windows/System32/sc.e...")

|15314|780:780|new| ---- WARNING ----
|15314|780:780|new| 2011-11-02
12:58:43|15314|780:780|new|Windows.pm:set_service_startup_mode(3644)|failed
 to set sshd service startup mode to auto, exit status: 127, output:
|15314|780:780|new| bash: C:/Windows/System32/sc.exe: No such file or
directory
|15314|780:780|new| ( 0) Windows.pm, set_service_startup_mode (line: 3644)
|15314|780:780|new| (-1) Windows.pm, post_load (line: 639)
|15314|780:780|new| (-2) VMware.pm, load (line: 415)
|15314|780:780|new| (-3) new.pm, reload_image (line: 618)
|15314|780:780|new| (-4) new.pm, process (line: 248)
|15314|780:780|new| (-5) vcld, make_new_child (line: 568)


|15314|780:780|new| ---- WARNING ----
|15314|780:780|new| 2011-11-02
12:58:43|15314|780:780|new|Windows.pm:post_load(640)|unable to set sshd
service startup mode to auto
|15314|780:780|new| ( 0) Windows.pm, post_load (line: 640)
|15314|780:780|new| (-1) VMware.pm, load (line: 415)
|15314|780:780|new| (-2) new.pm, reload_image (line: 618)
|15314|780:780|new| (-3) new.pm, process (line: 248)
|15314|780:780|new| (-4) vcld, make_new_child (line: 568)
|15314|780:780|new| (-5) vcld, main (line: 346)


|15314|780:780|new| ---- WARNING ----
|15314|780:780|new| 2011-11-02
12:58:43|15314|780:780|new|VMware.pm:load(419)|failed to perform OS
post-load tasks on VM vmguest-3 on VM host: CSB303
|15314|780:780|new| ( 0) VMware.pm, load (line: 419)
|15314|780:780|new| (-1) new.pm, reload_image (line: 618)
|15314|780:780|new| (-2) new.pm, process (line: 248)
|15314|780:780|new| (-3) vcld, make_new_child (line: 568)
|15314|780:780|new| (-4) vcld, main (line: 346)


|15314|780:780|new| ---- WARNING ----
|15314|780:780|new| 2011-11-02
12:58:43|15314|780:780|new|new.pm:reload_image(623)|vmwarewinxp-WindowsXPwi
thVisualStudio32-v0 failed to load on vmguest-3, returning
|15314|780:780|new| ( 0) new.pm, reload_image (line: 623)
|15314|780:780|new| (-1) new.pm, process (line: 248)
|15314|780:780|new| (-2) vcld, make_new_child (line: 568)
|15314|780:780|new| (-3) vcld, main (line: 346)

2011-11-02 
12:58:43|15314|780:780|new|utils.pm:insertloadlog(3875)|inserted
computer=4, loadimagefailed, vmwarewinxp-WindowsXPwithVisualStudio32-v0
failed to load on vmguest-3

|15314|780:780|new| ---- WARNING ----
|15314|780:780|new| 2011-11-02
12:58:43|15314|780:780|new|new.pm:process(295)|failed to load vmguest-3
with vmwarewinxp-WindowsXPwithVisualStudio32-v0
|15314|780:780|new| ( 0) new.pm, process (line: 295)
|15314|780:780|new| (-1) vcld, make_new_child (line: 568)
|15314|780:780|new| (-2) vcld, main (line: 346)

2011-11-02 
12:58:43|15314|780:780|new|DataStructure.pm:get_computer_state_name(2305)|a
ttempting to retrieve current state of computer vmguest-3 from the database
2011-11-02 
12:58:43|15314|780:780|new|DataStructure.pm:get_computer_state_name(2336)|r
etrieved current state of computer vmguest-3 from the database: reloading
2011-11-02 
12:58:43|15314|780:780|new|DataStructure.pm:_automethod(834)|data
structure updated: 
$self->request_data->{reservation}{780}{computer}{state}{name}
|15314|780:780|new| computer_state_name = reloading
2011-11-02 
12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_address
(1581)|attempting to retrieve private IP address for computer: vmguest-3
2011-11-02 
12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_address
(1585)|retrieved contents of /etc/hosts on this management node, contains
44 lines
2011-11-02 
12:58:43|15314|780:780|new|DataStructure.pm:get_computer_private_ip_address
(1645)|returning IP address from /etc/hosts file: 10.10.10.4
2011-11-02 
12:58:43|15314|780:780|new|utils.pm:is_inblockrequest(6163)|zero rows were
returned from database select
2011-11-02 
12:58:43|15314|780:780|new|DataStructure.pm:get_image_affiliation_name(2035
)|image owner id: 1
2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2709)|database
requested (information_schema) does not match handle stored in $ENV{dbh}
(vcl:localhost)
2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2760)|database
handle stored in $ENV{dbh}
2011-11-02 
12:58:43|15314|780:780|new|DataStructure.pm:retrieve_user_data(1352)|attemp
ting to retrieve and store data for user: user.id = '1'
2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2709)|database
requested (vcl) does not match handle stored in $ENV{dbh}
(information_schema:localhost)
2011-11-02 12:58:43|15314|780:780|new|utils.pm:getnewdbh(2760)|database
handle stored in $ENV{dbh}
2011-11-02 
12:58:43|15314|780:780|new|DataStructure.pm:retrieve_user_data(1415)|data
has been retrieved for user: admin (id: 1)
2011-11-02 12:58:43|15314|780:780|new|utils.pm:mail(1268)|SUCCESS --
Sending mail To: 0, PROBLEM --
780:780|new|State.pm|vmguest-3>CSB303|vmwarewinxp-WindowsXPwithVisualStudio
32-v0|admin





|15314|780:780|new| ---- CRITICAL ----
|15314|780:780|new| 2011-11-02
12:58:43|15314|780:780|new|State.pm:reservation_failed(213)|reservation
failed on vmguest-3: process failed after trying to load or make available
|15314|780:780|new| ( 0) State.pm, reservation_failed (line: 213)
|15314|780:780|new| (-1) new.pm, process (line: 298)
|15314|780:780|new| (-2) vcld, make_new_child (line: 568)
|15314|780:780|new| (-3) vcld, main (line: 346)


Re: Base Image creation error - Confused

Posted by Evelio Quiros <ev...@fiu.edu>.
Andy Kurth <an...@ncsu.edu> wrote:


The "selection not available" error is not directly caused by the
error in the log output you have included.  The reason why the failure
occurred is because the MAC address fields are not set on the
"linux64base" computer you previously added to VCL.

You will need to add computers using the "Add Multiple Computers"
option in order to have the MAC addresses properly configured in the
database. 


****

I am trying this again, but I must be missing something basic.
Here are my steps in capturing this base image:

1. The Vmware server is added to the vcl database.
2. 10 Vmware images are added to the vcl database in maintenance state.
3. The 10 image entries are added to dhcp configuration as host entries.
	** When I reboot the VM, it does not get one of the host entries, because
the dhcp server does not recognize it.
	** Adding a range to dhcp seems to give it an acceptable address to
proceed.
4. These 10 images are added to the Vmware host, turning their state to
"available".
5. I run vcld -setup.
	** At this point, the image to be captured is not one of the 10 images in
the database.
     ***** In previous attempts, I added the image to be captured
separately.
   ******* In my latest attempt, I made the MAC address one of the
machines I previously added.

***>> I was successful in capturing an image, but it would not reload a
reservation.

Here is my error message:

reservation failed on image1: process failed after trying to load or make
available
------------------------------------------------------------------------
time: 2011-11-01 15:54:44
caller: State.pm:reservation_failed(213)
( 0) State.pm, reservation_failed (line: 213)
(-1) new.pm, process (line: 298)
(-2) vcld, make_new_child (line: 568)
(-3) vcld, main (line: 346)
------------------------------------------------------------------------
management node: vltst.fiu.edu
reservation PID: 23935
parent vcld PID: 18854

request ID: 2
reservation ID: 2
request state/laststate: reload/image
request start time: 2011-11-01 15:43:10
request end time: 2011-11-01 16:13:10
for imaging: no
log ID: none

computer: image1
computer id: 2
computer type: virtualmachine
computer eth0 MAC address: 00:50:56:00:10:00
computer eth1 MAC address: 00:50:56:00:10:01
computer private IP address: 10.0.0.4
computer public IP address: 10.106.128.54
computer in block allocation: no
provisioning module: VCL::Module::Provisioning::VMware::VMware

vm host: vcldell01
vm host ID: 1
vm host computer ID: 1
vm profile: VMware ESX - local storage
vm profile VM path: /vmfs/volumes/datastore1
vm profile repository path: /images
vm profile datastore path: /vmfs/volumes/datastore1
vm profile disk type: localdisk

image: vmwarelinux-linuxbase5-v0
image display name: linuxbase
image ID: 5
image revision ID: 5
image size: 16384 MB
use Sysprep: yes
root access: yes
image owner ID: 1
image owner affiliation: Local
image revision date created: 2011-11-01 15:40:07
image revision production: yes
OS module: VCL::Module::OS::Linux

user: vclreload
user name: vcl reload
user ID: 2
user affiliation: Local
------------------------------------------------------------------------




In previous attempts, I added the base computer as a separate image

On 10/28/11 2:03 PM, "Andy Kurth" <an...@ncsu.edu> wrote:

>I think there may be 2 issues...
>
>> When I try to make a manual reservation, it tells me that there is no
>> computer available to run this image.
>> I wonder if I gave it some bad info for RAM or CPU ?
>
>Did you add the image to an image group after it was captured?  This
>page has a little more information:
>https://cwiki.apache.org/confluence/display/VCL/Capture+A+Base+Image
>
>If you did already add the image to a group, you may be seeing the
>"selection not available" error on the website because the only
>computer that is available for the image to run on is your
>"linux64base" computer.  The state of this computer may be "failed"
>because of the problem which occurred in the vcld.log output you
>included.  After an image is successfully captured, a "reload"
>reservation is automatically added to the database to load the new
>image on the same computer used to capture it.  I'm guessing the
>output you included is from this reload reservation.
>
>The "selection not available" error is not directly caused by the
>error in the log output you have included.  The reason why the failure
>occurred is because the MAC address fields are not set on the
>"linux64base" computer you previously added to VCL as evidenced by the
>following line:
>
>> 
>>15:52:10|19062|8:8|reload|DataStructure.pm:_automethod(812)|corresponding
>> data has not been initialized for get_computer_eth0_mac_address:
>>$self->request_data->{reservation}{8}{computer}{eth0macaddress}
>
>You will need to add computers uing the "Add Multiple Computers"
>option in order to have the MAC addresses properl configured in the
>database.  I would recommend looking at the "Adding Virtual Machines"
>section on the following page:
>https://cwiki.apache.org/confluence/display/VCL/VCL+2.2.1+-+Further+Steps+
>if+Using+VMware
>
>Also, you'll probably want to check the state of the "linux64base"
>computer by looking at Manage Computers > Computer Utilities.  It is
>probably "failed".  You can change this to available but reservations
>assigned to this computer will always fail because of the MAC address
>issue.  You will have to edit the database in order to set the MAC
>addresses for this computer.  However, it's probably easier to just
>delete this computer from VCL using Manage Computers > Edit Computer
>Information.  Once you have added the multiple VMs, you can use any of
>those to capture other base images in the future.
>
>Hope this helps,
>Andy
>
>
>
>
>
>> As Roseanne Rosanadana says: It's always something...
>>
>> The error message is below:
>>
>> reservation failed on linux64base: process failed after trying to load
>>or
>> make available
>> ------------------------------------------------------------------------
>> time: 2011-10-25 15:52:10
>> caller: State.pm:reservation_failed(213)
>> ( 0) State.pm, reservation_failed (line: 213)
>> (-1) new.pm, process (line: 298)
>> (-2) vcld, make_new_child (line: 568)
>> (-3) vcld, main (line: 346)
>> ------------------------------------------------------------------------
>> management node: vcltst.fiu.edu
>> reservation PID: 19062
>> parent vcld PID: 15838
>>
>> request ID: 8
>> reservation ID: 8
>> request state/laststate: reload/image
>> request start time: 2011-10-25 15:52:00
>> request end time: 2011-10-25 16:22:00
>> for imaging: no
>> log ID: none
>>
>> computer: linux64base
>> computer id: 14
>> computer type: virtualmachine
>> computer eth0 MAC address: <undefined>
>> computer eth1 MAC address: <undefined>
>> computer private IP address: 10.0.0.2
>> computer public IP address: 10.106.128.53
>> computer in block allocation: no
>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>
>> vm host: vcldell_01
>> vm host ID: 2
>> vm host computer ID: 13
>> vm profile: VMware ESX - local storage
>> vm profile VM path: /vmfs/volumes/datastore1/vclimages
>> vm profile repository path: /vmfs/volumes/datastore1/vclrepository
>> vm profile datastore path: /vmfs/volumes/datastore1/vclimages
>> vm profile disk type: localdisk
>>
>> image: vmwarelinux-base64linux19-v0
>> image display name: base64linux
>> image ID: 19
>> image revision ID: 11
>> image size: 857 MB
>> use Sysprep: yes
>> root access: yes
>> image owner ID: 1
>> image owner affiliation: Local
>> image revision date created: 2011-10-25 15:50:38
>> image revision production: yes
>> OS module: VCL::Module::OS::Linux
>>
>> user: vclreload
>> user name: vcl reload
>> user ID: 2
>> user affiliation: Local
>> ------------------------------------------------------------------------
>> RECENT LOG ENTRIES FOR THIS PROCESS:
>> 2011-10-25
>> 15:52:08|19062|8:8|reload|VMware.pm:get_image_size_bytes(3841)|retrieved
>> the size of the image from the datastore on the VM host: 17,179,869,673
>> 2011-10-25
>> 15:52:08|19062|8:8|reload|VMware.pm:get_image_size_bytes(3851)|image
>>size
>> retrieved from both the image repository and VM host datastore:
>> |19062|8:8|reload| image repository: 898,237,415
>> |19062|8:8|reload| VM host datastore: 17,179,869,673
>> 2011-10-25
>> 15:52:08|19062|8:8|reload|VMware.pm:get_image_size_bytes(3871)|size of
>> vmwarelinux-base64linux19-v0 image:
>> |19062|8:8|reload| 17,179,869,673 bytes
>> |19062|8:8|reload| 16,384 MB
>> |19062|8:8|reload| 16.00 GB
>> 2011-10-25
>> 
>>15:52:08|19062|8:8|reload|VMware.pm:get_vm_additional_vmx_bytes_required(
>>47
>> 13)|4294967418 additional bytes required for REDO files because VM disk
>> mode is NOT persistent
>> 2011-10-25
>> 
>>15:52:08|19062|8:8|reload|VMware.pm:get_vm_additional_vmx_bytes_required(
>>47
>> 16)|estimate of additional space required for the vmx directory:
>> |19062|8:8|reload| vmem/vswp file: 536,870,912 bytes, 512.0 MB, 0.50 GB
>> |19062|8:8|reload| redo files: 4,294,967,418 bytes, 4,096.0 MB, 4.00 GB
>> |19062|8:8|reload| total: 4,831,838,330 bytes, 4,608.0 MB, 4.50 GB
>> 2011-10-25
>> 
>>15:52:09|19062|8:8|reload|Linux.pm:file_exists(1404)|'/vmfs/volumes/datas
>>to
>> 
>>re1/vclimages/vmwarelinux-base64linux19-v0/vmwarelinux-base64linux19-v0.v
>>md
>> k' exists on vcldell_01, files: 1, directories: 0, links: 0
>> 2011-10-25
>> 15:52:09|19062|8:8|reload|VMware.pm:get_image_size_bytes(3819)|VM
>>profile
>> vmdisk is set to 'localdisk', attempting to retrieve image size from
>>image
>> repository
>> 2011-10-25
>> 
>>15:52:09|19062|8:8|reload|Linux.pm:file_exists(1404)|'/vmfs/volumes/datas
>>to
>> re1/vclrepository' exists on vcldell_01, files: 0, directories: 1,
>>links: 0
>> 2011-10-25
>> 
>>15:52:09|19062|8:8|reload|VMware.pm:is_repository_mounted_on_vmhost(5485)
>>|i
>> mage repository is mounted on VM host vcldell_01:
>> /vmfs/volumes/datastore1/vclrepository
>> 2011-10-25
>> 15:52:09|19062|8:8|reload|VMware.pm:get_image_size_bytes(3821)|checking
>> size of image in image repository mounted on VM host:
>> vcldell_01:/vmfs/volumes/datastore1/vclrepository
>> 2011-10-25 15:52:09|19062|8:8|reload|Linux.pm:get_file_size(2022)|size
>>of
>> 
>>'/vmfs/volumes/datastore1/vclrepository/vmwarelinux-base64linux19-v0/vmwa
>>re
>> linux-base64linux19-v0*.vmdk' on vcldell_01:
>> |19062|8:8|reload| used: 898,237,415 bytes, 856.6 MB, 0.84 GB
>> |19062|8:8|reload| allocated: 903,872,512 bytes, 862.0 MB, 0.84 GB
>> 2011-10-25 15:52:10|19062|8:8|reload|Linux.pm:get_file_size(2022)|size
>>of
>> 
>>'/vmfs/volumes/datastore1/vclimages/vmwarelinux-base64linux19-v0/vmwareli
>>nu
>> x-base64linux19-v0*.vmdk' on vcldell_01:
>> |19062|8:8|reload| used: 17,179,869,673 bytes, 16,384.0 MB, 16.00 GB
>> |19062|8:8|reload| allocated: 17,179,869,184 bytes, 16,384.0 MB, 16.00
>>GB
>> 2011-10-25
>> 15:52:10|19062|8:8|reload|VMware.pm:get_image_size_bytes(3841)|retrieved
>> the size of the image from the datastore on the VM host: 17,179,869,673
>> 2011-10-25
>> 15:52:10|19062|8:8|reload|VMware.pm:get_image_size_bytes(3851)|image
>>size
>> retrieved from both the image repository and VM host datastore:
>> |19062|8:8|reload| image repository: 898,237,415
>> |19062|8:8|reload| VM host datastore: 17,179,869,673
>> 2011-10-25
>> 15:52:10|19062|8:8|reload|VMware.pm:get_image_size_bytes(3871)|size of
>> vmwarelinux-base64linux19-v0 image:
>> |19062|8:8|reload| 17,179,869,673 bytes
>> |19062|8:8|reload| 16,384 MB
>> |19062|8:8|reload| 16.00 GB
>> 2011-10-25
>> 
>>15:52:10|19062|8:8|reload|VMware.pm:get_vm_additional_vmdk_bytes_required
>>(4
>> 657)|no additional space required for vmdk files because they already
>> exist on VM host
>> 2011-10-25
>> 
>>15:52:10|19062|8:8|reload|VMware.pm:get_vm_additional_vmdk_bytes_required
>>(4
>> 662)|VM requires appoximately 0 additional bytes (0 MB, 0 GB) of disk
>> space on the VM host for the vmdk directory
>> 2011-10-25
>> 15:52:10|19062|8:8|reload|VMware.pm:check_vmhost_disk_space(2070)|enough
>> space is available on shared vmx/vmdk volume on VM host vcldell_01:
>> '/vmfs/volumes/datastore1/vclimages'
>> |19062|8:8|reload| vmx additional space required:          4,831,838,330
>> bytes, 4,608.0 MB, 4.50 GB
>> |19062|8:8|reload| vmdk additional space required:         0 bytes, 0.0
>> MB, 0.00 GB
>> |19062|8:8|reload| total additional space required:        4,831,838,330
>> bytes, 4,608.0 MB, 4.50 GB
>> |19062|8:8|reload| shared vmx/vmdk volume available space:
>>248,047,992,832
>> bytes, 236,557.0 MB, 231.01 GB
>> 2011-10-25
>> 15:52:10|19062|8:8|reload|Module.pm:create_mn_os_object(335)|management
>> node OS object has already been created, address: 222db60, returning 1
>> 2011-10-25
>> 15:52:10|19062|8:8|reload|Module.pm:new(203)|VCL::Module::Semaphore
>>object
>> created, address: 1cac6c0
>> 2011-10-25
>> 15:52:10|19062|8:8|reload|Module.pm:code_loop_timeout(742)|attempting to
>> open lockfile, maximum of 1200 seconds
>> 2011-10-25
>> 15:52:10|19062|8:8|reload|Module.pm:code_loop_timeout(759)|attempt 1:
>> attempting to open lockfile
>> 2011-10-25
>> 15:52:10|19062|8:8|reload|Semaphore.pm:open_lockfile(146)|opened and
>> obtained an exclusive lock on file:
>> 
>>/tmp/vcldell_01-vmfs-volumes-datastore1-vclimages-vmwarelinux-base64linux
>>19
>> -v0.lock
>> 2011-10-25
>> 15:52:10|19062|8:8|reload|Module.pm:code_loop_timeout(762)|attempting to
>> open lockfile, code returned true
>> 2011-10-25 
>>15:52:10|19062|8:8|reload|Module.pm:get_semaphore(844)|created
>> Semaphore object, memory address: 1cac6c0
>> 2011-10-25
>> 
>>15:52:10|19062|8:8|reload|Linux.pm:file_exists(1404)|'/vmfs/volumes/datas
>>to
>> 
>>re1/vclimages/vmwarelinux-base64linux19-v0/vmwarelinux-base64linux19-v0.v
>>md
>> k' exists on vcldell_01, files: 1, directories: 0, links: 0
>> 2011-10-25 15:52:10|19062|8:8|reload|VMware.pm:prepare_vmdk(1785)|VM is
>> not persistent and nonpersistent vmdk file already exists on VM host
>> vcldell_01:
>> 
>>/vmfs/volumes/datastore1/vclimages/vmwarelinux-base64linux19-v0/vmwarelin
>>ux
>> -base64linux19-v0.vmdk
>> 2011-10-25
>> 15:52:10|19062|8:8|reload|Semaphore.pm:release_lockfile(248)|deleted
>>file:
>> 
>>/tmp/vcldell_01-vmfs-volumes-datastore1-vclimages-vmwarelinux-base64linux
>>19
>> -v0.lock
>> 2011-10-25 15:52:10|19062|8:8|reload|Semaphore.pm:DESTROY(281)|destroyed
>> Semaphore object, memory address: 1cac6c0
>> 2011-10-25 
>>15:52:10|19062|8:8|reload|utils.pm:insertloadlog(3875)|inserted
>> computer=14, transfervm, copied vmwarelinux-base64linux19-v0 to
>>linux64base
>> 2011-10-25 15:52:10|19062|8:8|reload|VMware.pm:get_vm_ram(4306)|image
>>ram
>> setting is too low: 0 MB, 512 MB will be used
>> 2011-10-25
>> 
>>15:52:10|19062|8:8|reload|VMware.pm:get_vm_os_configuration(4210)|retriev
>>ed
>>  default VM configuration for OS: linux-x86_64
>> |19062|8:8|reload| : {
>> |19062|8:8|reload| :   "ethernet-virtualDev" => "e1000",
>> |19062|8:8|reload| :   "guestOS" => "otherlinux-64",
>> |19062|8:8|reload| :   "scsi-virtualDev" => "lsiLogic"
>> |19062|8:8|reload| : }
>> |19062|8:8|reload| ---- WARNING ----
>> |19062|8:8|reload| 2011-10-25
>> 
>>15:52:10|19062|8:8|reload|DataStructure.pm:_automethod(812)|corresponding
>> data has not been initialized for get_computer_eth0_mac_address:
>> $self->request_data->{reservation}{8}{computer}{eth0macaddress}
>> |19062|8:8|reload| ( 0) DataStructure.pm, _automethod (line: 812)
>> |19062|8:8|reload| (-1) Autoload.pm, __ANON__ (line: 80)
>> |19062|8:8|reload| (-2) VMware.pm, prepare_vmx (line: 1457)
>> |19062|8:8|reload| (-3) VMware.pm, load (line: 394)
>> |19062|8:8|reload| (-4) new.pm, reload_image (line: 618)
>> |19062|8:8|reload| (-5) new.pm, process (line: 248)
>> |19062|8:8|reload| ---- WARNING ----
>> |19062|8:8|reload| 2011-10-25
>> 15:52:10|19062|8:8|reload|VMware.pm:load(395)|failed to prepare vmx file
>> for linux64base on VM host: vcldell_01
>> |19062|8:8|reload| ( 0) VMware.pm, load (line: 395)
>> |19062|8:8|reload| (-1) new.pm, reload_image (line: 618)
>> |19062|8:8|reload| (-2) new.pm, process (line: 248)
>> |19062|8:8|reload| (-3) vcld, make_new_child (line: 568)
>> |19062|8:8|reload| (-4) vcld, main (line: 346)
>> |19062|8:8|reload| ---- WARNING ----
>> |19062|8:8|reload| 2011-10-25
>> 
>>15:52:10|19062|8:8|reload|new.pm:reload_image(623)|vmwarelinux-base64linu
>>x1
>> 9-v0 failed to load on linux64base, returning
>> |19062|8:8|reload| ( 0) new.pm, reload_image (line: 623)
>> |19062|8:8|reload| (-1) new.pm, process (line: 248)
>> |19062|8:8|reload| (-2) vcld, make_new_child (line: 568)
>> |19062|8:8|reload| (-3) vcld, main (line: 346)
>> 2011-10-25 
>>15:52:10|19062|8:8|reload|utils.pm:insertloadlog(3875)|inserted
>> computer=14, loadimagefailed, vmwarelinux-base64linux19-v0 failed to
>>load
>> on linux64base
>> |19062|8:8|reload| ---- WARNING ----
>> |19062|8:8|reload| 2011-10-25
>> 15:52:10|19062|8:8|reload|new.pm:process(295)|failed to load linux64base
>> with vmwarelinux-base64linux19-v0
>> |19062|8:8|reload| ( 0) new.pm, process (line: 295)
>> |19062|8:8|reload| (-1) vcld, make_new_child (line: 568)
>> |19062|8:8|reload| (-2) vcld, main (line: 346)
>> 2011-10-25
>> 
>>15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_state_name(2305)|
>>at
>> tempting to retrieve current state of computer linux64base from the
>> database
>> 2011-10-25
>> 
>>15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_state_name(2336)|
>>re
>> trieved current state of computer linux64base from the database:
>>reloading
>> 2011-10-25
>> 15:52:10|19062|8:8|reload|DataStructure.pm:_automethod(834)|data
>>structure
>> updated: $self->request_data->{reservation}{8}{computer}{state}{name}
>> |19062|8:8|reload| computer_state_name = reloading
>> 2011-10-25
>> 
>>15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_private_ip_addres
>>s(
>> 1581)|attempting to retrieve private IP address for computer:
>>linux64base
>> 2011-10-25
>> 
>>15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_private_ip_addres
>>s(
>> 1585)|retrieved contents of /etc/hosts on this management node, contains
>> 10 lines
>> 2011-10-25
>> 
>>15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_private_ip_addres
>>s(
>> 1645)|returning IP address from /etc/hosts file: 10.0.0.2
>> 2011-10-25 
>>15:52:10|19062|8:8|reload|utils.pm:is_inblockrequest(6163)|zero
>> rows were returned from database select
>> 2011-10-25
>> 
>>15:52:10|19062|8:8|reload|DataStructure.pm:get_image_affiliation_name(203
>>5)
>> |image owner id: 1
>> 2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2709)|database
>> requested (information_schema) does not match handle stored in $ENV{dbh}
>> (vcl:localhost)
>> 2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2760)|database
>> handle stored in $ENV{dbh}
>> 2011-10-25
>> 
>>15:52:10|19062|8:8|reload|DataStructure.pm:retrieve_user_data(1352)|attem
>>pt
>> ing to retrieve and store data for user: user.id = '1'
>> 2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2709)|database
>> requested (vcl) does not match handle stored in $ENV{dbh}
>> (information_schema:localhost)
>> 2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2760)|database
>> handle stored in $ENV{dbh}
>> 2011-10-25
>> 15:52:10|19062|8:8|reload|DataStructure.pm:retrieve_user_data(1415)|data
>> has been retrieved for user: admin (id: 1)
>>
>>
>>
>>
>> On 10/25/11 12:00 PM, "Alexander Patterson"
>> <al...@csueastbay.edu> wrote:
>>
>>>Hello,
>>>
>>> Here is the main issue, You need to have your datastore the location
>>>that you are storing you VM images in the correct place. As of right
>>>now they are looking  in the /vmfs/volumes/local-datastore
>>>
>>>You can either move your images to this folder or change the default
>>>location.
>>>
>>>
>>>To do this go to Virtual Host
>>>Click on VM host Profiles
>>>Click on Configure Profile (Make to to select the VMware ESXI Standard
>>>Localdisk
>>>from the sounds of it you have Local storage and are storing your VM's
>>>locally.
>>>
>>>The Data Store Path can be changed to the current location or you can
>>>move the files the choice is yours. Make sure you have the Virtual
>>>Switches set up
>>>I'm using custom VLAN switch 0 = private and switch 1 = private
>>>You don't have to set a Repository Path but the Data Store Path has to
>>>be correct.
>>>
>>>-Alex
>>>
>>>327|5:5|image| ---- WARNING ----
>>>|5327|5:5|image| 2011-10-25
>>>11:38:43|5327|5:5|image|VMware.pm:_get_datastore_name(5848)|unable to
>>>determine datastore name from path: '/vmfs/volumes/local-datastore',
>>>path
>>>does not begin with any of the datastore paths:
>>>
>>>2011/10/25 Evelio Quiros <ev...@fiu.edu>:
>>>> OK,
>>>>
>>>> After adding the missing javascript, I am able to get the Virtual
>>>>Hosts
>>>> page to display.
>>>>
>>>> I added 10 VMs which have been added to the database, as well as the
>>>>base
>>>> image I want to capture, so 11 in all.
>>>>
>>>> Does VCL require the Vsphere module to add a virtual machine computer
>>>>?
>>>>
>>>> Also, I am using a free version of ESXi. Is there a licensing issue ?
>>>>
>>>>
>>>> I tried once again to capture the base image, and I got this error:
>>>>
>>>>
>>>> VCL::image object could not be created and initialized
>>>> 
>>>>-----------------------------------------------------------------------
>>>>-
>>>> time: 2011-10-25 11:38:43
>>>> caller: vcld:make_new_child(571)
>>>> ( 0) vcld, make_new_child (line: 571)
>>>> (-1) vcld, main (line: 346)
>>>> 
>>>>-----------------------------------------------------------------------
>>>>-
>>>> management node: vcltst.fiu.edu
>>>> reservation PID: 5327
>>>> parent vcld PID: 15838
>>>>
>>>> request ID: 5
>>>> reservation ID: 5
>>>> request state/laststate: image/image
>>>> request start time: 2011-10-25 11:38:35
>>>> request end time: 2011-10-25 12:38:35
>>>> for imaging: no
>>>> log ID: none
>>>>
>>>> computer: redhat64base
>>>> computer id: 12
>>>> computer type: virtualmachine
>>>> computer eth0 MAC address: <undefined>
>>>> computer eth1 MAC address: <undefined>
>>>> computer private IP address: 10.0.0.2
>>>> computer public IP address: 10.106.128.53
>>>> computer in block allocation: no
>>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>>
>>>> vm host: vcldell_01
>>>> vm host ID: 2
>>>> vm host computer ID: 13
>>>> vm profile: VMware ESX - local storage
>>>> vm profile VM path: /vmfs/volumes/local-datastore
>>>> vm profile repository path: 0
>>>> vm profile datastore path: /vmfs/volumes/local-datastore
>>>> vm profile disk type: localdisk
>>>>
>>>> image: vmwarelinux-redhat_linux16-v0
>>>> image display name: redhat_linux
>>>> image ID: 16
>>>> image revision ID: 9
>>>> image size: 1450 MB
>>>> use Sysprep: yes
>>>> root access: yes
>>>> image owner ID: 1
>>>> image owner affiliation: Local
>>>> image revision date created: 2011-10-25 11:38:35
>>>> image revision production: yes
>>>> OS module: VCL::Module::OS::Linux
>>>>
>>>> user: admin
>>>> user name: vcl admin
>>>> user ID: 1
>>>> user affiliation: Local
>>>> 
>>>>-----------------------------------------------------------------------
>>>>-
>>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>>> 2011-10-25
>>>>11:38:41|5327|5:5|image|vSphere_SDK.pm:initialize(1826)|vSphere
>>>> SDK for Perl does not appear to be installed on this managment node,
>>>> unable to load VMware vSphere SDK Perl modules
>>>> 2011-10-25
>>>> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>object
>>>> could not be created: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>> 2011-10-25
>>>> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(613)|computer ID
>>>> argument was specified, retrieving data for computer ID: 13
>>>> 2011-10-25
>>>>11:38:41|5327|5:5|image|DataStructure.pm:_initialize(643)|image
>>>> ID argument was specified: 4, DataStructure object will contain image
>>>> information for the production imagerevision of this image
>>>> 2011-10-25
>>>> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(660)|retrieved
>>>>data
>>>> for imagerevision ID: 4
>>>> 2011-10-25
>>>> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(676)|retrieved
>>>>data
>>>> for image ID: 4
>>>> 2011-10-25
>>>> 
>>>>11:38:41|5327|5:5|image|VMware.pm:get_vmhost_datastructure(1190)|create
>>>>d
>>>> DataStructure object for VM host: vcldell_01
>>>> 2011-10-25
>>>> 
>>>>11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1293)|attemptin
>>>>g
>>>> to load VMware control module:
>>>>VCL::Module::Provisioning::VMware::VIM_SSH
>>>> 2011-10-25
>>>> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>> VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
>>>> 2011-10-25 11:38:41|5327|5:5|image|Module.pm:new(172)|set
>>>>'vmhost_data'
>>>> key for VCL::Module::Provisioning::VMware::VIM_SSH object from
>>>>arguments
>>>> 2011-10-25 11:38:41|5327|5:5|image|Module.pm:new(172)|set 'vmhost_os'
>>>>key
>>>> for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
>>>> 2011-10-25
>>>> 11:38:41|5327|5:5|image|Module.pm:create_mn_os_object(335)|management
>>>>node
>>>> OS object has already been created, address: 219ab58, returning 1
>>>> 2011-10-25
>>>>
>>>>11:38:41|5327|5:5|image|Module.pm:new(200)|VCL::Module::Provisioning::V
>>>>Mw
>>>>ar
>>>> e::VIM_SSH object created for computer redhat64base, address: 1fd9588
>>>> 2011-10-25 11:38:42|5327|5:5|image|VIM_SSH.pm:initialize(138)|VIM
>>>> executable available on VM host: vim-cmd
>>>> 2011-10-25
>>>>
>>>>11:38:42|5327|5:5|image|VIM_SSH.pm:initialize(140)|VCL::Module::Provisi
>>>>on
>>>>in
>>>> g::VMware::VIM_SSH object initialized
>>>> 2011-10-25
>>>> 11:38:42|5327|5:5|image|VMware.pm:get_vmhost_api_object(1320)|created
>>>>API
>>>> object: VCL::Module::Provisioning::VMware::VIM_SSH
>>>> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(278)|VMware on
>>>>VM
>>>> host vcldell_01 will be controlled using vim-cmd via SSH
>>>> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(293)|VMware OS
>>>>and
>>>> API objects created for VM host vcldell_01:
>>>> |5327|5:5|image| VM host OS object type:
>>>>VCL::Module::OS::Linux::UnixLab
>>>> |5327|5:5|image| VMware API object type:
>>>> VCL::Module::Provisioning::VMware::VIM_SSH
>>>> 2011-10-25
>>>> 11:38:42|5327|5:5|image|VMware.pm:get_vmhost_product_name(5405)|VMware
>>>> product being used on VM host vcldell_01: 'VMware ESXi 5.0.0
>>>>build-469512'
>>>> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(307)|product:
>>>> VMware ESXi 5.0.0 build-469512, OS object:
>>>>VCL::Module::OS::Linux::UnixLab
>>>> 2011-10-25 
>>>>11:38:42|5327|5:5|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd
>>>> call count: 1 (hostsvc/datastore/listsummary)
>>>> 2011-10-25 
>>>>11:38:43|5327|5:5|image|VIM_SSH.pm:_run_vim_cmd(208)|executed
>>>> command on VM host vcldell_01: vim-cmd hostsvc/datastore/listsummary
>>>> 2011-10-25
>>>> 11:38:43|5327|5:5|image|VMware.pm:get_datastore_info(5531)|retrieved
>>>> datastore info from VM host:
>>>> |5327|5:5|image| datastore1
>>>> |5327|5:5|image| ---- WARNING ----
>>>> |5327|5:5|image| 2011-10-25
>>>> 11:38:43|5327|5:5|image|VMware.pm:_get_datastore_name(5848)|unable to
>>>> determine datastore name from path: '/vmfs/volumes/local-datastore',
>>>>path
>>>> does not begin with any of the datastore paths:
>>>> |5327|5:5|image| '[datastore1]'
>>>> |5327|5:5|image| '/vmfs/volumes/datastore1'
>>>> |5327|5:5|image| '/vmfs/volumes/4e96b3e5-a6562886-638a-00188be54b59'
>>>> |5327|5:5|image| ( 0) VMware.pm, _get_datastore_name (line: 5848)
>>>> |5327|5:5|image| (-1) VMware.pm, _get_datastore_root_normal_path
>>>>(line:
>>>> 5685)
>>>> |5327|5:5|image| (-2) VMware.pm, _get_normal_path (line: 5775)
>>>> |5327|5:5|image| (-3) VMware.pm, get_vmx_base_directory_path (line:
>>>>2743)
>>>> |5327|5:5|image| (-4) VMware.pm, initialize (line: 313)
>>>> |5327|5:5|image| (-5) Module.pm, new (line: 207)
>>>> |5327|5:5|image| ---- WARNING ----
>>>> |5327|5:5|image| 2011-10-25
>>>>
>>>>11:38:43|5327|5:5|image|VMware.pm:_get_datastore_root_normal_path(5687)
>>>>|f
>>>>ai
>>>> led to determine datastore root normal path, unable to determine
>>>>datastore
>>>> name: /vmfs/volumes/local-datastore
>>>> |5327|5:5|image| ( 0) VMware.pm, _get_datastore_root_normal_path
>>>>(line:
>>>> 5687)
>>>> |5327|5:5|image| (-1) VMware.pm, _get_normal_path (line: 5775)
>>>> |5327|5:5|image| (-2) VMware.pm, get_vmx_base_directory_path (line:
>>>>2743)
>>>> |5327|5:5|image| (-3) VMware.pm, initialize (line: 313)
>>>> |5327|5:5|image| (-4) Module.pm, new (line: 207)
>>>> |5327|5:5|image| (-5) Module.pm, create_provisioning_object (line:
>>>>423)
>>>> |5327|5:5|image| ---- WARNING ----
>>>> |5327|5:5|image| 2011-10-25
>>>> 11:38:43|5327|5:5|image|VMware.pm:_get_normal_path(5777)|unable to
>>>> determine normal path, failed to determine datastore root normal path:
>>>> /vmfs/volumes/local-datastore
>>>> |5327|5:5|image| ( 0) VMware.pm, _get_normal_path (line: 5777)
>>>> |5327|5:5|image| (-1) VMware.pm, get_vmx_base_directory_path (line:
>>>>2743)
>>>> |5327|5:5|image| (-2) VMware.pm, initialize (line: 313)
>>>> |5327|5:5|image| (-3) Module.pm, new (line: 207)
>>>> |5327|5:5|image| (-4) Module.pm, create_provisioning_object (line:
>>>>423)
>>>> |5327|5:5|image| (-5) State.pm, initialize (line: 117)
>>>> |5327|5:5|image| ---- WARNING ----
>>>> |5327|5:5|image| 2011-10-25
>>>>
>>>>11:38:43|5327|5:5|image|VMware.pm:get_vmx_base_directory_path(2749)|una
>>>>bl
>>>>e
>>>> to determine the vmx base directory path, failed to convert path
>>>> configured in the VM profile to a normal path:
>>>> /vmfs/volumes/local-datastore
>>>> |5327|5:5|image| ( 0) VMware.pm, get_vmx_base_directory_path (line:
>>>>2749)
>>>> |5327|5:5|image| (-1) VMware.pm, initialize (line: 313)
>>>> |5327|5:5|image| (-2) Module.pm, new (line: 207)
>>>> |5327|5:5|image| (-3) Module.pm, create_provisioning_object (line:
>>>>423)
>>>> |5327|5:5|image| (-4) State.pm, initialize (line: 117)
>>>> |5327|5:5|image| (-5) Module.pm, new (line: 207)
>>>> |5327|5:5|image| ---- WARNING ----
>>>> |5327|5:5|image| 2011-10-25
>>>> 11:38:43|5327|5:5|image|VMware.pm:initialize(315)|unable to determine
>>>>vmx
>>>> base directory path on VM host vcldell_01
>>>> |5327|5:5|image| ( 0) VMware.pm, initialize (line: 315)
>>>> |5327|5:5|image| (-1) Module.pm, new (line: 207)
>>>> |5327|5:5|image| (-2) Module.pm, create_provisioning_object (line:
>>>>423)
>>>> |5327|5:5|image| (-3) State.pm, initialize (line: 117)
>>>> |5327|5:5|image| (-4) Module.pm, new (line: 207)
>>>> |5327|5:5|image| (-5) vcld, make_new_child (line: 564)
>>>> |5327|5:5|image| ---- WARNING ----
>>>> |5327|5:5|image| 2011-10-25
>>>>
>>>>11:38:43|5327|5:5|image|Module.pm:create_provisioning_object(431)|provi
>>>>si
>>>>on
>>>> ing object could not be created, returning 0
>>>> |5327|5:5|image| ( 0) Module.pm, create_provisioning_object (line:
>>>>431)
>>>> |5327|5:5|image| (-1) State.pm, initialize (line: 117)
>>>> |5327|5:5|image| (-2) Module.pm, new (line: 207)
>>>> |5327|5:5|image| (-3) vcld, make_new_child (line: 564)
>>>> |5327|5:5|image| (-4) vcld, main (line: 346)
>>>> |5327|5:5|image| ---- WARNING ----
>>>> |5327|5:5|image| 2011-10-25
>>>> 11:38:43|5327|5:5|image|State.pm:initialize(118)|failed to create
>>>> provisioning object
>>>> |5327|5:5|image| ( 0) State.pm, initialize (line: 118)
>>>> |5327|5:5|image| (-1) Module.pm, new (line: 207)
>>>> |5327|5:5|image| (-2) vcld, make_new_child (line: 564)
>>>> |5327|5:5|image| (-3) vcld, main (line: 346)
>>>> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(829)|VCL::image
>>>> destructor called, address: 1e47a28
>>>> 2011-10-25
>>>>
>>>>11:38:43|5327|5:5|image|utils.pm:delete_computerloadlog_reservation(674
>>>>2)
>>>>|r
>>>> emoving computerloadlog entries matching loadstate = begin
>>>> 2011-10-25
>>>>
>>>>11:38:43|5327|5:5|image|utils.pm:delete_computerloadlog_reservation(678
>>>>9)
>>>>|d
>>>> eleted rows from computerloadlog for reservation id=5
>>>> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(848)|number of
>>>> database handles state process created: 1
>>>> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(876)|VCL::image
>>>> process duration: 4 seconds
>>>> 2011-10-25
>>>>
>>>>11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_addres
>>>>s(
>>>>15
>>>> 81)|attempting to retrieve private IP address for computer:
>>>>redhat64base
>>>> 2011-10-25
>>>>
>>>>11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_addres
>>>>s(
>>>>15
>>>> 85)|retrieved contents of /etc/hosts on this management node, contains
>>>>10
>>>> lines
>>>> 2011-10-25
>>>>
>>>>11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_addres
>>>>s(
>>>>16
>>>> 45)|returning IP address from /etc/hosts file: 10.0.0.2
>>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2703)|unable to
>>>>use
>>>> database handle stored in $ENV{dbh}
>>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
>>>> handle stored in $ENV{dbh}
>>>> 2011-10-25 
>>>>11:38:43|5327|5:5|image|utils.pm:is_inblockrequest(6163)|zero
>>>> rows were returned from database select
>>>> 2011-10-25
>>>>
>>>>11:38:43|5327|5:5|image|DataStructure.pm:get_image_affiliation_name(203
>>>>5)
>>>>|i
>>>> mage owner id: 1
>>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2709)|database
>>>> requested (information_schema) does not match handle stored in 
>>>>$ENV{dbh}
>>>> (vcl:localhost)
>>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
>>>> handle stored in $ENV{dbh}
>>>> 2011-10-25
>>>>
>>>>11:38:43|5327|5:5|image|DataStructure.pm:retrieve_user_data(1352)|attem
>>>>pt
>>>>in
>>>> g to retrieve and store data for user: user.id = '1'
>>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2709)|database
>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>> (information_schema:localhost)
>>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
>>>> handle stored in $ENV{dbh}
>>>> 2011-10-25
>>>> 11:38:43|5327|5:5|image|DataStructure.pm:retrieve_user_data(1415)|data
>>>>has
>>>> been retrieved for user: admin (id: 1)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 10/25/11 10:26 AM, "Aaron Coburn" <ac...@amherst.edu> wrote:
>>>>
>>>>>Al,
>>>>>if you plan to use the vSphere API, then you will need to install the
>>>>>vSphere SDK for Perl separately. The perl modules are available here 
>>>>>--
>>>>>just make sure that you download the release that matches your vCenter
>>>>>version.
>>>>>
>>>>>http://www.vmware.com/support/developer/viperltoolkit/
>>>>>
>>>>>Aaron Coburn
>>>>>
>>>>>
>>>>>On Oct 25, 2011, at 10:03 AM, Evelio Quiros wrote:
>>>>>
>>>>>> Thanks again Aaron. It seems we are taking baby steps here.
>>>>>>
>>>>>> Ok, next issue: When I click "Configure Host" in the vcl web
>>>>>>interface,
>>>>>> nothing happens.
>>>>>>
>>>>>> My Vmware server is listed there. It is in "vmhostinuse" state.
>>>>>>
>>>>>> I noticed some complaints below about the Vsphere perl module not
>>>>>>being
>>>>>> installed.
>>>>>> I thought that was done in the "install_perl_libraries script.
>>>>>>
>>>>>> Thanks again for all your help.
>>>>>>
>>>>>> Al Quiros
>>>>>>
>>>>>>
>>>>>> On 10/25/11 9:43 AM, "Aaron Peeler" <fa...@ncsu.edu> wrote:
>>>>>>
>>>>>>> In the log output your missing the vmhost information.
>>>>>>>
>>>>>>> Make sure your vm host server have a correctly configured vmhost
>>>>>>> profile and you have assigned your vms to the virtual host server 
>>>>>>>by
>>>>>>> using the Virtual Host interface.
>>>>>>>
>>>>>>>
>>>>>>>https://cwiki.apache.org/confluence/display/VCL/VCL+2.2.1+-+Further+
>>>>>>>St
>>>>>>>ep
>>>>>>>s+
>>>>>>> if+Using+VMware
>>>>>>> 
>>>>>>>https://cwiki.apache.org/confluence/display/VCL/VMware+Configuration
>>>>>>>
>>>>>>> I'm not seeing the virtual host interface mentioned directly in the
>>>>>>> vcl 2.2.1 install guide. I'll added that to the first link.
>>>>>>>
>>>>>>> Here is a link from a bootcamp that you can review this morning 
>>>>>>>while
>>>>>>> I work on adding the content to Apache VCL:
>>>>>>>
>>>>>>>https://sites.google.com/a/ncsu.edu/vcl-bootcamp/exercises/assign-a-
>>>>>>>vm
>>>>>>>-t
>>>>>>>o-
>>>>>>> a-virtual-host
>>>>>>>
>>>>>>> Aaron
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Oct 25, 2011 at 9:19 AM, Evelio Quiros <ev...@fiu.edu>
>>>>>>>wrote:
>>>>>>>> Thank you Aaron.
>>>>>>>>
>>>>>>>> Ok, now it can resolve the name redhat64base to the private IP
>>>>>>>>address
>>>>>>>> 10.0.0.2.
>>>>>>>> I tried to add the base image as the name linux64.
>>>>>>>> It resides in the database as redhat64base, with the public IP of
>>>>>>>> 10.106.128.53, and set as available.
>>>>>>>> I'm not sure what this error message is telling meŠ
>>>>>>>>
>>>>>>>> VCL::image object could not be created and initialized
>>>>>>>>
>>>>>>>>-------------------------------------------------------------------
>>>>>>>>--
>>>>>>>>--
>>>>>>>>-
>>>>>>>> time: 2011-10-25 09:30:44
>>>>>>>> caller: vcld:make_new_child(571)
>>>>>>>> ( 0) vcld, make_new_child (line: 571)
>>>>>>>> (-1) vcld, main (line: 346)
>>>>>>>>
>>>>>>>>-------------------------------------------------------------------
>>>>>>>>--
>>>>>>>>--
>>>>>>>>-
>>>>>>>> management node: vcltst.fiu.edu
>>>>>>>> reservation PID: 31318
>>>>>>>> parent vcld PID: 15838
>>>>>>>>
>>>>>>>> request ID: 4
>>>>>>>> reservation ID: 4
>>>>>>>> request state/laststate: image/image
>>>>>>>> request start time: 2011-10-25 09:30:37
>>>>>>>> request end time: 2011-10-25 10:30:37
>>>>>>>> for imaging: no
>>>>>>>> log ID: none
>>>>>>>>
>>>>>>>> computer: redhat64base
>>>>>>>> computer id: 12
>>>>>>>> computer type: blade
>>>>>>>> computer eth0 MAC address: <undefined>
>>>>>>>> computer eth1 MAC address: <undefined>
>>>>>>>> computer private IP address: 10.0.0.2
>>>>>>>> computer public IP address: 10.106.128.53
>>>>>>>> computer in block allocation: no
>>>>>>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>>>>>>
>>>>>>>> image: vmwarelinux-linux6414-v0
>>>>>>>> image display name: linux64
>>>>>>>> image ID: 14
>>>>>>>> image revision ID: 8
>>>>>>>> image size: 1450 MB
>>>>>>>> use Sysprep: yes
>>>>>>>> root access: yes
>>>>>>>> image owner ID: 1
>>>>>>>> image owner affiliation: Local
>>>>>>>> image revision date created: 2011-10-25 09:30:37
>>>>>>>> image revision production: yes
>>>>>>>> OS module: VCL::Module::OS::Linux
>>>>>>>>
>>>>>>>> user: admin
>>>>>>>> user name: vcl admin
>>>>>>>> user ID: 1
>>>>>>>> user affiliation: Local
>>>>>>>>
>>>>>>>>-------------------------------------------------------------------
>>>>>>>>--
>>>>>>>>--
>>>>>>>>-
>>>>>>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|atte
>>>>>>>>mp
>>>>>>>>ti
>>>>>>>>ng
>>>>>>>> to load VMware control module:
>>>>>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|load
>>>>>>>>ed
>>>>>>>> VMware control module:
>>>>>>>>VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>>'vmhost_data'
>>>>>>>> key for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>>> arguments
>>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>>'vmhost_os'
>>>>>>>> key
>>>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>>>arguments
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|managem
>>>>>>>>en
>>>>>>>>t
>>>>>>>> node OS object has already been created, address: 21956b8,
>>>>>>>>returning 1
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioni
>>>>>>>>ng
>>>>>>>>::
>>>>>>>>VM
>>>>>>>> wa
>>>>>>>> re::vSphere_SDK object created for computer redhat64base, address:
>>>>>>>> 21e6980
>>>>>>>> 2011-10-25
>>>>>>>> 09:30:43|31318|4:4|image|vSphere_SDK.pm:initialize(1826)|vSphere 
>>>>>>>>SDK
>>>>>>>>for
>>>>>>>> Perl does not appear to be installed on this managment node, 
>>>>>>>>unable
>>>>>>>>to
>>>>>>>> load VMware vSphere SDK Perl modules
>>>>>>>> 2011-10-25
>>>>>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>>>> object
>>>>>>>> could not be created: 
>>>>>>>>VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspo
>>>>>>>>nd
>>>>>>>>in
>>>>>>>>g
>>>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>>>> 
>>>>>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{computerid}
>>>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>>1161)
>>>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 
>>>>>>>>1282)
>>>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspo
>>>>>>>>nd
>>>>>>>>in
>>>>>>>>g
>>>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>>>>
>>>>>>>>
>>>>>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{vmprofile}{
>>>>>>>>im
>>>>>>>>ag
>>>>>>>>ei
>>>>>>>> d}
>>>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>>1162)
>>>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 
>>>>>>>>1282)
>>>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_datastructure(1190)|c
>>>>>>>>re
>>>>>>>>at
>>>>>>>>ed
>>>>>>>> DataStructure object for VM host: redhat64base
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|atte
>>>>>>>>mp
>>>>>>>>ti
>>>>>>>>ng
>>>>>>>> to load VMware control module:
>>>>>>>> VCL::Module::Provisioning::VMware::VIM_SSH
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|load
>>>>>>>>ed
>>>>>>>> VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
>>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>>'vmhost_data'
>>>>>>>> key for VCL::Module::Provisioning::VMware::VIM_SSH object from
>>>>>>>>arguments
>>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>>'vmhost_os'
>>>>>>>> key
>>>>>>>> for VCL::Module::Provisioning::VMware::VIM_SSH object from 
>>>>>>>>arguments
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|managem
>>>>>>>>en
>>>>>>>>t
>>>>>>>> node OS object has already been created, address: 21956b8,
>>>>>>>>returning 1
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioni
>>>>>>>>ng
>>>>>>>>::
>>>>>>>>VM
>>>>>>>> wa
>>>>>>>> re::VIM_SSH object created for computer redhat64base, address:
>>>>>>>>24f7888
>>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|VIM_SSH.pm:initialize(126)|VIM
>>>>>>>> executable is not available on the VM host, output:
>>>>>>>> |31318|4:4|image| bash: vim-cmd: command not found
>>>>>>>> |31318|4:4|image| bash: vmware-vim-cmd: command not found
>>>>>>>> 2011-10-25
>>>>>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>>>> object
>>>>>>>> could not be created: VCL::Module::Provisioning::VMware::VIM_SSH
>>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspo
>>>>>>>>nd
>>>>>>>>in
>>>>>>>>g
>>>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>>>> 
>>>>>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{computerid}
>>>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>>1161)
>>>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 
>>>>>>>>1282)
>>>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspo
>>>>>>>>nd
>>>>>>>>in
>>>>>>>>g
>>>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>>>>
>>>>>>>>
>>>>>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{vmprofile}{
>>>>>>>>im
>>>>>>>>ag
>>>>>>>>ei
>>>>>>>> d}
>>>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>>1162)
>>>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 
>>>>>>>>1282)
>>>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_datastructure(1190)|c
>>>>>>>>re
>>>>>>>>at
>>>>>>>>ed
>>>>>>>> DataStructure object for VM host: redhat64base
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|atte
>>>>>>>>mp
>>>>>>>>ti
>>>>>>>>ng
>>>>>>>> to load VMware control module:
>>>>>>>> VCL::Module::Provisioning::VMware::vmware_cmd
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|load
>>>>>>>>ed
>>>>>>>> VMware control module: 
>>>>>>>>VCL::Module::Provisioning::VMware::vmware_cmd
>>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>>'vmhost_data'
>>>>>>>> key for VCL::Module::Provisioning::VMware::vmware_cmd object from
>>>>>>>> arguments
>>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>>'vmhost_os'
>>>>>>>> key
>>>>>>>> for VCL::Module::Provisioning::VMware::vmware_cmd object from
>>>>>>>>arguments
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|managem
>>>>>>>>en
>>>>>>>>t
>>>>>>>> node OS object has already been created, address: 21956b8,
>>>>>>>>returning 1
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioni
>>>>>>>>ng
>>>>>>>>::
>>>>>>>>VM
>>>>>>>> wa
>>>>>>>> re::vmware_cmd object created for computer redhat64base, address:
>>>>>>>> 251d1e0
>>>>>>>> 2011-10-25
>>>>>>>> 09:30:44|31318|4:4|image|vmware_cmd.pm:initialize(107)|vmware-cmd 
>>>>>>>>is
>>>>>>>>not
>>>>>>>> available on the VM host, output:
>>>>>>>> |31318|4:4|image| bash: vmware-cmd: command not found
>>>>>>>> 2011-10-25
>>>>>>>> 09:30:44|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>>>> object
>>>>>>>> could not be created: 
>>>>>>>>VCL::Module::Provisioning::VMware::vmware_cmd
>>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>> 09:30:44|31318|4:4|image|VMware.pm:initialize(285)|failed to 
>>>>>>>>create
>>>>>>>>an
>>>>>>>> object to control VMware on VM host: redhat64base
>>>>>>>> |31318|4:4|image| ( 0) VMware.pm, initialize (line: 285)
>>>>>>>> |31318|4:4|image| (-1) Module.pm, new (line: 207)
>>>>>>>> |31318|4:4|image| (-2) Module.pm, create_provisioning_object 
>>>>>>>>(line:
>>>>>>>>423)
>>>>>>>> |31318|4:4|image| (-3) State.pm, initialize (line: 117)
>>>>>>>> |31318|4:4|image| (-4) Module.pm, new (line: 207)
>>>>>>>> |31318|4:4|image| (-5) vcld, make_new_child (line: 564)
>>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:44|31318|4:4|image|Module.pm:create_provisioning_object(431)|
>>>>>>>>pr
>>>>>>>>ov
>>>>>>>>is
>>>>>>>> io
>>>>>>>> ning object could not be created, returning 0
>>>>>>>> |31318|4:4|image| ( 0) Module.pm, create_provisioning_object 
>>>>>>>>(line:
>>>>>>>>431)
>>>>>>>> |31318|4:4|image| (-1) State.pm, initialize (line: 117)
>>>>>>>> |31318|4:4|image| (-2) Module.pm, new (line: 207)
>>>>>>>> |31318|4:4|image| (-3) vcld, make_new_child (line: 564)
>>>>>>>> |31318|4:4|image| (-4) vcld, main (line: 346)
>>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>> 09:30:44|31318|4:4|image|State.pm:initialize(118)|failed to create
>>>>>>>> provisioning object
>>>>>>>> |31318|4:4|image| ( 0) State.pm, initialize (line: 118)
>>>>>>>> |31318|4:4|image| (-1) Module.pm, new (line: 207)
>>>>>>>> |31318|4:4|image| (-2) vcld, make_new_child (line: 564)
>>>>>>>> |31318|4:4|image| (-3) vcld, main (line: 346)
>>>>>>>> 2011-10-25 
>>>>>>>>09:30:44|31318|4:4|image|State.pm:DESTROY(829)|VCL::image
>>>>>>>> destructor called, address: 1e47818
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:44|31318|4:4|image|utils.pm:delete_computerloadlog_reservatio
>>>>>>>>n(
>>>>>>>>67
>>>>>>>>42
>>>>>>>> )|
>>>>>>>> removing computerloadlog entries matching loadstate = begin
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:44|31318|4:4|image|utils.pm:delete_computerloadlog_reservatio
>>>>>>>>n(
>>>>>>>>67
>>>>>>>>89
>>>>>>>> )|
>>>>>>>> deleted rows from computerloadlog for reservation id=4
>>>>>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(848)|number 
>>>>>>>>of
>>>>>>>> database handles state process created: 1
>>>>>>>> 2011-10-25 
>>>>>>>>09:30:44|31318|4:4|image|State.pm:DESTROY(876)|VCL::image
>>>>>>>> process duration: 2 seconds
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_a
>>>>>>>>dd
>>>>>>>>re
>>>>>>>>ss
>>>>>>>> (1
>>>>>>>> 581)|attempting to retrieve private IP address for computer:
>>>>>>>> redhat64base
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_a
>>>>>>>>dd
>>>>>>>>re
>>>>>>>>ss
>>>>>>>> (1
>>>>>>>> 585)|retrieved contents of /etc/hosts on this management node,
>>>>>>>>contains
>>>>>>>> 9
>>>>>>>> lines
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_a
>>>>>>>>dd
>>>>>>>>re
>>>>>>>>ss
>>>>>>>> (1
>>>>>>>> 645)|returning IP address from /etc/hosts file: 10.0.0.2
>>>>>>>> 2011-10-25 
>>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2703)|unable
>>>>>>>>to
>>>>>>>> use
>>>>>>>> database handle stored in $ENV{dbh}
>>>>>>>> 2011-10-25
>>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>>>>> handle stored in $ENV{dbh}
>>>>>>>> 2011-10-25
>>>>>>>> 09:30:44|31318|4:4|image|utils.pm:is_inblockrequest(6163)|zero
>>>>>>>> rows were returned from database select
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_image_affiliation_nam
>>>>>>>>e(
>>>>>>>>20
>>>>>>>>35
>>>>>>>> )|
>>>>>>>> image owner id: 1
>>>>>>>> 2011-10-25
>>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2709)|database
>>>>>>>> requested (information_schema) does not match handle stored in
>>>>>>>>$ENV{dbh}
>>>>>>>> (vcl:localhost)
>>>>>>>> 2011-10-25
>>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>>>>> handle stored in $ENV{dbh}
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:retrieve_user_data(1352)|
>>>>>>>>at
>>>>>>>>te
>>>>>>>>mp
>>>>>>>> ti
>>>>>>>> ng to retrieve and store data for user: user.id = '1'
>>>>>>>> 2011-10-25
>>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2709)|database
>>>>>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>>>>>> (information_schema:localhost)
>>>>>>>> 2011-10-25
>>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>>>>> handle stored in $ENV{dbh}
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:retrieve_user_data(1415)|
>>>>>>>>da
>>>>>>>>ta
>>>>>>>> has been retrieved for user: admin (id: 1)
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 10/25/11 9:04 AM, "Aaron Peeler" <aa...@ncsu.edu> wrote:
>>>>>>>>
>>>>>>>>> Al,
>>>>>>>>>
>>>>>>>>> The hostname has to resolve.
>>>>>>>>>
>>>>>>>>> Put an entry in your /etc/hosts file.
>>>>>>>>>
>>>>>>>>> Aaron
>>>>>>>>>
>>>>>>>>> On Tue, Oct 25, 2011 at 8:52 AM, Evelio Quiros <ev...@fiu.edu>
>>>>>>>>>wrote:
>>>>>>>>>> Hello,
>>>>>>>>>> I am getting an error when I try to capture a linux base image 
>>>>>>>>>>in
>>>>>>>>>>vcl.
>>>>>>>>>> I am
>>>>>>>>>> following the instructions, but perhaps some parts of these may
>>>>>>>>>>have
>>>>>>>>>> been
>>>>>>>>>> misinterpreted.
>>>>>>>>>> My VCL server is at 10.0.0.1. My Vmware based virtual machine is
>>>>>>>>>>at
>>>>>>>>>> 10.0.0.2. I can ssh without passwords using keys from the vcl
>>>>>>>>>>server
>>>>>>>>>> to
>>>>>>>>>> the
>>>>>>>>>> VM.
>>>>>>>>>> The computer has been added to the database as hostname
>>>>>>>>>>redhat64base,
>>>>>>>>>> although I have no DNS entry to resolve that name, so I use it's
>>>>>>>>>> private IP
>>>>>>>>>> of 10.0.0.2.
>>>>>>>>>> Below is the result of vcld trying to capture the computer to
>>>>>>>>>>create a
>>>>>>>>>> new
>>>>>>>>>> base imageŠ.Any ideas about what could be wrong ?
>>>>>>>>>> Thanks,
>>>>>>>>>> Al Quiros
>>>>>>>>>>
>>>>>>>>>> VCL::image object could not be created and initialized
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>-----------------------------------------------------------------
>>>>>>>>>>--
>>>>>>>>>>--
>>>>>>>>>>--
>>>>>>>>>> -
>>>>>>>>>> time: 2011-10-25 08:58:38
>>>>>>>>>> caller: vcld:make_new_child(571)
>>>>>>>>>> ( 0) vcld, make_new_child (line: 571)
>>>>>>>>>> (-1) vcld, main (line: 346)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>-----------------------------------------------------------------
>>>>>>>>>>--
>>>>>>>>>>--
>>>>>>>>>>--
>>>>>>>>>> -
>>>>>>>>>> management node: vcltst.fiu.edu
>>>>>>>>>> reservation PID: 29609
>>>>>>>>>> parent vcld PID: 15838
>>>>>>>>>> request ID: 2
>>>>>>>>>> reservation ID: 2
>>>>>>>>>> request state/laststate: image/image
>>>>>>>>>> request start time: 2011-10-25 08:58:37
>>>>>>>>>> request end time: 2011-10-25 09:58:37
>>>>>>>>>> for imaging: no
>>>>>>>>>> log ID: none
>>>>>>>>>> computer: redhat64base
>>>>>>>>>> computer id: 12
>>>>>>>>>> computer type: blade
>>>>>>>>>> computer eth0 MAC address: <undefined>
>>>>>>>>>> computer eth1 MAC address: <undefined>
>>>>>>>>>> computer private IP address: <undefined>
>>>>>>>>>> computer public IP address: 10.0.0.2
>>>>>>>>>> computer in block allocation: no
>>>>>>>>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>>>>>>>> image: vmwarelinux-redhat64linux8-v0
>>>>>>>>>> image display name: redhat64linux
>>>>>>>>>> image ID: 8
>>>>>>>>>> image revision ID: 6
>>>>>>>>>> image size: 1450 MB
>>>>>>>>>> use Sysprep: yes
>>>>>>>>>> root access: yes
>>>>>>>>>> image owner ID: 1
>>>>>>>>>> image owner affiliation: Local
>>>>>>>>>> image revision date created: 2011-10-25 08:58:37
>>>>>>>>>> image revision production: yes
>>>>>>>>>> OS module: VCL::Module::OS::Linux
>>>>>>>>>> user: admin
>>>>>>>>>> user name: vcl admin
>>>>>>>>>> user ID: 1
>>>>>>>>>> user affiliation: Local
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>-----------------------------------------------------------------
>>>>>>>>>>--
>>>>>>>>>>--
>>>>>>>>>>--
>>>>>>>>>> -
>>>>>>>>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>>>>>>>>> 2011-10-25
>>>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_os_object(1238)|VM
>>>>>>>>>> host OS module loaded: VCL::Module::OS::Linux
>>>>>>>>>> 2011-10-25
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_mn_os_object(335)|manag
>>>>>>>>>>em
>>>>>>>>>>en
>>>>>>>>>>t
>>>>>>>>>> node
>>>>>>>>>> OS object has already been created, address: 1fbe730, returning 
>>>>>>>>>>1
>>>>>>>>>> 2011-10-25
>>>>>>>>>> 
>>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:new(196)|VCL::Module::OS::Linu
>>>>>>>>>>x
>>>>>>>>>> object
>>>>>>>>>> created for image vmwarelinux-redhat64linux8-v0, address: 
>>>>>>>>>>24f12f0
>>>>>>>>>> 2011-10-25
>>>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_os_object(1244)|VM
>>>>>>>>>> host OS object created: VCL::Module::OS::Linux
>>>>>>>>>> 2011-10-25 
>>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:run_command(8998)|$?
>>>>>>>>>>is
>>>>>>>>>> set to
>>>>>>>>>> -1, setting exit status to 0, Perl bug likely encountered
>>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>> 08:58:38|29609|2:2|image|utils.pm:nmap_port(2645)|error occurred
>>>>>>>>>> running
>>>>>>>>>> nmap command: '/usr/bin/nmap redhat64base -P0 -p 22 -T
>>>>>>>>>>Aggressive',
>>>>>>>>>> output:
>>>>>>>>>> |29609|2:2|image| Starting Nmap 5.21 ( http://nmap.org ) at
>>>>>>>>>>2011-10-25
>>>>>>>>>> 08:58
>>>>>>>>>> EDT
>>>>>>>>>> |29609|2:2|image| Failed to resolve given hostname/IP:
>>>>>>>>>>redhat64base.
>>>>>>>>>> Note
>>>>>>>>>> that you can't use '/mask' AND '1-4,7,100-' style IP ranges
>>>>>>>>>> |29609|2:2|image| WARNING: No targets were specified, so 0 hosts
>>>>>>>>>> scanned.
>>>>>>>>>> |29609|2:2|image| Nmap done: 0 IP addresses (0 hosts up) scanned
>>>>>>>>>>in
>>>>>>>>>> 0.05
>>>>>>>>>> seconds
>>>>>>>>>> |29609|2:2|image| ( 0) utils.pm, nmap_port (line: 2645)
>>>>>>>>>> |29609|2:2|image| (-1) OS.pm, is_ssh_responding (line: 383)
>>>>>>>>>> |29609|2:2|image| (-2) VMware.pm, initialize (line: 252)
>>>>>>>>>> |29609|2:2|image| (-3) Module.pm, new (line: 207)
>>>>>>>>>> |29609|2:2|image| (-4) Module.pm, create_provisioning_object
>>>>>>>>>>(line:
>>>>>>>>>> 423)
>>>>>>>>>> |29609|2:2|image| (-5) State.pm, initialize (line: 117)
>>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>> 08:58:38|29609|2:2|image|utils.pm:nmap_port(2645)|error occurred
>>>>>>>>>> running
>>>>>>>>>> nmap command: '/usr/bin/nmap redhat64base -P0 -p 24 -T
>>>>>>>>>>Aggressive',
>>>>>>>>>> output:
>>>>>>>>>> |29609|2:2|image| Starting Nmap 5.21 ( http://nmap.org ) at
>>>>>>>>>>2011-10-25
>>>>>>>>>> 08:58
>>>>>>>>>> EDT
>>>>>>>>>> |29609|2:2|image| Failed to resolve given hostname/IP:
>>>>>>>>>>redhat64base.
>>>>>>>>>> Note
>>>>>>>>>> that you can't use '/mask' AND '1-4,7,100-' style IP ranges
>>>>>>>>>> |29609|2:2|image| WARNING: No targets were specified, so 0 hosts
>>>>>>>>>> scanned.
>>>>>>>>>> |29609|2:2|image| Nmap done: 0 IP addresses (0 hosts up) scanned
>>>>>>>>>>in
>>>>>>>>>> 0.05
>>>>>>>>>> seconds
>>>>>>>>>> |29609|2:2|image| ( 0) utils.pm, nmap_port (line: 2645)
>>>>>>>>>> |29609|2:2|image| (-1) OS.pm, is_ssh_responding (line: 384)
>>>>>>>>>> |29609|2:2|image| (-2) VMware.pm, initialize (line: 252)
>>>>>>>>>> |29609|2:2|image| (-3) Module.pm, new (line: 207)
>>>>>>>>>> |29609|2:2|image| (-4) Module.pm, create_provisioning_object
>>>>>>>>>>(line:
>>>>>>>>>> 423)
>>>>>>>>>> |29609|2:2|image| (-5) State.pm, initialize (line: 117)
>>>>>>>>>> 2011-10-25
>>>>>>>>>> 
>>>>>>>>>>08:58:38|29609|2:2|image|OS.pm:is_ssh_responding(386)|redhat64bas
>>>>>>>>>>e
>>>>>>>>>>is
>>>>>>>>>> NOT
>>>>>>>>>> responding to SSH, ports 22 or 24 are both closed
>>>>>>>>>> 2011-10-25
>>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:initialize(257)|unable
>>>>>>>>>> to
>>>>>>>>>> control OS of VM host redhat64base using VCL::Module::OS::Linux 
>>>>>>>>>>OS
>>>>>>>>>> object
>>>>>>>>>> because VM host is not responding to SSH
>>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:_automethod(812)|corres
>>>>>>>>>>po
>>>>>>>>>>nd
>>>>>>>>>>in
>>>>>>>>>> g
>>>>>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>>>>>>
>>>>>>>>>>$self->request_data->{reservation}{2}{computer}{vmhost}{computeri
>>>>>>>>>>d}
>>>>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>>>>> |29609|2:2|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>>>>> |29609|2:2|image| (-2) VMware.pm, get_vmhost_datastructure 
>>>>>>>>>>(line:
>>>>>>>>>> 1161)
>>>>>>>>>> |29609|2:2|image| (-3) VMware.pm, get_vmhost_api_object (line:
>>>>>>>>>>1282)
>>>>>>>>>> |29609|2:2|image| (-4) VMware.pm, initialize (line: 265)
>>>>>>>>>> |29609|2:2|image| (-5) Module.pm, new (line: 207)
>>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:_automethod(812)|corres
>>>>>>>>>>po
>>>>>>>>>>nd
>>>>>>>>>>in
>>>>>>>>>> g
>>>>>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>$self->request_data->{reservation}{2}{computer}{vmhost}{vmprofile
>>>>>>>>>>}{
>>>>>>>>>>im
>>>>>>>>>>ag
>>>>>>>>>> ei
>>>>>>>>>> d}
>>>>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>>>>> |29609|2:2|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>>>>> |29609|2:2|image| (-2) VMware.pm, get_vmhost_datastructure 
>>>>>>>>>>(line:
>>>>>>>>>> 1162)
>>>>>>>>>> |29609|2:2|image| (-3) VMware.pm, get_vmhost_api_object (line:
>>>>>>>>>>1282)
>>>>>>>>>> |29609|2:2|image| (-4) VMware.pm, initialize (line: 265)
>>>>>>>>>> |29609|2:2|image| (-5) Module.pm, new (line: 207)
>>>>>>>>>> 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_datastructure(1190)
>>>>>>>>>>|c
>>>>>>>>>>re
>>>>>>>>>>at
>>>>>>>>>> ed
>>>>>>>>>> DataStructure object for VM host: redhat64base
>>>>>>>>>> 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1293)|at
>>>>>>>>>>te
>>>>>>>>>>mp
>>>>>>>>>>ti
>>>>>>>>>> ng
>>>>>>>>>> to
>>>>>>>>>> load VMware control module:
>>>>>>>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>>>> 2011-10-25
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1299)|lo
>>>>>>>>>>ad
>>>>>>>>>>ed
>>>>>>>>>> VMware
>>>>>>>>>> control module: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|Module.pm:new(172)|set
>>>>>>>>>> 'vmhost_data' key
>>>>>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>>>>> arguments
>>>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|Module.pm:new(172)|set
>>>>>>>>>>'vmhost_os'
>>>>>>>>>> key
>>>>>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>>>>> arguments
>>>>>>>>>> 2011-10-25
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_mn_os_object(335)|manag
>>>>>>>>>>em
>>>>>>>>>>en
>>>>>>>>>>t
>>>>>>>>>> node
>>>>>>>>>> OS object has already been created, address: 1fbe730, returning 
>>>>>>>>>>1
>>>>>>>>>> 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:new(200)|VCL::Module::Provisio
>>>>>>>>>>ni
>>>>>>>>>>ng
>>>>>>>>>>::
>>>>>>>>>> VM
>>>>>>>>>> ware::vSphere_SDK
>>>>>>>>>> object created for computer redhat64base, address: 2508cf8
>>>>>>>>>> 2011-10-25
>>>>>>>>>> 08:58:38|29609|2:2|image|vSphere_SDK.pm:initialize(1826)|vSphere
>>>>>>>>>> SDK for Perl does not appear to be installed on this managment
>>>>>>>>>>node,
>>>>>>>>>> unable
>>>>>>>>>> to load VMware vSphere SDK Perl modules
>>>>>>>>>> 2011-10-25
>>>>>>>>>> 
>>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1313)|AP
>>>>>>>>>>I
>>>>>>>>>> object
>>>>>>>>>> could not be created:
>>>>>>>>>>VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:initialize(273)|no methods 
>>>>>>>>>>are
>>>>>>>>>> available
>>>>>>>>>> to control VM host redhat64base, the vSphere SDK cannot be used 
>>>>>>>>>>to
>>>>>>>>>> control
>>>>>>>>>> the VM host and the host OS cannot be controlled via SSH
>>>>>>>>>> |29609|2:2|image| ( 0) VMware.pm, initialize (line: 273)
>>>>>>>>>> |29609|2:2|image| (-1) Module.pm, new (line: 207)
>>>>>>>>>> |29609|2:2|image| (-2) Module.pm, create_provisioning_object
>>>>>>>>>>(line:
>>>>>>>>>> 423)
>>>>>>>>>> |29609|2:2|image| (-3) State.pm, initialize (line: 117)
>>>>>>>>>> |29609|2:2|image| (-4) Module.pm, new (line: 207)
>>>>>>>>>> |29609|2:2|image| (-5) vcld, make_new_child (line: 564)
>>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_provisioning_object(431
>>>>>>>>>>)|
>>>>>>>>>>pr
>>>>>>>>>>ov
>>>>>>>>>> is
>>>>>>>>>> ioning
>>>>>>>>>> object could not be created, returning 0
>>>>>>>>>> |29609|2:2|image| ( 0) Module.pm, create_provisioning_object
>>>>>>>>>>(line:
>>>>>>>>>> 431)
>>>>>>>>>> |29609|2:2|image| (-1) State.pm, initialize (line: 117)
>>>>>>>>>> |29609|2:2|image| (-2) Module.pm, new (line: 207)
>>>>>>>>>> |29609|2:2|image| (-3) vcld, make_new_child (line: 564)
>>>>>>>>>> |29609|2:2|image| (-4) vcld, main (line: 346)
>>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>> 08:58:38|29609|2:2|image|State.pm:initialize(118)|failed to 
>>>>>>>>>>create
>>>>>>>>>> provisioning object
>>>>>>>>>> |29609|2:2|image| ( 0) State.pm, initialize (line: 118)
>>>>>>>>>> |29609|2:2|image| (-1) Module.pm, new (line: 207)
>>>>>>>>>> |29609|2:2|image| (-2) vcld, make_new_child (line: 564)
>>>>>>>>>> |29609|2:2|image| (-3) vcld, main (line: 346)
>>>>>>>>>> 2011-10-25
>>>>>>>>>>08:58:38|29609|2:2|image|State.pm:DESTROY(829)|VCL::image
>>>>>>>>>> destructor called, address: 1e52a60
>>>>>>>>>> 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:delete_computerloadlog_reservat
>>>>>>>>>>io
>>>>>>>>>>n(
>>>>>>>>>>67
>>>>>>>>>> 42
>>>>>>>>>> )|removing
>>>>>>>>>> computerloadlog entries matching loadstate = begin
>>>>>>>>>> 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:delete_computerloadlog_reservat
>>>>>>>>>>io
>>>>>>>>>>n(
>>>>>>>>>>67
>>>>>>>>>> 89
>>>>>>>>>> )|deleted
>>>>>>>>>> rows from computerloadlog for reservation id=2
>>>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|State.pm:DESTROY(848)|number
>>>>>>>>>>of
>>>>>>>>>> database
>>>>>>>>>> handles state process created: 1
>>>>>>>>>> 2011-10-25
>>>>>>>>>>08:58:38|29609|2:2|image|State.pm:DESTROY(876)|VCL::image
>>>>>>>>>> process
>>>>>>>>>> duration: 0 seconds
>>>>>>>>>> 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip
>>>>>>>>>>_a
>>>>>>>>>>dd
>>>>>>>>>>re
>>>>>>>>>> ss
>>>>>>>>>> (1581)|attempting
>>>>>>>>>> to retrieve private IP address for computer: redhat64base
>>>>>>>>>> 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip
>>>>>>>>>>_a
>>>>>>>>>>dd
>>>>>>>>>>re
>>>>>>>>>> ss
>>>>>>>>>> (1585)|retrieved
>>>>>>>>>> contents of /etc/hosts on this management node, contains 8 lines
>>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip
>>>>>>>>>>_a
>>>>>>>>>>dd
>>>>>>>>>>re
>>>>>>>>>> ss
>>>>>>>>>> (1629)|did
>>>>>>>>>> not find any lines in /etc/hosts containing 'redhat64base' and 
>>>>>>>>>>the
>>>>>>>>>> private
>>>>>>>>>> IP address is not defined in the database
>>>>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm,
>>>>>>>>>> get_computer_private_ip_address
>>>>>>>>>> (line: 1629)
>>>>>>>>>> |29609|2:2|image| (-1) DataStructure.pm,
>>>>>>>>>>get_reservation_info_string
>>>>>>>>>> (line:
>>>>>>>>>> 2419)
>>>>>>>>>> |29609|2:2|image| (-3) vcld, make_new_child (line: 571)
>>>>>>>>>> |29609|2:2|image| (-4) vcld, main (line: 346)
>>>>>>>>>> 2011-10-25
>>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2703)|unable
>>>>>>>>>>to
>>>>>>>>>> use
>>>>>>>>>> database handle stored in $ENV{dbh}
>>>>>>>>>> 2011-10-25
>>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>>>>> handle
>>>>>>>>>> stored in $ENV{dbh}
>>>>>>>>>> 2011-10-25
>>>>>>>>>> 08:58:38|29609|2:2|image|utils.pm:is_inblockrequest(6163)|zero
>>>>>>>>>> rows were returned from database select
>>>>>>>>>> 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_image_affiliation_n
>>>>>>>>>>am
>>>>>>>>>>e(
>>>>>>>>>>20
>>>>>>>>>> 35
>>>>>>>>>> )|image
>>>>>>>>>> owner id: 1
>>>>>>>>>> 2011-10-25
>>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2709)|database
>>>>>>>>>> requested (information_schema) does not match handle stored in
>>>>>>>>>> $ENV{dbh}
>>>>>>>>>> (vcl:localhost)
>>>>>>>>>> 2011-10-25
>>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>>>>> handle
>>>>>>>>>> stored in $ENV{dbh}
>>>>>>>>>> 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:retrieve_user_data(1352
>>>>>>>>>>)|
>>>>>>>>>>at
>>>>>>>>>>te
>>>>>>>>>> mp
>>>>>>>>>> ting
>>>>>>>>>> to retrieve and store data for user: user.id = '1'
>>>>>>>>>> 2011-10-25
>>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2709)|database
>>>>>>>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>>>>>>>> (information_schema:localhost)
>>>>>>>>>> 2011-10-25
>>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>>>>> handle
>>>>>>>>>> stored in $ENV{dbh}
>>>>>>>>>> 2011-10-25
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:retrieve_user_data(1415
>>>>>>>>>>)|
>>>>>>>>>>da
>>>>>>>>>>ta
>>>>>>>>>> has
>>>>>>>>>> been retrieved for user: admin (id: 1)
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Aaron Peeler
>>>>>>>>> Program Manager
>>>>>>>>> Virtual Computing Lab
>>>>>>>>> NC State University
>>>>>>>>>
>>>>>>>>> All electronic mail messages in connection with State business
>>>>>>>>>which
>>>>>>>>> are sent to or received by this account are subject to the NC
>>>>>>>>>Public
>>>>>>>>> Records Law and may be disclosed to third parties.
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Aaron Peeler
>>>>>>> Program Manager
>>>>>>> Virtual Computing Lab
>>>>>>> NC State University
>>>>>>>
>>>>>>> All electronic mail messages in connection with State business 
>>>>>>>which
>>>>>>> are sent to or received by this account are subject to the NC 
>>>>>>>Public
>>>>>>> Records Law and may be disclosed to third parties.
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>--
>>>Thanks,
>>>Alex  Patterson
>>>User Support Services
>>>Operating System Analyst
>>>California State University, East Bay
>>
>>


Re: Base Image creation error - Continued again

Posted by Andy Kurth <an...@ncsu.edu>.
I think there may be 2 issues...

> When I try to make a manual reservation, it tells me that there is no
> computer available to run this image.
> I wonder if I gave it some bad info for RAM or CPU ?

Did you add the image to an image group after it was captured?  This
page has a little more information:
https://cwiki.apache.org/confluence/display/VCL/Capture+A+Base+Image

If you did already add the image to a group, you may be seeing the
"selection not available" error on the website because the only
computer that is available for the image to run on is your
"linux64base" computer.  The state of this computer may be "failed"
because of the problem which occurred in the vcld.log output you
included.  After an image is successfully captured, a "reload"
reservation is automatically added to the database to load the new
image on the same computer used to capture it.  I'm guessing the
output you included is from this reload reservation.

The "selection not available" error is not directly caused by the
error in the log output you have included.  The reason why the failure
occurred is because the MAC address fields are not set on the
"linux64base" computer you previously added to VCL as evidenced by the
following line:

> 15:52:10|19062|8:8|reload|DataStructure.pm:_automethod(812)|corresponding data has not been initialized for get_computer_eth0_mac_address: $self->request_data->{reservation}{8}{computer}{eth0macaddress}

You will need to add computers using the "Add Multiple Computers"
option in order to have the MAC addresses properly configured in the
database.  I would recommend looking at the "Adding Virtual Machines"
section on the following page:
https://cwiki.apache.org/confluence/display/VCL/VCL+2.2.1+-+Further+Steps+if+Using+VMware

Also, you'll probably want to check the state of the "linux64base"
computer by looking at Manage Computers > Computer Utilities.  It is
probably "failed".  You can change this to available but reservations
assigned to this computer will always fail because of the MAC address
issue.  You will have to edit the database in order to set the MAC
addresses for this computer.  However, it's probably easier to just
delete this computer from VCL using Manage Computers > Edit Computer
Information.  Once you have added the multiple VMs, you can use any of
those to capture other base images in the future.

Hope this helps,
Andy





> As Roseanne Rosanadana says: It's always something...
>
> The error message is below:
>
> reservation failed on linux64base: process failed after trying to load or
> make available
> ------------------------------------------------------------------------
> time: 2011-10-25 15:52:10
> caller: State.pm:reservation_failed(213)
> ( 0) State.pm, reservation_failed (line: 213)
> (-1) new.pm, process (line: 298)
> (-2) vcld, make_new_child (line: 568)
> (-3) vcld, main (line: 346)
> ------------------------------------------------------------------------
> management node: vcltst.fiu.edu
> reservation PID: 19062
> parent vcld PID: 15838
>
> request ID: 8
> reservation ID: 8
> request state/laststate: reload/image
> request start time: 2011-10-25 15:52:00
> request end time: 2011-10-25 16:22:00
> for imaging: no
> log ID: none
>
> computer: linux64base
> computer id: 14
> computer type: virtualmachine
> computer eth0 MAC address: <undefined>
> computer eth1 MAC address: <undefined>
> computer private IP address: 10.0.0.2
> computer public IP address: 10.106.128.53
> computer in block allocation: no
> provisioning module: VCL::Module::Provisioning::VMware::VMware
>
> vm host: vcldell_01
> vm host ID: 2
> vm host computer ID: 13
> vm profile: VMware ESX - local storage
> vm profile VM path: /vmfs/volumes/datastore1/vclimages
> vm profile repository path: /vmfs/volumes/datastore1/vclrepository
> vm profile datastore path: /vmfs/volumes/datastore1/vclimages
> vm profile disk type: localdisk
>
> image: vmwarelinux-base64linux19-v0
> image display name: base64linux
> image ID: 19
> image revision ID: 11
> image size: 857 MB
> use Sysprep: yes
> root access: yes
> image owner ID: 1
> image owner affiliation: Local
> image revision date created: 2011-10-25 15:50:38
> image revision production: yes
> OS module: VCL::Module::OS::Linux
>
> user: vclreload
> user name: vcl reload
> user ID: 2
> user affiliation: Local
> ------------------------------------------------------------------------
> RECENT LOG ENTRIES FOR THIS PROCESS:
> 2011-10-25
> 15:52:08|19062|8:8|reload|VMware.pm:get_image_size_bytes(3841)|retrieved
> the size of the image from the datastore on the VM host: 17,179,869,673
> 2011-10-25
> 15:52:08|19062|8:8|reload|VMware.pm:get_image_size_bytes(3851)|image size
> retrieved from both the image repository and VM host datastore:
> |19062|8:8|reload| image repository: 898,237,415
> |19062|8:8|reload| VM host datastore: 17,179,869,673
> 2011-10-25
> 15:52:08|19062|8:8|reload|VMware.pm:get_image_size_bytes(3871)|size of
> vmwarelinux-base64linux19-v0 image:
> |19062|8:8|reload| 17,179,869,673 bytes
> |19062|8:8|reload| 16,384 MB
> |19062|8:8|reload| 16.00 GB
> 2011-10-25
> 15:52:08|19062|8:8|reload|VMware.pm:get_vm_additional_vmx_bytes_required(47
> 13)|4294967418 additional bytes required for REDO files because VM disk
> mode is NOT persistent
> 2011-10-25
> 15:52:08|19062|8:8|reload|VMware.pm:get_vm_additional_vmx_bytes_required(47
> 16)|estimate of additional space required for the vmx directory:
> |19062|8:8|reload| vmem/vswp file: 536,870,912 bytes, 512.0 MB, 0.50 GB
> |19062|8:8|reload| redo files: 4,294,967,418 bytes, 4,096.0 MB, 4.00 GB
> |19062|8:8|reload| total: 4,831,838,330 bytes, 4,608.0 MB, 4.50 GB
> 2011-10-25
> 15:52:09|19062|8:8|reload|Linux.pm:file_exists(1404)|'/vmfs/volumes/datasto
> re1/vclimages/vmwarelinux-base64linux19-v0/vmwarelinux-base64linux19-v0.vmd
> k' exists on vcldell_01, files: 1, directories: 0, links: 0
> 2011-10-25
> 15:52:09|19062|8:8|reload|VMware.pm:get_image_size_bytes(3819)|VM profile
> vmdisk is set to 'localdisk', attempting to retrieve image size from image
> repository
> 2011-10-25
> 15:52:09|19062|8:8|reload|Linux.pm:file_exists(1404)|'/vmfs/volumes/datasto
> re1/vclrepository' exists on vcldell_01, files: 0, directories: 1, links: 0
> 2011-10-25
> 15:52:09|19062|8:8|reload|VMware.pm:is_repository_mounted_on_vmhost(5485)|i
> mage repository is mounted on VM host vcldell_01:
> /vmfs/volumes/datastore1/vclrepository
> 2011-10-25
> 15:52:09|19062|8:8|reload|VMware.pm:get_image_size_bytes(3821)|checking
> size of image in image repository mounted on VM host:
> vcldell_01:/vmfs/volumes/datastore1/vclrepository
> 2011-10-25 15:52:09|19062|8:8|reload|Linux.pm:get_file_size(2022)|size of
> '/vmfs/volumes/datastore1/vclrepository/vmwarelinux-base64linux19-v0/vmware
> linux-base64linux19-v0*.vmdk' on vcldell_01:
> |19062|8:8|reload| used: 898,237,415 bytes, 856.6 MB, 0.84 GB
> |19062|8:8|reload| allocated: 903,872,512 bytes, 862.0 MB, 0.84 GB
> 2011-10-25 15:52:10|19062|8:8|reload|Linux.pm:get_file_size(2022)|size of
> '/vmfs/volumes/datastore1/vclimages/vmwarelinux-base64linux19-v0/vmwarelinu
> x-base64linux19-v0*.vmdk' on vcldell_01:
> |19062|8:8|reload| used: 17,179,869,673 bytes, 16,384.0 MB, 16.00 GB
> |19062|8:8|reload| allocated: 17,179,869,184 bytes, 16,384.0 MB, 16.00 GB
> 2011-10-25
> 15:52:10|19062|8:8|reload|VMware.pm:get_image_size_bytes(3841)|retrieved
> the size of the image from the datastore on the VM host: 17,179,869,673
> 2011-10-25
> 15:52:10|19062|8:8|reload|VMware.pm:get_image_size_bytes(3851)|image size
> retrieved from both the image repository and VM host datastore:
> |19062|8:8|reload| image repository: 898,237,415
> |19062|8:8|reload| VM host datastore: 17,179,869,673
> 2011-10-25
> 15:52:10|19062|8:8|reload|VMware.pm:get_image_size_bytes(3871)|size of
> vmwarelinux-base64linux19-v0 image:
> |19062|8:8|reload| 17,179,869,673 bytes
> |19062|8:8|reload| 16,384 MB
> |19062|8:8|reload| 16.00 GB
> 2011-10-25
> 15:52:10|19062|8:8|reload|VMware.pm:get_vm_additional_vmdk_bytes_required(4
> 657)|no additional space required for vmdk files because they already
> exist on VM host
> 2011-10-25
> 15:52:10|19062|8:8|reload|VMware.pm:get_vm_additional_vmdk_bytes_required(4
> 662)|VM requires appoximately 0 additional bytes (0 MB, 0 GB) of disk
> space on the VM host for the vmdk directory
> 2011-10-25
> 15:52:10|19062|8:8|reload|VMware.pm:check_vmhost_disk_space(2070)|enough
> space is available on shared vmx/vmdk volume on VM host vcldell_01:
> '/vmfs/volumes/datastore1/vclimages'
> |19062|8:8|reload| vmx additional space required:          4,831,838,330
> bytes, 4,608.0 MB, 4.50 GB
> |19062|8:8|reload| vmdk additional space required:         0 bytes, 0.0
> MB, 0.00 GB
> |19062|8:8|reload| total additional space required:        4,831,838,330
> bytes, 4,608.0 MB, 4.50 GB
> |19062|8:8|reload| shared vmx/vmdk volume available space: 248,047,992,832
> bytes, 236,557.0 MB, 231.01 GB
> 2011-10-25
> 15:52:10|19062|8:8|reload|Module.pm:create_mn_os_object(335)|management
> node OS object has already been created, address: 222db60, returning 1
> 2011-10-25
> 15:52:10|19062|8:8|reload|Module.pm:new(203)|VCL::Module::Semaphore object
> created, address: 1cac6c0
> 2011-10-25
> 15:52:10|19062|8:8|reload|Module.pm:code_loop_timeout(742)|attempting to
> open lockfile, maximum of 1200 seconds
> 2011-10-25
> 15:52:10|19062|8:8|reload|Module.pm:code_loop_timeout(759)|attempt 1:
> attempting to open lockfile
> 2011-10-25
> 15:52:10|19062|8:8|reload|Semaphore.pm:open_lockfile(146)|opened and
> obtained an exclusive lock on file:
> /tmp/vcldell_01-vmfs-volumes-datastore1-vclimages-vmwarelinux-base64linux19
> -v0.lock
> 2011-10-25
> 15:52:10|19062|8:8|reload|Module.pm:code_loop_timeout(762)|attempting to
> open lockfile, code returned true
> 2011-10-25 15:52:10|19062|8:8|reload|Module.pm:get_semaphore(844)|created
> Semaphore object, memory address: 1cac6c0
> 2011-10-25
> 15:52:10|19062|8:8|reload|Linux.pm:file_exists(1404)|'/vmfs/volumes/datasto
> re1/vclimages/vmwarelinux-base64linux19-v0/vmwarelinux-base64linux19-v0.vmd
> k' exists on vcldell_01, files: 1, directories: 0, links: 0
> 2011-10-25 15:52:10|19062|8:8|reload|VMware.pm:prepare_vmdk(1785)|VM is
> not persistent and nonpersistent vmdk file already exists on VM host
> vcldell_01:
> /vmfs/volumes/datastore1/vclimages/vmwarelinux-base64linux19-v0/vmwarelinux
> -base64linux19-v0.vmdk
> 2011-10-25
> 15:52:10|19062|8:8|reload|Semaphore.pm:release_lockfile(248)|deleted file:
> /tmp/vcldell_01-vmfs-volumes-datastore1-vclimages-vmwarelinux-base64linux19
> -v0.lock
> 2011-10-25 15:52:10|19062|8:8|reload|Semaphore.pm:DESTROY(281)|destroyed
> Semaphore object, memory address: 1cac6c0
> 2011-10-25 15:52:10|19062|8:8|reload|utils.pm:insertloadlog(3875)|inserted
> computer=14, transfervm, copied vmwarelinux-base64linux19-v0 to linux64base
> 2011-10-25 15:52:10|19062|8:8|reload|VMware.pm:get_vm_ram(4306)|image ram
> setting is too low: 0 MB, 512 MB will be used
> 2011-10-25
> 15:52:10|19062|8:8|reload|VMware.pm:get_vm_os_configuration(4210)|retrieved
>  default VM configuration for OS: linux-x86_64
> |19062|8:8|reload| : {
> |19062|8:8|reload| :   "ethernet-virtualDev" => "e1000",
> |19062|8:8|reload| :   "guestOS" => "otherlinux-64",
> |19062|8:8|reload| :   "scsi-virtualDev" => "lsiLogic"
> |19062|8:8|reload| : }
> |19062|8:8|reload| ---- WARNING ----
> |19062|8:8|reload| 2011-10-25
> 15:52:10|19062|8:8|reload|DataStructure.pm:_automethod(812)|corresponding
> data has not been initialized for get_computer_eth0_mac_address:
> $self->request_data->{reservation}{8}{computer}{eth0macaddress}
> |19062|8:8|reload| ( 0) DataStructure.pm, _automethod (line: 812)
> |19062|8:8|reload| (-1) Autoload.pm, __ANON__ (line: 80)
> |19062|8:8|reload| (-2) VMware.pm, prepare_vmx (line: 1457)
> |19062|8:8|reload| (-3) VMware.pm, load (line: 394)
> |19062|8:8|reload| (-4) new.pm, reload_image (line: 618)
> |19062|8:8|reload| (-5) new.pm, process (line: 248)
> |19062|8:8|reload| ---- WARNING ----
> |19062|8:8|reload| 2011-10-25
> 15:52:10|19062|8:8|reload|VMware.pm:load(395)|failed to prepare vmx file
> for linux64base on VM host: vcldell_01
> |19062|8:8|reload| ( 0) VMware.pm, load (line: 395)
> |19062|8:8|reload| (-1) new.pm, reload_image (line: 618)
> |19062|8:8|reload| (-2) new.pm, process (line: 248)
> |19062|8:8|reload| (-3) vcld, make_new_child (line: 568)
> |19062|8:8|reload| (-4) vcld, main (line: 346)
> |19062|8:8|reload| ---- WARNING ----
> |19062|8:8|reload| 2011-10-25
> 15:52:10|19062|8:8|reload|new.pm:reload_image(623)|vmwarelinux-base64linux1
> 9-v0 failed to load on linux64base, returning
> |19062|8:8|reload| ( 0) new.pm, reload_image (line: 623)
> |19062|8:8|reload| (-1) new.pm, process (line: 248)
> |19062|8:8|reload| (-2) vcld, make_new_child (line: 568)
> |19062|8:8|reload| (-3) vcld, main (line: 346)
> 2011-10-25 15:52:10|19062|8:8|reload|utils.pm:insertloadlog(3875)|inserted
> computer=14, loadimagefailed, vmwarelinux-base64linux19-v0 failed to load
> on linux64base
> |19062|8:8|reload| ---- WARNING ----
> |19062|8:8|reload| 2011-10-25
> 15:52:10|19062|8:8|reload|new.pm:process(295)|failed to load linux64base
> with vmwarelinux-base64linux19-v0
> |19062|8:8|reload| ( 0) new.pm, process (line: 295)
> |19062|8:8|reload| (-1) vcld, make_new_child (line: 568)
> |19062|8:8|reload| (-2) vcld, main (line: 346)
> 2011-10-25
> 15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_state_name(2305)|at
> tempting to retrieve current state of computer linux64base from the
> database
> 2011-10-25
> 15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_state_name(2336)|re
> trieved current state of computer linux64base from the database: reloading
> 2011-10-25
> 15:52:10|19062|8:8|reload|DataStructure.pm:_automethod(834)|data structure
> updated: $self->request_data->{reservation}{8}{computer}{state}{name}
> |19062|8:8|reload| computer_state_name = reloading
> 2011-10-25
> 15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_private_ip_address(
> 1581)|attempting to retrieve private IP address for computer: linux64base
> 2011-10-25
> 15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_private_ip_address(
> 1585)|retrieved contents of /etc/hosts on this management node, contains
> 10 lines
> 2011-10-25
> 15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_private_ip_address(
> 1645)|returning IP address from /etc/hosts file: 10.0.0.2
> 2011-10-25 15:52:10|19062|8:8|reload|utils.pm:is_inblockrequest(6163)|zero
> rows were returned from database select
> 2011-10-25
> 15:52:10|19062|8:8|reload|DataStructure.pm:get_image_affiliation_name(2035)
> |image owner id: 1
> 2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2709)|database
> requested (information_schema) does not match handle stored in $ENV{dbh}
> (vcl:localhost)
> 2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2760)|database
> handle stored in $ENV{dbh}
> 2011-10-25
> 15:52:10|19062|8:8|reload|DataStructure.pm:retrieve_user_data(1352)|attempt
> ing to retrieve and store data for user: user.id = '1'
> 2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2709)|database
> requested (vcl) does not match handle stored in $ENV{dbh}
> (information_schema:localhost)
> 2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2760)|database
> handle stored in $ENV{dbh}
> 2011-10-25
> 15:52:10|19062|8:8|reload|DataStructure.pm:retrieve_user_data(1415)|data
> has been retrieved for user: admin (id: 1)
>
>
>
>
> On 10/25/11 12:00 PM, "Alexander Patterson"
> <al...@csueastbay.edu> wrote:
>
>>Hello,
>>
>> Here is the main issue, You need to have your datastore the location
>>that you are storing you VM images in the correct place. As of right
>>now they are looking  in the /vmfs/volumes/local-datastore
>>
>>You can either move your images to this folder or change the default
>>location.
>>
>>
>>To do this go to Virtual Host
>>Click on VM host Profiles
>>Click on Configure Profile (Make to to select the VMware ESXI Standard
>>Localdisk
>>from the sounds of it you have Local storage and are storing your VM's
>>locally.
>>
>>The Data Store Path can be changed to the current location or you can
>>move the files the choice is yours. Make sure you have the Virtual
>>Switches set up
>>I'm using custom VLAN switch 0 = private and switch 1 = private
>>You don't have to set a Repository Path but the Data Store Path has to
>>be correct.
>>
>>-Alex
>>
>>327|5:5|image| ---- WARNING ----
>>|5327|5:5|image| 2011-10-25
>>11:38:43|5327|5:5|image|VMware.pm:_get_datastore_name(5848)|unable to
>>determine datastore name from path: '/vmfs/volumes/local-datastore', path
>>does not begin with any of the datastore paths:
>>
>>2011/10/25 Evelio Quiros <ev...@fiu.edu>:
>>> OK,
>>>
>>> After adding the missing javascript, I am able to get the Virtual Hosts
>>> page to display.
>>>
>>> I added 10 VMs which have been added to the database, as well as the
>>>base
>>> image I want to capture, so 11 in all.
>>>
>>> Does VCL require the Vsphere module to add a virtual machine computer ?
>>>
>>> Also, I am using a free version of ESXi. Is there a licensing issue ?
>>>
>>>
>>> I tried once again to capture the base image, and I got this error:
>>>
>>>
>>> VCL::image object could not be created and initialized
>>> ------------------------------------------------------------------------
>>> time: 2011-10-25 11:38:43
>>> caller: vcld:make_new_child(571)
>>> ( 0) vcld, make_new_child (line: 571)
>>> (-1) vcld, main (line: 346)
>>> ------------------------------------------------------------------------
>>> management node: vcltst.fiu.edu
>>> reservation PID: 5327
>>> parent vcld PID: 15838
>>>
>>> request ID: 5
>>> reservation ID: 5
>>> request state/laststate: image/image
>>> request start time: 2011-10-25 11:38:35
>>> request end time: 2011-10-25 12:38:35
>>> for imaging: no
>>> log ID: none
>>>
>>> computer: redhat64base
>>> computer id: 12
>>> computer type: virtualmachine
>>> computer eth0 MAC address: <undefined>
>>> computer eth1 MAC address: <undefined>
>>> computer private IP address: 10.0.0.2
>>> computer public IP address: 10.106.128.53
>>> computer in block allocation: no
>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>
>>> vm host: vcldell_01
>>> vm host ID: 2
>>> vm host computer ID: 13
>>> vm profile: VMware ESX - local storage
>>> vm profile VM path: /vmfs/volumes/local-datastore
>>> vm profile repository path: 0
>>> vm profile datastore path: /vmfs/volumes/local-datastore
>>> vm profile disk type: localdisk
>>>
>>> image: vmwarelinux-redhat_linux16-v0
>>> image display name: redhat_linux
>>> image ID: 16
>>> image revision ID: 9
>>> image size: 1450 MB
>>> use Sysprep: yes
>>> root access: yes
>>> image owner ID: 1
>>> image owner affiliation: Local
>>> image revision date created: 2011-10-25 11:38:35
>>> image revision production: yes
>>> OS module: VCL::Module::OS::Linux
>>>
>>> user: admin
>>> user name: vcl admin
>>> user ID: 1
>>> user affiliation: Local
>>> ------------------------------------------------------------------------
>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>> 2011-10-25
>>>11:38:41|5327|5:5|image|vSphere_SDK.pm:initialize(1826)|vSphere
>>> SDK for Perl does not appear to be installed on this managment node,
>>> unable to load VMware vSphere SDK Perl modules
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1313)|API object
>>> could not be created: VCL::Module::Provisioning::VMware::vSphere_SDK
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(613)|computer ID
>>> argument was specified, retrieving data for computer ID: 13
>>> 2011-10-25
>>>11:38:41|5327|5:5|image|DataStructure.pm:_initialize(643)|image
>>> ID argument was specified: 4, DataStructure object will contain image
>>> information for the production imagerevision of this image
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(660)|retrieved data
>>> for imagerevision ID: 4
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(676)|retrieved data
>>> for image ID: 4
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_datastructure(1190)|created
>>> DataStructure object for VM host: vcldell_01
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1293)|attempting
>>> to load VMware control module:
>>>VCL::Module::Provisioning::VMware::VIM_SSH
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>> VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
>>> 2011-10-25 11:38:41|5327|5:5|image|Module.pm:new(172)|set 'vmhost_data'
>>> key for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
>>> 2011-10-25 11:38:41|5327|5:5|image|Module.pm:new(172)|set 'vmhost_os'
>>>key
>>> for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|Module.pm:create_mn_os_object(335)|management
>>>node
>>> OS object has already been created, address: 219ab58, returning 1
>>> 2011-10-25
>>>
>>>11:38:41|5327|5:5|image|Module.pm:new(200)|VCL::Module::Provisioning::VMw
>>>ar
>>> e::VIM_SSH object created for computer redhat64base, address: 1fd9588
>>> 2011-10-25 11:38:42|5327|5:5|image|VIM_SSH.pm:initialize(138)|VIM
>>> executable available on VM host: vim-cmd
>>> 2011-10-25
>>>
>>>11:38:42|5327|5:5|image|VIM_SSH.pm:initialize(140)|VCL::Module::Provision
>>>in
>>> g::VMware::VIM_SSH object initialized
>>> 2011-10-25
>>> 11:38:42|5327|5:5|image|VMware.pm:get_vmhost_api_object(1320)|created
>>>API
>>> object: VCL::Module::Provisioning::VMware::VIM_SSH
>>> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(278)|VMware on
>>>VM
>>> host vcldell_01 will be controlled using vim-cmd via SSH
>>> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(293)|VMware OS
>>>and
>>> API objects created for VM host vcldell_01:
>>> |5327|5:5|image| VM host OS object type: VCL::Module::OS::Linux::UnixLab
>>> |5327|5:5|image| VMware API object type:
>>> VCL::Module::Provisioning::VMware::VIM_SSH
>>> 2011-10-25
>>> 11:38:42|5327|5:5|image|VMware.pm:get_vmhost_product_name(5405)|VMware
>>> product being used on VM host vcldell_01: 'VMware ESXi 5.0.0
>>>build-469512'
>>> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(307)|product:
>>> VMware ESXi 5.0.0 build-469512, OS object:
>>>VCL::Module::OS::Linux::UnixLab
>>> 2011-10-25 11:38:42|5327|5:5|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd
>>> call count: 1 (hostsvc/datastore/listsummary)
>>> 2011-10-25 11:38:43|5327|5:5|image|VIM_SSH.pm:_run_vim_cmd(208)|executed
>>> command on VM host vcldell_01: vim-cmd hostsvc/datastore/listsummary
>>> 2011-10-25
>>> 11:38:43|5327|5:5|image|VMware.pm:get_datastore_info(5531)|retrieved
>>> datastore info from VM host:
>>> |5327|5:5|image| datastore1
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>> 11:38:43|5327|5:5|image|VMware.pm:_get_datastore_name(5848)|unable to
>>> determine datastore name from path: '/vmfs/volumes/local-datastore',
>>>path
>>> does not begin with any of the datastore paths:
>>> |5327|5:5|image| '[datastore1]'
>>> |5327|5:5|image| '/vmfs/volumes/datastore1'
>>> |5327|5:5|image| '/vmfs/volumes/4e96b3e5-a6562886-638a-00188be54b59'
>>> |5327|5:5|image| ( 0) VMware.pm, _get_datastore_name (line: 5848)
>>> |5327|5:5|image| (-1) VMware.pm, _get_datastore_root_normal_path (line:
>>> 5685)
>>> |5327|5:5|image| (-2) VMware.pm, _get_normal_path (line: 5775)
>>> |5327|5:5|image| (-3) VMware.pm, get_vmx_base_directory_path (line:
>>>2743)
>>> |5327|5:5|image| (-4) VMware.pm, initialize (line: 313)
>>> |5327|5:5|image| (-5) Module.pm, new (line: 207)
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>>
>>>11:38:43|5327|5:5|image|VMware.pm:_get_datastore_root_normal_path(5687)|f
>>>ai
>>> led to determine datastore root normal path, unable to determine
>>>datastore
>>> name: /vmfs/volumes/local-datastore
>>> |5327|5:5|image| ( 0) VMware.pm, _get_datastore_root_normal_path (line:
>>> 5687)
>>> |5327|5:5|image| (-1) VMware.pm, _get_normal_path (line: 5775)
>>> |5327|5:5|image| (-2) VMware.pm, get_vmx_base_directory_path (line:
>>>2743)
>>> |5327|5:5|image| (-3) VMware.pm, initialize (line: 313)
>>> |5327|5:5|image| (-4) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-5) Module.pm, create_provisioning_object (line: 423)
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>> 11:38:43|5327|5:5|image|VMware.pm:_get_normal_path(5777)|unable to
>>> determine normal path, failed to determine datastore root normal path:
>>> /vmfs/volumes/local-datastore
>>> |5327|5:5|image| ( 0) VMware.pm, _get_normal_path (line: 5777)
>>> |5327|5:5|image| (-1) VMware.pm, get_vmx_base_directory_path (line:
>>>2743)
>>> |5327|5:5|image| (-2) VMware.pm, initialize (line: 313)
>>> |5327|5:5|image| (-3) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-4) Module.pm, create_provisioning_object (line: 423)
>>> |5327|5:5|image| (-5) State.pm, initialize (line: 117)
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>>
>>>11:38:43|5327|5:5|image|VMware.pm:get_vmx_base_directory_path(2749)|unabl
>>>e
>>> to determine the vmx base directory path, failed to convert path
>>> configured in the VM profile to a normal path:
>>> /vmfs/volumes/local-datastore
>>> |5327|5:5|image| ( 0) VMware.pm, get_vmx_base_directory_path (line:
>>>2749)
>>> |5327|5:5|image| (-1) VMware.pm, initialize (line: 313)
>>> |5327|5:5|image| (-2) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-3) Module.pm, create_provisioning_object (line: 423)
>>> |5327|5:5|image| (-4) State.pm, initialize (line: 117)
>>> |5327|5:5|image| (-5) Module.pm, new (line: 207)
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>> 11:38:43|5327|5:5|image|VMware.pm:initialize(315)|unable to determine
>>>vmx
>>> base directory path on VM host vcldell_01
>>> |5327|5:5|image| ( 0) VMware.pm, initialize (line: 315)
>>> |5327|5:5|image| (-1) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-2) Module.pm, create_provisioning_object (line: 423)
>>> |5327|5:5|image| (-3) State.pm, initialize (line: 117)
>>> |5327|5:5|image| (-4) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-5) vcld, make_new_child (line: 564)
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>>
>>>11:38:43|5327|5:5|image|Module.pm:create_provisioning_object(431)|provisi
>>>on
>>> ing object could not be created, returning 0
>>> |5327|5:5|image| ( 0) Module.pm, create_provisioning_object (line: 431)
>>> |5327|5:5|image| (-1) State.pm, initialize (line: 117)
>>> |5327|5:5|image| (-2) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-3) vcld, make_new_child (line: 564)
>>> |5327|5:5|image| (-4) vcld, main (line: 346)
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>> 11:38:43|5327|5:5|image|State.pm:initialize(118)|failed to create
>>> provisioning object
>>> |5327|5:5|image| ( 0) State.pm, initialize (line: 118)
>>> |5327|5:5|image| (-1) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-2) vcld, make_new_child (line: 564)
>>> |5327|5:5|image| (-3) vcld, main (line: 346)
>>> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(829)|VCL::image
>>> destructor called, address: 1e47a28
>>> 2011-10-25
>>>
>>>11:38:43|5327|5:5|image|utils.pm:delete_computerloadlog_reservation(6742)
>>>|r
>>> emoving computerloadlog entries matching loadstate = begin
>>> 2011-10-25
>>>
>>>11:38:43|5327|5:5|image|utils.pm:delete_computerloadlog_reservation(6789)
>>>|d
>>> eleted rows from computerloadlog for reservation id=5
>>> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(848)|number of
>>> database handles state process created: 1
>>> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(876)|VCL::image
>>> process duration: 4 seconds
>>> 2011-10-25
>>>
>>>11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address(
>>>15
>>> 81)|attempting to retrieve private IP address for computer: redhat64base
>>> 2011-10-25
>>>
>>>11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address(
>>>15
>>> 85)|retrieved contents of /etc/hosts on this management node, contains
>>>10
>>> lines
>>> 2011-10-25
>>>
>>>11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address(
>>>16
>>> 45)|returning IP address from /etc/hosts file: 10.0.0.2
>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2703)|unable to
>>>use
>>> database handle stored in $ENV{dbh}
>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
>>> handle stored in $ENV{dbh}
>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:is_inblockrequest(6163)|zero
>>> rows were returned from database select
>>> 2011-10-25
>>>
>>>11:38:43|5327|5:5|image|DataStructure.pm:get_image_affiliation_name(2035)
>>>|i
>>> mage owner id: 1
>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2709)|database
>>> requested (information_schema) does not match handle stored in $ENV{dbh}
>>> (vcl:localhost)
>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
>>> handle stored in $ENV{dbh}
>>> 2011-10-25
>>>
>>>11:38:43|5327|5:5|image|DataStructure.pm:retrieve_user_data(1352)|attempt
>>>in
>>> g to retrieve and store data for user: user.id = '1'
>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2709)|database
>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>> (information_schema:localhost)
>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
>>> handle stored in $ENV{dbh}
>>> 2011-10-25
>>> 11:38:43|5327|5:5|image|DataStructure.pm:retrieve_user_data(1415)|data
>>>has
>>> been retrieved for user: admin (id: 1)
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 10/25/11 10:26 AM, "Aaron Coburn" <ac...@amherst.edu> wrote:
>>>
>>>>Al,
>>>>if you plan to use the vSphere API, then you will need to install the
>>>>vSphere SDK for Perl separately. The perl modules are available here --
>>>>just make sure that you download the release that matches your vCenter
>>>>version.
>>>>
>>>>http://www.vmware.com/support/developer/viperltoolkit/
>>>>
>>>>Aaron Coburn
>>>>
>>>>
>>>>On Oct 25, 2011, at 10:03 AM, Evelio Quiros wrote:
>>>>
>>>>> Thanks again Aaron. It seems we are taking baby steps here.
>>>>>
>>>>> Ok, next issue: When I click "Configure Host" in the vcl web
>>>>>interface,
>>>>> nothing happens.
>>>>>
>>>>> My Vmware server is listed there. It is in "vmhostinuse" state.
>>>>>
>>>>> I noticed some complaints below about the Vsphere perl module not
>>>>>being
>>>>> installed.
>>>>> I thought that was done in the "install_perl_libraries script.
>>>>>
>>>>> Thanks again for all your help.
>>>>>
>>>>> Al Quiros
>>>>>
>>>>>
>>>>> On 10/25/11 9:43 AM, "Aaron Peeler" <fa...@ncsu.edu> wrote:
>>>>>
>>>>>> In the log output your missing the vmhost information.
>>>>>>
>>>>>> Make sure your vm host server have a correctly configured vmhost
>>>>>> profile and you have assigned your vms to the virtual host server by
>>>>>> using the Virtual Host interface.
>>>>>>
>>>>>>
>>>>>>https://cwiki.apache.org/confluence/display/VCL/VCL+2.2.1+-+Further+St
>>>>>>ep
>>>>>>s+
>>>>>> if+Using+VMware
>>>>>> https://cwiki.apache.org/confluence/display/VCL/VMware+Configuration
>>>>>>
>>>>>> I'm not seeing the virtual host interface mentioned directly in the
>>>>>> vcl 2.2.1 install guide. I'll added that to the first link.
>>>>>>
>>>>>> Here is a link from a bootcamp that you can review this morning while
>>>>>> I work on adding the content to Apache VCL:
>>>>>>
>>>>>>https://sites.google.com/a/ncsu.edu/vcl-bootcamp/exercises/assign-a-vm
>>>>>>-t
>>>>>>o-
>>>>>> a-virtual-host
>>>>>>
>>>>>> Aaron
>>>>>>
>>>>>>
>>>>>> On Tue, Oct 25, 2011 at 9:19 AM, Evelio Quiros <ev...@fiu.edu>
>>>>>>wrote:
>>>>>>> Thank you Aaron.
>>>>>>>
>>>>>>> Ok, now it can resolve the name redhat64base to the private IP
>>>>>>>address
>>>>>>> 10.0.0.2.
>>>>>>> I tried to add the base image as the name linux64.
>>>>>>> It resides in the database as redhat64base, with the public IP of
>>>>>>> 10.106.128.53, and set as available.
>>>>>>> I'm not sure what this error message is telling meŠ
>>>>>>>
>>>>>>> VCL::image object could not be created and initialized
>>>>>>>
>>>>>>>---------------------------------------------------------------------
>>>>>>>--
>>>>>>>-
>>>>>>> time: 2011-10-25 09:30:44
>>>>>>> caller: vcld:make_new_child(571)
>>>>>>> ( 0) vcld, make_new_child (line: 571)
>>>>>>> (-1) vcld, main (line: 346)
>>>>>>>
>>>>>>>---------------------------------------------------------------------
>>>>>>>--
>>>>>>>-
>>>>>>> management node: vcltst.fiu.edu
>>>>>>> reservation PID: 31318
>>>>>>> parent vcld PID: 15838
>>>>>>>
>>>>>>> request ID: 4
>>>>>>> reservation ID: 4
>>>>>>> request state/laststate: image/image
>>>>>>> request start time: 2011-10-25 09:30:37
>>>>>>> request end time: 2011-10-25 10:30:37
>>>>>>> for imaging: no
>>>>>>> log ID: none
>>>>>>>
>>>>>>> computer: redhat64base
>>>>>>> computer id: 12
>>>>>>> computer type: blade
>>>>>>> computer eth0 MAC address: <undefined>
>>>>>>> computer eth1 MAC address: <undefined>
>>>>>>> computer private IP address: 10.0.0.2
>>>>>>> computer public IP address: 10.106.128.53
>>>>>>> computer in block allocation: no
>>>>>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>>>>>
>>>>>>> image: vmwarelinux-linux6414-v0
>>>>>>> image display name: linux64
>>>>>>> image ID: 14
>>>>>>> image revision ID: 8
>>>>>>> image size: 1450 MB
>>>>>>> use Sysprep: yes
>>>>>>> root access: yes
>>>>>>> image owner ID: 1
>>>>>>> image owner affiliation: Local
>>>>>>> image revision date created: 2011-10-25 09:30:37
>>>>>>> image revision production: yes
>>>>>>> OS module: VCL::Module::OS::Linux
>>>>>>>
>>>>>>> user: admin
>>>>>>> user name: vcl admin
>>>>>>> user ID: 1
>>>>>>> user affiliation: Local
>>>>>>>
>>>>>>>---------------------------------------------------------------------
>>>>>>>--
>>>>>>>-
>>>>>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attemp
>>>>>>>ti
>>>>>>>ng
>>>>>>> to load VMware control module:
>>>>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>>>>> VMware control module:
>>>>>>>VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>'vmhost_data'
>>>>>>> key for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>> arguments
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>'vmhost_os'
>>>>>>> key
>>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>>arguments
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|managemen
>>>>>>>t
>>>>>>> node OS object has already been created, address: 21956b8,
>>>>>>>returning 1
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioning
>>>>>>>::
>>>>>>>VM
>>>>>>> wa
>>>>>>> re::vSphere_SDK object created for computer redhat64base, address:
>>>>>>> 21e6980
>>>>>>> 2011-10-25
>>>>>>> 09:30:43|31318|4:4|image|vSphere_SDK.pm:initialize(1826)|vSphere SDK
>>>>>>>for
>>>>>>> Perl does not appear to be installed on this managment node, unable
>>>>>>>to
>>>>>>> load VMware vSphere SDK Perl modules
>>>>>>> 2011-10-25
>>>>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>>> object
>>>>>>> could not be created: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspond
>>>>>>>in
>>>>>>>g
>>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>>> $self->request_data->{reservation}{4}{computer}{vmhost}{computerid}
>>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>1161)
>>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspond
>>>>>>>in
>>>>>>>g
>>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>>>
>>>>>>>
>>>>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{vmprofile}{im
>>>>>>>ag
>>>>>>>ei
>>>>>>> d}
>>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>1162)
>>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_datastructure(1190)|cre
>>>>>>>at
>>>>>>>ed
>>>>>>> DataStructure object for VM host: redhat64base
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attemp
>>>>>>>ti
>>>>>>>ng
>>>>>>> to load VMware control module:
>>>>>>> VCL::Module::Provisioning::VMware::VIM_SSH
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>>>>> VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>'vmhost_data'
>>>>>>> key for VCL::Module::Provisioning::VMware::VIM_SSH object from
>>>>>>>arguments
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>'vmhost_os'
>>>>>>> key
>>>>>>> for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|managemen
>>>>>>>t
>>>>>>> node OS object has already been created, address: 21956b8,
>>>>>>>returning 1
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioning
>>>>>>>::
>>>>>>>VM
>>>>>>> wa
>>>>>>> re::VIM_SSH object created for computer redhat64base, address:
>>>>>>>24f7888
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|VIM_SSH.pm:initialize(126)|VIM
>>>>>>> executable is not available on the VM host, output:
>>>>>>> |31318|4:4|image| bash: vim-cmd: command not found
>>>>>>> |31318|4:4|image| bash: vmware-vim-cmd: command not found
>>>>>>> 2011-10-25
>>>>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>>> object
>>>>>>> could not be created: VCL::Module::Provisioning::VMware::VIM_SSH
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspond
>>>>>>>in
>>>>>>>g
>>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>>> $self->request_data->{reservation}{4}{computer}{vmhost}{computerid}
>>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>1161)
>>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspond
>>>>>>>in
>>>>>>>g
>>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>>>
>>>>>>>
>>>>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{vmprofile}{im
>>>>>>>ag
>>>>>>>ei
>>>>>>> d}
>>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>1162)
>>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_datastructure(1190)|cre
>>>>>>>at
>>>>>>>ed
>>>>>>> DataStructure object for VM host: redhat64base
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attemp
>>>>>>>ti
>>>>>>>ng
>>>>>>> to load VMware control module:
>>>>>>> VCL::Module::Provisioning::VMware::vmware_cmd
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>>>>> VMware control module: VCL::Module::Provisioning::VMware::vmware_cmd
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>'vmhost_data'
>>>>>>> key for VCL::Module::Provisioning::VMware::vmware_cmd object from
>>>>>>> arguments
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>'vmhost_os'
>>>>>>> key
>>>>>>> for VCL::Module::Provisioning::VMware::vmware_cmd object from
>>>>>>>arguments
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|managemen
>>>>>>>t
>>>>>>> node OS object has already been created, address: 21956b8,
>>>>>>>returning 1
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioning
>>>>>>>::
>>>>>>>VM
>>>>>>> wa
>>>>>>> re::vmware_cmd object created for computer redhat64base, address:
>>>>>>> 251d1e0
>>>>>>> 2011-10-25
>>>>>>> 09:30:44|31318|4:4|image|vmware_cmd.pm:initialize(107)|vmware-cmd is
>>>>>>>not
>>>>>>> available on the VM host, output:
>>>>>>> |31318|4:4|image| bash: vmware-cmd: command not found
>>>>>>> 2011-10-25
>>>>>>> 09:30:44|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>>> object
>>>>>>> could not be created: VCL::Module::Provisioning::VMware::vmware_cmd
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>> 09:30:44|31318|4:4|image|VMware.pm:initialize(285)|failed to create
>>>>>>>an
>>>>>>> object to control VMware on VM host: redhat64base
>>>>>>> |31318|4:4|image| ( 0) VMware.pm, initialize (line: 285)
>>>>>>> |31318|4:4|image| (-1) Module.pm, new (line: 207)
>>>>>>> |31318|4:4|image| (-2) Module.pm, create_provisioning_object (line:
>>>>>>>423)
>>>>>>> |31318|4:4|image| (-3) State.pm, initialize (line: 117)
>>>>>>> |31318|4:4|image| (-4) Module.pm, new (line: 207)
>>>>>>> |31318|4:4|image| (-5) vcld, make_new_child (line: 564)
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|Module.pm:create_provisioning_object(431)|pr
>>>>>>>ov
>>>>>>>is
>>>>>>> io
>>>>>>> ning object could not be created, returning 0
>>>>>>> |31318|4:4|image| ( 0) Module.pm, create_provisioning_object (line:
>>>>>>>431)
>>>>>>> |31318|4:4|image| (-1) State.pm, initialize (line: 117)
>>>>>>> |31318|4:4|image| (-2) Module.pm, new (line: 207)
>>>>>>> |31318|4:4|image| (-3) vcld, make_new_child (line: 564)
>>>>>>> |31318|4:4|image| (-4) vcld, main (line: 346)
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>> 09:30:44|31318|4:4|image|State.pm:initialize(118)|failed to create
>>>>>>> provisioning object
>>>>>>> |31318|4:4|image| ( 0) State.pm, initialize (line: 118)
>>>>>>> |31318|4:4|image| (-1) Module.pm, new (line: 207)
>>>>>>> |31318|4:4|image| (-2) vcld, make_new_child (line: 564)
>>>>>>> |31318|4:4|image| (-3) vcld, main (line: 346)
>>>>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(829)|VCL::image
>>>>>>> destructor called, address: 1e47818
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|utils.pm:delete_computerloadlog_reservation(
>>>>>>>67
>>>>>>>42
>>>>>>> )|
>>>>>>> removing computerloadlog entries matching loadstate = begin
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|utils.pm:delete_computerloadlog_reservation(
>>>>>>>67
>>>>>>>89
>>>>>>> )|
>>>>>>> deleted rows from computerloadlog for reservation id=4
>>>>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(848)|number of
>>>>>>> database handles state process created: 1
>>>>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(876)|VCL::image
>>>>>>> process duration: 2 seconds
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_add
>>>>>>>re
>>>>>>>ss
>>>>>>> (1
>>>>>>> 581)|attempting to retrieve private IP address for computer:
>>>>>>> redhat64base
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_add
>>>>>>>re
>>>>>>>ss
>>>>>>> (1
>>>>>>> 585)|retrieved contents of /etc/hosts on this management node,
>>>>>>>contains
>>>>>>> 9
>>>>>>> lines
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_add
>>>>>>>re
>>>>>>>ss
>>>>>>> (1
>>>>>>> 645)|returning IP address from /etc/hosts file: 10.0.0.2
>>>>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2703)|unable
>>>>>>>to
>>>>>>> use
>>>>>>> database handle stored in $ENV{dbh}
>>>>>>> 2011-10-25
>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>>>> handle stored in $ENV{dbh}
>>>>>>> 2011-10-25
>>>>>>> 09:30:44|31318|4:4|image|utils.pm:is_inblockrequest(6163)|zero
>>>>>>> rows were returned from database select
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_image_affiliation_name(
>>>>>>>20
>>>>>>>35
>>>>>>> )|
>>>>>>> image owner id: 1
>>>>>>> 2011-10-25
>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2709)|database
>>>>>>> requested (information_schema) does not match handle stored in
>>>>>>>$ENV{dbh}
>>>>>>> (vcl:localhost)
>>>>>>> 2011-10-25
>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>>>> handle stored in $ENV{dbh}
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:retrieve_user_data(1352)|at
>>>>>>>te
>>>>>>>mp
>>>>>>> ti
>>>>>>> ng to retrieve and store data for user: user.id = '1'
>>>>>>> 2011-10-25
>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2709)|database
>>>>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>>>>> (information_schema:localhost)
>>>>>>> 2011-10-25
>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>>>> handle stored in $ENV{dbh}
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:retrieve_user_data(1415)|da
>>>>>>>ta
>>>>>>> has been retrieved for user: admin (id: 1)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 10/25/11 9:04 AM, "Aaron Peeler" <aa...@ncsu.edu> wrote:
>>>>>>>
>>>>>>>> Al,
>>>>>>>>
>>>>>>>> The hostname has to resolve.
>>>>>>>>
>>>>>>>> Put an entry in your /etc/hosts file.
>>>>>>>>
>>>>>>>> Aaron
>>>>>>>>
>>>>>>>> On Tue, Oct 25, 2011 at 8:52 AM, Evelio Quiros <ev...@fiu.edu>
>>>>>>>>wrote:
>>>>>>>>> Hello,
>>>>>>>>> I am getting an error when I try to capture a linux base image in
>>>>>>>>>vcl.
>>>>>>>>> I am
>>>>>>>>> following the instructions, but perhaps some parts of these may
>>>>>>>>>have
>>>>>>>>> been
>>>>>>>>> misinterpreted.
>>>>>>>>> My VCL server is at 10.0.0.1. My Vmware based virtual machine is
>>>>>>>>>at
>>>>>>>>> 10.0.0.2. I can ssh without passwords using keys from the vcl
>>>>>>>>>server
>>>>>>>>> to
>>>>>>>>> the
>>>>>>>>> VM.
>>>>>>>>> The computer has been added to the database as hostname
>>>>>>>>>redhat64base,
>>>>>>>>> although I have no DNS entry to resolve that name, so I use it's
>>>>>>>>> private IP
>>>>>>>>> of 10.0.0.2.
>>>>>>>>> Below is the result of vcld trying to capture the computer to
>>>>>>>>>create a
>>>>>>>>> new
>>>>>>>>> base imageŠ.Any ideas about what could be wrong ?
>>>>>>>>> Thanks,
>>>>>>>>> Al Quiros
>>>>>>>>>
>>>>>>>>> VCL::image object could not be created and initialized
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>-------------------------------------------------------------------
>>>>>>>>>--
>>>>>>>>>--
>>>>>>>>> -
>>>>>>>>> time: 2011-10-25 08:58:38
>>>>>>>>> caller: vcld:make_new_child(571)
>>>>>>>>> ( 0) vcld, make_new_child (line: 571)
>>>>>>>>> (-1) vcld, main (line: 346)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>-------------------------------------------------------------------
>>>>>>>>>--
>>>>>>>>>--
>>>>>>>>> -
>>>>>>>>> management node: vcltst.fiu.edu
>>>>>>>>> reservation PID: 29609
>>>>>>>>> parent vcld PID: 15838
>>>>>>>>> request ID: 2
>>>>>>>>> reservation ID: 2
>>>>>>>>> request state/laststate: image/image
>>>>>>>>> request start time: 2011-10-25 08:58:37
>>>>>>>>> request end time: 2011-10-25 09:58:37
>>>>>>>>> for imaging: no
>>>>>>>>> log ID: none
>>>>>>>>> computer: redhat64base
>>>>>>>>> computer id: 12
>>>>>>>>> computer type: blade
>>>>>>>>> computer eth0 MAC address: <undefined>
>>>>>>>>> computer eth1 MAC address: <undefined>
>>>>>>>>> computer private IP address: <undefined>
>>>>>>>>> computer public IP address: 10.0.0.2
>>>>>>>>> computer in block allocation: no
>>>>>>>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>>>>>>> image: vmwarelinux-redhat64linux8-v0
>>>>>>>>> image display name: redhat64linux
>>>>>>>>> image ID: 8
>>>>>>>>> image revision ID: 6
>>>>>>>>> image size: 1450 MB
>>>>>>>>> use Sysprep: yes
>>>>>>>>> root access: yes
>>>>>>>>> image owner ID: 1
>>>>>>>>> image owner affiliation: Local
>>>>>>>>> image revision date created: 2011-10-25 08:58:37
>>>>>>>>> image revision production: yes
>>>>>>>>> OS module: VCL::Module::OS::Linux
>>>>>>>>> user: admin
>>>>>>>>> user name: vcl admin
>>>>>>>>> user ID: 1
>>>>>>>>> user affiliation: Local
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>-------------------------------------------------------------------
>>>>>>>>>--
>>>>>>>>>--
>>>>>>>>> -
>>>>>>>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>>>>>>>> 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_os_object(1238)|VM
>>>>>>>>> host OS module loaded: VCL::Module::OS::Linux
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_mn_os_object(335)|managem
>>>>>>>>>en
>>>>>>>>>t
>>>>>>>>> node
>>>>>>>>> OS object has already been created, address: 1fbe730, returning 1
>>>>>>>>> 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|Module.pm:new(196)|VCL::Module::OS::Linux
>>>>>>>>> object
>>>>>>>>> created for image vmwarelinux-redhat64linux8-v0, address: 24f12f0
>>>>>>>>> 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_os_object(1244)|VM
>>>>>>>>> host OS object created: VCL::Module::OS::Linux
>>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|utils.pm:run_command(8998)|$?
>>>>>>>>>is
>>>>>>>>> set to
>>>>>>>>> -1, setting exit status to 0, Perl bug likely encountered
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|utils.pm:nmap_port(2645)|error occurred
>>>>>>>>> running
>>>>>>>>> nmap command: '/usr/bin/nmap redhat64base -P0 -p 22 -T
>>>>>>>>>Aggressive',
>>>>>>>>> output:
>>>>>>>>> |29609|2:2|image| Starting Nmap 5.21 ( http://nmap.org ) at
>>>>>>>>>2011-10-25
>>>>>>>>> 08:58
>>>>>>>>> EDT
>>>>>>>>> |29609|2:2|image| Failed to resolve given hostname/IP:
>>>>>>>>>redhat64base.
>>>>>>>>> Note
>>>>>>>>> that you can't use '/mask' AND '1-4,7,100-' style IP ranges
>>>>>>>>> |29609|2:2|image| WARNING: No targets were specified, so 0 hosts
>>>>>>>>> scanned.
>>>>>>>>> |29609|2:2|image| Nmap done: 0 IP addresses (0 hosts up) scanned
>>>>>>>>>in
>>>>>>>>> 0.05
>>>>>>>>> seconds
>>>>>>>>> |29609|2:2|image| ( 0) utils.pm, nmap_port (line: 2645)
>>>>>>>>> |29609|2:2|image| (-1) OS.pm, is_ssh_responding (line: 383)
>>>>>>>>> |29609|2:2|image| (-2) VMware.pm, initialize (line: 252)
>>>>>>>>> |29609|2:2|image| (-3) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| (-4) Module.pm, create_provisioning_object
>>>>>>>>>(line:
>>>>>>>>> 423)
>>>>>>>>> |29609|2:2|image| (-5) State.pm, initialize (line: 117)
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|utils.pm:nmap_port(2645)|error occurred
>>>>>>>>> running
>>>>>>>>> nmap command: '/usr/bin/nmap redhat64base -P0 -p 24 -T
>>>>>>>>>Aggressive',
>>>>>>>>> output:
>>>>>>>>> |29609|2:2|image| Starting Nmap 5.21 ( http://nmap.org ) at
>>>>>>>>>2011-10-25
>>>>>>>>> 08:58
>>>>>>>>> EDT
>>>>>>>>> |29609|2:2|image| Failed to resolve given hostname/IP:
>>>>>>>>>redhat64base.
>>>>>>>>> Note
>>>>>>>>> that you can't use '/mask' AND '1-4,7,100-' style IP ranges
>>>>>>>>> |29609|2:2|image| WARNING: No targets were specified, so 0 hosts
>>>>>>>>> scanned.
>>>>>>>>> |29609|2:2|image| Nmap done: 0 IP addresses (0 hosts up) scanned
>>>>>>>>>in
>>>>>>>>> 0.05
>>>>>>>>> seconds
>>>>>>>>> |29609|2:2|image| ( 0) utils.pm, nmap_port (line: 2645)
>>>>>>>>> |29609|2:2|image| (-1) OS.pm, is_ssh_responding (line: 384)
>>>>>>>>> |29609|2:2|image| (-2) VMware.pm, initialize (line: 252)
>>>>>>>>> |29609|2:2|image| (-3) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| (-4) Module.pm, create_provisioning_object
>>>>>>>>>(line:
>>>>>>>>> 423)
>>>>>>>>> |29609|2:2|image| (-5) State.pm, initialize (line: 117)
>>>>>>>>> 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|OS.pm:is_ssh_responding(386)|redhat64base
>>>>>>>>>is
>>>>>>>>> NOT
>>>>>>>>> responding to SSH, ports 22 or 24 are both closed
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:initialize(257)|unable
>>>>>>>>> to
>>>>>>>>> control OS of VM host redhat64base using VCL::Module::OS::Linux OS
>>>>>>>>> object
>>>>>>>>> because VM host is not responding to SSH
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:_automethod(812)|correspo
>>>>>>>>>nd
>>>>>>>>>in
>>>>>>>>> g
>>>>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>>>>>
>>>>>>>>>$self->request_data->{reservation}{2}{computer}{vmhost}{computerid}
>>>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>>>> |29609|2:2|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>>>> |29609|2:2|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>>> 1161)
>>>>>>>>> |29609|2:2|image| (-3) VMware.pm, get_vmhost_api_object (line:
>>>>>>>>>1282)
>>>>>>>>> |29609|2:2|image| (-4) VMware.pm, initialize (line: 265)
>>>>>>>>> |29609|2:2|image| (-5) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:_automethod(812)|correspo
>>>>>>>>>nd
>>>>>>>>>in
>>>>>>>>> g
>>>>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>$self->request_data->{reservation}{2}{computer}{vmhost}{vmprofile}{
>>>>>>>>>im
>>>>>>>>>ag
>>>>>>>>> ei
>>>>>>>>> d}
>>>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>>>> |29609|2:2|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>>>> |29609|2:2|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>>> 1162)
>>>>>>>>> |29609|2:2|image| (-3) VMware.pm, get_vmhost_api_object (line:
>>>>>>>>>1282)
>>>>>>>>> |29609|2:2|image| (-4) VMware.pm, initialize (line: 265)
>>>>>>>>> |29609|2:2|image| (-5) Module.pm, new (line: 207)
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_datastructure(1190)|c
>>>>>>>>>re
>>>>>>>>>at
>>>>>>>>> ed
>>>>>>>>> DataStructure object for VM host: redhat64base
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1293)|atte
>>>>>>>>>mp
>>>>>>>>>ti
>>>>>>>>> ng
>>>>>>>>> to
>>>>>>>>> load VMware control module:
>>>>>>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1299)|load
>>>>>>>>>ed
>>>>>>>>> VMware
>>>>>>>>> control module: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|Module.pm:new(172)|set
>>>>>>>>> 'vmhost_data' key
>>>>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>>>> arguments
>>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|Module.pm:new(172)|set
>>>>>>>>>'vmhost_os'
>>>>>>>>> key
>>>>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>>>> arguments
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_mn_os_object(335)|managem
>>>>>>>>>en
>>>>>>>>>t
>>>>>>>>> node
>>>>>>>>> OS object has already been created, address: 1fbe730, returning 1
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:new(200)|VCL::Module::Provisioni
>>>>>>>>>ng
>>>>>>>>>::
>>>>>>>>> VM
>>>>>>>>> ware::vSphere_SDK
>>>>>>>>> object created for computer redhat64base, address: 2508cf8
>>>>>>>>> 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|vSphere_SDK.pm:initialize(1826)|vSphere
>>>>>>>>> SDK for Perl does not appear to be installed on this managment
>>>>>>>>>node,
>>>>>>>>> unable
>>>>>>>>> to load VMware vSphere SDK Perl modules
>>>>>>>>> 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>>>>> object
>>>>>>>>> could not be created:
>>>>>>>>>VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:initialize(273)|no methods are
>>>>>>>>> available
>>>>>>>>> to control VM host redhat64base, the vSphere SDK cannot be used to
>>>>>>>>> control
>>>>>>>>> the VM host and the host OS cannot be controlled via SSH
>>>>>>>>> |29609|2:2|image| ( 0) VMware.pm, initialize (line: 273)
>>>>>>>>> |29609|2:2|image| (-1) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| (-2) Module.pm, create_provisioning_object
>>>>>>>>>(line:
>>>>>>>>> 423)
>>>>>>>>> |29609|2:2|image| (-3) State.pm, initialize (line: 117)
>>>>>>>>> |29609|2:2|image| (-4) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| (-5) vcld, make_new_child (line: 564)
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_provisioning_object(431)|
>>>>>>>>>pr
>>>>>>>>>ov
>>>>>>>>> is
>>>>>>>>> ioning
>>>>>>>>> object could not be created, returning 0
>>>>>>>>> |29609|2:2|image| ( 0) Module.pm, create_provisioning_object
>>>>>>>>>(line:
>>>>>>>>> 431)
>>>>>>>>> |29609|2:2|image| (-1) State.pm, initialize (line: 117)
>>>>>>>>> |29609|2:2|image| (-2) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| (-3) vcld, make_new_child (line: 564)
>>>>>>>>> |29609|2:2|image| (-4) vcld, main (line: 346)
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|State.pm:initialize(118)|failed to create
>>>>>>>>> provisioning object
>>>>>>>>> |29609|2:2|image| ( 0) State.pm, initialize (line: 118)
>>>>>>>>> |29609|2:2|image| (-1) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| (-2) vcld, make_new_child (line: 564)
>>>>>>>>> |29609|2:2|image| (-3) vcld, main (line: 346)
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|State.pm:DESTROY(829)|VCL::image
>>>>>>>>> destructor called, address: 1e52a60
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:delete_computerloadlog_reservatio
>>>>>>>>>n(
>>>>>>>>>67
>>>>>>>>> 42
>>>>>>>>> )|removing
>>>>>>>>> computerloadlog entries matching loadstate = begin
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:delete_computerloadlog_reservatio
>>>>>>>>>n(
>>>>>>>>>67
>>>>>>>>> 89
>>>>>>>>> )|deleted
>>>>>>>>> rows from computerloadlog for reservation id=2
>>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|State.pm:DESTROY(848)|number
>>>>>>>>>of
>>>>>>>>> database
>>>>>>>>> handles state process created: 1
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|State.pm:DESTROY(876)|VCL::image
>>>>>>>>> process
>>>>>>>>> duration: 0 seconds
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_a
>>>>>>>>>dd
>>>>>>>>>re
>>>>>>>>> ss
>>>>>>>>> (1581)|attempting
>>>>>>>>> to retrieve private IP address for computer: redhat64base
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_a
>>>>>>>>>dd
>>>>>>>>>re
>>>>>>>>> ss
>>>>>>>>> (1585)|retrieved
>>>>>>>>> contents of /etc/hosts on this management node, contains 8 lines
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_a
>>>>>>>>>dd
>>>>>>>>>re
>>>>>>>>> ss
>>>>>>>>> (1629)|did
>>>>>>>>> not find any lines in /etc/hosts containing 'redhat64base' and the
>>>>>>>>> private
>>>>>>>>> IP address is not defined in the database
>>>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm,
>>>>>>>>> get_computer_private_ip_address
>>>>>>>>> (line: 1629)
>>>>>>>>> |29609|2:2|image| (-1) DataStructure.pm,
>>>>>>>>>get_reservation_info_string
>>>>>>>>> (line:
>>>>>>>>> 2419)
>>>>>>>>> |29609|2:2|image| (-3) vcld, make_new_child (line: 571)
>>>>>>>>> |29609|2:2|image| (-4) vcld, main (line: 346)
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2703)|unable
>>>>>>>>>to
>>>>>>>>> use
>>>>>>>>> database handle stored in $ENV{dbh}
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>>>> handle
>>>>>>>>> stored in $ENV{dbh}
>>>>>>>>> 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|utils.pm:is_inblockrequest(6163)|zero
>>>>>>>>> rows were returned from database select
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_image_affiliation_nam
>>>>>>>>>e(
>>>>>>>>>20
>>>>>>>>> 35
>>>>>>>>> )|image
>>>>>>>>> owner id: 1
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2709)|database
>>>>>>>>> requested (information_schema) does not match handle stored in
>>>>>>>>> $ENV{dbh}
>>>>>>>>> (vcl:localhost)
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>>>> handle
>>>>>>>>> stored in $ENV{dbh}
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:retrieve_user_data(1352)|
>>>>>>>>>at
>>>>>>>>>te
>>>>>>>>> mp
>>>>>>>>> ting
>>>>>>>>> to retrieve and store data for user: user.id = '1'
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2709)|database
>>>>>>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>>>>>>> (information_schema:localhost)
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>>>> handle
>>>>>>>>> stored in $ENV{dbh}
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:retrieve_user_data(1415)|
>>>>>>>>>da
>>>>>>>>>ta
>>>>>>>>> has
>>>>>>>>> been retrieved for user: admin (id: 1)
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Aaron Peeler
>>>>>>>> Program Manager
>>>>>>>> Virtual Computing Lab
>>>>>>>> NC State University
>>>>>>>>
>>>>>>>> All electronic mail messages in connection with State business
>>>>>>>>which
>>>>>>>> are sent to or received by this account are subject to the NC
>>>>>>>>Public
>>>>>>>> Records Law and may be disclosed to third parties.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Aaron Peeler
>>>>>> Program Manager
>>>>>> Virtual Computing Lab
>>>>>> NC State University
>>>>>>
>>>>>> All electronic mail messages in connection with State business which
>>>>>> are sent to or received by this account are subject to the NC Public
>>>>>> Records Law and may be disclosed to third parties.
>>>>>
>>>>
>>>
>>>
>>
>>
>>
>>--
>>Thanks,
>>Alex  Patterson
>>User Support Services
>>Operating System Analyst
>>California State University, East Bay
>
>

Base Image creation error - Continued again

Posted by Evelio Quiros <ev...@fiu.edu>.
>Hello,
>
>
>I've gotten a bit further along the base image creation process.
>It has successfully created a base image, but then it could not make a
>reservation.
>When I try to make a manual reservation, it tells me that there is no
>computer available to run this image.
>I wonder if I gave it some bad info for RAM or CPU ?
>
>Any ideas why ?
>
>The error message is below:
>
>reservation failed on linux64base: process failed after trying to load or
>make available
>------------------------------------------------------------------------
>time: 2011-10-25 15:52:10
>caller: State.pm:reservation_failed(213)
>( 0) State.pm, reservation_failed (line: 213)
>(-1) new.pm, process (line: 298)
>(-2) vcld, make_new_child (line: 568)
>(-3) vcld, main (line: 346)
>------------------------------------------------------------------------
>management node: vcltst.fiu.edu
>reservation PID: 19062
>parent vcld PID: 15838
>
>request ID: 8
>reservation ID: 8
>request state/laststate: reload/image
>request start time: 2011-10-25 15:52:00
>request end time: 2011-10-25 16:22:00
>for imaging: no
>log ID: none
>
>computer: linux64base
>computer id: 14
>computer type: virtualmachine
>computer eth0 MAC address: <undefined>
>computer eth1 MAC address: <undefined>
>computer private IP address: 10.0.0.2
>computer public IP address: 10.106.128.53
>computer in block allocation: no
>provisioning module: VCL::Module::Provisioning::VMware::VMware
>
>vm host: vcldell_01
>vm host ID: 2
>vm host computer ID: 13
>vm profile: VMware ESX - local storage
>vm profile VM path: /vmfs/volumes/datastore1/vclimages
>vm profile repository path: /vmfs/volumes/datastore1/vclrepository
>vm profile datastore path: /vmfs/volumes/datastore1/vclimages
>vm profile disk type: localdisk
>
>image: vmwarelinux-base64linux19-v0
>image display name: base64linux
>image ID: 19
>image revision ID: 11
>image size: 857 MB
>use Sysprep: yes
>root access: yes
>image owner ID: 1
>image owner affiliation: Local
>image revision date created: 2011-10-25 15:50:38
>image revision production: yes
>OS module: VCL::Module::OS::Linux
>
>user: vclreload
>user name: vcl reload
>user ID: 2
>user affiliation: Local
>------------------------------------------------------------------------
>RECENT LOG ENTRIES FOR THIS PROCESS:
>2011-10-25 
>15:52:08|19062|8:8|reload|VMware.pm:get_image_size_bytes(3841)|retrieved
>the size of the image from the datastore on the VM host: 17,179,869,673
>2011-10-25 
>15:52:08|19062|8:8|reload|VMware.pm:get_image_size_bytes(3851)|image size
>retrieved from both the image repository and VM host datastore:
>|19062|8:8|reload| image repository: 898,237,415
>|19062|8:8|reload| VM host datastore: 17,179,869,673
>2011-10-25 
>15:52:08|19062|8:8|reload|VMware.pm:get_image_size_bytes(3871)|size of
>vmwarelinux-base64linux19-v0 image:
>|19062|8:8|reload| 17,179,869,673 bytes
>|19062|8:8|reload| 16,384 MB
>|19062|8:8|reload| 16.00 GB
>2011-10-25 
>15:52:08|19062|8:8|reload|VMware.pm:get_vm_additional_vmx_bytes_required(4
>7
>13)|4294967418 additional bytes required for REDO files because VM disk
>mode is NOT persistent
>2011-10-25 
>15:52:08|19062|8:8|reload|VMware.pm:get_vm_additional_vmx_bytes_required(4
>7
>16)|estimate of additional space required for the vmx directory:
>|19062|8:8|reload| vmem/vswp file: 536,870,912 bytes, 512.0 MB, 0.50 GB
>|19062|8:8|reload| redo files: 4,294,967,418 bytes, 4,096.0 MB, 4.00 GB
>|19062|8:8|reload| total: 4,831,838,330 bytes, 4,608.0 MB, 4.50 GB
>2011-10-25 
>15:52:09|19062|8:8|reload|Linux.pm:file_exists(1404)|'/vmfs/volumes/datast
>o
>re1/vclimages/vmwarelinux-base64linux19-v0/vmwarelinux-base64linux19-v0.vm
>d
>k' exists on vcldell_01, files: 1, directories: 0, links: 0
>2011-10-25 
>15:52:09|19062|8:8|reload|VMware.pm:get_image_size_bytes(3819)|VM profile
>vmdisk is set to 'localdisk', attempting to retrieve image size from image
>repository
>2011-10-25 
>15:52:09|19062|8:8|reload|Linux.pm:file_exists(1404)|'/vmfs/volumes/datast
>o
>re1/vclrepository' exists on vcldell_01, files: 0, directories: 1, links:
>0
>2011-10-25 
>15:52:09|19062|8:8|reload|VMware.pm:is_repository_mounted_on_vmhost(5485)|
>i
>mage repository is mounted on VM host vcldell_01:
>/vmfs/volumes/datastore1/vclrepository
>2011-10-25 
>15:52:09|19062|8:8|reload|VMware.pm:get_image_size_bytes(3821)|checking
>size of image in image repository mounted on VM host:
>vcldell_01:/vmfs/volumes/datastore1/vclrepository
>2011-10-25 15:52:09|19062|8:8|reload|Linux.pm:get_file_size(2022)|size of
>'/vmfs/volumes/datastore1/vclrepository/vmwarelinux-base64linux19-v0/vmwar
>e
>linux-base64linux19-v0*.vmdk' on vcldell_01:
>|19062|8:8|reload| used: 898,237,415 bytes, 856.6 MB, 0.84 GB
>|19062|8:8|reload| allocated: 903,872,512 bytes, 862.0 MB, 0.84 GB
>2011-10-25 15:52:10|19062|8:8|reload|Linux.pm:get_file_size(2022)|size of
>'/vmfs/volumes/datastore1/vclimages/vmwarelinux-base64linux19-v0/vmwarelin
>u
>x-base64linux19-v0*.vmdk' on vcldell_01:
>|19062|8:8|reload| used: 17,179,869,673 bytes, 16,384.0 MB, 16.00 GB
>|19062|8:8|reload| allocated: 17,179,869,184 bytes, 16,384.0 MB, 16.00 GB
>2011-10-25 
>15:52:10|19062|8:8|reload|VMware.pm:get_image_size_bytes(3841)|retrieved
>the size of the image from the datastore on the VM host: 17,179,869,673
>2011-10-25 
>15:52:10|19062|8:8|reload|VMware.pm:get_image_size_bytes(3851)|image size
>retrieved from both the image repository and VM host datastore:
>|19062|8:8|reload| image repository: 898,237,415
>|19062|8:8|reload| VM host datastore: 17,179,869,673
>2011-10-25 
>15:52:10|19062|8:8|reload|VMware.pm:get_image_size_bytes(3871)|size of
>vmwarelinux-base64linux19-v0 image:
>|19062|8:8|reload| 17,179,869,673 bytes
>|19062|8:8|reload| 16,384 MB
>|19062|8:8|reload| 16.00 GB
>2011-10-25 
>15:52:10|19062|8:8|reload|VMware.pm:get_vm_additional_vmdk_bytes_required(
>4
>657)|no additional space required for vmdk files because they already
>exist on VM host
>2011-10-25 
>15:52:10|19062|8:8|reload|VMware.pm:get_vm_additional_vmdk_bytes_required(
>4
>662)|VM requires appoximately 0 additional bytes (0 MB, 0 GB) of disk
>space on the VM host for the vmdk directory
>2011-10-25 
>15:52:10|19062|8:8|reload|VMware.pm:check_vmhost_disk_space(2070)|enough
>space is available on shared vmx/vmdk volume on VM host vcldell_01:
>'/vmfs/volumes/datastore1/vclimages'
>|19062|8:8|reload| vmx additional space required:          4,831,838,330
>bytes, 4,608.0 MB, 4.50 GB
>|19062|8:8|reload| vmdk additional space required:         0 bytes, 0.0
>MB, 0.00 GB
>|19062|8:8|reload| total additional space required:        4,831,838,330
>bytes, 4,608.0 MB, 4.50 GB
>|19062|8:8|reload| shared vmx/vmdk volume available space: 248,047,992,832
>bytes, 236,557.0 MB, 231.01 GB
>2011-10-25 
>15:52:10|19062|8:8|reload|Module.pm:create_mn_os_object(335)|management
>node OS object has already been created, address: 222db60, returning 1
>2011-10-25 
>15:52:10|19062|8:8|reload|Module.pm:new(203)|VCL::Module::Semaphore object
>created, address: 1cac6c0
>2011-10-25 
>15:52:10|19062|8:8|reload|Module.pm:code_loop_timeout(742)|attempting to
>open lockfile, maximum of 1200 seconds
>2011-10-25 
>15:52:10|19062|8:8|reload|Module.pm:code_loop_timeout(759)|attempt 1:
>attempting to open lockfile
>2011-10-25 
>15:52:10|19062|8:8|reload|Semaphore.pm:open_lockfile(146)|opened and
>obtained an exclusive lock on file:
>/tmp/vcldell_01-vmfs-volumes-datastore1-vclimages-vmwarelinux-base64linux1
>9
>-v0.lock
>2011-10-25 
>15:52:10|19062|8:8|reload|Module.pm:code_loop_timeout(762)|attempting to
>open lockfile, code returned true
>2011-10-25 15:52:10|19062|8:8|reload|Module.pm:get_semaphore(844)|created
>Semaphore object, memory address: 1cac6c0
>2011-10-25 
>15:52:10|19062|8:8|reload|Linux.pm:file_exists(1404)|'/vmfs/volumes/datast
>o
>re1/vclimages/vmwarelinux-base64linux19-v0/vmwarelinux-base64linux19-v0.vm
>d
>k' exists on vcldell_01, files: 1, directories: 0, links: 0
>2011-10-25 15:52:10|19062|8:8|reload|VMware.pm:prepare_vmdk(1785)|VM is
>not persistent and nonpersistent vmdk file already exists on VM host
>vcldell_01: 
>/vmfs/volumes/datastore1/vclimages/vmwarelinux-base64linux19-v0/vmwarelinu
>x
>-base64linux19-v0.vmdk
>2011-10-25 
>15:52:10|19062|8:8|reload|Semaphore.pm:release_lockfile(248)|deleted file:
>/tmp/vcldell_01-vmfs-volumes-datastore1-vclimages-vmwarelinux-base64linux1
>9
>-v0.lock
>2011-10-25 15:52:10|19062|8:8|reload|Semaphore.pm:DESTROY(281)|destroyed
>Semaphore object, memory address: 1cac6c0
>2011-10-25 15:52:10|19062|8:8|reload|utils.pm:insertloadlog(3875)|inserted
>computer=14, transfervm, copied vmwarelinux-base64linux19-v0 to
>linux64base
>2011-10-25 15:52:10|19062|8:8|reload|VMware.pm:get_vm_ram(4306)|image ram
>setting is too low: 0 MB, 512 MB will be used
>2011-10-25 
>15:52:10|19062|8:8|reload|VMware.pm:get_vm_os_configuration(4210)|retrieve
>d
> default VM configuration for OS: linux-x86_64
>|19062|8:8|reload| : {
>|19062|8:8|reload| :   "ethernet-virtualDev" => "e1000",
>|19062|8:8|reload| :   "guestOS" => "otherlinux-64",
>|19062|8:8|reload| :   "scsi-virtualDev" => "lsiLogic"
>|19062|8:8|reload| : }
>|19062|8:8|reload| ---- WARNING ----
>|19062|8:8|reload| 2011-10-25
>15:52:10|19062|8:8|reload|DataStructure.pm:_automethod(812)|corresponding
>data has not been initialized for get_computer_eth0_mac_address:
>$self->request_data->{reservation}{8}{computer}{eth0macaddress}
>|19062|8:8|reload| ( 0) DataStructure.pm, _automethod (line: 812)
>|19062|8:8|reload| (-1) Autoload.pm, __ANON__ (line: 80)
>|19062|8:8|reload| (-2) VMware.pm, prepare_vmx (line: 1457)
>|19062|8:8|reload| (-3) VMware.pm, load (line: 394)
>|19062|8:8|reload| (-4) new.pm, reload_image (line: 618)
>|19062|8:8|reload| (-5) new.pm, process (line: 248)
>|19062|8:8|reload| ---- WARNING ----
>|19062|8:8|reload| 2011-10-25
>15:52:10|19062|8:8|reload|VMware.pm:load(395)|failed to prepare vmx file
>for linux64base on VM host: vcldell_01
>|19062|8:8|reload| ( 0) VMware.pm, load (line: 395)
>|19062|8:8|reload| (-1) new.pm, reload_image (line: 618)
>|19062|8:8|reload| (-2) new.pm, process (line: 248)
>|19062|8:8|reload| (-3) vcld, make_new_child (line: 568)
>|19062|8:8|reload| (-4) vcld, main (line: 346)
>|19062|8:8|reload| ---- WARNING ----
>|19062|8:8|reload| 2011-10-25
>15:52:10|19062|8:8|reload|new.pm:reload_image(623)|vmwarelinux-base64linux
>1
>9-v0 failed to load on linux64base, returning
>|19062|8:8|reload| ( 0) new.pm, reload_image (line: 623)
>|19062|8:8|reload| (-1) new.pm, process (line: 248)
>|19062|8:8|reload| (-2) vcld, make_new_child (line: 568)
>|19062|8:8|reload| (-3) vcld, main (line: 346)
>2011-10-25 15:52:10|19062|8:8|reload|utils.pm:insertloadlog(3875)|inserted
>computer=14, loadimagefailed, vmwarelinux-base64linux19-v0 failed to load
>on linux64base
>|19062|8:8|reload| ---- WARNING ----
>|19062|8:8|reload| 2011-10-25
>15:52:10|19062|8:8|reload|new.pm:process(295)|failed to load linux64base
>with vmwarelinux-base64linux19-v0
>|19062|8:8|reload| ( 0) new.pm, process (line: 295)
>|19062|8:8|reload| (-1) vcld, make_new_child (line: 568)
>|19062|8:8|reload| (-2) vcld, main (line: 346)
>2011-10-25 
>15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_state_name(2305)|a
>t
>tempting to retrieve current state of computer linux64base from the
>database
>2011-10-25 
>15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_state_name(2336)|r
>e
>trieved current state of computer linux64base from the database: reloading
>2011-10-25 
>15:52:10|19062|8:8|reload|DataStructure.pm:_automethod(834)|data structure
>updated: $self->request_data->{reservation}{8}{computer}{state}{name}
>|19062|8:8|reload| computer_state_name = reloading
>2011-10-25 
>15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_private_ip_address
>(
>1581)|attempting to retrieve private IP address for computer: linux64base
>2011-10-25 
>15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_private_ip_address
>(
>1585)|retrieved contents of /etc/hosts on this management node, contains
>10 lines
>2011-10-25 
>15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_private_ip_address
>(
>1645)|returning IP address from /etc/hosts file: 10.0.0.2
>2011-10-25 15:52:10|19062|8:8|reload|utils.pm:is_inblockrequest(6163)|zero
>rows were returned from database select
>2011-10-25 
>15:52:10|19062|8:8|reload|DataStructure.pm:get_image_affiliation_name(2035
>)
>|image owner id: 1
>2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2709)|database
>requested (information_schema) does not match handle stored in $ENV{dbh}
>(vcl:localhost)
>2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2760)|database
>handle stored in $ENV{dbh}
>2011-10-25 
>15:52:10|19062|8:8|reload|DataStructure.pm:retrieve_user_data(1352)|attemp
>t
>ing to retrieve and store data for user: user.id = '1'
>2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2709)|database
>requested (vcl) does not match handle stored in $ENV{dbh}
>(information_schema:localhost)
>2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2760)|database
>handle stored in $ENV{dbh}
>2011-10-25 
>15:52:10|19062|8:8|reload|DataStructure.pm:retrieve_user_data(1415)|data
>has been retrieved for user: admin (id: 1)
>
>
>
>
>On 10/25/11 12:00 PM, "Alexander Patterson"
><al...@csueastbay.edu> wrote:
>
>>Hello,
>>
>> Here is the main issue, You need to have your datastore the location
>>that you are storing you VM images in the correct place. As of right
>>now they are looking  in the /vmfs/volumes/local-datastore
>>
>>You can either move your images to this folder or change the default
>>location.
>>
>>
>>To do this go to Virtual Host
>>Click on VM host Profiles
>>Click on Configure Profile (Make to to select the VMware ESXI Standard
>>Localdisk
>>from the sounds of it you have Local storage and are storing your VM's
>>locally.
>>
>>The Data Store Path can be changed to the current location or you can
>>move the files the choice is yours. Make sure you have the Virtual
>>Switches set up
>>I'm using custom VLAN switch 0 = private and switch 1 = private
>>You don't have to set a Repository Path but the Data Store Path has to
>>be correct.
>>
>>-Alex
>>
>>327|5:5|image| ---- WARNING ----
>>|5327|5:5|image| 2011-10-25
>>11:38:43|5327|5:5|image|VMware.pm:_get_datastore_name(5848)|unable to
>>determine datastore name from path: '/vmfs/volumes/local-datastore', path
>>does not begin with any of the datastore paths:
>>
>>2011/10/25 Evelio Quiros <ev...@fiu.edu>:
>>> OK,
>>>
>>> After adding the missing javascript, I am able to get the Virtual Hosts
>>> page to display.
>>>
>>> I added 10 VMs which have been added to the database, as well as the
>>>base
>>> image I want to capture, so 11 in all.
>>>
>>> Does VCL require the Vsphere module to add a virtual machine computer ?
>>>
>>> Also, I am using a free version of ESXi. Is there a licensing issue ?
>>>
>>>
>>> I tried once again to capture the base image, and I got this error:
>>>
>>>
>>> VCL::image object could not be created and initialized
>>> 
>>>------------------------------------------------------------------------
>>> time: 2011-10-25 11:38:43
>>> caller: vcld:make_new_child(571)
>>> ( 0) vcld, make_new_child (line: 571)
>>> (-1) vcld, main (line: 346)
>>> 
>>>------------------------------------------------------------------------
>>> management node: vcltst.fiu.edu
>>> reservation PID: 5327
>>> parent vcld PID: 15838
>>>
>>> request ID: 5
>>> reservation ID: 5
>>> request state/laststate: image/image
>>> request start time: 2011-10-25 11:38:35
>>> request end time: 2011-10-25 12:38:35
>>> for imaging: no
>>> log ID: none
>>>
>>> computer: redhat64base
>>> computer id: 12
>>> computer type: virtualmachine
>>> computer eth0 MAC address: <undefined>
>>> computer eth1 MAC address: <undefined>
>>> computer private IP address: 10.0.0.2
>>> computer public IP address: 10.106.128.53
>>> computer in block allocation: no
>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>
>>> vm host: vcldell_01
>>> vm host ID: 2
>>> vm host computer ID: 13
>>> vm profile: VMware ESX - local storage
>>> vm profile VM path: /vmfs/volumes/local-datastore
>>> vm profile repository path: 0
>>> vm profile datastore path: /vmfs/volumes/local-datastore
>>> vm profile disk type: localdisk
>>>
>>> image: vmwarelinux-redhat_linux16-v0
>>> image display name: redhat_linux
>>> image ID: 16
>>> image revision ID: 9
>>> image size: 1450 MB
>>> use Sysprep: yes
>>> root access: yes
>>> image owner ID: 1
>>> image owner affiliation: Local
>>> image revision date created: 2011-10-25 11:38:35
>>> image revision production: yes
>>> OS module: VCL::Module::OS::Linux
>>>
>>> user: admin
>>> user name: vcl admin
>>> user ID: 1
>>> user affiliation: Local
>>> 
>>>------------------------------------------------------------------------
>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>> 2011-10-25 
>>>11:38:41|5327|5:5|image|vSphere_SDK.pm:initialize(1826)|vSphere
>>> SDK for Perl does not appear to be installed on this managment node,
>>> unable to load VMware vSphere SDK Perl modules
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>object
>>> could not be created: VCL::Module::Provisioning::VMware::vSphere_SDK
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(613)|computer ID
>>> argument was specified, retrieving data for computer ID: 13
>>> 2011-10-25 
>>>11:38:41|5327|5:5|image|DataStructure.pm:_initialize(643)|image
>>> ID argument was specified: 4, DataStructure object will contain image
>>> information for the production imagerevision of this image
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(660)|retrieved
>>>data
>>> for imagerevision ID: 4
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(676)|retrieved
>>>data
>>> for image ID: 4
>>> 2011-10-25
>>> 
>>>11:38:41|5327|5:5|image|VMware.pm:get_vmhost_datastructure(1190)|created
>>> DataStructure object for VM host: vcldell_01
>>> 2011-10-25
>>> 
>>>11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1293)|attempting
>>> to load VMware control module:
>>>VCL::Module::Provisioning::VMware::VIM_SSH
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>> VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
>>> 2011-10-25 11:38:41|5327|5:5|image|Module.pm:new(172)|set 'vmhost_data'
>>> key for VCL::Module::Provisioning::VMware::VIM_SSH object from
>>>arguments
>>> 2011-10-25 11:38:41|5327|5:5|image|Module.pm:new(172)|set 'vmhost_os'
>>>key
>>> for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
>>> 2011-10-25
>>> 11:38:41|5327|5:5|image|Module.pm:create_mn_os_object(335)|management
>>>node
>>> OS object has already been created, address: 219ab58, returning 1
>>> 2011-10-25
>>> 
>>>11:38:41|5327|5:5|image|Module.pm:new(200)|VCL::Module::Provisioning::VM
>>>w
>>>ar
>>> e::VIM_SSH object created for computer redhat64base, address: 1fd9588
>>> 2011-10-25 11:38:42|5327|5:5|image|VIM_SSH.pm:initialize(138)|VIM
>>> executable available on VM host: vim-cmd
>>> 2011-10-25
>>> 
>>>11:38:42|5327|5:5|image|VIM_SSH.pm:initialize(140)|VCL::Module::Provisio
>>>n
>>>in
>>> g::VMware::VIM_SSH object initialized
>>> 2011-10-25
>>> 11:38:42|5327|5:5|image|VMware.pm:get_vmhost_api_object(1320)|created
>>>API
>>> object: VCL::Module::Provisioning::VMware::VIM_SSH
>>> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(278)|VMware on
>>>VM
>>> host vcldell_01 will be controlled using vim-cmd via SSH
>>> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(293)|VMware OS
>>>and
>>> API objects created for VM host vcldell_01:
>>> |5327|5:5|image| VM host OS object type:
>>>VCL::Module::OS::Linux::UnixLab
>>> |5327|5:5|image| VMware API object type:
>>> VCL::Module::Provisioning::VMware::VIM_SSH
>>> 2011-10-25
>>> 11:38:42|5327|5:5|image|VMware.pm:get_vmhost_product_name(5405)|VMware
>>> product being used on VM host vcldell_01: 'VMware ESXi 5.0.0
>>>build-469512'
>>> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(307)|product:
>>> VMware ESXi 5.0.0 build-469512, OS object:
>>>VCL::Module::OS::Linux::UnixLab
>>> 2011-10-25 11:38:42|5327|5:5|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd
>>> call count: 1 (hostsvc/datastore/listsummary)
>>> 2011-10-25 
>>>11:38:43|5327|5:5|image|VIM_SSH.pm:_run_vim_cmd(208)|executed
>>> command on VM host vcldell_01: vim-cmd hostsvc/datastore/listsummary
>>> 2011-10-25
>>> 11:38:43|5327|5:5|image|VMware.pm:get_datastore_info(5531)|retrieved
>>> datastore info from VM host:
>>> |5327|5:5|image| datastore1
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>> 11:38:43|5327|5:5|image|VMware.pm:_get_datastore_name(5848)|unable to
>>> determine datastore name from path: '/vmfs/volumes/local-datastore',
>>>path
>>> does not begin with any of the datastore paths:
>>> |5327|5:5|image| '[datastore1]'
>>> |5327|5:5|image| '/vmfs/volumes/datastore1'
>>> |5327|5:5|image| '/vmfs/volumes/4e96b3e5-a6562886-638a-00188be54b59'
>>> |5327|5:5|image| ( 0) VMware.pm, _get_datastore_name (line: 5848)
>>> |5327|5:5|image| (-1) VMware.pm, _get_datastore_root_normal_path (line:
>>> 5685)
>>> |5327|5:5|image| (-2) VMware.pm, _get_normal_path (line: 5775)
>>> |5327|5:5|image| (-3) VMware.pm, get_vmx_base_directory_path (line:
>>>2743)
>>> |5327|5:5|image| (-4) VMware.pm, initialize (line: 313)
>>> |5327|5:5|image| (-5) Module.pm, new (line: 207)
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>> 
>>>11:38:43|5327|5:5|image|VMware.pm:_get_datastore_root_normal_path(5687)|
>>>f
>>>ai
>>> led to determine datastore root normal path, unable to determine
>>>datastore
>>> name: /vmfs/volumes/local-datastore
>>> |5327|5:5|image| ( 0) VMware.pm, _get_datastore_root_normal_path (line:
>>> 5687)
>>> |5327|5:5|image| (-1) VMware.pm, _get_normal_path (line: 5775)
>>> |5327|5:5|image| (-2) VMware.pm, get_vmx_base_directory_path (line:
>>>2743)
>>> |5327|5:5|image| (-3) VMware.pm, initialize (line: 313)
>>> |5327|5:5|image| (-4) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-5) Module.pm, create_provisioning_object (line: 423)
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>> 11:38:43|5327|5:5|image|VMware.pm:_get_normal_path(5777)|unable to
>>> determine normal path, failed to determine datastore root normal path:
>>> /vmfs/volumes/local-datastore
>>> |5327|5:5|image| ( 0) VMware.pm, _get_normal_path (line: 5777)
>>> |5327|5:5|image| (-1) VMware.pm, get_vmx_base_directory_path (line:
>>>2743)
>>> |5327|5:5|image| (-2) VMware.pm, initialize (line: 313)
>>> |5327|5:5|image| (-3) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-4) Module.pm, create_provisioning_object (line: 423)
>>> |5327|5:5|image| (-5) State.pm, initialize (line: 117)
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>> 
>>>11:38:43|5327|5:5|image|VMware.pm:get_vmx_base_directory_path(2749)|unab
>>>l
>>>e
>>> to determine the vmx base directory path, failed to convert path
>>> configured in the VM profile to a normal path:
>>> /vmfs/volumes/local-datastore
>>> |5327|5:5|image| ( 0) VMware.pm, get_vmx_base_directory_path (line:
>>>2749)
>>> |5327|5:5|image| (-1) VMware.pm, initialize (line: 313)
>>> |5327|5:5|image| (-2) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-3) Module.pm, create_provisioning_object (line: 423)
>>> |5327|5:5|image| (-4) State.pm, initialize (line: 117)
>>> |5327|5:5|image| (-5) Module.pm, new (line: 207)
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>> 11:38:43|5327|5:5|image|VMware.pm:initialize(315)|unable to determine
>>>vmx
>>> base directory path on VM host vcldell_01
>>> |5327|5:5|image| ( 0) VMware.pm, initialize (line: 315)
>>> |5327|5:5|image| (-1) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-2) Module.pm, create_provisioning_object (line: 423)
>>> |5327|5:5|image| (-3) State.pm, initialize (line: 117)
>>> |5327|5:5|image| (-4) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-5) vcld, make_new_child (line: 564)
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>> 
>>>11:38:43|5327|5:5|image|Module.pm:create_provisioning_object(431)|provis
>>>i
>>>on
>>> ing object could not be created, returning 0
>>> |5327|5:5|image| ( 0) Module.pm, create_provisioning_object (line: 431)
>>> |5327|5:5|image| (-1) State.pm, initialize (line: 117)
>>> |5327|5:5|image| (-2) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-3) vcld, make_new_child (line: 564)
>>> |5327|5:5|image| (-4) vcld, main (line: 346)
>>> |5327|5:5|image| ---- WARNING ----
>>> |5327|5:5|image| 2011-10-25
>>> 11:38:43|5327|5:5|image|State.pm:initialize(118)|failed to create
>>> provisioning object
>>> |5327|5:5|image| ( 0) State.pm, initialize (line: 118)
>>> |5327|5:5|image| (-1) Module.pm, new (line: 207)
>>> |5327|5:5|image| (-2) vcld, make_new_child (line: 564)
>>> |5327|5:5|image| (-3) vcld, main (line: 346)
>>> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(829)|VCL::image
>>> destructor called, address: 1e47a28
>>> 2011-10-25
>>> 
>>>11:38:43|5327|5:5|image|utils.pm:delete_computerloadlog_reservation(6742
>>>)
>>>|r
>>> emoving computerloadlog entries matching loadstate = begin
>>> 2011-10-25
>>> 
>>>11:38:43|5327|5:5|image|utils.pm:delete_computerloadlog_reservation(6789
>>>)
>>>|d
>>> eleted rows from computerloadlog for reservation id=5
>>> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(848)|number of
>>> database handles state process created: 1
>>> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(876)|VCL::image
>>> process duration: 4 seconds
>>> 2011-10-25
>>> 
>>>11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address
>>>(
>>>15
>>> 81)|attempting to retrieve private IP address for computer:
>>>redhat64base
>>> 2011-10-25
>>> 
>>>11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address
>>>(
>>>15
>>> 85)|retrieved contents of /etc/hosts on this management node, contains
>>>10
>>> lines
>>> 2011-10-25
>>> 
>>>11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address
>>>(
>>>16
>>> 45)|returning IP address from /etc/hosts file: 10.0.0.2
>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2703)|unable to
>>>use
>>> database handle stored in $ENV{dbh}
>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
>>> handle stored in $ENV{dbh}
>>> 2011-10-25 
>>>11:38:43|5327|5:5|image|utils.pm:is_inblockrequest(6163)|zero
>>> rows were returned from database select
>>> 2011-10-25
>>> 
>>>11:38:43|5327|5:5|image|DataStructure.pm:get_image_affiliation_name(2035
>>>)
>>>|i
>>> mage owner id: 1
>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2709)|database
>>> requested (information_schema) does not match handle stored in
>>>$ENV{dbh}
>>> (vcl:localhost)
>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
>>> handle stored in $ENV{dbh}
>>> 2011-10-25
>>> 
>>>11:38:43|5327|5:5|image|DataStructure.pm:retrieve_user_data(1352)|attemp
>>>t
>>>in
>>> g to retrieve and store data for user: user.id = '1'
>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2709)|database
>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>> (information_schema:localhost)
>>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
>>> handle stored in $ENV{dbh}
>>> 2011-10-25
>>> 11:38:43|5327|5:5|image|DataStructure.pm:retrieve_user_data(1415)|data
>>>has
>>> been retrieved for user: admin (id: 1)
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 10/25/11 10:26 AM, "Aaron Coburn" <ac...@amherst.edu> wrote:
>>>
>>>>Al,
>>>>if you plan to use the vSphere API, then you will need to install the
>>>>vSphere SDK for Perl separately. The perl modules are available here --
>>>>just make sure that you download the release that matches your vCenter
>>>>version.
>>>>
>>>>http://www.vmware.com/support/developer/viperltoolkit/
>>>>
>>>>Aaron Coburn
>>>>
>>>>
>>>>On Oct 25, 2011, at 10:03 AM, Evelio Quiros wrote:
>>>>
>>>>> Thanks again Aaron. It seems we are taking baby steps here.
>>>>>
>>>>> Ok, next issue: When I click "Configure Host" in the vcl web
>>>>>interface,
>>>>> nothing happens.
>>>>>
>>>>> My Vmware server is listed there. It is in "vmhostinuse" state.
>>>>>
>>>>> I noticed some complaints below about the Vsphere perl module not
>>>>>being
>>>>> installed.
>>>>> I thought that was done in the "install_perl_libraries script.
>>>>>
>>>>> Thanks again for all your help.
>>>>>
>>>>> Al Quiros
>>>>>
>>>>>
>>>>> On 10/25/11 9:43 AM, "Aaron Peeler" <fa...@ncsu.edu> wrote:
>>>>>
>>>>>> In the log output your missing the vmhost information.
>>>>>>
>>>>>> Make sure your vm host server have a correctly configured vmhost
>>>>>> profile and you have assigned your vms to the virtual host server by
>>>>>> using the Virtual Host interface.
>>>>>>
>>>>>>
>>>>>>https://cwiki.apache.org/confluence/display/VCL/VCL+2.2.1+-+Further+S
>>>>>>t
>>>>>>ep
>>>>>>s+
>>>>>> if+Using+VMware
>>>>>> https://cwiki.apache.org/confluence/display/VCL/VMware+Configuration
>>>>>>
>>>>>> I'm not seeing the virtual host interface mentioned directly in the
>>>>>> vcl 2.2.1 install guide. I'll added that to the first link.
>>>>>>
>>>>>> Here is a link from a bootcamp that you can review this morning
>>>>>>while
>>>>>> I work on adding the content to Apache VCL:
>>>>>>
>>>>>>https://sites.google.com/a/ncsu.edu/vcl-bootcamp/exercises/assign-a-v
>>>>>>m
>>>>>>-t
>>>>>>o-
>>>>>> a-virtual-host
>>>>>>
>>>>>> Aaron
>>>>>>
>>>>>>
>>>>>> On Tue, Oct 25, 2011 at 9:19 AM, Evelio Quiros <ev...@fiu.edu>
>>>>>>wrote:
>>>>>>> Thank you Aaron.
>>>>>>>
>>>>>>> Ok, now it can resolve the name redhat64base to the private IP
>>>>>>>address
>>>>>>> 10.0.0.2.
>>>>>>> I tried to add the base image as the name linux64.
>>>>>>> It resides in the database as redhat64base, with the public IP of
>>>>>>> 10.106.128.53, and set as available.
>>>>>>> I'm not sure what this error message is telling meŠ
>>>>>>>
>>>>>>> VCL::image object could not be created and initialized
>>>>>>>
>>>>>>>--------------------------------------------------------------------
>>>>>>>-
>>>>>>>--
>>>>>>>-
>>>>>>> time: 2011-10-25 09:30:44
>>>>>>> caller: vcld:make_new_child(571)
>>>>>>> ( 0) vcld, make_new_child (line: 571)
>>>>>>> (-1) vcld, main (line: 346)
>>>>>>>
>>>>>>>--------------------------------------------------------------------
>>>>>>>-
>>>>>>>--
>>>>>>>-
>>>>>>> management node: vcltst.fiu.edu
>>>>>>> reservation PID: 31318
>>>>>>> parent vcld PID: 15838
>>>>>>>
>>>>>>> request ID: 4
>>>>>>> reservation ID: 4
>>>>>>> request state/laststate: image/image
>>>>>>> request start time: 2011-10-25 09:30:37
>>>>>>> request end time: 2011-10-25 10:30:37
>>>>>>> for imaging: no
>>>>>>> log ID: none
>>>>>>>
>>>>>>> computer: redhat64base
>>>>>>> computer id: 12
>>>>>>> computer type: blade
>>>>>>> computer eth0 MAC address: <undefined>
>>>>>>> computer eth1 MAC address: <undefined>
>>>>>>> computer private IP address: 10.0.0.2
>>>>>>> computer public IP address: 10.106.128.53
>>>>>>> computer in block allocation: no
>>>>>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>>>>>
>>>>>>> image: vmwarelinux-linux6414-v0
>>>>>>> image display name: linux64
>>>>>>> image ID: 14
>>>>>>> image revision ID: 8
>>>>>>> image size: 1450 MB
>>>>>>> use Sysprep: yes
>>>>>>> root access: yes
>>>>>>> image owner ID: 1
>>>>>>> image owner affiliation: Local
>>>>>>> image revision date created: 2011-10-25 09:30:37
>>>>>>> image revision production: yes
>>>>>>> OS module: VCL::Module::OS::Linux
>>>>>>>
>>>>>>> user: admin
>>>>>>> user name: vcl admin
>>>>>>> user ID: 1
>>>>>>> user affiliation: Local
>>>>>>>
>>>>>>>--------------------------------------------------------------------
>>>>>>>-
>>>>>>>--
>>>>>>>-
>>>>>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attem
>>>>>>>p
>>>>>>>ti
>>>>>>>ng
>>>>>>> to load VMware control module:
>>>>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>> 2011-10-25
>>>>>>> 
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loade
>>>>>>>d
>>>>>>> VMware control module:
>>>>>>>VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>'vmhost_data'
>>>>>>> key for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>> arguments
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>'vmhost_os'
>>>>>>> key
>>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>>arguments
>>>>>>> 2011-10-25
>>>>>>> 
>>>>>>>09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|manageme
>>>>>>>n
>>>>>>>t
>>>>>>> node OS object has already been created, address: 21956b8,
>>>>>>>returning 1
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisionin
>>>>>>>g
>>>>>>>::
>>>>>>>VM
>>>>>>> wa
>>>>>>> re::vSphere_SDK object created for computer redhat64base, address:
>>>>>>> 21e6980
>>>>>>> 2011-10-25
>>>>>>> 09:30:43|31318|4:4|image|vSphere_SDK.pm:initialize(1826)|vSphere 
>>>>>>>SDK
>>>>>>>for
>>>>>>> Perl does not appear to be installed on this managment node, unable
>>>>>>>to
>>>>>>> load VMware vSphere SDK Perl modules
>>>>>>> 2011-10-25
>>>>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>>> object
>>>>>>> could not be created: 
>>>>>>>VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspon
>>>>>>>d
>>>>>>>in
>>>>>>>g
>>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>>> $self->request_data->{reservation}{4}{computer}{vmhost}{computerid}
>>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>1161)
>>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 
>>>>>>>1282)
>>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspon
>>>>>>>d
>>>>>>>in
>>>>>>>g
>>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>>>
>>>>>>>
>>>>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{vmprofile}{i
>>>>>>>m
>>>>>>>ag
>>>>>>>ei
>>>>>>> d}
>>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>1162)
>>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 
>>>>>>>1282)
>>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_datastructure(1190)|cr
>>>>>>>e
>>>>>>>at
>>>>>>>ed
>>>>>>> DataStructure object for VM host: redhat64base
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attem
>>>>>>>p
>>>>>>>ti
>>>>>>>ng
>>>>>>> to load VMware control module:
>>>>>>> VCL::Module::Provisioning::VMware::VIM_SSH
>>>>>>> 2011-10-25
>>>>>>> 
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loade
>>>>>>>d
>>>>>>> VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>'vmhost_data'
>>>>>>> key for VCL::Module::Provisioning::VMware::VIM_SSH object from
>>>>>>>arguments
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set 
>>>>>>>'vmhost_os'
>>>>>>> key
>>>>>>> for VCL::Module::Provisioning::VMware::VIM_SSH object from 
>>>>>>>arguments
>>>>>>> 2011-10-25
>>>>>>> 
>>>>>>>09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|manageme
>>>>>>>n
>>>>>>>t
>>>>>>> node OS object has already been created, address: 21956b8, 
>>>>>>>returning 1
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisionin
>>>>>>>g
>>>>>>>::
>>>>>>>VM
>>>>>>> wa
>>>>>>> re::VIM_SSH object created for computer redhat64base, address: 
>>>>>>>24f7888
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|VIM_SSH.pm:initialize(126)|VIM
>>>>>>> executable is not available on the VM host, output:
>>>>>>> |31318|4:4|image| bash: vim-cmd: command not found
>>>>>>> |31318|4:4|image| bash: vmware-vim-cmd: command not found
>>>>>>> 2011-10-25
>>>>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>>> object
>>>>>>> could not be created: VCL::Module::Provisioning::VMware::VIM_SSH
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspon
>>>>>>>d
>>>>>>>in
>>>>>>>g
>>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>>> $self->request_data->{reservation}{4}{computer}{vmhost}{computerid}
>>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>1161)
>>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 
>>>>>>>1282)
>>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspon
>>>>>>>d
>>>>>>>in
>>>>>>>g
>>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>>>
>>>>>>>
>>>>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{vmprofile}{i
>>>>>>>m
>>>>>>>ag
>>>>>>>ei
>>>>>>> d}
>>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>1162)
>>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 
>>>>>>>1282)
>>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_datastructure(1190)|cr
>>>>>>>e
>>>>>>>at
>>>>>>>ed
>>>>>>> DataStructure object for VM host: redhat64base
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attem
>>>>>>>p
>>>>>>>ti
>>>>>>>ng
>>>>>>> to load VMware control module:
>>>>>>> VCL::Module::Provisioning::VMware::vmware_cmd
>>>>>>> 2011-10-25
>>>>>>> 
>>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loade
>>>>>>>d
>>>>>>> VMware control module: 
>>>>>>>VCL::Module::Provisioning::VMware::vmware_cmd
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>>'vmhost_data'
>>>>>>> key for VCL::Module::Provisioning::VMware::vmware_cmd object from
>>>>>>> arguments
>>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set 
>>>>>>>'vmhost_os'
>>>>>>> key
>>>>>>> for VCL::Module::Provisioning::VMware::vmware_cmd object from
>>>>>>>arguments
>>>>>>> 2011-10-25
>>>>>>> 
>>>>>>>09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|manageme
>>>>>>>n
>>>>>>>t
>>>>>>> node OS object has already been created, address: 21956b8, 
>>>>>>>returning 1
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisionin
>>>>>>>g
>>>>>>>::
>>>>>>>VM
>>>>>>> wa
>>>>>>> re::vmware_cmd object created for computer redhat64base, address:
>>>>>>> 251d1e0
>>>>>>> 2011-10-25
>>>>>>> 09:30:44|31318|4:4|image|vmware_cmd.pm:initialize(107)|vmware-cmd 
>>>>>>>is
>>>>>>>not
>>>>>>> available on the VM host, output:
>>>>>>> |31318|4:4|image| bash: vmware-cmd: command not found
>>>>>>> 2011-10-25
>>>>>>> 09:30:44|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>>> object
>>>>>>> could not be created: VCL::Module::Provisioning::VMware::vmware_cmd
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>> 09:30:44|31318|4:4|image|VMware.pm:initialize(285)|failed to 
>>>>>>>create 
>>>>>>>an
>>>>>>> object to control VMware on VM host: redhat64base
>>>>>>> |31318|4:4|image| ( 0) VMware.pm, initialize (line: 285)
>>>>>>> |31318|4:4|image| (-1) Module.pm, new (line: 207)
>>>>>>> |31318|4:4|image| (-2) Module.pm, create_provisioning_object (line:
>>>>>>>423)
>>>>>>> |31318|4:4|image| (-3) State.pm, initialize (line: 117)
>>>>>>> |31318|4:4|image| (-4) Module.pm, new (line: 207)
>>>>>>> |31318|4:4|image| (-5) vcld, make_new_child (line: 564)
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|Module.pm:create_provisioning_object(431)|p
>>>>>>>r
>>>>>>>ov
>>>>>>>is
>>>>>>> io
>>>>>>> ning object could not be created, returning 0
>>>>>>> |31318|4:4|image| ( 0) Module.pm, create_provisioning_object (line:
>>>>>>>431)
>>>>>>> |31318|4:4|image| (-1) State.pm, initialize (line: 117)
>>>>>>> |31318|4:4|image| (-2) Module.pm, new (line: 207)
>>>>>>> |31318|4:4|image| (-3) vcld, make_new_child (line: 564)
>>>>>>> |31318|4:4|image| (-4) vcld, main (line: 346)
>>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>> 09:30:44|31318|4:4|image|State.pm:initialize(118)|failed to create
>>>>>>> provisioning object
>>>>>>> |31318|4:4|image| ( 0) State.pm, initialize (line: 118)
>>>>>>> |31318|4:4|image| (-1) Module.pm, new (line: 207)
>>>>>>> |31318|4:4|image| (-2) vcld, make_new_child (line: 564)
>>>>>>> |31318|4:4|image| (-3) vcld, main (line: 346)
>>>>>>> 2011-10-25 
>>>>>>>09:30:44|31318|4:4|image|State.pm:DESTROY(829)|VCL::image
>>>>>>> destructor called, address: 1e47818
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|utils.pm:delete_computerloadlog_reservation
>>>>>>>(
>>>>>>>67
>>>>>>>42
>>>>>>> )|
>>>>>>> removing computerloadlog entries matching loadstate = begin
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|utils.pm:delete_computerloadlog_reservation
>>>>>>>(
>>>>>>>67
>>>>>>>89
>>>>>>> )|
>>>>>>> deleted rows from computerloadlog for reservation id=4
>>>>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(848)|number of
>>>>>>> database handles state process created: 1
>>>>>>> 2011-10-25 
>>>>>>>09:30:44|31318|4:4|image|State.pm:DESTROY(876)|VCL::image
>>>>>>> process duration: 2 seconds
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_ad
>>>>>>>d
>>>>>>>re
>>>>>>>ss
>>>>>>> (1
>>>>>>> 581)|attempting to retrieve private IP address for computer:
>>>>>>> redhat64base
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_ad
>>>>>>>d
>>>>>>>re
>>>>>>>ss
>>>>>>> (1
>>>>>>> 585)|retrieved contents of /etc/hosts on this management node,
>>>>>>>contains
>>>>>>> 9
>>>>>>> lines
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_ad
>>>>>>>d
>>>>>>>re
>>>>>>>ss
>>>>>>> (1
>>>>>>> 645)|returning IP address from /etc/hosts file: 10.0.0.2
>>>>>>> 2011-10-25 
>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2703)|unable 
>>>>>>>to
>>>>>>> use
>>>>>>> database handle stored in $ENV{dbh}
>>>>>>> 2011-10-25 
>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>>>> handle stored in $ENV{dbh}
>>>>>>> 2011-10-25
>>>>>>> 09:30:44|31318|4:4|image|utils.pm:is_inblockrequest(6163)|zero
>>>>>>> rows were returned from database select
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_image_affiliation_name
>>>>>>>(
>>>>>>>20
>>>>>>>35
>>>>>>> )|
>>>>>>> image owner id: 1
>>>>>>> 2011-10-25 
>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2709)|database
>>>>>>> requested (information_schema) does not match handle stored in
>>>>>>>$ENV{dbh}
>>>>>>> (vcl:localhost)
>>>>>>> 2011-10-25 
>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>>>> handle stored in $ENV{dbh}
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:retrieve_user_data(1352)|a
>>>>>>>t
>>>>>>>te
>>>>>>>mp
>>>>>>> ti
>>>>>>> ng to retrieve and store data for user: user.id = '1'
>>>>>>> 2011-10-25 
>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2709)|database
>>>>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>>>>> (information_schema:localhost)
>>>>>>> 2011-10-25 
>>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>>>> handle stored in $ENV{dbh}
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:retrieve_user_data(1415)|d
>>>>>>>a
>>>>>>>ta
>>>>>>> has been retrieved for user: admin (id: 1)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 10/25/11 9:04 AM, "Aaron Peeler" <aa...@ncsu.edu> wrote:
>>>>>>>
>>>>>>>> Al,
>>>>>>>>
>>>>>>>> The hostname has to resolve.
>>>>>>>>
>>>>>>>> Put an entry in your /etc/hosts file.
>>>>>>>>
>>>>>>>> Aaron
>>>>>>>>
>>>>>>>> On Tue, Oct 25, 2011 at 8:52 AM, Evelio Quiros <ev...@fiu.edu>
>>>>>>>>wrote:
>>>>>>>>> Hello,
>>>>>>>>> I am getting an error when I try to capture a linux base image in
>>>>>>>>>vcl.
>>>>>>>>> I am
>>>>>>>>> following the instructions, but perhaps some parts of these may 
>>>>>>>>>have
>>>>>>>>> been
>>>>>>>>> misinterpreted.
>>>>>>>>> My VCL server is at 10.0.0.1. My Vmware based virtual machine is 
>>>>>>>>>at
>>>>>>>>> 10.0.0.2. I can ssh without passwords using keys from the vcl 
>>>>>>>>>server
>>>>>>>>> to
>>>>>>>>> the
>>>>>>>>> VM.
>>>>>>>>> The computer has been added to the database as hostname
>>>>>>>>>redhat64base,
>>>>>>>>> although I have no DNS entry to resolve that name, so I use it's
>>>>>>>>> private IP
>>>>>>>>> of 10.0.0.2.
>>>>>>>>> Below is the result of vcld trying to capture the computer to
>>>>>>>>>create a
>>>>>>>>> new
>>>>>>>>> base imageŠ.Any ideas about what could be wrong ?
>>>>>>>>> Thanks,
>>>>>>>>> Al Quiros
>>>>>>>>>
>>>>>>>>> VCL::image object could not be created and initialized
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>------------------------------------------------------------------
>>>>>>>>>-
>>>>>>>>>--
>>>>>>>>>--
>>>>>>>>> -
>>>>>>>>> time: 2011-10-25 08:58:38
>>>>>>>>> caller: vcld:make_new_child(571)
>>>>>>>>> ( 0) vcld, make_new_child (line: 571)
>>>>>>>>> (-1) vcld, main (line: 346)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>------------------------------------------------------------------
>>>>>>>>>-
>>>>>>>>>--
>>>>>>>>>--
>>>>>>>>> -
>>>>>>>>> management node: vcltst.fiu.edu
>>>>>>>>> reservation PID: 29609
>>>>>>>>> parent vcld PID: 15838
>>>>>>>>> request ID: 2
>>>>>>>>> reservation ID: 2
>>>>>>>>> request state/laststate: image/image
>>>>>>>>> request start time: 2011-10-25 08:58:37
>>>>>>>>> request end time: 2011-10-25 09:58:37
>>>>>>>>> for imaging: no
>>>>>>>>> log ID: none
>>>>>>>>> computer: redhat64base
>>>>>>>>> computer id: 12
>>>>>>>>> computer type: blade
>>>>>>>>> computer eth0 MAC address: <undefined>
>>>>>>>>> computer eth1 MAC address: <undefined>
>>>>>>>>> computer private IP address: <undefined>
>>>>>>>>> computer public IP address: 10.0.0.2
>>>>>>>>> computer in block allocation: no
>>>>>>>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>>>>>>> image: vmwarelinux-redhat64linux8-v0
>>>>>>>>> image display name: redhat64linux
>>>>>>>>> image ID: 8
>>>>>>>>> image revision ID: 6
>>>>>>>>> image size: 1450 MB
>>>>>>>>> use Sysprep: yes
>>>>>>>>> root access: yes
>>>>>>>>> image owner ID: 1
>>>>>>>>> image owner affiliation: Local
>>>>>>>>> image revision date created: 2011-10-25 08:58:37
>>>>>>>>> image revision production: yes
>>>>>>>>> OS module: VCL::Module::OS::Linux
>>>>>>>>> user: admin
>>>>>>>>> user name: vcl admin
>>>>>>>>> user ID: 1
>>>>>>>>> user affiliation: Local
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>------------------------------------------------------------------
>>>>>>>>>-
>>>>>>>>>--
>>>>>>>>>--
>>>>>>>>> -
>>>>>>>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>>>>>>>> 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_os_object(1238)|VM
>>>>>>>>> host OS module loaded: VCL::Module::OS::Linux
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_mn_os_object(335)|manage
>>>>>>>>>m
>>>>>>>>>en
>>>>>>>>>t
>>>>>>>>> node
>>>>>>>>> OS object has already been created, address: 1fbe730, returning 1
>>>>>>>>> 2011-10-25
>>>>>>>>> 
>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:new(196)|VCL::Module::OS::Linux
>>>>>>>>> object
>>>>>>>>> created for image vmwarelinux-redhat64linux8-v0, address: 24f12f0
>>>>>>>>> 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_os_object(1244)|VM
>>>>>>>>> host OS object created: VCL::Module::OS::Linux
>>>>>>>>> 2011-10-25 
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:run_command(8998)|$? 
>>>>>>>>>is
>>>>>>>>> set to
>>>>>>>>> -1, setting exit status to 0, Perl bug likely encountered
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|utils.pm:nmap_port(2645)|error occurred
>>>>>>>>> running
>>>>>>>>> nmap command: '/usr/bin/nmap redhat64base -P0 -p 22 -T 
>>>>>>>>>Aggressive',
>>>>>>>>> output:
>>>>>>>>> |29609|2:2|image| Starting Nmap 5.21 ( http://nmap.org ) at
>>>>>>>>>2011-10-25
>>>>>>>>> 08:58
>>>>>>>>> EDT
>>>>>>>>> |29609|2:2|image| Failed to resolve given hostname/IP: 
>>>>>>>>>redhat64base.
>>>>>>>>> Note
>>>>>>>>> that you can't use '/mask' AND '1-4,7,100-' style IP ranges
>>>>>>>>> |29609|2:2|image| WARNING: No targets were specified, so 0 hosts
>>>>>>>>> scanned.
>>>>>>>>> |29609|2:2|image| Nmap done: 0 IP addresses (0 hosts up) scanned 
>>>>>>>>>in
>>>>>>>>> 0.05
>>>>>>>>> seconds
>>>>>>>>> |29609|2:2|image| ( 0) utils.pm, nmap_port (line: 2645)
>>>>>>>>> |29609|2:2|image| (-1) OS.pm, is_ssh_responding (line: 383)
>>>>>>>>> |29609|2:2|image| (-2) VMware.pm, initialize (line: 252)
>>>>>>>>> |29609|2:2|image| (-3) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| (-4) Module.pm, create_provisioning_object 
>>>>>>>>>(line:
>>>>>>>>> 423)
>>>>>>>>> |29609|2:2|image| (-5) State.pm, initialize (line: 117)
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|utils.pm:nmap_port(2645)|error occurred
>>>>>>>>> running
>>>>>>>>> nmap command: '/usr/bin/nmap redhat64base -P0 -p 24 -T 
>>>>>>>>>Aggressive',
>>>>>>>>> output:
>>>>>>>>> |29609|2:2|image| Starting Nmap 5.21 ( http://nmap.org ) at
>>>>>>>>>2011-10-25
>>>>>>>>> 08:58
>>>>>>>>> EDT
>>>>>>>>> |29609|2:2|image| Failed to resolve given hostname/IP: 
>>>>>>>>>redhat64base.
>>>>>>>>> Note
>>>>>>>>> that you can't use '/mask' AND '1-4,7,100-' style IP ranges
>>>>>>>>> |29609|2:2|image| WARNING: No targets were specified, so 0 hosts
>>>>>>>>> scanned.
>>>>>>>>> |29609|2:2|image| Nmap done: 0 IP addresses (0 hosts up) scanned 
>>>>>>>>>in
>>>>>>>>> 0.05
>>>>>>>>> seconds
>>>>>>>>> |29609|2:2|image| ( 0) utils.pm, nmap_port (line: 2645)
>>>>>>>>> |29609|2:2|image| (-1) OS.pm, is_ssh_responding (line: 384)
>>>>>>>>> |29609|2:2|image| (-2) VMware.pm, initialize (line: 252)
>>>>>>>>> |29609|2:2|image| (-3) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| (-4) Module.pm, create_provisioning_object 
>>>>>>>>>(line:
>>>>>>>>> 423)
>>>>>>>>> |29609|2:2|image| (-5) State.pm, initialize (line: 117)
>>>>>>>>> 2011-10-25
>>>>>>>>> 
>>>>>>>>>08:58:38|29609|2:2|image|OS.pm:is_ssh_responding(386)|redhat64base
>>>>>>>>>is
>>>>>>>>> NOT
>>>>>>>>> responding to SSH, ports 22 or 24 are both closed
>>>>>>>>> 2011-10-25 
>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:initialize(257)|unable
>>>>>>>>> to
>>>>>>>>> control OS of VM host redhat64base using VCL::Module::OS::Linux 
>>>>>>>>>OS
>>>>>>>>> object
>>>>>>>>> because VM host is not responding to SSH
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:_automethod(812)|corresp
>>>>>>>>>o
>>>>>>>>>nd
>>>>>>>>>in
>>>>>>>>> g
>>>>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>>>>> 
>>>>>>>>>$self->request_data->{reservation}{2}{computer}{vmhost}{computerid
>>>>>>>>>}
>>>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>>>> |29609|2:2|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>>>> |29609|2:2|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>>> 1161)
>>>>>>>>> |29609|2:2|image| (-3) VMware.pm, get_vmhost_api_object (line: 
>>>>>>>>>1282)
>>>>>>>>> |29609|2:2|image| (-4) VMware.pm, initialize (line: 265)
>>>>>>>>> |29609|2:2|image| (-5) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:_automethod(812)|corresp
>>>>>>>>>o
>>>>>>>>>nd
>>>>>>>>>in
>>>>>>>>> g
>>>>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>$self->request_data->{reservation}{2}{computer}{vmhost}{vmprofile}
>>>>>>>>>{
>>>>>>>>>im
>>>>>>>>>ag
>>>>>>>>> ei
>>>>>>>>> d}
>>>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>>>> |29609|2:2|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>>>> |29609|2:2|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>>> 1162)
>>>>>>>>> |29609|2:2|image| (-3) VMware.pm, get_vmhost_api_object (line: 
>>>>>>>>>1282)
>>>>>>>>> |29609|2:2|image| (-4) VMware.pm, initialize (line: 265)
>>>>>>>>> |29609|2:2|image| (-5) Module.pm, new (line: 207)
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_datastructure(1190)|
>>>>>>>>>c
>>>>>>>>>re
>>>>>>>>>at
>>>>>>>>> ed
>>>>>>>>> DataStructure object for VM host: redhat64base
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1293)|att
>>>>>>>>>e
>>>>>>>>>mp
>>>>>>>>>ti
>>>>>>>>> ng
>>>>>>>>> to
>>>>>>>>> load VMware control module:
>>>>>>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1299)|loa
>>>>>>>>>d
>>>>>>>>>ed
>>>>>>>>> VMware
>>>>>>>>> control module: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|Module.pm:new(172)|set
>>>>>>>>> 'vmhost_data' key
>>>>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>>>> arguments
>>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|Module.pm:new(172)|set
>>>>>>>>>'vmhost_os'
>>>>>>>>> key
>>>>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>>>> arguments
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_mn_os_object(335)|manage
>>>>>>>>>m
>>>>>>>>>en
>>>>>>>>>t
>>>>>>>>> node
>>>>>>>>> OS object has already been created, address: 1fbe730, returning 1
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:new(200)|VCL::Module::Provision
>>>>>>>>>i
>>>>>>>>>ng
>>>>>>>>>::
>>>>>>>>> VM
>>>>>>>>> ware::vSphere_SDK
>>>>>>>>> object created for computer redhat64base, address: 2508cf8
>>>>>>>>> 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|vSphere_SDK.pm:initialize(1826)|vSphere
>>>>>>>>> SDK for Perl does not appear to be installed on this managment 
>>>>>>>>>node,
>>>>>>>>> unable
>>>>>>>>> to load VMware vSphere SDK Perl modules
>>>>>>>>> 2011-10-25
>>>>>>>>> 
>>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>>>>> object
>>>>>>>>> could not be created: 
>>>>>>>>>VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:initialize(273)|no methods are
>>>>>>>>> available
>>>>>>>>> to control VM host redhat64base, the vSphere SDK cannot be used 
>>>>>>>>>to
>>>>>>>>> control
>>>>>>>>> the VM host and the host OS cannot be controlled via SSH
>>>>>>>>> |29609|2:2|image| ( 0) VMware.pm, initialize (line: 273)
>>>>>>>>> |29609|2:2|image| (-1) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| (-2) Module.pm, create_provisioning_object 
>>>>>>>>>(line:
>>>>>>>>> 423)
>>>>>>>>> |29609|2:2|image| (-3) State.pm, initialize (line: 117)
>>>>>>>>> |29609|2:2|image| (-4) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| (-5) vcld, make_new_child (line: 564)
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_provisioning_object(431)
>>>>>>>>>|
>>>>>>>>>pr
>>>>>>>>>ov
>>>>>>>>> is
>>>>>>>>> ioning
>>>>>>>>> object could not be created, returning 0
>>>>>>>>> |29609|2:2|image| ( 0) Module.pm, create_provisioning_object 
>>>>>>>>>(line:
>>>>>>>>> 431)
>>>>>>>>> |29609|2:2|image| (-1) State.pm, initialize (line: 117)
>>>>>>>>> |29609|2:2|image| (-2) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| (-3) vcld, make_new_child (line: 564)
>>>>>>>>> |29609|2:2|image| (-4) vcld, main (line: 346)
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|State.pm:initialize(118)|failed to 
>>>>>>>>>create
>>>>>>>>> provisioning object
>>>>>>>>> |29609|2:2|image| ( 0) State.pm, initialize (line: 118)
>>>>>>>>> |29609|2:2|image| (-1) Module.pm, new (line: 207)
>>>>>>>>> |29609|2:2|image| (-2) vcld, make_new_child (line: 564)
>>>>>>>>> |29609|2:2|image| (-3) vcld, main (line: 346)
>>>>>>>>> 2011-10-25 
>>>>>>>>>08:58:38|29609|2:2|image|State.pm:DESTROY(829)|VCL::image
>>>>>>>>> destructor called, address: 1e52a60
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:delete_computerloadlog_reservati
>>>>>>>>>o
>>>>>>>>>n(
>>>>>>>>>67
>>>>>>>>> 42
>>>>>>>>> )|removing
>>>>>>>>> computerloadlog entries matching loadstate = begin
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:delete_computerloadlog_reservati
>>>>>>>>>o
>>>>>>>>>n(
>>>>>>>>>67
>>>>>>>>> 89
>>>>>>>>> )|deleted
>>>>>>>>> rows from computerloadlog for reservation id=2
>>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|State.pm:DESTROY(848)|number 
>>>>>>>>>of
>>>>>>>>> database
>>>>>>>>> handles state process created: 1
>>>>>>>>> 2011-10-25 
>>>>>>>>>08:58:38|29609|2:2|image|State.pm:DESTROY(876)|VCL::image
>>>>>>>>> process
>>>>>>>>> duration: 0 seconds
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_
>>>>>>>>>a
>>>>>>>>>dd
>>>>>>>>>re
>>>>>>>>> ss
>>>>>>>>> (1581)|attempting
>>>>>>>>> to retrieve private IP address for computer: redhat64base
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_
>>>>>>>>>a
>>>>>>>>>dd
>>>>>>>>>re
>>>>>>>>> ss
>>>>>>>>> (1585)|retrieved
>>>>>>>>> contents of /etc/hosts on this management node, contains 8 lines
>>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_
>>>>>>>>>a
>>>>>>>>>dd
>>>>>>>>>re
>>>>>>>>> ss
>>>>>>>>> (1629)|did
>>>>>>>>> not find any lines in /etc/hosts containing 'redhat64base' and 
>>>>>>>>>the
>>>>>>>>> private
>>>>>>>>> IP address is not defined in the database
>>>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm,
>>>>>>>>> get_computer_private_ip_address
>>>>>>>>> (line: 1629)
>>>>>>>>> |29609|2:2|image| (-1) DataStructure.pm, 
>>>>>>>>>get_reservation_info_string
>>>>>>>>> (line:
>>>>>>>>> 2419)
>>>>>>>>> |29609|2:2|image| (-3) vcld, make_new_child (line: 571)
>>>>>>>>> |29609|2:2|image| (-4) vcld, main (line: 346)
>>>>>>>>> 2011-10-25 
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2703)|unable
>>>>>>>>>to
>>>>>>>>> use
>>>>>>>>> database handle stored in $ENV{dbh}
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>>>> handle
>>>>>>>>> stored in $ENV{dbh}
>>>>>>>>> 2011-10-25
>>>>>>>>> 08:58:38|29609|2:2|image|utils.pm:is_inblockrequest(6163)|zero
>>>>>>>>> rows were returned from database select
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_image_affiliation_na
>>>>>>>>>m
>>>>>>>>>e(
>>>>>>>>>20
>>>>>>>>> 35
>>>>>>>>> )|image
>>>>>>>>> owner id: 1
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2709)|database
>>>>>>>>> requested (information_schema) does not match handle stored in
>>>>>>>>> $ENV{dbh}
>>>>>>>>> (vcl:localhost)
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>>>> handle
>>>>>>>>> stored in $ENV{dbh}
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:retrieve_user_data(1352)
>>>>>>>>>|
>>>>>>>>>at
>>>>>>>>>te
>>>>>>>>> mp
>>>>>>>>> ting
>>>>>>>>> to retrieve and store data for user: user.id = '1'
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2709)|database
>>>>>>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>>>>>>> (information_schema:localhost)
>>>>>>>>> 2011-10-25
>>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>>>> handle
>>>>>>>>> stored in $ENV{dbh}
>>>>>>>>> 2011-10-25
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:retrieve_user_data(1415)
>>>>>>>>>|
>>>>>>>>>da
>>>>>>>>>ta
>>>>>>>>> has
>>>>>>>>> been retrieved for user: admin (id: 1)
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Aaron Peeler
>>>>>>>> Program Manager
>>>>>>>> Virtual Computing Lab
>>>>>>>> NC State University
>>>>>>>>
>>>>>>>> All electronic mail messages in connection with State business 
>>>>>>>>which
>>>>>>>> are sent to or received by this account are subject to the NC 
>>>>>>>>Public
>>>>>>>> Records Law and may be disclosed to third parties.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Aaron Peeler
>>>>>> Program Manager
>>>>>> Virtual Computing Lab
>>>>>> NC State University
>>>>>>
>>>>>> All electronic mail messages in connection with State business which
>>>>>> are sent to or received by this account are subject to the NC Public
>>>>>> Records Law and may be disclosed to third parties.
>>>>>
>>>>
>>>
>>>
>>
>>
>>
>>-- 
>>Thanks,
>>Alex  Patterson
>>User Support Services
>>Operating System Analyst
>>California State University, East Bay
>


Re: Base Image creation error - Continued again

Posted by Evelio Quiros <ev...@fiu.edu>.
Hello,

Thank you Alex for that insight. I added the correct paths for the
datastore and the repository.

I've gotten a bit further along the base image creation process.
It has successfully created a base image, but then it could not make a
reservation.
When I try to make a manual reservation, it tells me that there is no
computer available to run this image.
I wonder if I gave it some bad info for RAM or CPU ?

As Roseanne Rosanadana says: It's always something...

The error message is below:

reservation failed on linux64base: process failed after trying to load or
make available
------------------------------------------------------------------------
time: 2011-10-25 15:52:10
caller: State.pm:reservation_failed(213)
( 0) State.pm, reservation_failed (line: 213)
(-1) new.pm, process (line: 298)
(-2) vcld, make_new_child (line: 568)
(-3) vcld, main (line: 346)
------------------------------------------------------------------------
management node: vcltst.fiu.edu
reservation PID: 19062
parent vcld PID: 15838

request ID: 8
reservation ID: 8
request state/laststate: reload/image
request start time: 2011-10-25 15:52:00
request end time: 2011-10-25 16:22:00
for imaging: no
log ID: none

computer: linux64base
computer id: 14
computer type: virtualmachine
computer eth0 MAC address: <undefined>
computer eth1 MAC address: <undefined>
computer private IP address: 10.0.0.2
computer public IP address: 10.106.128.53
computer in block allocation: no
provisioning module: VCL::Module::Provisioning::VMware::VMware

vm host: vcldell_01
vm host ID: 2
vm host computer ID: 13
vm profile: VMware ESX - local storage
vm profile VM path: /vmfs/volumes/datastore1/vclimages
vm profile repository path: /vmfs/volumes/datastore1/vclrepository
vm profile datastore path: /vmfs/volumes/datastore1/vclimages
vm profile disk type: localdisk

image: vmwarelinux-base64linux19-v0
image display name: base64linux
image ID: 19
image revision ID: 11
image size: 857 MB
use Sysprep: yes
root access: yes
image owner ID: 1
image owner affiliation: Local
image revision date created: 2011-10-25 15:50:38
image revision production: yes
OS module: VCL::Module::OS::Linux

user: vclreload
user name: vcl reload
user ID: 2
user affiliation: Local
------------------------------------------------------------------------
RECENT LOG ENTRIES FOR THIS PROCESS:
2011-10-25 
15:52:08|19062|8:8|reload|VMware.pm:get_image_size_bytes(3841)|retrieved
the size of the image from the datastore on the VM host: 17,179,869,673
2011-10-25 
15:52:08|19062|8:8|reload|VMware.pm:get_image_size_bytes(3851)|image size
retrieved from both the image repository and VM host datastore:
|19062|8:8|reload| image repository: 898,237,415
|19062|8:8|reload| VM host datastore: 17,179,869,673
2011-10-25 
15:52:08|19062|8:8|reload|VMware.pm:get_image_size_bytes(3871)|size of
vmwarelinux-base64linux19-v0 image:
|19062|8:8|reload| 17,179,869,673 bytes
|19062|8:8|reload| 16,384 MB
|19062|8:8|reload| 16.00 GB
2011-10-25 
15:52:08|19062|8:8|reload|VMware.pm:get_vm_additional_vmx_bytes_required(47
13)|4294967418 additional bytes required for REDO files because VM disk
mode is NOT persistent
2011-10-25 
15:52:08|19062|8:8|reload|VMware.pm:get_vm_additional_vmx_bytes_required(47
16)|estimate of additional space required for the vmx directory:
|19062|8:8|reload| vmem/vswp file: 536,870,912 bytes, 512.0 MB, 0.50 GB
|19062|8:8|reload| redo files: 4,294,967,418 bytes, 4,096.0 MB, 4.00 GB
|19062|8:8|reload| total: 4,831,838,330 bytes, 4,608.0 MB, 4.50 GB
2011-10-25 
15:52:09|19062|8:8|reload|Linux.pm:file_exists(1404)|'/vmfs/volumes/datasto
re1/vclimages/vmwarelinux-base64linux19-v0/vmwarelinux-base64linux19-v0.vmd
k' exists on vcldell_01, files: 1, directories: 0, links: 0
2011-10-25 
15:52:09|19062|8:8|reload|VMware.pm:get_image_size_bytes(3819)|VM profile
vmdisk is set to 'localdisk', attempting to retrieve image size from image
repository
2011-10-25 
15:52:09|19062|8:8|reload|Linux.pm:file_exists(1404)|'/vmfs/volumes/datasto
re1/vclrepository' exists on vcldell_01, files: 0, directories: 1, links: 0
2011-10-25 
15:52:09|19062|8:8|reload|VMware.pm:is_repository_mounted_on_vmhost(5485)|i
mage repository is mounted on VM host vcldell_01:
/vmfs/volumes/datastore1/vclrepository
2011-10-25 
15:52:09|19062|8:8|reload|VMware.pm:get_image_size_bytes(3821)|checking
size of image in image repository mounted on VM host:
vcldell_01:/vmfs/volumes/datastore1/vclrepository
2011-10-25 15:52:09|19062|8:8|reload|Linux.pm:get_file_size(2022)|size of
'/vmfs/volumes/datastore1/vclrepository/vmwarelinux-base64linux19-v0/vmware
linux-base64linux19-v0*.vmdk' on vcldell_01:
|19062|8:8|reload| used: 898,237,415 bytes, 856.6 MB, 0.84 GB
|19062|8:8|reload| allocated: 903,872,512 bytes, 862.0 MB, 0.84 GB
2011-10-25 15:52:10|19062|8:8|reload|Linux.pm:get_file_size(2022)|size of
'/vmfs/volumes/datastore1/vclimages/vmwarelinux-base64linux19-v0/vmwarelinu
x-base64linux19-v0*.vmdk' on vcldell_01:
|19062|8:8|reload| used: 17,179,869,673 bytes, 16,384.0 MB, 16.00 GB
|19062|8:8|reload| allocated: 17,179,869,184 bytes, 16,384.0 MB, 16.00 GB
2011-10-25 
15:52:10|19062|8:8|reload|VMware.pm:get_image_size_bytes(3841)|retrieved
the size of the image from the datastore on the VM host: 17,179,869,673
2011-10-25 
15:52:10|19062|8:8|reload|VMware.pm:get_image_size_bytes(3851)|image size
retrieved from both the image repository and VM host datastore:
|19062|8:8|reload| image repository: 898,237,415
|19062|8:8|reload| VM host datastore: 17,179,869,673
2011-10-25 
15:52:10|19062|8:8|reload|VMware.pm:get_image_size_bytes(3871)|size of
vmwarelinux-base64linux19-v0 image:
|19062|8:8|reload| 17,179,869,673 bytes
|19062|8:8|reload| 16,384 MB
|19062|8:8|reload| 16.00 GB
2011-10-25 
15:52:10|19062|8:8|reload|VMware.pm:get_vm_additional_vmdk_bytes_required(4
657)|no additional space required for vmdk files because they already
exist on VM host
2011-10-25 
15:52:10|19062|8:8|reload|VMware.pm:get_vm_additional_vmdk_bytes_required(4
662)|VM requires appoximately 0 additional bytes (0 MB, 0 GB) of disk
space on the VM host for the vmdk directory
2011-10-25 
15:52:10|19062|8:8|reload|VMware.pm:check_vmhost_disk_space(2070)|enough
space is available on shared vmx/vmdk volume on VM host vcldell_01:
'/vmfs/volumes/datastore1/vclimages'
|19062|8:8|reload| vmx additional space required:          4,831,838,330
bytes, 4,608.0 MB, 4.50 GB
|19062|8:8|reload| vmdk additional space required:         0 bytes, 0.0
MB, 0.00 GB
|19062|8:8|reload| total additional space required:        4,831,838,330
bytes, 4,608.0 MB, 4.50 GB
|19062|8:8|reload| shared vmx/vmdk volume available space: 248,047,992,832
bytes, 236,557.0 MB, 231.01 GB
2011-10-25 
15:52:10|19062|8:8|reload|Module.pm:create_mn_os_object(335)|management
node OS object has already been created, address: 222db60, returning 1
2011-10-25 
15:52:10|19062|8:8|reload|Module.pm:new(203)|VCL::Module::Semaphore object
created, address: 1cac6c0
2011-10-25 
15:52:10|19062|8:8|reload|Module.pm:code_loop_timeout(742)|attempting to
open lockfile, maximum of 1200 seconds
2011-10-25 
15:52:10|19062|8:8|reload|Module.pm:code_loop_timeout(759)|attempt 1:
attempting to open lockfile
2011-10-25 
15:52:10|19062|8:8|reload|Semaphore.pm:open_lockfile(146)|opened and
obtained an exclusive lock on file:
/tmp/vcldell_01-vmfs-volumes-datastore1-vclimages-vmwarelinux-base64linux19
-v0.lock
2011-10-25 
15:52:10|19062|8:8|reload|Module.pm:code_loop_timeout(762)|attempting to
open lockfile, code returned true
2011-10-25 15:52:10|19062|8:8|reload|Module.pm:get_semaphore(844)|created
Semaphore object, memory address: 1cac6c0
2011-10-25 
15:52:10|19062|8:8|reload|Linux.pm:file_exists(1404)|'/vmfs/volumes/datasto
re1/vclimages/vmwarelinux-base64linux19-v0/vmwarelinux-base64linux19-v0.vmd
k' exists on vcldell_01, files: 1, directories: 0, links: 0
2011-10-25 15:52:10|19062|8:8|reload|VMware.pm:prepare_vmdk(1785)|VM is
not persistent and nonpersistent vmdk file already exists on VM host
vcldell_01: 
/vmfs/volumes/datastore1/vclimages/vmwarelinux-base64linux19-v0/vmwarelinux
-base64linux19-v0.vmdk
2011-10-25 
15:52:10|19062|8:8|reload|Semaphore.pm:release_lockfile(248)|deleted file:
/tmp/vcldell_01-vmfs-volumes-datastore1-vclimages-vmwarelinux-base64linux19
-v0.lock
2011-10-25 15:52:10|19062|8:8|reload|Semaphore.pm:DESTROY(281)|destroyed
Semaphore object, memory address: 1cac6c0
2011-10-25 15:52:10|19062|8:8|reload|utils.pm:insertloadlog(3875)|inserted
computer=14, transfervm, copied vmwarelinux-base64linux19-v0 to linux64base
2011-10-25 15:52:10|19062|8:8|reload|VMware.pm:get_vm_ram(4306)|image ram
setting is too low: 0 MB, 512 MB will be used
2011-10-25 
15:52:10|19062|8:8|reload|VMware.pm:get_vm_os_configuration(4210)|retrieved
 default VM configuration for OS: linux-x86_64
|19062|8:8|reload| : {
|19062|8:8|reload| :   "ethernet-virtualDev" => "e1000",
|19062|8:8|reload| :   "guestOS" => "otherlinux-64",
|19062|8:8|reload| :   "scsi-virtualDev" => "lsiLogic"
|19062|8:8|reload| : }
|19062|8:8|reload| ---- WARNING ----
|19062|8:8|reload| 2011-10-25
15:52:10|19062|8:8|reload|DataStructure.pm:_automethod(812)|corresponding
data has not been initialized for get_computer_eth0_mac_address:
$self->request_data->{reservation}{8}{computer}{eth0macaddress}
|19062|8:8|reload| ( 0) DataStructure.pm, _automethod (line: 812)
|19062|8:8|reload| (-1) Autoload.pm, __ANON__ (line: 80)
|19062|8:8|reload| (-2) VMware.pm, prepare_vmx (line: 1457)
|19062|8:8|reload| (-3) VMware.pm, load (line: 394)
|19062|8:8|reload| (-4) new.pm, reload_image (line: 618)
|19062|8:8|reload| (-5) new.pm, process (line: 248)
|19062|8:8|reload| ---- WARNING ----
|19062|8:8|reload| 2011-10-25
15:52:10|19062|8:8|reload|VMware.pm:load(395)|failed to prepare vmx file
for linux64base on VM host: vcldell_01
|19062|8:8|reload| ( 0) VMware.pm, load (line: 395)
|19062|8:8|reload| (-1) new.pm, reload_image (line: 618)
|19062|8:8|reload| (-2) new.pm, process (line: 248)
|19062|8:8|reload| (-3) vcld, make_new_child (line: 568)
|19062|8:8|reload| (-4) vcld, main (line: 346)
|19062|8:8|reload| ---- WARNING ----
|19062|8:8|reload| 2011-10-25
15:52:10|19062|8:8|reload|new.pm:reload_image(623)|vmwarelinux-base64linux1
9-v0 failed to load on linux64base, returning
|19062|8:8|reload| ( 0) new.pm, reload_image (line: 623)
|19062|8:8|reload| (-1) new.pm, process (line: 248)
|19062|8:8|reload| (-2) vcld, make_new_child (line: 568)
|19062|8:8|reload| (-3) vcld, main (line: 346)
2011-10-25 15:52:10|19062|8:8|reload|utils.pm:insertloadlog(3875)|inserted
computer=14, loadimagefailed, vmwarelinux-base64linux19-v0 failed to load
on linux64base
|19062|8:8|reload| ---- WARNING ----
|19062|8:8|reload| 2011-10-25
15:52:10|19062|8:8|reload|new.pm:process(295)|failed to load linux64base
with vmwarelinux-base64linux19-v0
|19062|8:8|reload| ( 0) new.pm, process (line: 295)
|19062|8:8|reload| (-1) vcld, make_new_child (line: 568)
|19062|8:8|reload| (-2) vcld, main (line: 346)
2011-10-25 
15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_state_name(2305)|at
tempting to retrieve current state of computer linux64base from the
database
2011-10-25 
15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_state_name(2336)|re
trieved current state of computer linux64base from the database: reloading
2011-10-25 
15:52:10|19062|8:8|reload|DataStructure.pm:_automethod(834)|data structure
updated: $self->request_data->{reservation}{8}{computer}{state}{name}
|19062|8:8|reload| computer_state_name = reloading
2011-10-25 
15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_private_ip_address(
1581)|attempting to retrieve private IP address for computer: linux64base
2011-10-25 
15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_private_ip_address(
1585)|retrieved contents of /etc/hosts on this management node, contains
10 lines
2011-10-25 
15:52:10|19062|8:8|reload|DataStructure.pm:get_computer_private_ip_address(
1645)|returning IP address from /etc/hosts file: 10.0.0.2
2011-10-25 15:52:10|19062|8:8|reload|utils.pm:is_inblockrequest(6163)|zero
rows were returned from database select
2011-10-25 
15:52:10|19062|8:8|reload|DataStructure.pm:get_image_affiliation_name(2035)
|image owner id: 1
2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2709)|database
requested (information_schema) does not match handle stored in $ENV{dbh}
(vcl:localhost)
2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2760)|database
handle stored in $ENV{dbh}
2011-10-25 
15:52:10|19062|8:8|reload|DataStructure.pm:retrieve_user_data(1352)|attempt
ing to retrieve and store data for user: user.id = '1'
2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2709)|database
requested (vcl) does not match handle stored in $ENV{dbh}
(information_schema:localhost)
2011-10-25 15:52:10|19062|8:8|reload|utils.pm:getnewdbh(2760)|database
handle stored in $ENV{dbh}
2011-10-25 
15:52:10|19062|8:8|reload|DataStructure.pm:retrieve_user_data(1415)|data
has been retrieved for user: admin (id: 1)




On 10/25/11 12:00 PM, "Alexander Patterson"
<al...@csueastbay.edu> wrote:

>Hello,
>
> Here is the main issue, You need to have your datastore the location
>that you are storing you VM images in the correct place. As of right
>now they are looking  in the /vmfs/volumes/local-datastore
>
>You can either move your images to this folder or change the default
>location.
>
>
>To do this go to Virtual Host
>Click on VM host Profiles
>Click on Configure Profile (Make to to select the VMware ESXI Standard
>Localdisk
>from the sounds of it you have Local storage and are storing your VM's
>locally.
>
>The Data Store Path can be changed to the current location or you can
>move the files the choice is yours. Make sure you have the Virtual
>Switches set up
>I'm using custom VLAN switch 0 = private and switch 1 = private
>You don't have to set a Repository Path but the Data Store Path has to
>be correct.
>
>-Alex
>
>327|5:5|image| ---- WARNING ----
>|5327|5:5|image| 2011-10-25
>11:38:43|5327|5:5|image|VMware.pm:_get_datastore_name(5848)|unable to
>determine datastore name from path: '/vmfs/volumes/local-datastore', path
>does not begin with any of the datastore paths:
>
>2011/10/25 Evelio Quiros <ev...@fiu.edu>:
>> OK,
>>
>> After adding the missing javascript, I am able to get the Virtual Hosts
>> page to display.
>>
>> I added 10 VMs which have been added to the database, as well as the
>>base
>> image I want to capture, so 11 in all.
>>
>> Does VCL require the Vsphere module to add a virtual machine computer ?
>>
>> Also, I am using a free version of ESXi. Is there a licensing issue ?
>>
>>
>> I tried once again to capture the base image, and I got this error:
>>
>>
>> VCL::image object could not be created and initialized
>> ------------------------------------------------------------------------
>> time: 2011-10-25 11:38:43
>> caller: vcld:make_new_child(571)
>> ( 0) vcld, make_new_child (line: 571)
>> (-1) vcld, main (line: 346)
>> ------------------------------------------------------------------------
>> management node: vcltst.fiu.edu
>> reservation PID: 5327
>> parent vcld PID: 15838
>>
>> request ID: 5
>> reservation ID: 5
>> request state/laststate: image/image
>> request start time: 2011-10-25 11:38:35
>> request end time: 2011-10-25 12:38:35
>> for imaging: no
>> log ID: none
>>
>> computer: redhat64base
>> computer id: 12
>> computer type: virtualmachine
>> computer eth0 MAC address: <undefined>
>> computer eth1 MAC address: <undefined>
>> computer private IP address: 10.0.0.2
>> computer public IP address: 10.106.128.53
>> computer in block allocation: no
>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>
>> vm host: vcldell_01
>> vm host ID: 2
>> vm host computer ID: 13
>> vm profile: VMware ESX - local storage
>> vm profile VM path: /vmfs/volumes/local-datastore
>> vm profile repository path: 0
>> vm profile datastore path: /vmfs/volumes/local-datastore
>> vm profile disk type: localdisk
>>
>> image: vmwarelinux-redhat_linux16-v0
>> image display name: redhat_linux
>> image ID: 16
>> image revision ID: 9
>> image size: 1450 MB
>> use Sysprep: yes
>> root access: yes
>> image owner ID: 1
>> image owner affiliation: Local
>> image revision date created: 2011-10-25 11:38:35
>> image revision production: yes
>> OS module: VCL::Module::OS::Linux
>>
>> user: admin
>> user name: vcl admin
>> user ID: 1
>> user affiliation: Local
>> ------------------------------------------------------------------------
>> RECENT LOG ENTRIES FOR THIS PROCESS:
>> 2011-10-25 
>>11:38:41|5327|5:5|image|vSphere_SDK.pm:initialize(1826)|vSphere
>> SDK for Perl does not appear to be installed on this managment node,
>> unable to load VMware vSphere SDK Perl modules
>> 2011-10-25
>> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1313)|API object
>> could not be created: VCL::Module::Provisioning::VMware::vSphere_SDK
>> 2011-10-25
>> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(613)|computer ID
>> argument was specified, retrieving data for computer ID: 13
>> 2011-10-25 
>>11:38:41|5327|5:5|image|DataStructure.pm:_initialize(643)|image
>> ID argument was specified: 4, DataStructure object will contain image
>> information for the production imagerevision of this image
>> 2011-10-25
>> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(660)|retrieved data
>> for imagerevision ID: 4
>> 2011-10-25
>> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(676)|retrieved data
>> for image ID: 4
>> 2011-10-25
>> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_datastructure(1190)|created
>> DataStructure object for VM host: vcldell_01
>> 2011-10-25
>> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1293)|attempting
>> to load VMware control module:
>>VCL::Module::Provisioning::VMware::VIM_SSH
>> 2011-10-25
>> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>> VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
>> 2011-10-25 11:38:41|5327|5:5|image|Module.pm:new(172)|set 'vmhost_data'
>> key for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
>> 2011-10-25 11:38:41|5327|5:5|image|Module.pm:new(172)|set 'vmhost_os'
>>key
>> for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
>> 2011-10-25
>> 11:38:41|5327|5:5|image|Module.pm:create_mn_os_object(335)|management
>>node
>> OS object has already been created, address: 219ab58, returning 1
>> 2011-10-25
>> 
>>11:38:41|5327|5:5|image|Module.pm:new(200)|VCL::Module::Provisioning::VMw
>>ar
>> e::VIM_SSH object created for computer redhat64base, address: 1fd9588
>> 2011-10-25 11:38:42|5327|5:5|image|VIM_SSH.pm:initialize(138)|VIM
>> executable available on VM host: vim-cmd
>> 2011-10-25
>> 
>>11:38:42|5327|5:5|image|VIM_SSH.pm:initialize(140)|VCL::Module::Provision
>>in
>> g::VMware::VIM_SSH object initialized
>> 2011-10-25
>> 11:38:42|5327|5:5|image|VMware.pm:get_vmhost_api_object(1320)|created
>>API
>> object: VCL::Module::Provisioning::VMware::VIM_SSH
>> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(278)|VMware on
>>VM
>> host vcldell_01 will be controlled using vim-cmd via SSH
>> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(293)|VMware OS
>>and
>> API objects created for VM host vcldell_01:
>> |5327|5:5|image| VM host OS object type: VCL::Module::OS::Linux::UnixLab
>> |5327|5:5|image| VMware API object type:
>> VCL::Module::Provisioning::VMware::VIM_SSH
>> 2011-10-25
>> 11:38:42|5327|5:5|image|VMware.pm:get_vmhost_product_name(5405)|VMware
>> product being used on VM host vcldell_01: 'VMware ESXi 5.0.0
>>build-469512'
>> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(307)|product:
>> VMware ESXi 5.0.0 build-469512, OS object:
>>VCL::Module::OS::Linux::UnixLab
>> 2011-10-25 11:38:42|5327|5:5|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd
>> call count: 1 (hostsvc/datastore/listsummary)
>> 2011-10-25 11:38:43|5327|5:5|image|VIM_SSH.pm:_run_vim_cmd(208)|executed
>> command on VM host vcldell_01: vim-cmd hostsvc/datastore/listsummary
>> 2011-10-25
>> 11:38:43|5327|5:5|image|VMware.pm:get_datastore_info(5531)|retrieved
>> datastore info from VM host:
>> |5327|5:5|image| datastore1
>> |5327|5:5|image| ---- WARNING ----
>> |5327|5:5|image| 2011-10-25
>> 11:38:43|5327|5:5|image|VMware.pm:_get_datastore_name(5848)|unable to
>> determine datastore name from path: '/vmfs/volumes/local-datastore',
>>path
>> does not begin with any of the datastore paths:
>> |5327|5:5|image| '[datastore1]'
>> |5327|5:5|image| '/vmfs/volumes/datastore1'
>> |5327|5:5|image| '/vmfs/volumes/4e96b3e5-a6562886-638a-00188be54b59'
>> |5327|5:5|image| ( 0) VMware.pm, _get_datastore_name (line: 5848)
>> |5327|5:5|image| (-1) VMware.pm, _get_datastore_root_normal_path (line:
>> 5685)
>> |5327|5:5|image| (-2) VMware.pm, _get_normal_path (line: 5775)
>> |5327|5:5|image| (-3) VMware.pm, get_vmx_base_directory_path (line:
>>2743)
>> |5327|5:5|image| (-4) VMware.pm, initialize (line: 313)
>> |5327|5:5|image| (-5) Module.pm, new (line: 207)
>> |5327|5:5|image| ---- WARNING ----
>> |5327|5:5|image| 2011-10-25
>> 
>>11:38:43|5327|5:5|image|VMware.pm:_get_datastore_root_normal_path(5687)|f
>>ai
>> led to determine datastore root normal path, unable to determine
>>datastore
>> name: /vmfs/volumes/local-datastore
>> |5327|5:5|image| ( 0) VMware.pm, _get_datastore_root_normal_path (line:
>> 5687)
>> |5327|5:5|image| (-1) VMware.pm, _get_normal_path (line: 5775)
>> |5327|5:5|image| (-2) VMware.pm, get_vmx_base_directory_path (line:
>>2743)
>> |5327|5:5|image| (-3) VMware.pm, initialize (line: 313)
>> |5327|5:5|image| (-4) Module.pm, new (line: 207)
>> |5327|5:5|image| (-5) Module.pm, create_provisioning_object (line: 423)
>> |5327|5:5|image| ---- WARNING ----
>> |5327|5:5|image| 2011-10-25
>> 11:38:43|5327|5:5|image|VMware.pm:_get_normal_path(5777)|unable to
>> determine normal path, failed to determine datastore root normal path:
>> /vmfs/volumes/local-datastore
>> |5327|5:5|image| ( 0) VMware.pm, _get_normal_path (line: 5777)
>> |5327|5:5|image| (-1) VMware.pm, get_vmx_base_directory_path (line:
>>2743)
>> |5327|5:5|image| (-2) VMware.pm, initialize (line: 313)
>> |5327|5:5|image| (-3) Module.pm, new (line: 207)
>> |5327|5:5|image| (-4) Module.pm, create_provisioning_object (line: 423)
>> |5327|5:5|image| (-5) State.pm, initialize (line: 117)
>> |5327|5:5|image| ---- WARNING ----
>> |5327|5:5|image| 2011-10-25
>> 
>>11:38:43|5327|5:5|image|VMware.pm:get_vmx_base_directory_path(2749)|unabl
>>e
>> to determine the vmx base directory path, failed to convert path
>> configured in the VM profile to a normal path:
>> /vmfs/volumes/local-datastore
>> |5327|5:5|image| ( 0) VMware.pm, get_vmx_base_directory_path (line:
>>2749)
>> |5327|5:5|image| (-1) VMware.pm, initialize (line: 313)
>> |5327|5:5|image| (-2) Module.pm, new (line: 207)
>> |5327|5:5|image| (-3) Module.pm, create_provisioning_object (line: 423)
>> |5327|5:5|image| (-4) State.pm, initialize (line: 117)
>> |5327|5:5|image| (-5) Module.pm, new (line: 207)
>> |5327|5:5|image| ---- WARNING ----
>> |5327|5:5|image| 2011-10-25
>> 11:38:43|5327|5:5|image|VMware.pm:initialize(315)|unable to determine
>>vmx
>> base directory path on VM host vcldell_01
>> |5327|5:5|image| ( 0) VMware.pm, initialize (line: 315)
>> |5327|5:5|image| (-1) Module.pm, new (line: 207)
>> |5327|5:5|image| (-2) Module.pm, create_provisioning_object (line: 423)
>> |5327|5:5|image| (-3) State.pm, initialize (line: 117)
>> |5327|5:5|image| (-4) Module.pm, new (line: 207)
>> |5327|5:5|image| (-5) vcld, make_new_child (line: 564)
>> |5327|5:5|image| ---- WARNING ----
>> |5327|5:5|image| 2011-10-25
>> 
>>11:38:43|5327|5:5|image|Module.pm:create_provisioning_object(431)|provisi
>>on
>> ing object could not be created, returning 0
>> |5327|5:5|image| ( 0) Module.pm, create_provisioning_object (line: 431)
>> |5327|5:5|image| (-1) State.pm, initialize (line: 117)
>> |5327|5:5|image| (-2) Module.pm, new (line: 207)
>> |5327|5:5|image| (-3) vcld, make_new_child (line: 564)
>> |5327|5:5|image| (-4) vcld, main (line: 346)
>> |5327|5:5|image| ---- WARNING ----
>> |5327|5:5|image| 2011-10-25
>> 11:38:43|5327|5:5|image|State.pm:initialize(118)|failed to create
>> provisioning object
>> |5327|5:5|image| ( 0) State.pm, initialize (line: 118)
>> |5327|5:5|image| (-1) Module.pm, new (line: 207)
>> |5327|5:5|image| (-2) vcld, make_new_child (line: 564)
>> |5327|5:5|image| (-3) vcld, main (line: 346)
>> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(829)|VCL::image
>> destructor called, address: 1e47a28
>> 2011-10-25
>> 
>>11:38:43|5327|5:5|image|utils.pm:delete_computerloadlog_reservation(6742)
>>|r
>> emoving computerloadlog entries matching loadstate = begin
>> 2011-10-25
>> 
>>11:38:43|5327|5:5|image|utils.pm:delete_computerloadlog_reservation(6789)
>>|d
>> eleted rows from computerloadlog for reservation id=5
>> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(848)|number of
>> database handles state process created: 1
>> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(876)|VCL::image
>> process duration: 4 seconds
>> 2011-10-25
>> 
>>11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address(
>>15
>> 81)|attempting to retrieve private IP address for computer: redhat64base
>> 2011-10-25
>> 
>>11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address(
>>15
>> 85)|retrieved contents of /etc/hosts on this management node, contains
>>10
>> lines
>> 2011-10-25
>> 
>>11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address(
>>16
>> 45)|returning IP address from /etc/hosts file: 10.0.0.2
>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2703)|unable to
>>use
>> database handle stored in $ENV{dbh}
>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
>> handle stored in $ENV{dbh}
>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:is_inblockrequest(6163)|zero
>> rows were returned from database select
>> 2011-10-25
>> 
>>11:38:43|5327|5:5|image|DataStructure.pm:get_image_affiliation_name(2035)
>>|i
>> mage owner id: 1
>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2709)|database
>> requested (information_schema) does not match handle stored in $ENV{dbh}
>> (vcl:localhost)
>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
>> handle stored in $ENV{dbh}
>> 2011-10-25
>> 
>>11:38:43|5327|5:5|image|DataStructure.pm:retrieve_user_data(1352)|attempt
>>in
>> g to retrieve and store data for user: user.id = '1'
>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2709)|database
>> requested (vcl) does not match handle stored in $ENV{dbh}
>> (information_schema:localhost)
>> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
>> handle stored in $ENV{dbh}
>> 2011-10-25
>> 11:38:43|5327|5:5|image|DataStructure.pm:retrieve_user_data(1415)|data
>>has
>> been retrieved for user: admin (id: 1)
>>
>>
>>
>>
>>
>>
>>
>> On 10/25/11 10:26 AM, "Aaron Coburn" <ac...@amherst.edu> wrote:
>>
>>>Al,
>>>if you plan to use the vSphere API, then you will need to install the
>>>vSphere SDK for Perl separately. The perl modules are available here --
>>>just make sure that you download the release that matches your vCenter
>>>version.
>>>
>>>http://www.vmware.com/support/developer/viperltoolkit/
>>>
>>>Aaron Coburn
>>>
>>>
>>>On Oct 25, 2011, at 10:03 AM, Evelio Quiros wrote:
>>>
>>>> Thanks again Aaron. It seems we are taking baby steps here.
>>>>
>>>> Ok, next issue: When I click "Configure Host" in the vcl web
>>>>interface,
>>>> nothing happens.
>>>>
>>>> My Vmware server is listed there. It is in "vmhostinuse" state.
>>>>
>>>> I noticed some complaints below about the Vsphere perl module not
>>>>being
>>>> installed.
>>>> I thought that was done in the "install_perl_libraries script.
>>>>
>>>> Thanks again for all your help.
>>>>
>>>> Al Quiros
>>>>
>>>>
>>>> On 10/25/11 9:43 AM, "Aaron Peeler" <fa...@ncsu.edu> wrote:
>>>>
>>>>> In the log output your missing the vmhost information.
>>>>>
>>>>> Make sure your vm host server have a correctly configured vmhost
>>>>> profile and you have assigned your vms to the virtual host server by
>>>>> using the Virtual Host interface.
>>>>>
>>>>>
>>>>>https://cwiki.apache.org/confluence/display/VCL/VCL+2.2.1+-+Further+St
>>>>>ep
>>>>>s+
>>>>> if+Using+VMware
>>>>> https://cwiki.apache.org/confluence/display/VCL/VMware+Configuration
>>>>>
>>>>> I'm not seeing the virtual host interface mentioned directly in the
>>>>> vcl 2.2.1 install guide. I'll added that to the first link.
>>>>>
>>>>> Here is a link from a bootcamp that you can review this morning while
>>>>> I work on adding the content to Apache VCL:
>>>>>
>>>>>https://sites.google.com/a/ncsu.edu/vcl-bootcamp/exercises/assign-a-vm
>>>>>-t
>>>>>o-
>>>>> a-virtual-host
>>>>>
>>>>> Aaron
>>>>>
>>>>>
>>>>> On Tue, Oct 25, 2011 at 9:19 AM, Evelio Quiros <ev...@fiu.edu>
>>>>>wrote:
>>>>>> Thank you Aaron.
>>>>>>
>>>>>> Ok, now it can resolve the name redhat64base to the private IP
>>>>>>address
>>>>>> 10.0.0.2.
>>>>>> I tried to add the base image as the name linux64.
>>>>>> It resides in the database as redhat64base, with the public IP of
>>>>>> 10.106.128.53, and set as available.
>>>>>> I'm not sure what this error message is telling meŠ
>>>>>>
>>>>>> VCL::image object could not be created and initialized
>>>>>>
>>>>>>---------------------------------------------------------------------
>>>>>>--
>>>>>>-
>>>>>> time: 2011-10-25 09:30:44
>>>>>> caller: vcld:make_new_child(571)
>>>>>> ( 0) vcld, make_new_child (line: 571)
>>>>>> (-1) vcld, main (line: 346)
>>>>>>
>>>>>>---------------------------------------------------------------------
>>>>>>--
>>>>>>-
>>>>>> management node: vcltst.fiu.edu
>>>>>> reservation PID: 31318
>>>>>> parent vcld PID: 15838
>>>>>>
>>>>>> request ID: 4
>>>>>> reservation ID: 4
>>>>>> request state/laststate: image/image
>>>>>> request start time: 2011-10-25 09:30:37
>>>>>> request end time: 2011-10-25 10:30:37
>>>>>> for imaging: no
>>>>>> log ID: none
>>>>>>
>>>>>> computer: redhat64base
>>>>>> computer id: 12
>>>>>> computer type: blade
>>>>>> computer eth0 MAC address: <undefined>
>>>>>> computer eth1 MAC address: <undefined>
>>>>>> computer private IP address: 10.0.0.2
>>>>>> computer public IP address: 10.106.128.53
>>>>>> computer in block allocation: no
>>>>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>>>>
>>>>>> image: vmwarelinux-linux6414-v0
>>>>>> image display name: linux64
>>>>>> image ID: 14
>>>>>> image revision ID: 8
>>>>>> image size: 1450 MB
>>>>>> use Sysprep: yes
>>>>>> root access: yes
>>>>>> image owner ID: 1
>>>>>> image owner affiliation: Local
>>>>>> image revision date created: 2011-10-25 09:30:37
>>>>>> image revision production: yes
>>>>>> OS module: VCL::Module::OS::Linux
>>>>>>
>>>>>> user: admin
>>>>>> user name: vcl admin
>>>>>> user ID: 1
>>>>>> user affiliation: Local
>>>>>>
>>>>>>---------------------------------------------------------------------
>>>>>>--
>>>>>>-
>>>>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attemp
>>>>>>ti
>>>>>>ng
>>>>>> to load VMware control module:
>>>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>> 2011-10-25
>>>>>> 
>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>>>> VMware control module:
>>>>>>VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>'vmhost_data'
>>>>>> key for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>> arguments
>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>'vmhost_os'
>>>>>> key
>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>arguments
>>>>>> 2011-10-25
>>>>>> 
>>>>>>09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|managemen
>>>>>>t
>>>>>> node OS object has already been created, address: 21956b8,
>>>>>>returning 1
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioning
>>>>>>::
>>>>>>VM
>>>>>> wa
>>>>>> re::vSphere_SDK object created for computer redhat64base, address:
>>>>>> 21e6980
>>>>>> 2011-10-25
>>>>>> 09:30:43|31318|4:4|image|vSphere_SDK.pm:initialize(1826)|vSphere SDK
>>>>>>for
>>>>>> Perl does not appear to be installed on this managment node, unable
>>>>>>to
>>>>>> load VMware vSphere SDK Perl modules
>>>>>> 2011-10-25
>>>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>> object
>>>>>> could not be created: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>
>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspond
>>>>>>in
>>>>>>g
>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>> $self->request_data->{reservation}{4}{computer}{vmhost}{computerid}
>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>1161)
>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>
>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspond
>>>>>>in
>>>>>>g
>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>>
>>>>>>
>>>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{vmprofile}{im
>>>>>>ag
>>>>>>ei
>>>>>> d}
>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>1162)
>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_datastructure(1190)|cre
>>>>>>at
>>>>>>ed
>>>>>> DataStructure object for VM host: redhat64base
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attemp
>>>>>>ti
>>>>>>ng
>>>>>> to load VMware control module:
>>>>>> VCL::Module::Provisioning::VMware::VIM_SSH
>>>>>> 2011-10-25
>>>>>> 
>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>>>> VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>'vmhost_data'
>>>>>> key for VCL::Module::Provisioning::VMware::VIM_SSH object from
>>>>>>arguments
>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set 
>>>>>>'vmhost_os'
>>>>>> key
>>>>>> for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
>>>>>> 2011-10-25
>>>>>> 
>>>>>>09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|managemen
>>>>>>t
>>>>>> node OS object has already been created, address: 21956b8, 
>>>>>>returning 1
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioning
>>>>>>::
>>>>>>VM
>>>>>> wa
>>>>>> re::VIM_SSH object created for computer redhat64base, address: 
>>>>>>24f7888
>>>>>> 2011-10-25 09:30:43|31318|4:4|image|VIM_SSH.pm:initialize(126)|VIM
>>>>>> executable is not available on the VM host, output:
>>>>>> |31318|4:4|image| bash: vim-cmd: command not found
>>>>>> |31318|4:4|image| bash: vmware-vim-cmd: command not found
>>>>>> 2011-10-25
>>>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>> object
>>>>>> could not be created: VCL::Module::Provisioning::VMware::VIM_SSH
>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>
>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspond
>>>>>>in
>>>>>>g
>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>> $self->request_data->{reservation}{4}{computer}{vmhost}{computerid}
>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>1161)
>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>
>>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspond
>>>>>>in
>>>>>>g
>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>>
>>>>>>
>>>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{vmprofile}{im
>>>>>>ag
>>>>>>ei
>>>>>> d}
>>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>1162)
>>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_datastructure(1190)|cre
>>>>>>at
>>>>>>ed
>>>>>> DataStructure object for VM host: redhat64base
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attemp
>>>>>>ti
>>>>>>ng
>>>>>> to load VMware control module:
>>>>>> VCL::Module::Provisioning::VMware::vmware_cmd
>>>>>> 2011-10-25
>>>>>> 
>>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>>>> VMware control module: VCL::Module::Provisioning::VMware::vmware_cmd
>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>>'vmhost_data'
>>>>>> key for VCL::Module::Provisioning::VMware::vmware_cmd object from
>>>>>> arguments
>>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set 
>>>>>>'vmhost_os'
>>>>>> key
>>>>>> for VCL::Module::Provisioning::VMware::vmware_cmd object from
>>>>>>arguments
>>>>>> 2011-10-25
>>>>>> 
>>>>>>09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|managemen
>>>>>>t
>>>>>> node OS object has already been created, address: 21956b8, 
>>>>>>returning 1
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioning
>>>>>>::
>>>>>>VM
>>>>>> wa
>>>>>> re::vmware_cmd object created for computer redhat64base, address:
>>>>>> 251d1e0
>>>>>> 2011-10-25
>>>>>> 09:30:44|31318|4:4|image|vmware_cmd.pm:initialize(107)|vmware-cmd is
>>>>>>not
>>>>>> available on the VM host, output:
>>>>>> |31318|4:4|image| bash: vmware-cmd: command not found
>>>>>> 2011-10-25
>>>>>> 09:30:44|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>> object
>>>>>> could not be created: VCL::Module::Provisioning::VMware::vmware_cmd
>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>> |31318|4:4|image| 2011-10-25
>>>>>> 09:30:44|31318|4:4|image|VMware.pm:initialize(285)|failed to create 
>>>>>>an
>>>>>> object to control VMware on VM host: redhat64base
>>>>>> |31318|4:4|image| ( 0) VMware.pm, initialize (line: 285)
>>>>>> |31318|4:4|image| (-1) Module.pm, new (line: 207)
>>>>>> |31318|4:4|image| (-2) Module.pm, create_provisioning_object (line:
>>>>>>423)
>>>>>> |31318|4:4|image| (-3) State.pm, initialize (line: 117)
>>>>>> |31318|4:4|image| (-4) Module.pm, new (line: 207)
>>>>>> |31318|4:4|image| (-5) vcld, make_new_child (line: 564)
>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>> |31318|4:4|image| 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:44|31318|4:4|image|Module.pm:create_provisioning_object(431)|pr
>>>>>>ov
>>>>>>is
>>>>>> io
>>>>>> ning object could not be created, returning 0
>>>>>> |31318|4:4|image| ( 0) Module.pm, create_provisioning_object (line:
>>>>>>431)
>>>>>> |31318|4:4|image| (-1) State.pm, initialize (line: 117)
>>>>>> |31318|4:4|image| (-2) Module.pm, new (line: 207)
>>>>>> |31318|4:4|image| (-3) vcld, make_new_child (line: 564)
>>>>>> |31318|4:4|image| (-4) vcld, main (line: 346)
>>>>>> |31318|4:4|image| ---- WARNING ----
>>>>>> |31318|4:4|image| 2011-10-25
>>>>>> 09:30:44|31318|4:4|image|State.pm:initialize(118)|failed to create
>>>>>> provisioning object
>>>>>> |31318|4:4|image| ( 0) State.pm, initialize (line: 118)
>>>>>> |31318|4:4|image| (-1) Module.pm, new (line: 207)
>>>>>> |31318|4:4|image| (-2) vcld, make_new_child (line: 564)
>>>>>> |31318|4:4|image| (-3) vcld, main (line: 346)
>>>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(829)|VCL::image
>>>>>> destructor called, address: 1e47818
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:44|31318|4:4|image|utils.pm:delete_computerloadlog_reservation(
>>>>>>67
>>>>>>42
>>>>>> )|
>>>>>> removing computerloadlog entries matching loadstate = begin
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:44|31318|4:4|image|utils.pm:delete_computerloadlog_reservation(
>>>>>>67
>>>>>>89
>>>>>> )|
>>>>>> deleted rows from computerloadlog for reservation id=4
>>>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(848)|number of
>>>>>> database handles state process created: 1
>>>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(876)|VCL::image
>>>>>> process duration: 2 seconds
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_add
>>>>>>re
>>>>>>ss
>>>>>> (1
>>>>>> 581)|attempting to retrieve private IP address for computer:
>>>>>> redhat64base
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_add
>>>>>>re
>>>>>>ss
>>>>>> (1
>>>>>> 585)|retrieved contents of /etc/hosts on this management node,
>>>>>>contains
>>>>>> 9
>>>>>> lines
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_add
>>>>>>re
>>>>>>ss
>>>>>> (1
>>>>>> 645)|returning IP address from /etc/hosts file: 10.0.0.2
>>>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2703)|unable 
>>>>>>to
>>>>>> use
>>>>>> database handle stored in $ENV{dbh}
>>>>>> 2011-10-25 
>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>>> handle stored in $ENV{dbh}
>>>>>> 2011-10-25
>>>>>> 09:30:44|31318|4:4|image|utils.pm:is_inblockrequest(6163)|zero
>>>>>> rows were returned from database select
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_image_affiliation_name(
>>>>>>20
>>>>>>35
>>>>>> )|
>>>>>> image owner id: 1
>>>>>> 2011-10-25 
>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2709)|database
>>>>>> requested (information_schema) does not match handle stored in
>>>>>>$ENV{dbh}
>>>>>> (vcl:localhost)
>>>>>> 2011-10-25 
>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>>> handle stored in $ENV{dbh}
>>>>>> 2011-10-25
>>>>>>
>>>>>>
>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:retrieve_user_data(1352)|at
>>>>>>te
>>>>>>mp
>>>>>> ti
>>>>>> ng to retrieve and store data for user: user.id = '1'
>>>>>> 2011-10-25 
>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2709)|database
>>>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>>>> (information_schema:localhost)
>>>>>> 2011-10-25 
>>>>>>09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>>> handle stored in $ENV{dbh}
>>>>>> 2011-10-25
>>>>>>
>>>>>>09:30:44|31318|4:4|image|DataStructure.pm:retrieve_user_data(1415)|da
>>>>>>ta
>>>>>> has been retrieved for user: admin (id: 1)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 10/25/11 9:04 AM, "Aaron Peeler" <aa...@ncsu.edu> wrote:
>>>>>>
>>>>>>> Al,
>>>>>>>
>>>>>>> The hostname has to resolve.
>>>>>>>
>>>>>>> Put an entry in your /etc/hosts file.
>>>>>>>
>>>>>>> Aaron
>>>>>>>
>>>>>>> On Tue, Oct 25, 2011 at 8:52 AM, Evelio Quiros <ev...@fiu.edu>
>>>>>>>wrote:
>>>>>>>> Hello,
>>>>>>>> I am getting an error when I try to capture a linux base image in
>>>>>>>>vcl.
>>>>>>>> I am
>>>>>>>> following the instructions, but perhaps some parts of these may 
>>>>>>>>have
>>>>>>>> been
>>>>>>>> misinterpreted.
>>>>>>>> My VCL server is at 10.0.0.1. My Vmware based virtual machine is 
>>>>>>>>at
>>>>>>>> 10.0.0.2. I can ssh without passwords using keys from the vcl 
>>>>>>>>server
>>>>>>>> to
>>>>>>>> the
>>>>>>>> VM.
>>>>>>>> The computer has been added to the database as hostname
>>>>>>>>redhat64base,
>>>>>>>> although I have no DNS entry to resolve that name, so I use it's
>>>>>>>> private IP
>>>>>>>> of 10.0.0.2.
>>>>>>>> Below is the result of vcld trying to capture the computer to
>>>>>>>>create a
>>>>>>>> new
>>>>>>>> base imageŠ.Any ideas about what could be wrong ?
>>>>>>>> Thanks,
>>>>>>>> Al Quiros
>>>>>>>>
>>>>>>>> VCL::image object could not be created and initialized
>>>>>>>>
>>>>>>>>
>>>>>>>>-------------------------------------------------------------------
>>>>>>>>--
>>>>>>>>--
>>>>>>>> -
>>>>>>>> time: 2011-10-25 08:58:38
>>>>>>>> caller: vcld:make_new_child(571)
>>>>>>>> ( 0) vcld, make_new_child (line: 571)
>>>>>>>> (-1) vcld, main (line: 346)
>>>>>>>>
>>>>>>>>
>>>>>>>>-------------------------------------------------------------------
>>>>>>>>--
>>>>>>>>--
>>>>>>>> -
>>>>>>>> management node: vcltst.fiu.edu
>>>>>>>> reservation PID: 29609
>>>>>>>> parent vcld PID: 15838
>>>>>>>> request ID: 2
>>>>>>>> reservation ID: 2
>>>>>>>> request state/laststate: image/image
>>>>>>>> request start time: 2011-10-25 08:58:37
>>>>>>>> request end time: 2011-10-25 09:58:37
>>>>>>>> for imaging: no
>>>>>>>> log ID: none
>>>>>>>> computer: redhat64base
>>>>>>>> computer id: 12
>>>>>>>> computer type: blade
>>>>>>>> computer eth0 MAC address: <undefined>
>>>>>>>> computer eth1 MAC address: <undefined>
>>>>>>>> computer private IP address: <undefined>
>>>>>>>> computer public IP address: 10.0.0.2
>>>>>>>> computer in block allocation: no
>>>>>>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>>>>>> image: vmwarelinux-redhat64linux8-v0
>>>>>>>> image display name: redhat64linux
>>>>>>>> image ID: 8
>>>>>>>> image revision ID: 6
>>>>>>>> image size: 1450 MB
>>>>>>>> use Sysprep: yes
>>>>>>>> root access: yes
>>>>>>>> image owner ID: 1
>>>>>>>> image owner affiliation: Local
>>>>>>>> image revision date created: 2011-10-25 08:58:37
>>>>>>>> image revision production: yes
>>>>>>>> OS module: VCL::Module::OS::Linux
>>>>>>>> user: admin
>>>>>>>> user name: vcl admin
>>>>>>>> user ID: 1
>>>>>>>> user affiliation: Local
>>>>>>>>
>>>>>>>>
>>>>>>>>-------------------------------------------------------------------
>>>>>>>>--
>>>>>>>>--
>>>>>>>> -
>>>>>>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>>>>>>> 2011-10-25
>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_os_object(1238)|VM
>>>>>>>> host OS module loaded: VCL::Module::OS::Linux
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_mn_os_object(335)|managem
>>>>>>>>en
>>>>>>>>t
>>>>>>>> node
>>>>>>>> OS object has already been created, address: 1fbe730, returning 1
>>>>>>>> 2011-10-25
>>>>>>>> 08:58:38|29609|2:2|image|Module.pm:new(196)|VCL::Module::OS::Linux
>>>>>>>> object
>>>>>>>> created for image vmwarelinux-redhat64linux8-v0, address: 24f12f0
>>>>>>>> 2011-10-25
>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_os_object(1244)|VM
>>>>>>>> host OS object created: VCL::Module::OS::Linux
>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|utils.pm:run_command(8998)|$? 
>>>>>>>>is
>>>>>>>> set to
>>>>>>>> -1, setting exit status to 0, Perl bug likely encountered
>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>> 08:58:38|29609|2:2|image|utils.pm:nmap_port(2645)|error occurred
>>>>>>>> running
>>>>>>>> nmap command: '/usr/bin/nmap redhat64base -P0 -p 22 -T 
>>>>>>>>Aggressive',
>>>>>>>> output:
>>>>>>>> |29609|2:2|image| Starting Nmap 5.21 ( http://nmap.org ) at
>>>>>>>>2011-10-25
>>>>>>>> 08:58
>>>>>>>> EDT
>>>>>>>> |29609|2:2|image| Failed to resolve given hostname/IP: 
>>>>>>>>redhat64base.
>>>>>>>> Note
>>>>>>>> that you can't use '/mask' AND '1-4,7,100-' style IP ranges
>>>>>>>> |29609|2:2|image| WARNING: No targets were specified, so 0 hosts
>>>>>>>> scanned.
>>>>>>>> |29609|2:2|image| Nmap done: 0 IP addresses (0 hosts up) scanned 
>>>>>>>>in
>>>>>>>> 0.05
>>>>>>>> seconds
>>>>>>>> |29609|2:2|image| ( 0) utils.pm, nmap_port (line: 2645)
>>>>>>>> |29609|2:2|image| (-1) OS.pm, is_ssh_responding (line: 383)
>>>>>>>> |29609|2:2|image| (-2) VMware.pm, initialize (line: 252)
>>>>>>>> |29609|2:2|image| (-3) Module.pm, new (line: 207)
>>>>>>>> |29609|2:2|image| (-4) Module.pm, create_provisioning_object 
>>>>>>>>(line:
>>>>>>>> 423)
>>>>>>>> |29609|2:2|image| (-5) State.pm, initialize (line: 117)
>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>> 08:58:38|29609|2:2|image|utils.pm:nmap_port(2645)|error occurred
>>>>>>>> running
>>>>>>>> nmap command: '/usr/bin/nmap redhat64base -P0 -p 24 -T 
>>>>>>>>Aggressive',
>>>>>>>> output:
>>>>>>>> |29609|2:2|image| Starting Nmap 5.21 ( http://nmap.org ) at
>>>>>>>>2011-10-25
>>>>>>>> 08:58
>>>>>>>> EDT
>>>>>>>> |29609|2:2|image| Failed to resolve given hostname/IP: 
>>>>>>>>redhat64base.
>>>>>>>> Note
>>>>>>>> that you can't use '/mask' AND '1-4,7,100-' style IP ranges
>>>>>>>> |29609|2:2|image| WARNING: No targets were specified, so 0 hosts
>>>>>>>> scanned.
>>>>>>>> |29609|2:2|image| Nmap done: 0 IP addresses (0 hosts up) scanned 
>>>>>>>>in
>>>>>>>> 0.05
>>>>>>>> seconds
>>>>>>>> |29609|2:2|image| ( 0) utils.pm, nmap_port (line: 2645)
>>>>>>>> |29609|2:2|image| (-1) OS.pm, is_ssh_responding (line: 384)
>>>>>>>> |29609|2:2|image| (-2) VMware.pm, initialize (line: 252)
>>>>>>>> |29609|2:2|image| (-3) Module.pm, new (line: 207)
>>>>>>>> |29609|2:2|image| (-4) Module.pm, create_provisioning_object 
>>>>>>>>(line:
>>>>>>>> 423)
>>>>>>>> |29609|2:2|image| (-5) State.pm, initialize (line: 117)
>>>>>>>> 2011-10-25
>>>>>>>> 08:58:38|29609|2:2|image|OS.pm:is_ssh_responding(386)|redhat64base
>>>>>>>>is
>>>>>>>> NOT
>>>>>>>> responding to SSH, ports 22 or 24 are both closed
>>>>>>>> 2011-10-25 
>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:initialize(257)|unable
>>>>>>>> to
>>>>>>>> control OS of VM host redhat64base using VCL::Module::OS::Linux OS
>>>>>>>> object
>>>>>>>> because VM host is not responding to SSH
>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:_automethod(812)|correspo
>>>>>>>>nd
>>>>>>>>in
>>>>>>>> g
>>>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>>>> 
>>>>>>>>$self->request_data->{reservation}{2}{computer}{vmhost}{computerid}
>>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>>> |29609|2:2|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>>> |29609|2:2|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>> 1161)
>>>>>>>> |29609|2:2|image| (-3) VMware.pm, get_vmhost_api_object (line: 
>>>>>>>>1282)
>>>>>>>> |29609|2:2|image| (-4) VMware.pm, initialize (line: 265)
>>>>>>>> |29609|2:2|image| (-5) Module.pm, new (line: 207)
>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:_automethod(812)|correspo
>>>>>>>>nd
>>>>>>>>in
>>>>>>>> g
>>>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>>>>
>>>>>>>>
>>>>>>>>$self->request_data->{reservation}{2}{computer}{vmhost}{vmprofile}{
>>>>>>>>im
>>>>>>>>ag
>>>>>>>> ei
>>>>>>>> d}
>>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>>> |29609|2:2|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>>> |29609|2:2|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>>> 1162)
>>>>>>>> |29609|2:2|image| (-3) VMware.pm, get_vmhost_api_object (line: 
>>>>>>>>1282)
>>>>>>>> |29609|2:2|image| (-4) VMware.pm, initialize (line: 265)
>>>>>>>> |29609|2:2|image| (-5) Module.pm, new (line: 207)
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_datastructure(1190)|c
>>>>>>>>re
>>>>>>>>at
>>>>>>>> ed
>>>>>>>> DataStructure object for VM host: redhat64base
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1293)|atte
>>>>>>>>mp
>>>>>>>>ti
>>>>>>>> ng
>>>>>>>> to
>>>>>>>> load VMware control module:
>>>>>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1299)|load
>>>>>>>>ed
>>>>>>>> VMware
>>>>>>>> control module: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|Module.pm:new(172)|set
>>>>>>>> 'vmhost_data' key
>>>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>>> arguments
>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|Module.pm:new(172)|set
>>>>>>>>'vmhost_os'
>>>>>>>> key
>>>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>>> arguments
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_mn_os_object(335)|managem
>>>>>>>>en
>>>>>>>>t
>>>>>>>> node
>>>>>>>> OS object has already been created, address: 1fbe730, returning 1
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|Module.pm:new(200)|VCL::Module::Provisioni
>>>>>>>>ng
>>>>>>>>::
>>>>>>>> VM
>>>>>>>> ware::vSphere_SDK
>>>>>>>> object created for computer redhat64base, address: 2508cf8
>>>>>>>> 2011-10-25
>>>>>>>> 08:58:38|29609|2:2|image|vSphere_SDK.pm:initialize(1826)|vSphere
>>>>>>>> SDK for Perl does not appear to be installed on this managment 
>>>>>>>>node,
>>>>>>>> unable
>>>>>>>> to load VMware vSphere SDK Perl modules
>>>>>>>> 2011-10-25
>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>>>> object
>>>>>>>> could not be created: 
>>>>>>>>VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:initialize(273)|no methods are
>>>>>>>> available
>>>>>>>> to control VM host redhat64base, the vSphere SDK cannot be used to
>>>>>>>> control
>>>>>>>> the VM host and the host OS cannot be controlled via SSH
>>>>>>>> |29609|2:2|image| ( 0) VMware.pm, initialize (line: 273)
>>>>>>>> |29609|2:2|image| (-1) Module.pm, new (line: 207)
>>>>>>>> |29609|2:2|image| (-2) Module.pm, create_provisioning_object 
>>>>>>>>(line:
>>>>>>>> 423)
>>>>>>>> |29609|2:2|image| (-3) State.pm, initialize (line: 117)
>>>>>>>> |29609|2:2|image| (-4) Module.pm, new (line: 207)
>>>>>>>> |29609|2:2|image| (-5) vcld, make_new_child (line: 564)
>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_provisioning_object(431)|
>>>>>>>>pr
>>>>>>>>ov
>>>>>>>> is
>>>>>>>> ioning
>>>>>>>> object could not be created, returning 0
>>>>>>>> |29609|2:2|image| ( 0) Module.pm, create_provisioning_object 
>>>>>>>>(line:
>>>>>>>> 431)
>>>>>>>> |29609|2:2|image| (-1) State.pm, initialize (line: 117)
>>>>>>>> |29609|2:2|image| (-2) Module.pm, new (line: 207)
>>>>>>>> |29609|2:2|image| (-3) vcld, make_new_child (line: 564)
>>>>>>>> |29609|2:2|image| (-4) vcld, main (line: 346)
>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>> 08:58:38|29609|2:2|image|State.pm:initialize(118)|failed to create
>>>>>>>> provisioning object
>>>>>>>> |29609|2:2|image| ( 0) State.pm, initialize (line: 118)
>>>>>>>> |29609|2:2|image| (-1) Module.pm, new (line: 207)
>>>>>>>> |29609|2:2|image| (-2) vcld, make_new_child (line: 564)
>>>>>>>> |29609|2:2|image| (-3) vcld, main (line: 346)
>>>>>>>> 2011-10-25 
>>>>>>>>08:58:38|29609|2:2|image|State.pm:DESTROY(829)|VCL::image
>>>>>>>> destructor called, address: 1e52a60
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|utils.pm:delete_computerloadlog_reservatio
>>>>>>>>n(
>>>>>>>>67
>>>>>>>> 42
>>>>>>>> )|removing
>>>>>>>> computerloadlog entries matching loadstate = begin
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|utils.pm:delete_computerloadlog_reservatio
>>>>>>>>n(
>>>>>>>>67
>>>>>>>> 89
>>>>>>>> )|deleted
>>>>>>>> rows from computerloadlog for reservation id=2
>>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|State.pm:DESTROY(848)|number 
>>>>>>>>of
>>>>>>>> database
>>>>>>>> handles state process created: 1
>>>>>>>> 2011-10-25 
>>>>>>>>08:58:38|29609|2:2|image|State.pm:DESTROY(876)|VCL::image
>>>>>>>> process
>>>>>>>> duration: 0 seconds
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_a
>>>>>>>>dd
>>>>>>>>re
>>>>>>>> ss
>>>>>>>> (1581)|attempting
>>>>>>>> to retrieve private IP address for computer: redhat64base
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_a
>>>>>>>>dd
>>>>>>>>re
>>>>>>>> ss
>>>>>>>> (1585)|retrieved
>>>>>>>> contents of /etc/hosts on this management node, contains 8 lines
>>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_a
>>>>>>>>dd
>>>>>>>>re
>>>>>>>> ss
>>>>>>>> (1629)|did
>>>>>>>> not find any lines in /etc/hosts containing 'redhat64base' and the
>>>>>>>> private
>>>>>>>> IP address is not defined in the database
>>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm,
>>>>>>>> get_computer_private_ip_address
>>>>>>>> (line: 1629)
>>>>>>>> |29609|2:2|image| (-1) DataStructure.pm, 
>>>>>>>>get_reservation_info_string
>>>>>>>> (line:
>>>>>>>> 2419)
>>>>>>>> |29609|2:2|image| (-3) vcld, make_new_child (line: 571)
>>>>>>>> |29609|2:2|image| (-4) vcld, main (line: 346)
>>>>>>>> 2011-10-25 
>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2703)|unable
>>>>>>>>to
>>>>>>>> use
>>>>>>>> database handle stored in $ENV{dbh}
>>>>>>>> 2011-10-25
>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>>> handle
>>>>>>>> stored in $ENV{dbh}
>>>>>>>> 2011-10-25
>>>>>>>> 08:58:38|29609|2:2|image|utils.pm:is_inblockrequest(6163)|zero
>>>>>>>> rows were returned from database select
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_image_affiliation_nam
>>>>>>>>e(
>>>>>>>>20
>>>>>>>> 35
>>>>>>>> )|image
>>>>>>>> owner id: 1
>>>>>>>> 2011-10-25
>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2709)|database
>>>>>>>> requested (information_schema) does not match handle stored in
>>>>>>>> $ENV{dbh}
>>>>>>>> (vcl:localhost)
>>>>>>>> 2011-10-25
>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>>> handle
>>>>>>>> stored in $ENV{dbh}
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:retrieve_user_data(1352)|
>>>>>>>>at
>>>>>>>>te
>>>>>>>> mp
>>>>>>>> ting
>>>>>>>> to retrieve and store data for user: user.id = '1'
>>>>>>>> 2011-10-25
>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2709)|database
>>>>>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>>>>>> (information_schema:localhost)
>>>>>>>> 2011-10-25
>>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>>> handle
>>>>>>>> stored in $ENV{dbh}
>>>>>>>> 2011-10-25
>>>>>>>>
>>>>>>>>
>>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:retrieve_user_data(1415)|
>>>>>>>>da
>>>>>>>>ta
>>>>>>>> has
>>>>>>>> been retrieved for user: admin (id: 1)
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Aaron Peeler
>>>>>>> Program Manager
>>>>>>> Virtual Computing Lab
>>>>>>> NC State University
>>>>>>>
>>>>>>> All electronic mail messages in connection with State business 
>>>>>>>which
>>>>>>> are sent to or received by this account are subject to the NC 
>>>>>>>Public
>>>>>>> Records Law and may be disclosed to third parties.
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Aaron Peeler
>>>>> Program Manager
>>>>> Virtual Computing Lab
>>>>> NC State University
>>>>>
>>>>> All electronic mail messages in connection with State business which
>>>>> are sent to or received by this account are subject to the NC Public
>>>>> Records Law and may be disclosed to third parties.
>>>>
>>>
>>
>>
>
>
>
>-- 
>Thanks,
>Alex  Patterson
>User Support Services
>Operating System Analyst
>California State University, East Bay


Re: Base Image creation error - Continued

Posted by Alexander Patterson <al...@csueastbay.edu>.
Hello,

 Here is the main issue, You need to have your datastore the location
that you are storing you VM images in the correct place. As of right
now they are looking  in the /vmfs/volumes/local-datastore

You can either move your images to this folder or change the default location.


To do this go to Virtual Host
Click on VM host Profiles
Click on Configure Profile (Make to to select the VMware ESXI Standard
Localdisk
from the sounds of it you have Local storage and are storing your VM's locally.

The Data Store Path can be changed to the current location or you can
move the files the choice is yours. Make sure you have the Virtual
Switches set up
I'm using custom VLAN switch 0 = private and switch 1 = private
You don't have to set a Repository Path but the Data Store Path has to
be correct.

-Alex

327|5:5|image| ---- WARNING ----
|5327|5:5|image| 2011-10-25
11:38:43|5327|5:5|image|VMware.pm:_get_datastore_name(5848)|unable to
determine datastore name from path: '/vmfs/volumes/local-datastore', path
does not begin with any of the datastore paths:

2011/10/25 Evelio Quiros <ev...@fiu.edu>:
> OK,
>
> After adding the missing javascript, I am able to get the Virtual Hosts
> page to display.
>
> I added 10 VMs which have been added to the database, as well as the base
> image I want to capture, so 11 in all.
>
> Does VCL require the Vsphere module to add a virtual machine computer ?
>
> Also, I am using a free version of ESXi. Is there a licensing issue ?
>
>
> I tried once again to capture the base image, and I got this error:
>
>
> VCL::image object could not be created and initialized
> ------------------------------------------------------------------------
> time: 2011-10-25 11:38:43
> caller: vcld:make_new_child(571)
> ( 0) vcld, make_new_child (line: 571)
> (-1) vcld, main (line: 346)
> ------------------------------------------------------------------------
> management node: vcltst.fiu.edu
> reservation PID: 5327
> parent vcld PID: 15838
>
> request ID: 5
> reservation ID: 5
> request state/laststate: image/image
> request start time: 2011-10-25 11:38:35
> request end time: 2011-10-25 12:38:35
> for imaging: no
> log ID: none
>
> computer: redhat64base
> computer id: 12
> computer type: virtualmachine
> computer eth0 MAC address: <undefined>
> computer eth1 MAC address: <undefined>
> computer private IP address: 10.0.0.2
> computer public IP address: 10.106.128.53
> computer in block allocation: no
> provisioning module: VCL::Module::Provisioning::VMware::VMware
>
> vm host: vcldell_01
> vm host ID: 2
> vm host computer ID: 13
> vm profile: VMware ESX - local storage
> vm profile VM path: /vmfs/volumes/local-datastore
> vm profile repository path: 0
> vm profile datastore path: /vmfs/volumes/local-datastore
> vm profile disk type: localdisk
>
> image: vmwarelinux-redhat_linux16-v0
> image display name: redhat_linux
> image ID: 16
> image revision ID: 9
> image size: 1450 MB
> use Sysprep: yes
> root access: yes
> image owner ID: 1
> image owner affiliation: Local
> image revision date created: 2011-10-25 11:38:35
> image revision production: yes
> OS module: VCL::Module::OS::Linux
>
> user: admin
> user name: vcl admin
> user ID: 1
> user affiliation: Local
> ------------------------------------------------------------------------
> RECENT LOG ENTRIES FOR THIS PROCESS:
> 2011-10-25 11:38:41|5327|5:5|image|vSphere_SDK.pm:initialize(1826)|vSphere
> SDK for Perl does not appear to be installed on this managment node,
> unable to load VMware vSphere SDK Perl modules
> 2011-10-25
> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1313)|API object
> could not be created: VCL::Module::Provisioning::VMware::vSphere_SDK
> 2011-10-25
> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(613)|computer ID
> argument was specified, retrieving data for computer ID: 13
> 2011-10-25 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(643)|image
> ID argument was specified: 4, DataStructure object will contain image
> information for the production imagerevision of this image
> 2011-10-25
> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(660)|retrieved data
> for imagerevision ID: 4
> 2011-10-25
> 11:38:41|5327|5:5|image|DataStructure.pm:_initialize(676)|retrieved data
> for image ID: 4
> 2011-10-25
> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_datastructure(1190)|created
> DataStructure object for VM host: vcldell_01
> 2011-10-25
> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1293)|attempting
> to load VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
> 2011-10-25
> 11:38:41|5327|5:5|image|VMware.pm:get_vmhost_api_object(1299)|loaded
> VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
> 2011-10-25 11:38:41|5327|5:5|image|Module.pm:new(172)|set 'vmhost_data'
> key for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
> 2011-10-25 11:38:41|5327|5:5|image|Module.pm:new(172)|set 'vmhost_os' key
> for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
> 2011-10-25
> 11:38:41|5327|5:5|image|Module.pm:create_mn_os_object(335)|management node
> OS object has already been created, address: 219ab58, returning 1
> 2011-10-25
> 11:38:41|5327|5:5|image|Module.pm:new(200)|VCL::Module::Provisioning::VMwar
> e::VIM_SSH object created for computer redhat64base, address: 1fd9588
> 2011-10-25 11:38:42|5327|5:5|image|VIM_SSH.pm:initialize(138)|VIM
> executable available on VM host: vim-cmd
> 2011-10-25
> 11:38:42|5327|5:5|image|VIM_SSH.pm:initialize(140)|VCL::Module::Provisionin
> g::VMware::VIM_SSH object initialized
> 2011-10-25
> 11:38:42|5327|5:5|image|VMware.pm:get_vmhost_api_object(1320)|created API
> object: VCL::Module::Provisioning::VMware::VIM_SSH
> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(278)|VMware on VM
> host vcldell_01 will be controlled using vim-cmd via SSH
> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(293)|VMware OS and
> API objects created for VM host vcldell_01:
> |5327|5:5|image| VM host OS object type: VCL::Module::OS::Linux::UnixLab
> |5327|5:5|image| VMware API object type:
> VCL::Module::Provisioning::VMware::VIM_SSH
> 2011-10-25
> 11:38:42|5327|5:5|image|VMware.pm:get_vmhost_product_name(5405)|VMware
> product being used on VM host vcldell_01: 'VMware ESXi 5.0.0 build-469512'
> 2011-10-25 11:38:42|5327|5:5|image|VMware.pm:initialize(307)|product:
> VMware ESXi 5.0.0 build-469512, OS object: VCL::Module::OS::Linux::UnixLab
> 2011-10-25 11:38:42|5327|5:5|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd
> call count: 1 (hostsvc/datastore/listsummary)
> 2011-10-25 11:38:43|5327|5:5|image|VIM_SSH.pm:_run_vim_cmd(208)|executed
> command on VM host vcldell_01: vim-cmd hostsvc/datastore/listsummary
> 2011-10-25
> 11:38:43|5327|5:5|image|VMware.pm:get_datastore_info(5531)|retrieved
> datastore info from VM host:
> |5327|5:5|image| datastore1
> |5327|5:5|image| ---- WARNING ----
> |5327|5:5|image| 2011-10-25
> 11:38:43|5327|5:5|image|VMware.pm:_get_datastore_name(5848)|unable to
> determine datastore name from path: '/vmfs/volumes/local-datastore', path
> does not begin with any of the datastore paths:
> |5327|5:5|image| '[datastore1]'
> |5327|5:5|image| '/vmfs/volumes/datastore1'
> |5327|5:5|image| '/vmfs/volumes/4e96b3e5-a6562886-638a-00188be54b59'
> |5327|5:5|image| ( 0) VMware.pm, _get_datastore_name (line: 5848)
> |5327|5:5|image| (-1) VMware.pm, _get_datastore_root_normal_path (line:
> 5685)
> |5327|5:5|image| (-2) VMware.pm, _get_normal_path (line: 5775)
> |5327|5:5|image| (-3) VMware.pm, get_vmx_base_directory_path (line: 2743)
> |5327|5:5|image| (-4) VMware.pm, initialize (line: 313)
> |5327|5:5|image| (-5) Module.pm, new (line: 207)
> |5327|5:5|image| ---- WARNING ----
> |5327|5:5|image| 2011-10-25
> 11:38:43|5327|5:5|image|VMware.pm:_get_datastore_root_normal_path(5687)|fai
> led to determine datastore root normal path, unable to determine datastore
> name: /vmfs/volumes/local-datastore
> |5327|5:5|image| ( 0) VMware.pm, _get_datastore_root_normal_path (line:
> 5687)
> |5327|5:5|image| (-1) VMware.pm, _get_normal_path (line: 5775)
> |5327|5:5|image| (-2) VMware.pm, get_vmx_base_directory_path (line: 2743)
> |5327|5:5|image| (-3) VMware.pm, initialize (line: 313)
> |5327|5:5|image| (-4) Module.pm, new (line: 207)
> |5327|5:5|image| (-5) Module.pm, create_provisioning_object (line: 423)
> |5327|5:5|image| ---- WARNING ----
> |5327|5:5|image| 2011-10-25
> 11:38:43|5327|5:5|image|VMware.pm:_get_normal_path(5777)|unable to
> determine normal path, failed to determine datastore root normal path:
> /vmfs/volumes/local-datastore
> |5327|5:5|image| ( 0) VMware.pm, _get_normal_path (line: 5777)
> |5327|5:5|image| (-1) VMware.pm, get_vmx_base_directory_path (line: 2743)
> |5327|5:5|image| (-2) VMware.pm, initialize (line: 313)
> |5327|5:5|image| (-3) Module.pm, new (line: 207)
> |5327|5:5|image| (-4) Module.pm, create_provisioning_object (line: 423)
> |5327|5:5|image| (-5) State.pm, initialize (line: 117)
> |5327|5:5|image| ---- WARNING ----
> |5327|5:5|image| 2011-10-25
> 11:38:43|5327|5:5|image|VMware.pm:get_vmx_base_directory_path(2749)|unable
> to determine the vmx base directory path, failed to convert path
> configured in the VM profile to a normal path:
> /vmfs/volumes/local-datastore
> |5327|5:5|image| ( 0) VMware.pm, get_vmx_base_directory_path (line: 2749)
> |5327|5:5|image| (-1) VMware.pm, initialize (line: 313)
> |5327|5:5|image| (-2) Module.pm, new (line: 207)
> |5327|5:5|image| (-3) Module.pm, create_provisioning_object (line: 423)
> |5327|5:5|image| (-4) State.pm, initialize (line: 117)
> |5327|5:5|image| (-5) Module.pm, new (line: 207)
> |5327|5:5|image| ---- WARNING ----
> |5327|5:5|image| 2011-10-25
> 11:38:43|5327|5:5|image|VMware.pm:initialize(315)|unable to determine vmx
> base directory path on VM host vcldell_01
> |5327|5:5|image| ( 0) VMware.pm, initialize (line: 315)
> |5327|5:5|image| (-1) Module.pm, new (line: 207)
> |5327|5:5|image| (-2) Module.pm, create_provisioning_object (line: 423)
> |5327|5:5|image| (-3) State.pm, initialize (line: 117)
> |5327|5:5|image| (-4) Module.pm, new (line: 207)
> |5327|5:5|image| (-5) vcld, make_new_child (line: 564)
> |5327|5:5|image| ---- WARNING ----
> |5327|5:5|image| 2011-10-25
> 11:38:43|5327|5:5|image|Module.pm:create_provisioning_object(431)|provision
> ing object could not be created, returning 0
> |5327|5:5|image| ( 0) Module.pm, create_provisioning_object (line: 431)
> |5327|5:5|image| (-1) State.pm, initialize (line: 117)
> |5327|5:5|image| (-2) Module.pm, new (line: 207)
> |5327|5:5|image| (-3) vcld, make_new_child (line: 564)
> |5327|5:5|image| (-4) vcld, main (line: 346)
> |5327|5:5|image| ---- WARNING ----
> |5327|5:5|image| 2011-10-25
> 11:38:43|5327|5:5|image|State.pm:initialize(118)|failed to create
> provisioning object
> |5327|5:5|image| ( 0) State.pm, initialize (line: 118)
> |5327|5:5|image| (-1) Module.pm, new (line: 207)
> |5327|5:5|image| (-2) vcld, make_new_child (line: 564)
> |5327|5:5|image| (-3) vcld, main (line: 346)
> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(829)|VCL::image
> destructor called, address: 1e47a28
> 2011-10-25
> 11:38:43|5327|5:5|image|utils.pm:delete_computerloadlog_reservation(6742)|r
> emoving computerloadlog entries matching loadstate = begin
> 2011-10-25
> 11:38:43|5327|5:5|image|utils.pm:delete_computerloadlog_reservation(6789)|d
> eleted rows from computerloadlog for reservation id=5
> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(848)|number of
> database handles state process created: 1
> 2011-10-25 11:38:43|5327|5:5|image|State.pm:DESTROY(876)|VCL::image
> process duration: 4 seconds
> 2011-10-25
> 11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address(15
> 81)|attempting to retrieve private IP address for computer: redhat64base
> 2011-10-25
> 11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address(15
> 85)|retrieved contents of /etc/hosts on this management node, contains 10
> lines
> 2011-10-25
> 11:38:43|5327|5:5|image|DataStructure.pm:get_computer_private_ip_address(16
> 45)|returning IP address from /etc/hosts file: 10.0.0.2
> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2703)|unable to use
> database handle stored in $ENV{dbh}
> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
> handle stored in $ENV{dbh}
> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:is_inblockrequest(6163)|zero
> rows were returned from database select
> 2011-10-25
> 11:38:43|5327|5:5|image|DataStructure.pm:get_image_affiliation_name(2035)|i
> mage owner id: 1
> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2709)|database
> requested (information_schema) does not match handle stored in $ENV{dbh}
> (vcl:localhost)
> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
> handle stored in $ENV{dbh}
> 2011-10-25
> 11:38:43|5327|5:5|image|DataStructure.pm:retrieve_user_data(1352)|attemptin
> g to retrieve and store data for user: user.id = '1'
> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2709)|database
> requested (vcl) does not match handle stored in $ENV{dbh}
> (information_schema:localhost)
> 2011-10-25 11:38:43|5327|5:5|image|utils.pm:getnewdbh(2760)|database
> handle stored in $ENV{dbh}
> 2011-10-25
> 11:38:43|5327|5:5|image|DataStructure.pm:retrieve_user_data(1415)|data has
> been retrieved for user: admin (id: 1)
>
>
>
>
>
>
>
> On 10/25/11 10:26 AM, "Aaron Coburn" <ac...@amherst.edu> wrote:
>
>>Al,
>>if you plan to use the vSphere API, then you will need to install the
>>vSphere SDK for Perl separately. The perl modules are available here --
>>just make sure that you download the release that matches your vCenter
>>version.
>>
>>http://www.vmware.com/support/developer/viperltoolkit/
>>
>>Aaron Coburn
>>
>>
>>On Oct 25, 2011, at 10:03 AM, Evelio Quiros wrote:
>>
>>> Thanks again Aaron. It seems we are taking baby steps here.
>>>
>>> Ok, next issue: When I click "Configure Host" in the vcl web interface,
>>> nothing happens.
>>>
>>> My Vmware server is listed there. It is in "vmhostinuse" state.
>>>
>>> I noticed some complaints below about the Vsphere perl module not being
>>> installed.
>>> I thought that was done in the "install_perl_libraries script.
>>>
>>> Thanks again for all your help.
>>>
>>> Al Quiros
>>>
>>>
>>> On 10/25/11 9:43 AM, "Aaron Peeler" <fa...@ncsu.edu> wrote:
>>>
>>>> In the log output your missing the vmhost information.
>>>>
>>>> Make sure your vm host server have a correctly configured vmhost
>>>> profile and you have assigned your vms to the virtual host server by
>>>> using the Virtual Host interface.
>>>>
>>>>
>>>>https://cwiki.apache.org/confluence/display/VCL/VCL+2.2.1+-+Further+Step
>>>>s+
>>>> if+Using+VMware
>>>> https://cwiki.apache.org/confluence/display/VCL/VMware+Configuration
>>>>
>>>> I'm not seeing the virtual host interface mentioned directly in the
>>>> vcl 2.2.1 install guide. I'll added that to the first link.
>>>>
>>>> Here is a link from a bootcamp that you can review this morning while
>>>> I work on adding the content to Apache VCL:
>>>>
>>>>https://sites.google.com/a/ncsu.edu/vcl-bootcamp/exercises/assign-a-vm-t
>>>>o-
>>>> a-virtual-host
>>>>
>>>> Aaron
>>>>
>>>>
>>>> On Tue, Oct 25, 2011 at 9:19 AM, Evelio Quiros <ev...@fiu.edu> wrote:
>>>>> Thank you Aaron.
>>>>>
>>>>> Ok, now it can resolve the name redhat64base to the private IP address
>>>>> 10.0.0.2.
>>>>> I tried to add the base image as the name linux64.
>>>>> It resides in the database as redhat64base, with the public IP of
>>>>> 10.106.128.53, and set as available.
>>>>> I'm not sure what this error message is telling meŠ
>>>>>
>>>>> VCL::image object could not be created and initialized
>>>>>
>>>>>-----------------------------------------------------------------------
>>>>>-
>>>>> time: 2011-10-25 09:30:44
>>>>> caller: vcld:make_new_child(571)
>>>>> ( 0) vcld, make_new_child (line: 571)
>>>>> (-1) vcld, main (line: 346)
>>>>>
>>>>>-----------------------------------------------------------------------
>>>>>-
>>>>> management node: vcltst.fiu.edu
>>>>> reservation PID: 31318
>>>>> parent vcld PID: 15838
>>>>>
>>>>> request ID: 4
>>>>> reservation ID: 4
>>>>> request state/laststate: image/image
>>>>> request start time: 2011-10-25 09:30:37
>>>>> request end time: 2011-10-25 10:30:37
>>>>> for imaging: no
>>>>> log ID: none
>>>>>
>>>>> computer: redhat64base
>>>>> computer id: 12
>>>>> computer type: blade
>>>>> computer eth0 MAC address: <undefined>
>>>>> computer eth1 MAC address: <undefined>
>>>>> computer private IP address: 10.0.0.2
>>>>> computer public IP address: 10.106.128.53
>>>>> computer in block allocation: no
>>>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>>>
>>>>> image: vmwarelinux-linux6414-v0
>>>>> image display name: linux64
>>>>> image ID: 14
>>>>> image revision ID: 8
>>>>> image size: 1450 MB
>>>>> use Sysprep: yes
>>>>> root access: yes
>>>>> image owner ID: 1
>>>>> image owner affiliation: Local
>>>>> image revision date created: 2011-10-25 09:30:37
>>>>> image revision production: yes
>>>>> OS module: VCL::Module::OS::Linux
>>>>>
>>>>> user: admin
>>>>> user name: vcl admin
>>>>> user ID: 1
>>>>> user affiliation: Local
>>>>>
>>>>>-----------------------------------------------------------------------
>>>>>-
>>>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attempti
>>>>>ng
>>>>> to load VMware control module:
>>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>> 2011-10-25
>>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>>> VMware control module: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>'vmhost_data'
>>>>> key for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>> arguments
>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set 'vmhost_os'
>>>>> key
>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>arguments
>>>>> 2011-10-25
>>>>> 09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|management
>>>>> node OS object has already been created, address: 21956b8, returning 1
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioning::
>>>>>VM
>>>>> wa
>>>>> re::vSphere_SDK object created for computer redhat64base, address:
>>>>> 21e6980
>>>>> 2011-10-25
>>>>> 09:30:43|31318|4:4|image|vSphere_SDK.pm:initialize(1826)|vSphere SDK
>>>>>for
>>>>> Perl does not appear to be installed on this managment node, unable to
>>>>> load VMware vSphere SDK Perl modules
>>>>> 2011-10-25
>>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>> object
>>>>> could not be created: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>> |31318|4:4|image| ---- WARNING ----
>>>>> |31318|4:4|image| 2011-10-25
>>>>>
>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspondin
>>>>>g
>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>> $self->request_data->{reservation}{4}{computer}{vmhost}{computerid}
>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>1161)
>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>> |31318|4:4|image| ---- WARNING ----
>>>>> |31318|4:4|image| 2011-10-25
>>>>>
>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspondin
>>>>>g
>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>
>>>>>
>>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{vmprofile}{imag
>>>>>ei
>>>>> d}
>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>1162)
>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_datastructure(1190)|creat
>>>>>ed
>>>>> DataStructure object for VM host: redhat64base
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attempti
>>>>>ng
>>>>> to load VMware control module:
>>>>> VCL::Module::Provisioning::VMware::VIM_SSH
>>>>> 2011-10-25
>>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>>> VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>'vmhost_data'
>>>>> key for VCL::Module::Provisioning::VMware::VIM_SSH object from
>>>>>arguments
>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set 'vmhost_os'
>>>>> key
>>>>> for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
>>>>> 2011-10-25
>>>>> 09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|management
>>>>> node OS object has already been created, address: 21956b8, returning 1
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioning::
>>>>>VM
>>>>> wa
>>>>> re::VIM_SSH object created for computer redhat64base, address: 24f7888
>>>>> 2011-10-25 09:30:43|31318|4:4|image|VIM_SSH.pm:initialize(126)|VIM
>>>>> executable is not available on the VM host, output:
>>>>> |31318|4:4|image| bash: vim-cmd: command not found
>>>>> |31318|4:4|image| bash: vmware-vim-cmd: command not found
>>>>> 2011-10-25
>>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>> object
>>>>> could not be created: VCL::Module::Provisioning::VMware::VIM_SSH
>>>>> |31318|4:4|image| ---- WARNING ----
>>>>> |31318|4:4|image| 2011-10-25
>>>>>
>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspondin
>>>>>g
>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>> $self->request_data->{reservation}{4}{computer}{vmhost}{computerid}
>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>1161)
>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>> |31318|4:4|image| ---- WARNING ----
>>>>> |31318|4:4|image| 2011-10-25
>>>>>
>>>>>09:30:43|31318|4:4|image|DataStructure.pm:_automethod(812)|correspondin
>>>>>g
>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>
>>>>>
>>>>>$self->request_data->{reservation}{4}{computer}{vmhost}{vmprofile}{imag
>>>>>ei
>>>>> d}
>>>>> |31318|4:4|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>> |31318|4:4|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>> |31318|4:4|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>1162)
>>>>> |31318|4:4|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>> |31318|4:4|image| (-4) VMware.pm, initialize (line: 278)
>>>>> |31318|4:4|image| (-5) Module.pm, new (line: 207)
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_datastructure(1190)|creat
>>>>>ed
>>>>> DataStructure object for VM host: redhat64base
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1293)|attempti
>>>>>ng
>>>>> to load VMware control module:
>>>>> VCL::Module::Provisioning::VMware::vmware_cmd
>>>>> 2011-10-25
>>>>> 09:30:43|31318|4:4|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>>> VMware control module: VCL::Module::Provisioning::VMware::vmware_cmd
>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set
>>>>>'vmhost_data'
>>>>> key for VCL::Module::Provisioning::VMware::vmware_cmd object from
>>>>> arguments
>>>>> 2011-10-25 09:30:43|31318|4:4|image|Module.pm:new(172)|set 'vmhost_os'
>>>>> key
>>>>> for VCL::Module::Provisioning::VMware::vmware_cmd object from
>>>>>arguments
>>>>> 2011-10-25
>>>>> 09:30:43|31318|4:4|image|Module.pm:create_mn_os_object(335)|management
>>>>> node OS object has already been created, address: 21956b8, returning 1
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:43|31318|4:4|image|Module.pm:new(200)|VCL::Module::Provisioning::
>>>>>VM
>>>>> wa
>>>>> re::vmware_cmd object created for computer redhat64base, address:
>>>>> 251d1e0
>>>>> 2011-10-25
>>>>> 09:30:44|31318|4:4|image|vmware_cmd.pm:initialize(107)|vmware-cmd is
>>>>>not
>>>>> available on the VM host, output:
>>>>> |31318|4:4|image| bash: vmware-cmd: command not found
>>>>> 2011-10-25
>>>>> 09:30:44|31318|4:4|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>> object
>>>>> could not be created: VCL::Module::Provisioning::VMware::vmware_cmd
>>>>> |31318|4:4|image| ---- WARNING ----
>>>>> |31318|4:4|image| 2011-10-25
>>>>> 09:30:44|31318|4:4|image|VMware.pm:initialize(285)|failed to create an
>>>>> object to control VMware on VM host: redhat64base
>>>>> |31318|4:4|image| ( 0) VMware.pm, initialize (line: 285)
>>>>> |31318|4:4|image| (-1) Module.pm, new (line: 207)
>>>>> |31318|4:4|image| (-2) Module.pm, create_provisioning_object (line:
>>>>>423)
>>>>> |31318|4:4|image| (-3) State.pm, initialize (line: 117)
>>>>> |31318|4:4|image| (-4) Module.pm, new (line: 207)
>>>>> |31318|4:4|image| (-5) vcld, make_new_child (line: 564)
>>>>> |31318|4:4|image| ---- WARNING ----
>>>>> |31318|4:4|image| 2011-10-25
>>>>>
>>>>>
>>>>>09:30:44|31318|4:4|image|Module.pm:create_provisioning_object(431)|prov
>>>>>is
>>>>> io
>>>>> ning object could not be created, returning 0
>>>>> |31318|4:4|image| ( 0) Module.pm, create_provisioning_object (line:
>>>>>431)
>>>>> |31318|4:4|image| (-1) State.pm, initialize (line: 117)
>>>>> |31318|4:4|image| (-2) Module.pm, new (line: 207)
>>>>> |31318|4:4|image| (-3) vcld, make_new_child (line: 564)
>>>>> |31318|4:4|image| (-4) vcld, main (line: 346)
>>>>> |31318|4:4|image| ---- WARNING ----
>>>>> |31318|4:4|image| 2011-10-25
>>>>> 09:30:44|31318|4:4|image|State.pm:initialize(118)|failed to create
>>>>> provisioning object
>>>>> |31318|4:4|image| ( 0) State.pm, initialize (line: 118)
>>>>> |31318|4:4|image| (-1) Module.pm, new (line: 207)
>>>>> |31318|4:4|image| (-2) vcld, make_new_child (line: 564)
>>>>> |31318|4:4|image| (-3) vcld, main (line: 346)
>>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(829)|VCL::image
>>>>> destructor called, address: 1e47818
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:44|31318|4:4|image|utils.pm:delete_computerloadlog_reservation(67
>>>>>42
>>>>> )|
>>>>> removing computerloadlog entries matching loadstate = begin
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:44|31318|4:4|image|utils.pm:delete_computerloadlog_reservation(67
>>>>>89
>>>>> )|
>>>>> deleted rows from computerloadlog for reservation id=4
>>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(848)|number of
>>>>> database handles state process created: 1
>>>>> 2011-10-25 09:30:44|31318|4:4|image|State.pm:DESTROY(876)|VCL::image
>>>>> process duration: 2 seconds
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_addre
>>>>>ss
>>>>> (1
>>>>> 581)|attempting to retrieve private IP address for computer:
>>>>> redhat64base
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_addre
>>>>>ss
>>>>> (1
>>>>> 585)|retrieved contents of /etc/hosts on this management node,
>>>>>contains
>>>>> 9
>>>>> lines
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_computer_private_ip_addre
>>>>>ss
>>>>> (1
>>>>> 645)|returning IP address from /etc/hosts file: 10.0.0.2
>>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2703)|unable to
>>>>> use
>>>>> database handle stored in $ENV{dbh}
>>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>> handle stored in $ENV{dbh}
>>>>> 2011-10-25
>>>>> 09:30:44|31318|4:4|image|utils.pm:is_inblockrequest(6163)|zero
>>>>> rows were returned from database select
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:44|31318|4:4|image|DataStructure.pm:get_image_affiliation_name(20
>>>>>35
>>>>> )|
>>>>> image owner id: 1
>>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2709)|database
>>>>> requested (information_schema) does not match handle stored in
>>>>>$ENV{dbh}
>>>>> (vcl:localhost)
>>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>> handle stored in $ENV{dbh}
>>>>> 2011-10-25
>>>>>
>>>>>
>>>>>09:30:44|31318|4:4|image|DataStructure.pm:retrieve_user_data(1352)|atte
>>>>>mp
>>>>> ti
>>>>> ng to retrieve and store data for user: user.id = '1'
>>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2709)|database
>>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>>> (information_schema:localhost)
>>>>> 2011-10-25 09:30:44|31318|4:4|image|utils.pm:getnewdbh(2760)|database
>>>>> handle stored in $ENV{dbh}
>>>>> 2011-10-25
>>>>>
>>>>>09:30:44|31318|4:4|image|DataStructure.pm:retrieve_user_data(1415)|data
>>>>> has been retrieved for user: admin (id: 1)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 10/25/11 9:04 AM, "Aaron Peeler" <aa...@ncsu.edu> wrote:
>>>>>
>>>>>> Al,
>>>>>>
>>>>>> The hostname has to resolve.
>>>>>>
>>>>>> Put an entry in your /etc/hosts file.
>>>>>>
>>>>>> Aaron
>>>>>>
>>>>>> On Tue, Oct 25, 2011 at 8:52 AM, Evelio Quiros <ev...@fiu.edu>
>>>>>>wrote:
>>>>>>> Hello,
>>>>>>> I am getting an error when I try to capture a linux base image in
>>>>>>>vcl.
>>>>>>> I am
>>>>>>> following the instructions, but perhaps some parts of these may have
>>>>>>> been
>>>>>>> misinterpreted.
>>>>>>> My VCL server is at 10.0.0.1. My Vmware based virtual machine is at
>>>>>>> 10.0.0.2. I can ssh without passwords using keys from the vcl server
>>>>>>> to
>>>>>>> the
>>>>>>> VM.
>>>>>>> The computer has been added to the database as hostname
>>>>>>>redhat64base,
>>>>>>> although I have no DNS entry to resolve that name, so I use it's
>>>>>>> private IP
>>>>>>> of 10.0.0.2.
>>>>>>> Below is the result of vcld trying to capture the computer to
>>>>>>>create a
>>>>>>> new
>>>>>>> base imageŠ.Any ideas about what could be wrong ?
>>>>>>> Thanks,
>>>>>>> Al Quiros
>>>>>>>
>>>>>>> VCL::image object could not be created and initialized
>>>>>>>
>>>>>>>
>>>>>>>---------------------------------------------------------------------
>>>>>>>--
>>>>>>> -
>>>>>>> time: 2011-10-25 08:58:38
>>>>>>> caller: vcld:make_new_child(571)
>>>>>>> ( 0) vcld, make_new_child (line: 571)
>>>>>>> (-1) vcld, main (line: 346)
>>>>>>>
>>>>>>>
>>>>>>>---------------------------------------------------------------------
>>>>>>>--
>>>>>>> -
>>>>>>> management node: vcltst.fiu.edu
>>>>>>> reservation PID: 29609
>>>>>>> parent vcld PID: 15838
>>>>>>> request ID: 2
>>>>>>> reservation ID: 2
>>>>>>> request state/laststate: image/image
>>>>>>> request start time: 2011-10-25 08:58:37
>>>>>>> request end time: 2011-10-25 09:58:37
>>>>>>> for imaging: no
>>>>>>> log ID: none
>>>>>>> computer: redhat64base
>>>>>>> computer id: 12
>>>>>>> computer type: blade
>>>>>>> computer eth0 MAC address: <undefined>
>>>>>>> computer eth1 MAC address: <undefined>
>>>>>>> computer private IP address: <undefined>
>>>>>>> computer public IP address: 10.0.0.2
>>>>>>> computer in block allocation: no
>>>>>>> provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>>>>> image: vmwarelinux-redhat64linux8-v0
>>>>>>> image display name: redhat64linux
>>>>>>> image ID: 8
>>>>>>> image revision ID: 6
>>>>>>> image size: 1450 MB
>>>>>>> use Sysprep: yes
>>>>>>> root access: yes
>>>>>>> image owner ID: 1
>>>>>>> image owner affiliation: Local
>>>>>>> image revision date created: 2011-10-25 08:58:37
>>>>>>> image revision production: yes
>>>>>>> OS module: VCL::Module::OS::Linux
>>>>>>> user: admin
>>>>>>> user name: vcl admin
>>>>>>> user ID: 1
>>>>>>> user affiliation: Local
>>>>>>>
>>>>>>>
>>>>>>>---------------------------------------------------------------------
>>>>>>>--
>>>>>>> -
>>>>>>> RECENT LOG ENTRIES FOR THIS PROCESS:
>>>>>>> 2011-10-25
>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_os_object(1238)|VM
>>>>>>> host OS module loaded: VCL::Module::OS::Linux
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_mn_os_object(335)|managemen
>>>>>>>t
>>>>>>> node
>>>>>>> OS object has already been created, address: 1fbe730, returning 1
>>>>>>> 2011-10-25
>>>>>>> 08:58:38|29609|2:2|image|Module.pm:new(196)|VCL::Module::OS::Linux
>>>>>>> object
>>>>>>> created for image vmwarelinux-redhat64linux8-v0, address: 24f12f0
>>>>>>> 2011-10-25
>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_os_object(1244)|VM
>>>>>>> host OS object created: VCL::Module::OS::Linux
>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|utils.pm:run_command(8998)|$? is
>>>>>>> set to
>>>>>>> -1, setting exit status to 0, Perl bug likely encountered
>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>> 08:58:38|29609|2:2|image|utils.pm:nmap_port(2645)|error occurred
>>>>>>> running
>>>>>>> nmap command: '/usr/bin/nmap redhat64base -P0 -p 22 -T Aggressive',
>>>>>>> output:
>>>>>>> |29609|2:2|image| Starting Nmap 5.21 ( http://nmap.org ) at
>>>>>>>2011-10-25
>>>>>>> 08:58
>>>>>>> EDT
>>>>>>> |29609|2:2|image| Failed to resolve given hostname/IP: redhat64base.
>>>>>>> Note
>>>>>>> that you can't use '/mask' AND '1-4,7,100-' style IP ranges
>>>>>>> |29609|2:2|image| WARNING: No targets were specified, so 0 hosts
>>>>>>> scanned.
>>>>>>> |29609|2:2|image| Nmap done: 0 IP addresses (0 hosts up) scanned in
>>>>>>> 0.05
>>>>>>> seconds
>>>>>>> |29609|2:2|image| ( 0) utils.pm, nmap_port (line: 2645)
>>>>>>> |29609|2:2|image| (-1) OS.pm, is_ssh_responding (line: 383)
>>>>>>> |29609|2:2|image| (-2) VMware.pm, initialize (line: 252)
>>>>>>> |29609|2:2|image| (-3) Module.pm, new (line: 207)
>>>>>>> |29609|2:2|image| (-4) Module.pm, create_provisioning_object (line:
>>>>>>> 423)
>>>>>>> |29609|2:2|image| (-5) State.pm, initialize (line: 117)
>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>> 08:58:38|29609|2:2|image|utils.pm:nmap_port(2645)|error occurred
>>>>>>> running
>>>>>>> nmap command: '/usr/bin/nmap redhat64base -P0 -p 24 -T Aggressive',
>>>>>>> output:
>>>>>>> |29609|2:2|image| Starting Nmap 5.21 ( http://nmap.org ) at
>>>>>>>2011-10-25
>>>>>>> 08:58
>>>>>>> EDT
>>>>>>> |29609|2:2|image| Failed to resolve given hostname/IP: redhat64base.
>>>>>>> Note
>>>>>>> that you can't use '/mask' AND '1-4,7,100-' style IP ranges
>>>>>>> |29609|2:2|image| WARNING: No targets were specified, so 0 hosts
>>>>>>> scanned.
>>>>>>> |29609|2:2|image| Nmap done: 0 IP addresses (0 hosts up) scanned in
>>>>>>> 0.05
>>>>>>> seconds
>>>>>>> |29609|2:2|image| ( 0) utils.pm, nmap_port (line: 2645)
>>>>>>> |29609|2:2|image| (-1) OS.pm, is_ssh_responding (line: 384)
>>>>>>> |29609|2:2|image| (-2) VMware.pm, initialize (line: 252)
>>>>>>> |29609|2:2|image| (-3) Module.pm, new (line: 207)
>>>>>>> |29609|2:2|image| (-4) Module.pm, create_provisioning_object (line:
>>>>>>> 423)
>>>>>>> |29609|2:2|image| (-5) State.pm, initialize (line: 117)
>>>>>>> 2011-10-25
>>>>>>> 08:58:38|29609|2:2|image|OS.pm:is_ssh_responding(386)|redhat64base
>>>>>>>is
>>>>>>> NOT
>>>>>>> responding to SSH, ports 22 or 24 are both closed
>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|VMware.pm:initialize(257)|unable
>>>>>>> to
>>>>>>> control OS of VM host redhat64base using VCL::Module::OS::Linux OS
>>>>>>> object
>>>>>>> because VM host is not responding to SSH
>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:_automethod(812)|correspond
>>>>>>>in
>>>>>>> g
>>>>>>> data has not been initialized for get_vmhost_computer_id:
>>>>>>> $self->request_data->{reservation}{2}{computer}{vmhost}{computerid}
>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>> |29609|2:2|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>> |29609|2:2|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>> 1161)
>>>>>>> |29609|2:2|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>>>> |29609|2:2|image| (-4) VMware.pm, initialize (line: 265)
>>>>>>> |29609|2:2|image| (-5) Module.pm, new (line: 207)
>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:_automethod(812)|correspond
>>>>>>>in
>>>>>>> g
>>>>>>> data has not been initialized for get_vmhost_profile_image_id:
>>>>>>>
>>>>>>>
>>>>>>>$self->request_data->{reservation}{2}{computer}{vmhost}{vmprofile}{im
>>>>>>>ag
>>>>>>> ei
>>>>>>> d}
>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm, _automethod (line: 812)
>>>>>>> |29609|2:2|image| (-1) Autoload.pm, __ANON__ (line: 80)
>>>>>>> |29609|2:2|image| (-2) VMware.pm, get_vmhost_datastructure (line:
>>>>>>> 1162)
>>>>>>> |29609|2:2|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
>>>>>>> |29609|2:2|image| (-4) VMware.pm, initialize (line: 265)
>>>>>>> |29609|2:2|image| (-5) Module.pm, new (line: 207)
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_datastructure(1190)|cre
>>>>>>>at
>>>>>>> ed
>>>>>>> DataStructure object for VM host: redhat64base
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1293)|attemp
>>>>>>>ti
>>>>>>> ng
>>>>>>> to
>>>>>>> load VMware control module:
>>>>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1299)|loaded
>>>>>>> VMware
>>>>>>> control module: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|Module.pm:new(172)|set
>>>>>>> 'vmhost_data' key
>>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>> arguments
>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|Module.pm:new(172)|set
>>>>>>>'vmhost_os'
>>>>>>> key
>>>>>>> for VCL::Module::Provisioning::VMware::vSphere_SDK object from
>>>>>>> arguments
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_mn_os_object(335)|managemen
>>>>>>>t
>>>>>>> node
>>>>>>> OS object has already been created, address: 1fbe730, returning 1
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|Module.pm:new(200)|VCL::Module::Provisioning
>>>>>>>::
>>>>>>> VM
>>>>>>> ware::vSphere_SDK
>>>>>>> object created for computer redhat64base, address: 2508cf8
>>>>>>> 2011-10-25
>>>>>>> 08:58:38|29609|2:2|image|vSphere_SDK.pm:initialize(1826)|vSphere
>>>>>>> SDK for Perl does not appear to be installed on this managment node,
>>>>>>> unable
>>>>>>> to load VMware vSphere SDK Perl modules
>>>>>>> 2011-10-25
>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:get_vmhost_api_object(1313)|API
>>>>>>> object
>>>>>>> could not be created: VCL::Module::Provisioning::VMware::vSphere_SDK
>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>> 08:58:38|29609|2:2|image|VMware.pm:initialize(273)|no methods are
>>>>>>> available
>>>>>>> to control VM host redhat64base, the vSphere SDK cannot be used to
>>>>>>> control
>>>>>>> the VM host and the host OS cannot be controlled via SSH
>>>>>>> |29609|2:2|image| ( 0) VMware.pm, initialize (line: 273)
>>>>>>> |29609|2:2|image| (-1) Module.pm, new (line: 207)
>>>>>>> |29609|2:2|image| (-2) Module.pm, create_provisioning_object (line:
>>>>>>> 423)
>>>>>>> |29609|2:2|image| (-3) State.pm, initialize (line: 117)
>>>>>>> |29609|2:2|image| (-4) Module.pm, new (line: 207)
>>>>>>> |29609|2:2|image| (-5) vcld, make_new_child (line: 564)
>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|Module.pm:create_provisioning_object(431)|pr
>>>>>>>ov
>>>>>>> is
>>>>>>> ioning
>>>>>>> object could not be created, returning 0
>>>>>>> |29609|2:2|image| ( 0) Module.pm, create_provisioning_object (line:
>>>>>>> 431)
>>>>>>> |29609|2:2|image| (-1) State.pm, initialize (line: 117)
>>>>>>> |29609|2:2|image| (-2) Module.pm, new (line: 207)
>>>>>>> |29609|2:2|image| (-3) vcld, make_new_child (line: 564)
>>>>>>> |29609|2:2|image| (-4) vcld, main (line: 346)
>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>> 08:58:38|29609|2:2|image|State.pm:initialize(118)|failed to create
>>>>>>> provisioning object
>>>>>>> |29609|2:2|image| ( 0) State.pm, initialize (line: 118)
>>>>>>> |29609|2:2|image| (-1) Module.pm, new (line: 207)
>>>>>>> |29609|2:2|image| (-2) vcld, make_new_child (line: 564)
>>>>>>> |29609|2:2|image| (-3) vcld, main (line: 346)
>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|State.pm:DESTROY(829)|VCL::image
>>>>>>> destructor called, address: 1e52a60
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|utils.pm:delete_computerloadlog_reservation(
>>>>>>>67
>>>>>>> 42
>>>>>>> )|removing
>>>>>>> computerloadlog entries matching loadstate = begin
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|utils.pm:delete_computerloadlog_reservation(
>>>>>>>67
>>>>>>> 89
>>>>>>> )|deleted
>>>>>>> rows from computerloadlog for reservation id=2
>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|State.pm:DESTROY(848)|number of
>>>>>>> database
>>>>>>> handles state process created: 1
>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|State.pm:DESTROY(876)|VCL::image
>>>>>>> process
>>>>>>> duration: 0 seconds
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_add
>>>>>>>re
>>>>>>> ss
>>>>>>> (1581)|attempting
>>>>>>> to retrieve private IP address for computer: redhat64base
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_add
>>>>>>>re
>>>>>>> ss
>>>>>>> (1585)|retrieved
>>>>>>> contents of /etc/hosts on this management node, contains 8 lines
>>>>>>> |29609|2:2|image| ---- WARNING ----
>>>>>>> |29609|2:2|image| 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_computer_private_ip_add
>>>>>>>re
>>>>>>> ss
>>>>>>> (1629)|did
>>>>>>> not find any lines in /etc/hosts containing 'redhat64base' and the
>>>>>>> private
>>>>>>> IP address is not defined in the database
>>>>>>> |29609|2:2|image| ( 0) DataStructure.pm,
>>>>>>> get_computer_private_ip_address
>>>>>>> (line: 1629)
>>>>>>> |29609|2:2|image| (-1) DataStructure.pm, get_reservation_info_string
>>>>>>> (line:
>>>>>>> 2419)
>>>>>>> |29609|2:2|image| (-3) vcld, make_new_child (line: 571)
>>>>>>> |29609|2:2|image| (-4) vcld, main (line: 346)
>>>>>>> 2011-10-25 08:58:38|29609|2:2|image|utils.pm:getnewdbh(2703)|unable
>>>>>>>to
>>>>>>> use
>>>>>>> database handle stored in $ENV{dbh}
>>>>>>> 2011-10-25
>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>> handle
>>>>>>> stored in $ENV{dbh}
>>>>>>> 2011-10-25
>>>>>>> 08:58:38|29609|2:2|image|utils.pm:is_inblockrequest(6163)|zero
>>>>>>> rows were returned from database select
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:get_image_affiliation_name(
>>>>>>>20
>>>>>>> 35
>>>>>>> )|image
>>>>>>> owner id: 1
>>>>>>> 2011-10-25
>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2709)|database
>>>>>>> requested (information_schema) does not match handle stored in
>>>>>>> $ENV{dbh}
>>>>>>> (vcl:localhost)
>>>>>>> 2011-10-25
>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>> handle
>>>>>>> stored in $ENV{dbh}
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:retrieve_user_data(1352)|at
>>>>>>>te
>>>>>>> mp
>>>>>>> ting
>>>>>>> to retrieve and store data for user: user.id = '1'
>>>>>>> 2011-10-25
>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2709)|database
>>>>>>> requested (vcl) does not match handle stored in $ENV{dbh}
>>>>>>> (information_schema:localhost)
>>>>>>> 2011-10-25
>>>>>>>08:58:38|29609|2:2|image|utils.pm:getnewdbh(2760)|database
>>>>>>> handle
>>>>>>> stored in $ENV{dbh}
>>>>>>> 2011-10-25
>>>>>>>
>>>>>>>
>>>>>>>08:58:38|29609|2:2|image|DataStructure.pm:retrieve_user_data(1415)|da
>>>>>>>ta
>>>>>>> has
>>>>>>> been retrieved for user: admin (id: 1)
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Aaron Peeler
>>>>>> Program Manager
>>>>>> Virtual Computing Lab
>>>>>> NC State University
>>>>>>
>>>>>> All electronic mail messages in connection with State business which
>>>>>> are sent to or received by this account are subject to the NC Public
>>>>>> Records Law and may be disclosed to third parties.
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Aaron Peeler
>>>> Program Manager
>>>> Virtual Computing Lab
>>>> NC State University
>>>>
>>>> All electronic mail messages in connection with State business which
>>>> are sent to or received by this account are subject to the NC Public
>>>> Records Law and may be disclosed to third parties.
>>>
>>
>
>



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