Apache2 entered FATAL state, too many start retries too quickly

[jmarquez54]

I deployed ampache docker this week and everything worked perfectly.

After rebooting the system, ampache is not able to start again and returns the error :

2024-03-13 17:36:44,351 INFO spawned: 'apache2' with pid 132
2024-03-13 17:36:44,390 WARN exited: apache2 (exit status 0; not expected)
2024-03-13 17:36:45,391 INFO gave up: apache2 entered FATAL state, too many start retries too quickly

restarting the container or even the host, does not solve the problem. Only stopping the container and recreating it makes it work again.

I am very new to linux and docker and I am quite lost with this error. Any help would be great.

the container is running on a Ubuntu VM in Proxmox

[lachlan-00]

in the container you could run apachectl -DFOREGROUND to see if the server has any errors when starting.

the startup scripts are all in the bin folder https://github.com/ampache/ampache-docker/tree/master/data/bin

[vctls]

I ran into that issue after restarting my server.
Nuked and recreated the containers. That «fixed» the issue. For now.
I'll probably end up changing my setup to use separate containers as suggested in #123 anyway. Maybe drop apache entirely.

Edit: actually, just restarting the container is enough to make apache fail.

[lachlan-00]

i need more detail about it as i don't really get these problems often. i have about 30 ampache containers in various forms that all reboot okay for testing

[vctls]

Here's what the apache2 error log says:

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.20.0.3. Set the 'ServerName' directive globally to suppress this message
[Wed Nov 20 17:33:19.971250 2024] [core:warn] [pid 13:tid 13] AH00098: pid file /var/run/apache2/apache2.pid overwritten -- Unclean shutdown of previous Apache run?
[Wed Nov 20 17:33:19.975409 2024] [mpm_prefork:notice] [pid 13:tid 13] AH00163: Apache/2.4.62 (Debian) configured -- resuming normal operations
[Wed Nov 20 17:33:19.975444 2024] [core:notice] [pid 13:tid 13] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'

[lachlan-00]

AH00098: pid file /var/run/apache2/apache2.pid overwritten -- Unclean shutdown of previous Apache run?

okay so i'm assuming that means we need to clear any pid on startup which would explain why you're getting an error after restarting

[Responseless]

I've had the same issue multiple times too. Deleting and recreating the container from the stack fixes it. It's quite annoying...

[lachlan-00]

i've updated develop with an rm in the start scripts. need to check mariadb doesn't leave one as well. i'll check out the container now and then update the others

[lachlan-00]

seems okay, i'll add one in for mysql and then rebuild them all.

i killed in portainer and restarted. a new file was created

[lachlan-00]

i've killed mine a few times and can't recreate it, i'll see if i can pkill the docker service instead of just the container to be sure