OpenVZ Forum - RDF feed
type: channel
items: Can OOM be the cause of container stoppage?

Can OOM be the cause of container stoppage?
type: item
description: One of the containers was stopped and I'm trying to find out what caused that. I couldn't find any information on node or in container how it was stopped. But there is one thing that makes me think that it was stopped automatically somehow(some quota mechanisms in vzkernel or something like that): Right before container was stopped there was tons of messages that apache was killed in that container: ./messages:Nov 16 12:56:53 vps kernel: [32346656.250399] Out of memory in UB 999: OOM killed process 283507 (apache2) score 0 vm:344684kB, rss:16876kB, swap:25940kB ./messages:Nov 16 12:56:55 vps kernel: [32346658.125520] Out of memory in UB 999: OOM killed process 283525 (apache2) score 0 vm:344948kB, rss:16276kB, swap:26992kB ./vzctl.log:2015-11-16T12:56:55+0300 vzeventd : CT 999 : CTID = 999, event = ve-stop (len=7) ./vzctl.log:2015-11-16T12:56:55+0300 vzeventd : CT 999 : Running stop event script ./vzctl.log:2015-11-16T12:56:55+0300 vzeventd : CT 999 : Forked child 283926 for stop event ./vzctl.log:2015-11-16T12:56:55+0300 vzeventd : CT 999 : Running: /usr/libexec/vzctl/scripts/vzevent-stop Could be that this two things are related?
creator: KingOfFools
date: 2015-11-17T10:34:29-00:00