izpbx docker container crashing after restart of the whole server

[flowersofpepper]

If the server restarts by itself the docker container crashes every 12 seconds and enters a restart loop. Can someone please help me how to solve this? Thank you

[ugoviti]

What distro and izPBX version are you using?

do you have tested other installations?

[flowersofpepper]

@ugoviti Initially, we deployed ixPBX version 20.16.19 on a Debian 12. However, we encountered issues, particularly after server restarts following module updates or SSL certificate renewals. To resolve the problem, we attempted various troubleshooting steps, including executing fwconsole reload, fwconsole restart, and restarting the Docker container running ixPBX. On some occasions, these actions resolved the issue, but when they didn't, we reverted to a previous backup that was functioning correctly.

Thinking that the problem might be related to compatibility between ixPBX and the Debian environment, we migrated to an Ubuntu server. Since making this change, we have not experienced any further crashes, and ixPBX has been operating reliably.

[marcosrohrig]

I'm facing the same error. I'm running on Ubuntu Server 24.4. The container starts, but after a few seconds, it restarts.

This is the log:
izpbx | Server ready
izpbx | 2025-05-15 09:56:26,941 INFO success: izpbx-watchdog_0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
izpbx | 2025-05-15 09:56:26,942 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
izpbx | 2025-05-15 09:56:26,942 INFO success: httpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
izpbx | 2025-05-15 09:56:26,942 INFO success: izpbx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
izpbx | 2025-05-15 09:56:26,943 INFO reaped unknown pid 1066 (exit status 0)
izpbx | 2025-05-15 09:56:30,948 INFO success: fail2ban entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
izpbx |
izpbx | In Start.class.php line 193:
izpbx |
izpbx | Unable to connect to Asterisk. Did it start?
izpbx |
izpbx |
izpbx | start [--pre] [--post] [--skipchown] [--] []...
izpbx |
izpbx | 2025-05-15 09:56:58,005 INFO exited: izpbx (exit status 1; not expected)
izpbx | 2025-05-15 09:56:58,011 INFO spawned: 'izpbx' with pid 1306
izpbx | 2025-05-15 09:56:58,012 WARN received SIGQUIT indicating exit request
izpbx | 2025-05-15 09:56:58,015 INFO waiting for izpbx-watchdog_0, cron, fail2ban, httpd, izpbx to die
izpbx | 2025-05-15 09:56:59,017 INFO success: izpbx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
izpbx | 2025-05-15 09:56:59,017 INFO reaped unknown pid 1390 (exit status 0)
izpbx | 2025-05-15 09:57:01,021 INFO waiting for izpbx-watchdog_0, cron, fail2ban, httpd, izpbx to die
izpbx-db | 2025-05-15 9:57:01 1277 [Warning] Aborted connection 1277 to db: 'asterisk' user: 'asterisk' host: '172.18.0.1' (Got an error reading communication packets)
izpbx | Terminated
izpbx | 2025-05-15 09:57:01,029 INFO reaped unknown pid 1403 (terminated by SIGTERM)
izpbx | 2025-05-15 09:57:01,029 INFO reaped unknown pid 1419 (terminated by SIGTERM)
izpbx | Running FreePBX shutdown...
izpbx |
izpbx | Running Asterisk pre from Core module
izpbx | Stopping Call Transfer Monitoring Service
izpbx | Core FastAGI Server is not running
izpbx | Shutting down Asterisk Gracefully. Will forcefully kill after 30 seconds.
izpbx | Press C to Cancel
izpbx | Press N to shut down NOW
izpbx | stty: 'standard input': Inappropriate ioctl for device
izpbx | stty: 'standard input': Inappropriate ioctl for device
izpbx | 2025-05-15 09:57:02,421 INFO reaped unknown pid 1498 (exit status 1)
izpbx | [>---------------------------] < 1 sec[>---------------------------] < 1 sec[>---------------------------] < 1 sec
izpbx |
izpbx | [---------------->-----------] < 1 secstty: 'standard input': Inappropriate ioctl for device
izpbx | 2025-05-15 09:57:02,438 INFO stopped: izpbx (exit status 0)
izpbx | 2025-05-15 09:57:02,538 INFO stopped: httpd (exit status 0)
izpbx | 2025-05-15 09:57:04,215 INFO stopped: fail2ban (exit status 0)
izpbx | 2025-05-15 09:57:04,215 INFO waiting for izpbx-watchdog_0, cron to die
izpbx | 2025-05-15 09:57:05,218 INFO stopped: cron (exit status 0)
izpbx | log_it: (CRON 903) INFO (Shutting down)
izpbx | 2025-05-15 09:57:05,219 INFO stopped: izpbx-watchdog_0 (terminated by SIGTERM)
izpbx exited with code 0

[flowersofpepper]

@marcosrohrig Try installing it on Ubuntu Server 22.04. It was giving us a lot of errors on all other versions.

[marcosrohrig]

@flowersofpepper Thanks for the tip. I tried it on Ubuntu 22.04 and it worked. The service uses the network in host mode. Do you think there has been any significant change in Ubuntu's networking from 22.04 to 24.04? I can't think of another cause.

[flowersofpepper]

@marcosrohrig Yes, your suspicion is likely correct. Ubuntu Server 24.04 introduced several low-level system changes that could be causing issues with how ixPBX interacts with the Docker environment, especially in host network mode.