Symptoms
PACI container is not manageable trough Customer CP in POA. Stop and Start operations fail with error "Failed to stop/Failed to start"
Cause
From PACI-vm2vf.log:
<Vm2VfCallback>
); reqId=88850; corbaReqId=1113178.
2014-02-11 20:13:16,196 () INFO LoggingProxy [RequestProcessor-14347] - invoked: stop_ve_cb(
"192.168.139.12",
"Administrator",
<hidden>,
"<NAME>",
java.nio.DirectByteBuffer[pos=0 lim=32 cap=32]
); reqId=88850; corbaReqId=1113178.
.....
2014-02-11 20:13:20,624 (9bcae5d0-aae5-44dd-9066-e42f65869395) ERROR NativeVm2VfCode [Thread-2361296] - [88850:1113178] ERR open_vm_get_uuid2_pipeline(ve_action_cb_ex, start.c, 479): failure: PRL_ERR_VM_UUID_NOT_FOUND @[common/generic_sdk_cb.c][284][generic_sdk_cb][31449])
.....
PRL_ERR_VM_UUID_NOT_FOUND this error mean that Dispatcher can not find container "<NAME>"
On the HW node:
>prlctl list <NAME>
UUID STATUS IP_ADDR T NAME
Failed to get VM config: The virtual machine could not be found. The virtual machine is not registered in the virtual machine directory on this server. Contact your Parallels Server administrator for assistance.
Resolution
Restart Dispatcher to force it reinitialize containers and VMs located on the HW node:
Go to Services > Parallels Dispatcher Service > Restart
>prlctl list <NAME>
UUID STATUS IP_ADDR T NAME
{6f72e018-d3a9-4e00-9a7e-3b3c682bf219} running 10.127.190.192 CT <NAME>