Is possible to disable OOM killer in dockers?



  • Hi, i am trying to find a way to disable the OOM killer, because is stupid if a server to touch/reach to the ram limit, to be killed, i know that devs are working on a new version with optional docker option, since i run a networking with 500 players and randomly my server get easy killed every day (caused by docker implementation)
    I have find something in https://github.com/docker/docker/issues/12528
    But i don't know how to act with pufferpanel/scales/dockers.... somesone can help?
    i am sure that is the killer i just checked the log...
    http://hastebin.com/viwijirime.vhdl

    HuKeping created this issue in docker/docker

    closed New Feature: disable oom killer #12528



  • The issue in the end there is that docker is still going to be used, and since it seems to be the actual cause, we don't have a way to resolve that. The only thing I can think of doing is manually setting the RAM that the java heap can use to be less than what the docker container has, maybe that will help something.
    i.e set the java Xmx to be 75% of how much you said the server would be.



  • also with dockers, my sql is a lot stressed, i have like 150% 100% mysql usage, i am gonna to reinstall puffer panel and dockers and keep the old version for now that was working great



  • That seems a bit odd that sql is dying cpuwise. have you looked at logs to insure that sql is not being overloaded by queries and that the cpu/io limits are acceptable?



  • which log i have to look?



  • sql's logs



  • i got only this on this morning start:
    160104 11:43:42 [Note] /usr/sbin/mysqld: Normal shutdown

    160104 11:43:42 [Note] Event Scheduler: Purging the queue. 0 events
    160104 11:43:44 InnoDB: Starting shutdown...
    160104 11:43:46 InnoDB: Shutdown completed; log sequence number 1988576510
    160104 11:43:46 [Note] /usr/sbin/mysqld: Shutdown complete

    160104 11:46:09 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
    160104 11:46:09 [Note] Plugin 'FEDERATED' is disabled.
    160104 11:46:09 InnoDB: The InnoDB memory heap is disabled
    160104 11:46:09 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    160104 11:46:09 InnoDB: Compressed tables use zlib 1.2.8
    160104 11:46:09 InnoDB: Using Linux native AIO
    160104 11:46:09 InnoDB: Initializing buffer pool, size = 128.0M
    160104 11:46:09 InnoDB: Completed initialization of buffer pool
    160104 11:46:09 InnoDB: highest supported file format is Barracuda.
    160104 11:46:09 InnoDB: Waiting for the background threads to start
    160104 11:46:10 InnoDB: 5.5.46 started; log sequence number 1988576510
    160104 11:46:10 [Note] Server hostname (bind-address): '172.17.0.1'; port: 3306
    160104 11:46:10 [Note] - '172.17.0.1' resolves to '172.17.0.1';
    160104 11:46:10 [Note] Server socket created on IP: '172.17.0.1'.
    160104 11:46:10 [Note] Event Scheduler: Loaded 0 events
    160104 11:46:10 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.5.46-0ubuntu0.14.04.2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
    160104 11:48:00 [Warning] IP address '172.17.0.2' could not be resolved: Name or service not known
    160104 11:48:11 [Warning] IP address '172.17.0.3' could not be resolved: Name or service not known
    160104 11:48:16 [Warning] IP address '172.17.0.4' could not be resolved: Name or service not known
    160104 11:48:24 [Warning] IP address '172.17.0.5' could not be resolved: Name or service not known
    160104 11:48:32 [Warning] IP address '172.17.0.6' could not be resolved: Name or service not known
    160104 11:48:45 [Warning] IP address '172.17.0.8' could not be resolved: Name or service not known
    160104 11:48:53 [Warning] IP address '172.17.0.9' could not be resolved: Name or service not known
    160104 11:49:09 [Warning] IP address '172.17.0.11' could not be resolved: Name or service not known
    160104 11:49:46 [Warning] IP address '172.17.0.14' could not be resolved: Name or service not known
    160104 11:50:11 [Warning] IP address '172.17.0.15' could not be resolved: Name or service not known
    160104 11:50:22 [Warning] IP address '172.17.0.16' could not be resolved: Name or service not known
    160104 11:50:37 [Warning] IP address '172.17.0.17' could not be resolved: Name or service not known
    160104 11:50:45 [Warning] IP address '172.17.0.18' could not be resolved: Name or service not known
    160104 12:04:35 [Warning] IP address '172.17.0.23' could not be resolved: Name or service not known
    160104 12:04:51 [Warning] IP address '172.17.0.24' could not be resolved: Name or service not known
    160104 13:46:56 [Warning] IP address '172.17.0.22' could not be resolved: Name or service not known



  • Hmm, nothing really concerning there. I would not be sure how docker would be causing that problem.



  • We have released a new version of PufferPanel and Scales with an improved installation process and many bug fixes. Please try the latest version and see if it fixes your issues.

    I’m marking this question as solved since there has been a long period of inactivity on it. If you are still experiencing issues, please create a new question. Thanks!


Log in to reply
 

Looks like your connection to PufferPanel Community was lost, please wait while we try to reconnect.