If we enable Distributed Database arbiter in secondary servers then its running in secondary machines but only issue is if we enable in primary server,which showing mongod-arbiter---Shutdown...
Regards, Kumaran T On 9/17/2012 12:12 PM, Chitra wrote: > Hi All, > > There is an issue with respect to mongod-arbiter shutting down after we > reboot the server once yum update is done. > (http://track.sipfoundry.org/browse/XX-10433). If we try to start the > mongod-arbiter service manually, it will show start ok, but status is > dead i.e.: > > [root@1 ~]# /etc/init.d/mongod-arbiter start > Starting mongod-arbiter: forked process: 14340 > all output going to: /var/log/mongodb/mongod-arbiter.log > [ OK ] > > And checked the status: > > [root@1 ~]# /etc/init.d/mongod-arbiter status > mongod-arbiter dead but pid file exists > > So tried the following: > [root@1 ~]# ls -la /var/log/mongo/mongod* > -rw-r--r--. 1 mongod mongod 1338730 Sep 11 10:31 > /var/log/mongo/mongod-arbiter.log > -rw-r-----. 1 mongod mongod 8182264 Sep 11 10:31 > /var/log/mongo/mongod.log.rpmsave > > And changed the owner > chown mongodb:mongodb /var/log/mongo/mongod-arbiter.log > and then checked : > [root@1 ~]# ls -la /var/log/mongo/mongod* > -rw-r--r--. 1 mongodb mongodb 1338730 Sep 11 10:31 > /var/log/mongo/mongod-arbiter.log > -rw-r-----. 1 mongod mongod 8182264 Sep 11 10:31 > /var/log/mongo/mongod.log.rpmsave > > ,then started manually, still same result: > > [root@1 ~]# /etc/init.d/mongod-arbiter status > mongod-arbiter dead but pid file exists > > So could anybody look into this and guide us. > > Thanks, > Chitra > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
