Sip Server Service stopped?

[Aiv]

Hi All,

To day we encountered a very strange issue with our 3CX server. 3CX PhoneSystem 01 SIP Server service has stopped by it self?

When looking in event log I saw the fallowing:

17/06/2019 12:13:59 SIP Server/Call Manager ID: 4098 Service got signal to stop: stop service

17/06/2019 12:13:59 SIP Server/Call Manager ID: 4098 Service got signal to stop: 22

To me this looks like someone would have stopped this service by hand. So i tried looking in the logs. Could not find much except in 3CXConfService saw these few lines:
12:14:00.187|000010ec| Info|DBServ.cpp(533): SL:Receive failed with code 10054
12:14:00.187|000010ec| Info|DBServ.cpp(533): SL:Remote disconnect: "EC2AMAZ-PQ485D8:5482/CallManager" stopped
12:14:00.187|000010ec| Info|DBServ.cpp(72): EC2AMAZ-PQ485D8:5482/CallManager disconnected
12:33:43.313|00001014| Info|DBServ.cpp(533): SL:ConnectionThread. Accepting new connection
12:33:43.313|00001014| Info|DBServ.cpp(533): SL:ConnectionThread. Connection from: '127.0.0.1' has been accepted
12:33:43.313|00001014| Info|DBServ.cpp(533): SL:ConnectionThread. Configuring new socket.
12:33:43.313|00001014| Info|DBServ.cpp(533): SL:ConnectionThread. Starting new application
12:33:43.314|00001014| Info|DBServ.cpp(533): SL:Start management threads for EC2AMAZ-PQ485D8:5482/CallManager
12:33:43.314|000006ec| Info|DBServ.cpp(533): SL:Application connected:EC2AMAZ-PQ485D8:5482/CallManager
12:33:43.314|00001014| Info|DBServ.cpp(533): SL:Startup completed for EC2AMAZ-PQ485D8:5482/CallManager
12:33:43.314|000006ec| Info|DBServ.cpp(79): EC2AMAZ-PQ485D8:5482/CallManager from 127.0.0.1:56246 to 127.0.0.1:5485 Connection accepted.
12:33:43.314|00001014| Info|DBServ.cpp(533): SL:ConnectionThread. Initialization of new connection is completed.
12:33:43.404|0000101c| Warn|ObjectManager.cpp(284): Runtime table 'registration' already initialized.
12:33:43.415|0000101c| Warn|ObjectManager.cpp(284): Runtime table 'connection' already initialized.


At 12:33:43 is where I manualy started SIP Server service. But the stuff above it is a mystery for me as there is also no log entry before 12:14:00 until 11:05:10.


Anyone got an idea why this service stopped or tips so I can figure out why this happend?

 

[JohnS_3CX]

We need some more information on this like OS, Version, Host type

Only the SIP Server was stopped or did you see other services stopped too?

Is there a chance you may have run out of resources? This can cause the OS to shut down processes.

Do you have a swap file?

 

[Aiv]

Hi,

The server is running:
Windows Server 2019 VW ( hosted on AWS EC2)
2 CPU cores
8GB Ram

3CX version: 15.5.15502 Pro.

Yes only 1 service was stopped according to event log and when starting manually that was also the only service I needed to start.

I thought about running out of resource but according to Elastic monitoring server had plenty of resources the only peak in CPU usage was when I RDP'ed to VM and opened console.

 

[JohnS_3CX]

You could also check the windows event logs to see if anything went wrong, normally the service would stop if it could not bind to the SIP port.

Did you get an email notification about the service?

 

[Aiv]

Yes I go 2 emails from 3cx.

1, Stopped Services Notification
Saying:
Following service(s) were stopped recently:
3CXPhoneSystem01
( and nothing else)

2, Trunk -xxxxxxxxxxxx has been changed
Saying: Trunk xxxxxxxxxxxx has changed status to registered.


Regarding the Windows logs I must admit I did not check.


After looking in windows logs I found only these 2 errors:

Systemlog:
17/06/2019 12:14:00 The 3CX PhoneSystem 01 SIP Server service terminated unexpectedly. It has done this 1 time(s).

Application log:
17/06/2019 12:13:59 Faulting application name: 3CXPhoneSystem.exe, version: 15.5.15502.6, time stamp: 0x5b838e08
Faulting module name: 3CXPhoneSystem.exe, version: 15.5.15502.6, time stamp: 0x5b838e08
Exception code: 0xc0000409
Fault offset: 0x00000000004abd80
Faulting process id: 0x10b8
Faulting application start time: 0x01d52272d4f02195
Faulting application path: C:\Program Files\3CX Phone System\Instance1\Bin\3CXPhoneSystem.exe
Faulting module path: C:\Program Files\3CX Phone System\Instance1\Bin\3CXPhoneSystem.exe
Report Id: 189a25d4-dba0-47af-8fcd-13e6f639bd88
Faulting package full name:

 

[JohnS_3CX]

Hi Aiv,

Ok so it looks like a crash but the reason is not clear unfortunately unless there is an in depth investigation with replication.

Given that we have made quite a few changes in our latest version that address various scenarios that can cause a crash, I would recommend to upgrade to V16 as soon as possible especially if you continue to have issues with the old version.

Also ensure there are no other 3rd party services or software running on the machine that could interfere and if there are any pending Windows updates install them and reboot as needed.

 

[Aiv]

Hi,

Thank you for the help very appreciated.