Toggle sidebar Toggle sidebar

3CX PhoneSystem 01 SIP Server crashing

Status
Not open for further replies.

AS19

Free User
Joined
Jul 23, 2019
Messages
28
Reaction score
1
Hi,

For the past few days, the 3CX PhoneSystem 01 SIP Server service is crashing on my debian 16.0.676 PBX.

Can anyone assist me in figureing out why this service keeps stopping?

The lines I think are relevant from the syslog follow:

Oct 9 08:55:01 3cx CRON[25816]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Oct 9 08:55:56 3cx kernel: [495315.889285] 3CXPhoneSystem[11154]: segfault at 1160 ip 00007f81e2b8e7a0 sp 00007f81c69cd1f8 error 4 in libresip-1.10.so[7f81e2a20000+24d000]
Oct 9 08:55:57 3cx systemd[1]: 3CXPhoneSystem01.service: Main process exited, code=killed, status=11/SEGV
Oct 9 08:55:57 3cx systemd[1]: 3CXPhoneSystem01.service: Unit entered failed state.
Oct 9 08:55:57 3cx systemd[1]: 3CXPhoneSystem01.service: Failed with result 'signal'.


The full syslog is attached
 

Attachments

Hi , can you provide PBX hardware ressources? most often service failure is due to lack of memory or space disk
 
I dont think its a resource issue see the following and the attached screen shot. Disk isnt full and ive got plenty of resources.


I installed from the debian cd, but I just upgraded to v16 a few days ago.


root@3cx:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 2.0G 0 2.0G 0% /dev
tmpfs 396M 16M 380M 4% /run
/dev/sda1 153G 2.6G 143G 2% /
tmpfs 2.0G 12K 2.0G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
tmpfs 396M 0 396M 0% /run/user/0
root@3cx:~#


I also have 4gb of swap configured


root@3cx:/var/lib/3cxpbx# cat /proc/swaps
Filename Type Size Used Priority
/dev/sda5 partition 4192252 0 -1


Please see the screen shot of an htop of the VM to see the cpu / ram and utilization.
 

Attachments

  • htop.png
    htop.png
    139.3 KB · Views: 12
Last edited:
Please provide the additional infor as per my link above so we know how you are set up
 
  • 3CX Version, Standard Annual16.0.676
  • Server OS, Debian 9
  • Is the 3CX Server Hosted and where? Local VM, hypervisor VMware ESXi, 6.7.0, 14320388
  • IP Phone Make/Model/Firmware: Various granstream handsets
  • Provisioning Method: Local / VPN / STUN / SBC: Local
  • Trunk Provider or Gateway Make/Model: Patton 4114 & Grandstream GXW4104
  • Has the Firewall Checker passed: YES
  • Are custom Phone Templates being used: NO
 
Last edited:
Hi @AS19

You might have to open a ticket with support for this one and provide logs and possibly a memory dump to them (they will let you know exactly what is required).
 
  • Like
Reactions: Fabian Skrbinjek
@AS19 Can you please let us know what was the issue?
I kind of had the same kind of issue, eventhough not the same.

What created the issue?
 
3cx said it was a known bug, this issue has not actually been fixed as of yet.

the temporary fix 3cx suggested was to use systemd to automatically restart the sip service upon a crash.

see the following instrucitons to auto restart the sip server upon a crash:

login on SSH as root at a scheduled maintenance time
run the following command: nano /etc/systemd/system/3CXPhoneSystem01.service
at the bottom of the [Service] section add these 2 lines:
Restart=always
RestartSec=3
Press Ctrl+O and Enter to save change, then Ctrl+X to close file
Run commands below which will reload and restart the SIP service:
systemctl daemon-reload
systemctl restart 3CXPhoneSystem01
 
  • Like
Reactions: Yellow_Flash
AS19 said:
3cx said it was a known bug, this issue has not actually been fixed as of yet.

the temporary fix 3cx suggested was to use systemd to automatically restart the sip service upon a crash.

see the following instrucitons to auto restart the sip server upon a crash:

login on SSH as root at a scheduled maintenance time
run the following command: nano /etc/systemd/system/3CXPhoneSystem01.service
at the bottom of the [Service] section add these 2 lines:
Restart=always
RestartSec=3
Press Ctrl+O and Enter to save change, then Ctrl+X to close file
Run commands below which will reload and restart the SIP service:
systemctl daemon-reload
systemctl restart 3CXPhoneSystem01
Click to expand...

Thank you for sharing the information.
Hopefully, the issue gets fixed in the next update.
 
Last edited:
3cx says its 16.0.676, im not sure where to look for more specific version into. But 3cx says its up to date.

I'm also haveing issues with my handsets on this version, I made a new thread about that earlier today.
 
@TechieGuy

Just to be clear - note that this only affects specific scenarios, you should not auto-restart services under normal conditions because you will lose the logs that tell you what happened. This procedure was suggested to the above AS19 only as a temporary workaround and we do not recommend you do it.
 
JohnS_3CX said:
@TechieGuy

Just to be clear - note that this only affects specific scenarios, you should not auto-restart services under normal conditions because you will lose the logs that tell you what happened. This procedure was suggested to the above AS19 only as a temporary workaround and we do not recommend you do it.
Click to expand...
I understand, the issue that I faced isn't as severe as this one but I could see the similarity.
Just wanted to know what caused it.
I wouldn't do this unless the support tells me to, I hope I wouldnt face any such issues though.

Thank you. :)
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,934
Messages
589,819
Members
164,811
Latest member
aurorasigntrtechitnet
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom