Symptoms
All VPS related tasks for a certain hardware node fail with error "307 : Message processing was terminated because timeout was reached waiting for a response".
For example:
Task name Update containers eid on HW node:<hostname_of_hw_node>
Last execution output 307 : Message processing was terminated because timeout was reached waiting for a response
Task name Create VPS w-123123-809
Last execution output 307 : Message processing was terminated because timeout was reached waiting for a response
Possible addditional symptom: when you open this hardware node in OA provider control panel and click on VPSs > Not registered VPSs screen hangs loading.
Cause
PVA Agent on hardware node does not respond correctly.
Resolution
Make sure there are no VPS Backup tasks running for the hardware node (task name "Create backup of VPS 'hostname_of_vps' from HN 'hostname_of_hw_node'") and restart PVA Agent on this Windows hardware node via command line:
net stop pvaagent
net start pvaagent
If it does not start after that, please review the instructions from the article #115821 to resolve this issue. In case PVA Agent version is higher than 6.0-2584 and already includes the fix for the PVA Agent startup problem, as described in the referenced article, it's possible that a misbehaving VPS prevents communication with PVA Agent vzaenvm
operator. Use the steps from this article to detect the stuck VPS and stop it:
vzctl stop CTID
After that complete the task and start the VPS again:
vzctl start CTID