This container won't start after exhausting its memory. There are no relevant or helpful messages in dmesg or vzctl.log as well. Standard troubleshooting such as disabling PPP etc has not helped.
2017-07-06T23:33:29-0400 vzctl : CT 888171 : Locked by: pid 166029, cmdline vzctl start 888171
2017-07-06T23:33:29-0400 vzctl : CT 888171 : Container already locked
2017-07-06T23:33:29-0400 vzctl : CT 888171 : Container was stopped
2017-07-06T23:33:29-0400 vzctl : CT 888171 : Container is unmounted
2017-07-06T23:33:39-0400 vzctl : CT 888171 : Starting container...
2017-07-06T23:33:39-0400 vzctl : CT 888171 : Container is mounted
2017-07-06T23:33:39-0400 vzctl : CT 888171 : Adding IP address(es): 103.25.61.245
2017-07-06T23:33:40-0400 vzctl : CT 888171 : Setting CPU units: 1000
2017-07-06T23:33:40-0400 vzctl : CT 888171 : Setting devices
2017-07-06T23:33:40-0400 vzctl : CT 888171 : Container start failed (try to check kernel messages, e.g. "dmesg | tail")
2017-07-06T23:33:40-0400 vzctl : CT 888171 : Killing container ...
2017-07-06T23:33:42-0400 vzctl : CT 888171 : Locked by: pid 166638, cmdline vzctl start 888171
2017-07-06T23:33:42-0400 vzctl : CT 888171 : Container already locked
2017-07-06T23:33:42-0400 vzctl : CT 888171 : Container was stopped
2017-07-06T23:33:42-0400 vzctl : CT 888171 : Container is unmounted
openvz, container, kernel, dmesg, pid, cmdline, vzctl, exhausting, relevant, troubleshooting, disabling, ppp, etc, ct, unmounted, mounted, adding, ip, es, cpu, devices, quot,