Dockerized MySQL eating RAM for systemd-coredump

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • davide445
    Member
    • Nov 2020
    • 81

    Dockerized MySQL eating RAM for systemd-coredump

    Installed EspoCRM using official Docker image, on Ubuntu Server with Docker Engine and Docker Composer, using Webmin for remote admin.
    Was not installing updates at the beginning, installed after EspoCRM. The updates required the system to restart, and after this I found this process

    Owner: systemd-coredump
    Command: mysqld --default-authentication-plugin=mysql_native_password

    eating 2.65GB RAM on my PC with 4GB RAM.
    Trying to reboot the system didn't solve the problem.

    Using Webmin I got these info:
    Parent process: containerd-shim -namespace mob
    Command: containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/4bc1164209cf096f46b6215ef223563b83b1b35e84a8f8e208 af6adea585f1c9 -address /run/containerd/containerd.sock -containerd-binary /usr/bin/containerd -runtime-root /var/run/docker/runtime-runc
    File and connections: Files and connections.txt

    The process is running since this morning, want to know if there might be something related to the docker image configuration or need to check anything else.
  • Maximus
    Senior Member
    • Nov 2018
    • 2731

    #2
    Hi,
    I haven't encountered with such RAM overloading issue. If it will work all the time, you can try to run a container with a disabled core dump process. Check this https://stackoverflow.com/questions/...nswer-59611557.

    Comment

    Working...