Seems like the vmx files were never created for that node. I browsed the
datastore and did not find any vmx files. I've been getting these errors
since yesterday and I'm not sure what could be causing it. Thanks

David DeMizio
*Academic Systems Coordinator*
Office of Information Technology
New College of Florida
Phone: 941-487-4222 | Fax: 941-487-4356
www.ncf.edu


On Wed, Dec 4, 2013 at 9:49 AM, David DeMizio <[email protected]> wrote:

> Hello,
>
> I'm not sure if it's coincidence but it  seems like since I created a new
> revision to one of the linux images that I  intermittently get the error
> below
>
> VM is still running after attempting to delete all existing matching VMs:
> vcl-n-001 (10.10.12.41)
> vmx file path: '/vmfs/volumes/vcl_workspace/vcl-n-001_13-v2/vcl
> -n-001_13-v2.vmx'
> ------------------------------------------------------------------------
> time: 2013-12-04 09:29:57
> caller: VMware.pm:remove_existing_vms(1625)
> ( 0) VMware.pm, remove_existing_vms (line: 1625)
> (-1) VMware.pm, load (line: 469)
> (-2) new.pm, reload_image (line: 671)
> (-3) new.pm, process (line: 291)
> (-4) vcld, make_new_child (line: 571)
> (-5) vcld, main (line: 350)
> ------------------------------------------------------------------------
> management node: vcl <http://vcl.network.ncf.edu/>
> reservation PID: 26442
> parent vcld PID: 19399
>
> request ID: 225
> reservation ID: 225
> request state/laststate: reload/reload
> request start time: 2013-12-04 09:28:35
> request end time: 2013-12-04 09:45:00
> for imaging: no
> log ID: none
>
> The log also shows some warnings. It seems like the reservation and OS
> type are not matching as indicated by the last two lines.
>
> |26442|225:225|reload| ---- WARNING ----
> |26442|225:225|reload| 2013-12-04 09:29:18|26442|225:225|reload|VMware
> .pm:remove_existing_vms(1622)|vcl-n-001 (10.10.12.41) is still responding
> to SSH after deleting deleting matching VMs, attempting to determine vmxfile 
> path
> |26442|225:225|reload| ( 0) VMware.pm, remove_existing_vms (line: 1622)
> |26442|225:225|reload| (-1) VMware.pm, load (line: 469)
> |26442|225:225|reload| (-2) new.pm, reload_image (line: 671)
> |26442|225:225|reload| (-3) new.pm, process (line: 291)
> |26442|225:225|reload| (-4) vcld, make_new_child (line: 571)
> |26442|225:225|reload| (-5) vcld, main (line: 350)
> 2013-12-04 09:29:18|26442|225:225|reload|OS.pm:get_os_type(2292)|Linux OS
> is currently installed on vcl-n-001, output:
> |26442|225:225|reload| Linux 
> centOS64.network.ncf.edu2.6.32-358.18.1.el6.x86_64 #1
> SMP Wed Aug 28 17:19:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> 2013-12-04 
> 09:29:18|26442|225:225|reload|VMware.pm:get_active_vmx_file_path(944)|OS
> type currently installed on vcl-n-001 does not match the OS type of the
> reservation image:
> |26442|225:225|reload| OS type installed on vcl-n-001: linux
> |26442|225:225|reload| reservation image OS type: windows
>
>
>
> |26442|225:225|reload| ---- CRITICAL ----
> |26442|225:225|reload| 2013-12-04 09:29:57|26442|225:225|reload|VMware
> .pm:remove_existing_vms(1625)|VM is still running after attempting to
> delete all existing matching VMs: vcl-n-001 (10.10.12.41)
> |26442|225:225|reload| vmx file path: '/vmfs/volumes/vcl_workspace/vcl
> -n-001_13-v2/vcl-n-001_13-v2.vmx'
> |26442|225:225|reload| ( 0) VMware.pm, remove_existing_vms (line: 1625)
> |26442|225:225|reload| (-1) VMware.pm, load (line: 469)
> |26442|225:225|reload| (-2) new.pm, reload_image (line: 671)
> |26442|225:225|reload| (-3) new.pm, process (line: 291)
> |26442|225:225|reload| (-4) vcld, make_new_child (line: 571)
> |26442|225:225|reload| (-5) vcld, main (line: 350)
>
>
>

Reply via email to