Cannot start 3CXPhoneSystem - segfault

Status
Not open for further replies.

yetopen

Customer
Joined
Jul 18, 2019
Messages
110
Reaction score
14
Hi.
Today I wasn't able to use my 3CX app, so I logged into the console and found CallFlow server stopped. It wouldn't start so I tried upgrading, maybe it was a fixed bug... Now I have 16.0.5.612 (was 16.0.5.611 before) and not even 3CXPhoneSystem will start!

```
May 11 14:40:56 tel systemd[1]: Starting 3CX PhoneSystem 01 SIP Server...
May 11 14:40:57 tel kernel: [ 418.304025] 3CXPhoneSystem[1998]: segfault at 0 ip 000055f6470d9d83 sp 00007ffea273c2d0 error 4 in 3CXPhoneSystem[55f646f6a000+460000]
May 11 14:40:57 tel systemd[1]: 3CXPhoneSystem01.service: Main process exited, code=dumped, status=11/SEGV
May 11 14:40:57 tel systemd[1]: Failed to start 3CX PhoneSystem 01 SIP Server.
May 11 14:40:57 tel systemd[1]: 3CXPhoneSystem01.service: Unit entered failed state.
May 11 14:40:57 tel systemd[1]: 3CXPhoneSystem01.service: Failed with result 'core-dump'.
```

I didn't change anything recently. The only change was the trial Pro which expired over the weekend and it's now a Standard.

Host is a Debian 9.12. I tried purging and restoring the backup but it's still crashing.
 
Last edited:
Callflow requires Pro or Enterprise license

Can you remove the CallFlow settings via the management console
 
I found the culprit: I had installed OpenVPN client to link the remote cloud server to the office net. As soon as the VPN starts 3CX crashes:

Code:
May 11 15:23:17 tel ovpn-grandi[4562]: TUN/TAP device tun0 opened
May 11 15:23:17 tel ovpn-grandi[4562]: do_ifconfig, tt->did_ifconfig_ipv6_setup=0
May 11 15:23:17 tel ovpn-grandi[4562]: /sbin/ip link set dev tun0 up mtu 1500
May 11 15:23:17 tel ovpn-grandi[4562]: /sbin/ip addr add dev tun0 local 192.168.15.14 peer 192.168.15.13
May 11 15:23:17 tel ovpn-grandi[4562]: Initialization Sequence Completed
May 11 15:23:22 tel kernel: [ 1617.737750] 3CXPhoneSystem[4246]: segfault at 0 ip 0000564e00732d83 sp 00007fd5fdbdc070 error 4 in 3CXPhoneSystem[564e005c3000+460000]
May 11 15:23:22 tel systemd[1]: 3CXPhoneSystem01.service: Main process exited, code=killed, status=11/SEGV
May 11 15:23:22 tel systemd[1]: 3CXPhoneSystem01.service: Unit entered failed state.
May 11 15:23:22 tel systemd[1]: 3CXPhoneSystem01.service: Failed with result 'signal'.

License Standard Annual, version 16.0.612
 
  • Like
Reactions: JohnS_3CX
So is there any workaround to avoid sefgault when OpenVPN is enabled? Thanks
 
OpenVPN is not supported for running on the PBX.

However, if the PBX is not the endpoint, you should be able to have a VPN. Perhaps another machine can take care of the VPN part, acting as a switch/router, to which the PBX will eventually connect to.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,948
Messages
589,880
Members
164,841
Latest member
erre