"Killing oom-notifier process" but without OOM


John Wong
 

Hi

One of our NodeJS applications constantly crash with exit status 1.

I was reviewing the warden log on our DEA and I found this.

{"timestamp":1463013061.7575436,"message":"Killing oom-notifier
process","log_level":"debug","source":"Warden::Container::Features::MemLimit::OomNotifier","data":{},"thread_id":70306976232240,"fiber_id":70306988476180,"process_id":314,"file":"/var/vcap/data/packages/warden/88b0ad837f313990ce408e50cd904f7025983213.1-12d37c30c75c53ce5158f1b3d97cd1be85956f85/warden/lib/warden/container/features/mem_limit.rb","lineno":51,"method":"kill"}

Is this normal or does this indicate an OOM? If so, how is cf events' OOM
(we didn't see that entry) different from this?

Thanks.

John