SipRegistrar is unable to initialize the server

[archan...@ecosmob.com]

Dear all,

I am facing the following the issue, regarding the sipregistrar.

Following is the log of sipregistrar.....

2019-03-22T10:04:44.824208Z":4:SIP:NOTICE:localhost.localdomain::7f7238ffb800:sipxregistry:"SipRegistrar >>>>>>>>>>>>>>>> STARTED"

"2019-03-22T10:04:44.885610Z":5:KERNEL:NOTICE:localhost.localdomain:SipRegistrar:7f722e55c700:sipxregistry:"OsTimer::TimerService STARTED."

"2019-03-22T10:04:44.885934Z":6:SIP:NOTICE:localhost.localdomain:SipRegistrar:7f722e55c700:sipxregistry:"SIP Timer Values -  mUnreliableTransportTimeoutMs : 100 mMaxResendTimeoutMs : 800 mTransactionStateTimeoutMs : 8000 mDefaultExpiresSeconds : 180 mDefaultSerialExpiresSeconds : 20"

"2019-03-22T10:04:44.889322Z":7:SIP:NOTICE:localhost.localdomain::7f722b752700:sipxregistry:"SipUserAgent::handleCancelQueue - STARTED"

"2019-03-22T10:04:44.889378Z":8:SIP:CRIT:localhost.localdomain:SipRegistrar:7f722e55c700:sipxregistry:"[150-ISN] SipRedirectorISN::readConfig BASE_DOMAIN parameter missing or empty"

"2019-03-22T10:04:44.889733Z":9:SIP:CRIT:localhost.localdomain:SipRegistrar:7f722e55c700:sipxregistry:"[160-ENUM] SipRedirectorENUM::readConfig BASE_DOMAIN parameter missing or empty"

"2019-03-22T10:04:44.892136Z":10:SIP:ERR:localhost.localdomain:SipRegistrar:7f722e55c700:sipxregistry:"SipRegistrar::operationalPhase Exception: Failed to call findOne, no good nodes in sipxecs"

"2019-03-22T10:04:44.892157Z":11:SIP:EMERG:localhost.localdomain:SipRegistrar:7f722e55c700:sipxregistry:"SipRegistrar::run Unable to initialize server"

"2019-03-22T10:04:45.880956Z":12:SIP:NOTICE:localhost.localdomain::7f7238ffb800:sipxregistry:"main: cleaning up."

"2019-03-22T10:04:45.881336Z":13:KERNEL:NOTICE:localhost.localdomain::7f7238ffb800:sipxregistry:"Exiting sipxregistry"

In the application settings, I kept it as :

Primary Server : Yes

Host : localhost

SIP Domain: localhost.localdomain

Network Domain: localhost.localdomain

It is still showing the same error, can you help me out?

Thanks

[Todd Hodgen]

Is this a fresh installation?    You should be giving it a host – localhost, and a domain  - localdomain, and a sip domain – localdomain most likely.

 

There has been a lot of chatter on this email list the past couple of weeks – regarding pretty basic concepts with sipXcom.  This system is pretty well proven over many years, and it works.   If you are struggling with basics on the system – the wiki is your friend, as it has some great documentation on setting a system up.  Most of what we generally see on these lists are issues related to new features, or software updates, etc., but not the basic installation of the system.

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/6b18540e-e051-49e1-97f6-efc04178c5b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Picher]

And there are videos too ;-)

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/DM6PR07MB469767A1BEA1773B66FF66BDFD5E0%40DM6PR07MB4697.namprd07.prod.outlook.com.

[archan...@ecosmob.com]

Yea, I did followed the steps as mentioned in the WiKi, tried to install several times. I resolved the BASEDOMAIN warning. Following is the log of the error.

"2019-03-26T12:25:04.811938Z":241:MONGO_CLIENT:DEBUG:localhost.localdomain:SipRegistrar:7fa57c4e1700:sipxregistry:"Updating host localhost.localdomain:27017 based on ismaster reply: { setName: \"sipxecs\", setVersion: 1, ismaster: true, secondary: false, hosts: [ \"localhost.localdomain:27017\" ], primary: \"localhost.localdomain:27017\", me: \"localhost.localdomain:27017\", maxBsonObjectSize: 16777216, maxMessageSizeBytes: 48000000, maxWriteBatchSize: 1000, localTime: new Date(1553603104811), maxWireVersion: 2, minWireVersion: 0, ok: 1.0 }"

"2019-03-26T12:25:04.811960Z":242:MONGO_CLIENT:DEBUG:localhost.localdomain:SipRegistrar:7fa57c4e1700:sipxregistry:"dbclient_rs no compatible node found\n"

"2019-03-26T12:25:04.811969Z":243:MONGO_CLIENT:DEBUG:localhost.localdomain:SipRegistrar:7fa57c4e1700:sipxregistry:"ReplicaSetMonitor::get sipxecs"

"2019-03-26T12:25:04.811982Z":244:MONGO_CLIENT:DEBUG:localhost.localdomain:SipRegistrar:7fa57c4e1700:sipxregistry:"User Assertion: 16379:Failed to call findOne, no good nodes in sipxecs\n"

"2019-03-26T12:25:04.812064Z":245:MONGO_CLIENT:DEBUG:localhost.localdomain:SipRegistrar:7fa57c4e1700:sipxregistry:"ReplicaSetMonitor::get sipxecs"

"2019-03-26T12:25:04.812075Z":246:MONGO_CLIENT:INFO:localhost.localdomain:SipRegistrar:7fa57c4e1700:sipxregistry:"scoped connection to sipxecs/localhost.localdomain:27017 not being returned to the pool\n"

"2019-03-26T12:25:04.812161Z":247:KERNEL:DEBUG:localhost.localdomain:SipRegistrar:7fa57c4e1700:sipxregistry:"OsServerTask::~ 'SipRedirectServer-10' UNINITIALIZED"

"2019-03-26T12:25:04.813208Z":248:SIP:ERR:localhost.localdomain:SipRegistrar:7fa57c4e1700:sipxregistry:"SipRegistrar::operationalPhase Exception: Failed to call findOne, no good nodes in sipxecs"

"2019-03-26T12:25:04.813232Z":249:SIP:EMERG:localhost.localdomain:SipRegistrar:7fa57c4e1700:sipxregistry:"SipRegistrar::run Unable to initialize server"

"2019-03-26T12:25:04.813288Z":250:KERNEL:DEBUG:localhost.localdomain:SipRegistrar:7fa57c4e1700:sipxregistry:"OsTaskLinux::ackShutdown 'SipRegistrar' RUNNING"

PS: I am using Virtual Box to install Sipxcom.

Thank You

[pmkr...@gmail.com]

I've encountered this error frequently over the past several weeks during HA failover testing and characterizing Mongo DB recovery - in my case, this issue appears because. secondary servers are split across virtual and physical servers and Mongo cannot elect a new primary server when the network is rejoined. In your case, the Sipxecs-setup host name / SIP domain name defaults are problematic for Mongo so it has trouble coming up immediately. The SIP registrar is stored in Mongo so when the Mongo DB is unavailable, the Sipxregistrar process complains.

Mongo is a replicated database, and expects host names like 'database0.example.com, database1.example.com...' see https://docs.mongodb.com/manual/tutorial/change-hostnames-in-a-replica-set/. Sipxcom builds the underying Mongo database definitions from your host name and domain name selection. Use a hostname such as pbx and domain name such as testserver.com. When the server is built and comes up, the server name will show up in Sipxcom as pbx.testserver.com and Mongo will come up without issue.

Peter

[archan...@ecosmob.com]

Thanks. It is working Fine now.