- 13:02 GMT +0 27/01/2017 -

The issues in Phoenix are known, they are being caused by a solusvm related process that gathers ram info for the servers to display in solusvm.

Sadly despite having reported and escalated it a number of times a permanent fix does not seem to be available, I have again escalated this within solusvm and hope for a long term resolution.

The net effect of this is when soluvm fails to correctly gather the info from the VPS it continues to try every 5 minutes which results in thousands of processes per container until the containers fail to respond at all which in turn locks up the main OpenVZ functions used with vzctl across the entire node.

The node has to be rebooted to free off the unkillable locked processes which is being done now.

- 13:32 GMT +0 27/01/2017 -

The node has been rebooted, containers are starting now.


Friday, January 27, 2017

« Back