Search Engine: Elastic

Article ID: 128508, created on Mar 6, 2016, last review on Mar 6, 2016

  • Applies to:
  • Operations Automation 6.0


A container state has been changed from RUNNING to MOUNTED as a result of either a direct shutdown from inside of the container or CT init process killed by OOM killer.

However, the state is not reflected in CCP and subsequent VE stop/restart operations fail.

In /var/log/IM/paci-snmp.log the following message can be obtained:

2016-02-20 15:30:11,382 (23f434f4-88f2-485f-bc62-55b2c031418c) TRACE SnmpManager [Shared executor thread #1 @1] - State discrepancy STARTED != STOPPED for VE 1000001.test has been ignored as 6653556764220510731 <= 6653556764221931990


SNMP agent is down on the target Virtuozzo hardware node:

[root@vz ~]#  service snmpd status
snmpd is stopped

Backwards VE state monitoring is handled by paciagent SNMP module on the hardware node, installed with PACI-agent RPM.


Make sure SNMP agent is up and running and configured for automatic start-up:

# service snmpd start
# chkconfig snmpd on

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF