0

I have the following docker configuration for Mautic (A PHP based CRM):

x-mautic-volumes: &mautic-volumes - ./mautic/config:/var/www/html/config:z - ./mautic/logs:/var/www/html/var/logs:z - ./mautic/media/files:/var/www/html/docroot/media/files:z - ./mautic/media/images:/var/www/html/docroot/media/images:z - ./mautic/themes/leeway_newsletter:/var/www/html/docroot/themes/leeway_newsletter:z - ./mautic/themes/leeway_responsive:/var/www/html/docroot/themes/leeway_responsive:z - ./session.ini:/usr/local/etc/php/conf.d/session.ini:z - ./cron:/opt/mautic/cron:z - mautic-docroot:/var/www/html/docroot:z - mautic-vendor:/var/www/html/vendor:z services: nginx: image: nginx volumes: - ./nginx.conf:/etc/nginx/conf.d/default.conf - mautic-docroot:/var/www/html/docroot:z - ./mautic/media/files:/var/www/html/docroot/media/files:z - ./mautic/media/images:/var/www/html/docroot/media/images:z - ./.well-known:/var/www/html/docroot/.well-known depends_on: - web ports: - "127.0.0.1:8002:80" networks: - default restart: always web: image: my_mautic:5.2.1 build: . volumes: *mautic-volumes env_file: - .mautic_env healthcheck: test: cgi-fcgi -bind -connect 127.0.0.1:9000 start_period: 5s interval: 5s timeout: 5s retries: 100 networks: - default restart: always cron: image: my_mautic:5.2.1 build: . volumes: *mautic-volumes environment: - DOCKER_MAUTIC_ROLE=mautic_cron env_file: - .mautic_env depends_on: web: condition: service_healthy networks: - default restart: always volumes: mautic-docroot: name: mautic-5.2.1 mautic-vendor: name: mautic-5.2.1-vendor networks: default: name: ${COMPOSE_PROJECT_NAME}-docker

This application is accessed through an NginX that takes care of SSL and forwards traffic to both this docker container and a regular WordPress hosted directly on the server using php8.2-fpm.

I have my servers on DigitalOcean droplets (1 GB Ram, 1vCPU, 25GB disk).

The app is currently running just fine on an Ubuntu 23.10 server.

I tried to put together a new server using Ubuntu 24.04 and, using the exact same configuration, after running for about 20 minutes, the CPU usage will go to 100% and stay there until I manually kill the in-docker php-fpm process.

I tried installing docker from the official sources, re-install the whole thing from scratch to make sure I wasn't using old volumes, explicitly limited resources for the web container but I always end up in the same place.

Any idea?

Thanks!

Improve this question
3
  • 1
    when you say: on ubuntu24 the CPU goes up 100% after 20min, did you check the logs and process list, what the system is doing (swapping, error logs)? And what docker version you're using on 23.10 in comparison to 24.04? Does the health check still says running? Commented Jan 22 at 9:37
  • I got the 100% cpu from htop. I still need to dig into the logs a bit deeper to see if I get any clue. Docker version is 24.0.5 on Ubuntu 23.10, on 24.04 I couldn't get one that old Commented Jan 22 at 15:20
  • @TRW on 23.10 I have docker 24.0.5, on 24.04 I have 27.5.1. The healtcheck is not reporting any problems (At least, I'm not seeing anything). Also, on the logs I can't see anything significant. I noticed that the system crashes a few minutes after traffic is sent to the server (And it's not a particularly heavy load) Commented Jan 24 at 9:24

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.