Some Services Won't Start

[thereverendd]

My install was working 100% and then today I went to make a call and ...... Nothing..
Went into my server and found this :



Tried to start them but they won't start, Can someone PLEASE help me get these online.. Thank you so much in advance.

 

[leejor]

Please provide additional information about your system. See...

https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Have you re-booted the entire system? How long has it been working?

 

[thereverendd]

I have rebooted the whole server 2x with no resolve.

Here is what is show in the Activity (IP ADDRESSES AND FQDN REMOVED)

04/11/2020 10:49:29 PM - STUN discovery of public IP is disabled

04/11/2020 10:49:29 PM - Exception: DumException Cannot create new sessions when DUM is shutting down. @ DialogUsageManager.cxx:517

04/11/2020 10:49:09 PM - Set log verbosity to MaxLevel = 2, Severity mask = 7

04/11/2020 10:49:09 PM - Loading Contact records from database

04/11/2020 10:49:09 PM - Line 90000 has been updated from DB

04/11/2020 10:49:09 PM - Dev(1450585941):[sip:90000 / 90000]: PBX contact is public IP: <sip:90000@XXX:5060>

04/11/2020 10:49:09 PM - Signal: stopHandler got: 15

04/11/2020 10:48:59 PM - Failed to add outbound CID reformating rule for DN:10003: <Rules />

04/11/2020 10:48:59 PM - Failed to add outbound CID reformating rule for DN:10003: <Rules />

04/11/2020 10:48:59 PM - Line 10003 has been updated from DB

04/11/2020 10:48:59 PM - Dev(452529583):[sip:[email protected]:5060 / XXX]: PBX contact is public IP: <sip:XXX@XXX:5060>

04/11/2020 10:48:41 PM - Currently active calls [none]

04/11/2020 10:48:39 PM - Failed to add outbound CID reformating rule for DN:10002: <Rules />

04/11/2020 10:48:39 PM - Failed to add outbound CID reformating rule for DN:10002: <Rules />

04/11/2020 10:48:39 PM - Line 10002 has been updated from DB

04/11/2020 10:48:39 PM - Dev(1162158051):[sip:[email protected]:5060 / XXX]: PBX contact is public IP: <sip:XXX@XXX:5060>

04/11/2020 10:48:19 PM - Failed to add outbound CID reformating rule for DN:10001: <Rules />

04/11/2020 10:48:19 PM - Failed to add outbound CID reformating rule for DN:10001: <Rules />

04/11/2020 10:48:19 PM - Line 10001 has been updated from DB

04/11/2020 10:48:19 PM - Dev(XXX):[sip:[email protected]:5060 / XXX]: PBX contact is public IP: <sip:XXX@7XX:5060>

04/11/2020 10:48:11 PM - Currently active calls [none]

04/11/2020 10:47:59 PM - Failed to add outbound CID reformating rule for DN:10000: <Rules />

04/11/2020 10:47:59 PM - Failed to add outbound CID reformating rule for DN:10000: <Rules />

04/11/2020 10:47:59 PM - Line 10000 has been updated from DB

04/11/2020 10:47:59 PM - Dev(279808887):[sip:[email protected]:5060 / XXX]: PBX contact is public IP: <sip:XXX@XXX:5060>

04/11/2020 10:47:41 PM - Currently active calls [none]

04/11/2020 10:47:39 PM - Supported Mime Type added:MESSAGE(x-chat/control)

04/11/2020 10:47:39 PM - User-Agent's that is configured to ignore: friendly-scanner,sipsak,smap,Elite 1.0 Brcm Callctrl,sipcli,VaxSIPUserAgent,VaxIPUserAgent,PortSIP,friendly-request,sip-scan,sipvicious,sundayddr,iWar,SIVuS,Gulp,sipv,siparmyknife,Test Agent,eyeBeam release 3006o stamp 17551,SIP Call,PortSIP VoIP,Conaito,Ozeki,Gbomba,MizuPhone,VoIP v11.2.4,VoIP SIP v11.0.0,VoIP v11.1.2,sdfsfsdfsdfdf,Nmap NSE,BaSeL-X,dr.pes,Z 3.14.38765 rv2.8.3,pplsip,sipptk,eyeBeam release 3004t stamp 16741,eyeBeam release 3007n stamp 17816,eyeBeam release 3010n stamp 19039,MGKsip,Z 10.14.38765 rv2.8.3,A_B_C,UsaAirport,KPhone/3.14,zxcvfdf11,eXosip,eyeBeam release 3015c stamp 27107,SipClinte2019,yarab100,eXosip2,SipReg v1.0,IPOffice,VoIP SIP

04/11/2020 10:47:39 PM - License loaded sucessfully. License level: 2

04/11/2020 10:47:39 PM - Secure SIP (IPv6) is available at XXXXXX

04/11/2020 10:47:39 PM - Secure SIP (IPv4) is available at XXXXXX

04/11/2020 10:47:39 PM - Adding secure SIP transport (IPv4) for sXXXs:5061

04/11/2020 10:47:39 PM - [CM506005]: Public IP=XXX is used for WAN communications through local interface with IP=XXX

04/11/2020 10:47:39 PM - UDP transport is joined to SIP multicast group on interfaceXXX

04/11/2020 10:47:39 PM - Folder for SSL certificates : /var/lib/3cxpbx/Instance1/Bin/Cert

04/11/2020 10:47:39 PM - ** Initializing SIP stack **

04/11/2020 10:47:39 PM - Local IP addresses detected: XXXX

04/11/2020 10:47:39 PM - [CM501006]: Default Local IP address: XX

04/11/2020 10:47:39 PM - Default best-route IP is determined as XX

04/11/2020 10:47:39 PM - [CM501002]: Version: 16.0.2.910

04/11/2020 10:47:39 PM - [CM501007]: *** Started Calls Controller thread ***

04/11/2020 10:47:39 PM - [CM501001]: Start 3CX PhoneSystem Call Manager

04/11/2020 10:47:39 PM - [EC200001]: Configuration server is connected: application:3cx2019:5485/DBProvider local:127.0.0.1:46864 remote:127.0.0.1:5485

04/11/2020 10:47:39 PM - Application connected:3cx2019:5485/DBProvider

04/11/2020 10:47:39 PM - Startup completed for 3cx2019:5485/DBProvider

04/11/2020 10:47:39 PM - Start management threads for 3cx2019:5485/DBProvider

04/11/2020 10:47:39 PM - Timezone offset: -240 min.

 

[thereverendd]

Did a restore from a backup made previous to this and that also did not help at all

 

[leejor]

04/11/2020 10:49:29 PM - Exception: DumException Cannot create new sessions when DUM is shutting down. @ DialogUsageManager.cxx:517

This would seem to be an important clue to the problem. But, as it also seems to be Linux (which I don't use), I'm afraid can't help you. You still haven't listed the version(s) you are using, which may help someone else diagnose the issue.

 

[AWS2P]

Do you have enough free memory and other hardware ressources, do you use recordings?

 

[thereverendd]

I am not sure why, but a reboot of the HARDWARE server seems to have fixed the issue.. ODD that the reboot of the VM did not work but the hardware reboot did.. Had to go on site and reboot the physical server.. Then.. it started to work.. odd...

 

[YiannisH_3CX]

It looks like you had a problem starting the SIP server service (the rest are dependencies) which could be related to any number of reasons but i suspect it had to do something with the server NIC which would explain why a server restart fixed the issue. Keep an eye on it and let us know if you experience the issue again.