• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Docker containers crash randomly any few days

devnull

New Pleskian
Hey guys,

I have an issue with the Docker feature on Ubuntu Ubuntu 20.04.5 LTS. I have automatic updated enabled so I always use the latest Plesk version.

Every few days my Docker containers crash. Sometimes it's a network related error (I cant reproduce this right now) and sometimes its the following error:
Fehler: {"message":"driver failed programming external connectivity on endpoint mongodb (...): (iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 27017 -j DNAT --to-destination 172.17.0.2:27017 ! -i docker0: iptables: Memory allocation problem.\n (exit status 1))"}

I have 16GB ram and the ram is at very low usage all time. I have just a backup task running at night which caches the whole ram (dont know why this is happening). So there is enough RAM for the Docker containers.

To restart the containers I have to restart the whole server! Please tell me how to fix this issue in Plesk. I cant use Plesk anymore if this stuff doesn't work.

Unbenannt.JPG
 
Sorry to see that you did not get any responses so far. Are you really on Plesk Onyx as this has been posted in that forum? Or should the thread be moved to the Obsidian forum?

The error message says "Memory allocation problem". Then there is the information "I have just a backup task running at night which caches the whole ram". And we already know that every night the Docker container crashes for insufficient RAM. Your conclusion from that is: "there is enough RAM for the Docker containers."

Maybe the conclusion is not right?
 
Hey Peter,

thank your for your answer!

I have invested another few hours in research and found out that it wasn't related to the actual memory but to the allowed number of numiptent. It is limited to 2000 on my VPS and I had to much fail2ban entries and reached that number fast.

I have reset my fail2ban and shortened the ban duration a bit (I had a few weeks for sshd).

Seems to work now.
 
Back
Top