3CX Crashing after auto update

[maxrobz]

Hi,

3CX automatically updated last night and it is constantly crashing this morning. I get the following message and have to restart the service:

The following service(s) were interrupted:

3CXPhoneSystem01

I restarted all services to see if that might help but it crashed again.

I have to restart 3CX PhoneSystem 01 SIP Server constantly.

We have now found that this appears to be caused by users attempting to use Shared Parking.

Please help!

Max

 

[Saqqara]

What version of 3cx , and which platform I.e hosted , self hosted , windows, debian

 

[maxrobz]

V18 Update 4. Self hosted on AWS Lightsail with Debian. All phones etc are running on latest firmware.

 

[Charles_3CX]

@maxrobz

Regarding your issue, do you have any extra packages installed on the machine other than what is installed via the 3cx wizard when deploying the machine? Additionally, does the machine specification meet the minimum requirements as per the guide: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/?

If no extra packages are installed, and hardware specifications are as required, please open a ticket with 3cx technical support from your customer portal, portal.3cx.com, logging in with the email address used to register the subscription (license key), as we cannot troubleshoot this type of issue within the forum, and will require some data gathered from the Linux OS via SSH as well, support info, etc...

 

[maxrobz]

Hi Charles, we have nothing extra installed, running on AWS Lightsail with a standard install. It has run perfectly for the last 2.5 years without issue until the auto install of Service Pack 4 last night. I don't think we will be the only customer with the issue so I think it would be wise for you to start investigating this as it seems to be caused by this SP and only happens when you put a caller into Shared Parking. The Service is stopped immediately.

Max

 

[Charles_3CX]

Regarding your reply, please note this is not something we can replicate and check; we will require the appropriate data from the machine, which includes the time of the crash. Additionally, we have had no issues reported of any similar occurrences. As such, we will need to check the logs and data from the machine to advise. I can only suggest opening a ticket with 3cx technical support to investigate this for you.

One thing to also check on your side is that there are no loops caused by the configuration of the shared parking under the management console > settings. Call the parking section for the option to Automatically unpark forgotten calls going to a location where it would cause the call to be transferred back and forth between endpoints.

 

[maxrobz]

In SSH I see the following when this happens:

Jul 14 18:38:13 ip-XXXX kernel: [6020916.941591] 3CXPhoneSystem[32421]: segfault at 150 ip 00007fb209c513a0 sp 00007fb1e77f75c8 error 4 in libresip-1.13.so[7fb209c18000+135000]
Jul 14 18:38:13 ip-XXXX kernel: [6020916.941601] Code: 48 8b b3 18 02 00 00 e8 ee 6c fc ff 48 8d 73 70 48 8d 7d 70 e8 41 f8 fc ff 48 83 c4 08 48 89 e8 5b 5d c3 90 66 0f 1f 44 00 00 <8b> 47 18 53 48 89 fb 85 c0 74 0d 48 8d 43 70 5b c3 0f 1f 80 00 00
Jul 14 18:38:13 ip-XXXX systemd[1]: 3CXPhoneSystem01.service: Main process exited, code=killed, status=11/SEGV
Jul 14 18:38:13 ip-XXXX systemd[1]: 3CXPhoneSystem01.service: Failed with result 'signal'.

 

[Charles_3CX]

Can you please open a support ticket so we may request all the required files to check this for you?

 

[JohnS_3CX]

Those having this issue should ensure that parameter DISALLOWREFERTOBUSYSP is set to 0.

 

[maxrobz]

Currently set to 1. Description is as follows:

Available options 0 and 1. 0=PBX will allow transfer request to a busy parking place. 1=PBX will reject transfer request to a busy parking place

Why would we set to 0? We have never changed this but I see that the default is 0 at this link:

https://www.3cx.com/docs/parameters-table/

 

[JohnS_3CX]

Because that is the default and should remain that way.

If its 1 then somebobody changed it at some point because I can confirm that the system installs with the value 0 by default.