Any time I restart the container portainer log give me this

[DylanHP]

The container is on a Ubuntu 21.10 docker installation As I wrote in the title of the issue any time I restart the container the log give me this:

Welcome to Debian GNU/Linux 10 (buster)!

[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Reached target Slices.
[  OK  ] Listening on Journal Socket.
[  OK  ] Reached target Local File Systems.
[  OK  ] Reached target Network is Online.
[  OK  ] Reached target Swap.
[  OK  ] Started Dispatch Password...s to Console Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Created slice system-postgresql.slice.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Sockets.
         Starting Journal Service...
         Starting Create System Users...
[  OK  ] Started Create System Users.
[  OK  ] Started Journal Service.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timers.
[  OK  ] Reached target Basic System.
         Starting 3CX Event Notification Manager...
         Starting 3CX PhoneSystem Firewall...
         Starting 3CX PhoneSystem Media Server...
         Starting PostgreSQL Cluster 11-main...
         Starting A high performan...and a reverse proxy server...
         Starting Flush Journal to Persistent Storage...
[FAILED] Failed to start 3CX PhoneSystem Firewall.
See 'systemctl status 3CXFirewall.service' for details.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started 3CX PhoneSystem Media Server.
[  OK  ] Started A high performanc...r and a reverse proxy server.
[FAILED] Failed to start 3CX Event Notification Manager.
See 'systemctl status 3CXEventNotificationManager.service' for details.
[  OK  ] Started PostgreSQL Cluster 11-main.
         Starting PostgreSQL RDBMS...
[  OK  ] Started PostgreSQL RDBMS.
         Starting 3CX PhoneSystem Configuration Service...
[  OK  ] Started 3CX PhoneSystem Configuration Service.
         Starting 3CX PhoneSystem 01 Audio Provider Server...
         Starting 3CX PhoneSystem 01 Management Console...
         Starting 3CX PhoneSystem 01 SIP Server...
         Starting 3CX PhoneSystem 01 System Server...
[  OK  ] Started 3CX PhoneSystem 01 Audio Provider Server.
[  OK  ] Started 3CX PhoneSystem 01 SIP Server.
         Starting 3CX PhoneSystem 01 CallFlow Server...
         Starting 3CX PhoneSystem 01 IVR Server...
         Starting 3CX PhoneSystem 01 Queue Manager Server...
[  OK  ] Started 3CX PhoneSystem 01 IVR Server.
[FAILED] Failed to start 3CX PhoneSystem 01 System Server.
See 'systemctl status 3CXSystemService01.service' for details.
[FAILED] Failed to start 3CX PhoneSystem 01 CallFlow Server.
See 'systemctl status 3CXCallFlow01.service' for details.
[FAILED] Failed to start 3CX PhoneSystem 01 Queue Manager Server.
See 'systemctl status 3CXQueueManager01.service' for details.
[FAILED] Failed to start 3CX PhoneSystem 01 Management Console.
See 'systemctl status 3CXPhoneSystemMC01.service' for details.
[DEPEND] Dependency failed for 3CX Gateway Service.
[  OK  ] Reached target Multi-User System.</log>

I don't know why. also the login page gives me this error that translate to english as server error.

I also add journalctl -xe details:

-- Logs begin at Sun 2022-02-27 18:29:01 CET, end at Sun 2022-02-27 18:29:01 CET. --
Feb 27 18:29:01 1f83ca7dea18 systemd-journald[25]: Journal started
-- Subject: The journal has been started
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The system journal process has started up, opened the journal
-- files for writing and is now ready to process requests.
Feb 27 18:29:01 1f83ca7dea18 systemd-journald[25]: Runtime journal (/run/log/journal/88544b92092430bc5d3fbbffc12a2f04) is 8.0M, max 190.3M, 182.3M free.
-- Subject: Disk space used by the journal
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Runtime journal (/run/log/journal/88544b92092430bc5d3fbbffc12a2f04) is currently using 8.0M.
-- Maximum allowed usage is set to 190.3M.
-- Leaving at least 285.5M free (of currently available 1.8G of disk space).
-- Enforced usage limit is thus 190.3M, of which 182.3M are still available.
-- 
-- The limits controlling how much disk space is used by the journal may
-- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
-- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
-- /etc/systemd/journald.conf. See journald.conf(5) for details.
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:3:1-22: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 systemd-journald[25]: Runtime journal (/run/log/journal/88544b92092430bc5d3fbbffc12a2f04) is 8.0M, max 190.3M, 182.3M free.
-- Subject: Disk space used by the journal
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Runtime journal (/run/log/journal/88544b92092430bc5d3fbbffc12a2f04) is currently using 8.0M.
-- Maximum allowed usage is set to 190.3M.
-- Leaving at least 285.5M free (of currently available 1.8G of disk space).
-- Enforced usage limit is thus 190.3M, of which 182.3M are still available.
-- 
-- The limits controlling how much disk space is used by the journal may
-- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
-- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
-- /etc/systemd/journald.conf. See journald.conf(5) for details.
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add table inet filter
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:4:1-28: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add chain inet filter input
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:5:1-34: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add chain inet filter phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:6:1-47: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: insert rule inet filter input jump phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:7:1-36: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: flush chain inet filter phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:9:1-20: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add table ip filter
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:10:1-26: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add chain ip filter INPUT
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:11:1-32: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add chain ip filter phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:12:1-45: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: insert rule ip filter INPUT jump phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:13:1-34: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: flush chain ip filter phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:15:1-21: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add table ip6 filter
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:16:1-27: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add chain ip6 filter INPUT
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:17:1-33: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: add chain ip6 filter phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:18:1-46: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: insert rule ip6 filter INPUT jump phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:19:1-35: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: flush chain ip6 filter phonesystem
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:21:1-2: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: table inet filter {
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:22:15-25: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:         chain phonesystem {
Feb 27 18:29:01 1f83ca7dea18 nft[28]:               ^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:24:27-59: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 tcp dport { 5000,5001,5060,5061,5090,5062 } ct state new counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:25:27-50: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 udp dport { 5060,5090,7000-10999 } counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                           ^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:23:17-50: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ip daddr 224.0.1.75 counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:24:17-87: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 tcp dport { 5000,5001,5060,5061,5090,5062 } ct state new counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:25:17-65: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 udp dport { 5060,5090,7000-10999 } counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:29:1-2: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: table ip filter {
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:30:15-25: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:         chain phonesystem {
Feb 27 18:29:01 1f83ca7dea18 nft[28]:               ^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:32:27-59: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 tcp dport { 5000,5001,5060,5061,5090,5062 } ct state new counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:33:27-50: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 udp dport { 5060,5090,7000-10999 } counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                           ^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:31:17-50: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ip daddr 224.0.1.75 counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:32:17-87: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 tcp dport { 5000,5001,5060,5061,5090,5062 } ct state new counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:33:17-65: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 udp dport { 5060,5090,7000-10999 } counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:37:1-2: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]: table ip6 filter {
Feb 27 18:29:01 1f83ca7dea18 nft[28]: ^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:38:15-25: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:         chain phonesystem {
Feb 27 18:29:01 1f83ca7dea18 nft[28]:               ^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:39:27-59: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 tcp dport { 5000,5001,5060,5061,5090,5062 } ct state new counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:40:27-50: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 udp dport { 5060,5090,7000-10999 } counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                           ^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:39:17-87: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 tcp dport { 5000,5001,5060,5061,5090,5062 } ct state new counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nft[28]: /var/lib/3cxpbx/Bin/nftables.conf:40:17-65: Error: Could not process rule: Operation not permitted
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 udp dport { 5060,5090,7000-10999 } counter accept;
Feb 27 18:29:01 1f83ca7dea18 nft[28]:                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 27 18:29:01 1f83ca7dea18 nginx[31]: nginx: [warn] duplicate network "::0/0", value: "0", old value: "1" in /etc/nginx/sites-enabled/3cxpbx:14
Feb 27 18:29:01 1f83ca7dea18 postgresql@11-main[30]: Removed stale pid file.
Feb 27 18:29:01 1f83ca7dea18 nginx[68]: nginx: [warn] duplicate network "::0/0", value: "0", old value: "1" in /etc/nginx/sites-enabled/3cxpbx:14

[sinegar]

Firewall errors are normal. However, there seems to be other issues.

Would you check the logs in /var/lib/3cxpbx/Data/Logs (you probably don’t want to share these as they contain things like you license /IP etc.) ?

How did you start the container (compose vs run) and what where the parameters? Did it ever start successfully?

[DylanHP]

I see those inside /var/lib/3cxpbx/Data/Logs

root@1f83ca7dea18:/var/lib/3cxpbx/Data/Logs# ls
3CXMediaServer.2022-02-27.182542.log  3CXMediaServer.2022-02-28.000125.log  3CXTunnel.2022-02-27.185859.log  Backup                   PbxWebConfigTool.log
3CXMediaServer.2022-02-27.185859.log  3CXTunnel.2022-02-27.182542.log       3CXTunnel.2022-02-28.000125.log  CloudServiceWatcher.log

which one do you need?

[sinegar]

Actually, I have the same issue… will look into it in my system.

[sinegar]

Would you confirm that you also have a /var/lib/3cxpbx/core.minidump file?

(restore from backup brought my system back - now I will need to reproduce)

[sinegar]

The problem is that a reboot wipes the /run/phonesystem folder with /run (which it should). However, 3cx doesn’t seem to recreate it on startup if it’s missing…

[sinegar]

ghcr.io/izer-xyz/3cx:test is available with a fix

[sinegar]

and release 18.0.2.314-68 with tags latest, 18.0.2.314

[DylanHP]

Sorry for the late answer but thanks a lot it worked