I finally have a lead as how to fix this.

I turns out when you run the command you not only have to specify the port, but 
also the hostname.  So the following command worked without errors:

vmware-vim-cmd -H localhost -O 904 -U <USERNAME> -P <PASSWORD> vmsvc/getallvms

I ran a grep -r in the management node directory for vmware-vim-cmd and found 
these commands are being run from VIM.SHH.pm.

So I guess my new question is, how to I go about editing this and/or did I miss 
a database configuration that specifies the parameters I'm missing?

Kindest Regards,

Patrick Sigmon

On Jan 6, 2011, at 9:45 AM, Andy Kurth wrote:

> I'm aware of the issue where the reservation process will die if the VMware 
> SDK isn't installed even if the VM host can be controlled via SSH/vim-cmd.  I 
> will fix this for 2.3.  For now, in order to use the new VMware.pm module you 
> must have the vSphere SDK installed on the management node.
> 
> Patrick - did you attempt to run vim-cmd on the management node, VM host, or 
> are they the same box?  I'm not sure what localhost is referring to.
> 
> -Andy
> 
> On 1/4/2011 3:50 PM, James Patrick Sigmon wrote:
>> Hey Aaron,
>> 
>> Version 4.1 didn't work (SOAP Fault) but 4.0 worked just fine.  Thanks :)
>> 
>> I've gotten to another bump in the road.  This one I believe is a firewall 
>> issue.
>> 
>> |23184|20:20|new| ---- WARNING ----
>> |23184|20:20|new| 2011-01-04 
>> 15:20:06|23184|20:20|new|Linux.pm:execute(1224)|failed to run command on 
>> localhost: vmware-vim-cmd vmsvc/getallvms
>> |23184|20:20|new| ( 0) utils.pm, notify (line: 630)
>> |23184|20:20|new| (-1) Linux.pm, execute (line: 1224)
>> |23184|20:20|new| (-2) VIM_SSH.pm, _run_vim_cmd (line: 182)
>> |23184|20:20|new| (-3) VIM_SSH.pm, _get_vm_list (line: 219)
>> |23184|20:20|new| (-4) VIM_SSH.pm, get_registered_vms (line: 772)
>> |23184|20:20|new| (-5) VMware.pm, remove_existing_vms (line: 1321)
>> |23184|20:20|new| (-6) VMware.pm, load (line: 362)
>> 
>> When I run it manually I get:
>> 
>> Failed to connect: Cannot connect to host localhost: Connection refused
>> 
>> So I guess my question is, what port do I need to open for this to work?
>> 
>> Thanks,
>> 
>> Patrick
>> 
>> On Jan 3, 2011, at 11:07 AM, Aaron Peeler wrote:
>> 
>>> Hi Patrick,
>>> 
>>> Make sure you have the vsphere SDK for perl toolkit installed on the 
>>> management node.  Version 4.1 should work well. This will get you past the 
>>> module load failure.
>>> 
>>> Aaron
>>> 
>>> On 1/2/11 4:34 PM, James Patrick Sigmon wrote:
>>>> Hey guys,
>>>> 
>>>> I've been trying to make a reservation using the VCL 2.2 and I've been 
>>>> running into the following error:
>>>> 
>>>> "Can't locate VMware/VIRuntime.pm"
>>>> 
>>>> And if I look at up the vcld.log I notice this:
>>>> 
>>>> 2011-01-02 
>>>> 16:11:43|23951|2:2|deleted|VMware.pm:get_vmhost_api_object(1027)|attempting
>>>>  to load VMware control module: 
>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>> 
>>>> Now as far as I know, vSphere is used for ESX/ESXi, but in my VCL instance 
>>>> I'm using VMware server 2.  I assume this to be the reason why I'm getting 
>>>> this error.  My question is where and how can I fix this.
>>>> 
>>>> I have the vmhost profile set to : VMware Server 2.x - local storage.
>>>> 
>>>> Below is the full output for the error.
>>>> 
>>>> Thanks,
>>>> 
>>>> Patrick Sigmon
>>>> 
>>>> 2011-01-02 
>>>> 15:22:02|6857|3:3|reload|utils.pm:reservation_being_processed(9010)|computerloadlog
>>>>  'begin' entry does NOT exist for reservation 3
>>>> 2011-01-02 15:22:02|6857|3:3|reload|utils.pm:run_command(9082)|executed 
>>>> command: pgrep -fl 'vcld [0-9]+:3 ', pid: 12243, exit status: 1, output:
>>>> 2011-01-02 
>>>> 15:22:02|6857|3:3|reload|utils.pm:is_management_node_process_running(9259)|process
>>>>  is NOT running, identifier: 'vcld [0-9]+:3 '
>>>> 2011-01-02 
>>>> 15:22:02|6857|3:3|reload|utils.pm:reservation_being_processed(9031)|reservation
>>>>  is NOT currently being processed
>>>> 2011-01-02 15:22:02|6857|3:3|reload|vcld:main(277)|reservation 3 is NOT 
>>>> already being processed
>>>> 2011-01-02 
>>>> 15:22:03|6857|3:3|reload|utils.pm:get_request_info(4589)|standalone 
>>>> affiliation found: Local
>>>> 2011-01-02 15:22:03|6857|3:3|reload|utils.pm:get_request_info(4596)|found 
>>>> NULL uid setting standalone flag: vclreload, uid: NULL
>>>> 2011-01-02 15:22:03|6857|3:3|reload|vcld:main(282)|retrieved request 
>>>> information from database
>>>> 2011-01-02 
>>>> 15:22:03|6857|3:3|reload|DataStructure.pm:is_parent_reservation(943)|returning
>>>>  true: parent reservation ID for this request: 3
>>>> 2011-01-02 
>>>> 15:22:03|6857|3:3|reload|utils.pm:update_request_state(2049)|request 3 
>>>> state updated to: pending, laststate to: reload
>>>> 2011-01-02 15:22:03|6857|3:3|reload|utils.pm:insertloadlog(3933)|inserted 
>>>> computer=2, begin, beginning to process, state is reload
>>>> 2011-01-02 15:22:03|6857|3:3|reload|vcld:make_new_child(502)|request will 
>>>> be processed by new.pm
>>>> 2011-01-02 15:22:03|6857|3:3|reload|vcld:make_new_child(510)|loaded 
>>>> VCL::new module
>>>> 2011-01-02 15:22:03|12245|3:3|reload|vcld:make_new_child(583)|vcld 
>>>> environment variable set to 0 for this process
>>>> 2011-01-02 15:22:03|12245|3:3|reload|Module.pm:new(134)|constructor 
>>>> called, class=VCL::new
>>>> 2011-01-02 15:22:03|12245|3:3|reload|Module.pm:new(156)|VCL::new object 
>>>> created
>>>> 2011-01-02 15:22:03|6857|3:3|reload|vcld:make_new_child(567)|current 
>>>> number of forked kids: 1
>>>> 2011-01-02 15:22:04|12245|3:3|reload|State.pm:initialize(85)|obtained a 
>>>> database handle for this state process, stored as $ENV{dbh}
>>>> 2011-01-02 15:22:04|12245|3:3|reload|State.pm:check_image_os(817)|no 
>>>> corrections need to be made, not an imaging request, returning 1
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|DataStructure.pm:is_parent_reservation(943)|returning
>>>>  true: parent reservation ID for this request: 3
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|utils.pm:rename_vcld_process(7183)|reservation 
>>>> count: 1
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|utils.pm:rename_vcld_process(7202)|PARENTIMAGE: 1
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|utils.pm:rename_vcld_process(7203)|SUBIMAGE: 0
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|utils.pm:rename_vcld_process(7221)|renamed 
>>>> process to 'vcld 3:3 reload vmguest-1 vmwarelinux-CentOSBase-v0 vclreload'
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|DataStructure.pm:is_parent_reservation(943)|returning
>>>>  true: parent reservation ID for this request: 3
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|DataStructure.pm:is_parent_reservation(943)|returning
>>>>  true: parent reservation ID for this request: 3
>>>> 2011-01-02 15:22:04|12245|3:3|reload|State.pm:initialize(118)|attempting 
>>>> to load provisioning module: VCL::Module::Provisioning::VMware::VMware
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|State.pm:initialize(124)|VCL::Module::Provisioning::VMware::VMware
>>>>  module loaded
>>>> 2011-01-02 15:22:04|12245|3:3|reload|Module.pm:new(134)|constructor 
>>>> called, class=VCL::Module::Provisioning::VMware::VMware
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|Module.pm:new(156)|VCL::Module::Provisioning::VMware::VMware
>>>>  object created
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|DataStructure.pm:_initialize(594)|computer ID 
>>>> argument was specified, retrieving data for computer ID: 3
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|VMware.pm:get_vmhost_datastructure(923)|created 
>>>> DataStructure object for VM host: vcl
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|DataStructure.pm:_initialize(594)|computer ID 
>>>> argument was specified, retrieving data for computer ID: 3
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|VMware.pm:get_vmhost_datastructure(923)|created 
>>>> DataStructure object for VM host: vcl
>>>> 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|VMware.pm:get_vmhost_api_object(1027)|attempting 
>>>> to load VMware control module: 
>>>> VCL::Module::Provisioning::VMware::vSphere_SDK
>>>> 2011-01-02 15:22:04|12245|3:3|reload|utils.pm:mail(1247)|SUCCESS -- 
>>>> Sending mail To: 0, PROBLEM -- vcld
>>>> 
>>>> |12245|3:3|reload| ---- CRITICAL ----
>>>> |12245|3:3|reload| 2011-01-02 
>>>> 15:22:04|12245|3:3|reload|vcld:die_handler(663)|Can't locate 
>>>> VMware/VIRuntime.pm in @INC (@INC contains: /usr/local/vcl/bin/../../../.. 
>>>> /usr/local/vcl/bin/../.. /usr/local/vcl/bin/.. /usr/local/vcl/bin/../lib 
>>>> /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi 
>>>> /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl 
>>>> /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi 
>>>> /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl 
>>>> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) 
>>>> at /usr/local/vcl/bin/../lib/VCL/Module/Provisioning/VMware/vSphere_SDK.pm 
>>>> line 64.
>>>> |12245|3:3|reload| ( 0) utils.pm, notify (line: 630)
>>>> |12245|3:3|reload| (-1) vcld, die_handler (line: 663)
>>>> |12245|3:3|reload| (-2) vSphere_SDK.pm, BEGIN (line: 64)
>>>> |12245|3:3|reload| (-3) VIRuntime.pm, (eval) (line: 64)
>>>> |12245|3:3|reload| (-4) VIRuntime.pm, (eval) (line: 64)
>>>> |12245|3:3|reload| (-5) (eval 166), BEGIN (line: 2)
>>>> |12245|3:3|reload| (-6) VIRuntime.pm, (eval) (line: 64)
>>>> 
>>>> 2011-01-02 15:22:04|6857|vcld:REAPER(745)|VCL process exited for 
>>>> reservation 3, PID: 12245, signal: CHLD
>>>> 
>>> 
>>> 
>>> --
>>> 
>>> Aaron Peeler
>>> Program Manager
>>> Virtual Computing Lab
>>> NC State University
>>> aaron_pee...@ncsu.edu
>>> 919-513-4571
>>> 
>> 

Reply via email to