Container state change on the node does not update the state in IM
Modified on: Fri, 17 Nov 2023 12:08 PM2020-01-22
Symptoms
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
Cause
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.
Resolution
Make sure SNMP agent is up and running and configured for automatic start-up:
# service snmpd start
# chkconfig snmpd on