Search Engine: Elastic

Article ID: 127517, created on Nov 22, 2015, last review on Nov 22, 2015

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5
  • Operations Automation 5.4
  • Operations Automation 5.3

Symptoms

A "Stop VPS" task in POA fails in the following way:

 Task ID    XXXXXXXX
 Task name Stop VPS YYY
 Task description Task that stops VPS YYY
 Subscription ID    XXXXXXXXX
 Queue name vps_operations_YYY
 Method name taskStopVPS
 Execution status Failed
 Start not earlier than Nov-27-2013 11:37
 Finished Nov-27-2013 12:07
 Output 307 : Message processing was terminated because timeout was reached waiting for a response

Cause

On the Virtuozzo Hardware node the VPS is still in "stopping" state, you may want to check the VPS/Hardware node performance

Resolution

Wait till the VPS is stopped on the Hardware node, then rerun the task. If the tasks fails with:

1027 : Container is already stopped :
ERROR:Container YYYY is not started

Start the container on Hardware node using:

# vzctl start YYYY

Wait until it is started, then rerun the task.

a8cdca46e4357a6e38fded820770e272 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 5b048d9bddf8048a00aba7e0bdadef37 ac82ce33439a9c1feec4ff4f2f638899 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF