-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/07/08 06:11 AM, Kaushal Shriyan wrote:
> Hi Thomas > Its running fine. > $ sudo fuser /var/nagios/ndo.sock > /var/nagios/ndo.sock: 7592 7639 7640 7711 7833 19676 > $ ps -aef | grep ndo2db > nagios 7592 19676 0 03:06 ? 00:00:00 > /usr/nagios/bin/ndo2db-2x -c /etc/nagios/ndo2db.cfg > nagios 7639 19676 0 03:06 ? 00:00:00 > /usr/nagios/bin/ndo2db-2x -c /etc/nagios/ndo2db.cfg > nagios 7640 19676 0 03:06 ? 00:00:00 > /usr/nagios/bin/ndo2db-2x -c /etc/nagios/ndo2db.cfg > nagios 7711 19676 0 03:06 ? 00:00:00 > /usr/nagios/bin/ndo2db-2x -c /etc/nagios/ndo2db.cfg > nagios 7833 19676 0 03:07 ? 00:00:00 > /usr/nagios/bin/ndo2db-2x -c /etc/nagios/ndo2db.cfg > kaushal 14691 24061 0 03:10 pts/0 00:00:00 grep --colour=auto ndo2db > nagios 19676 1 0 Jul09 ? 00:00:00 > /usr/nagios/bin/ndo2db-2x -c /etc/nagios/ndo2db.cfg > $ > Any further ideas Maybe a permission problem on the socket file? One of your ndodb processes is much older than the others... are you sure you don't have a stale ndo2db-2x running? You can try shutting down the daemon, doing a "killall -9 ndo2db-2x" as root and starting it again... NDODB users might have a better idea what could go wrong... Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIdeWL6dZ+Kt5BchYRAua0AKCyWSoSg/LM6tymaa1HIUJj0VDrigCfWGa+ ygNRwm8VYD4ElSPDUp6rhuk= =7mCy -----END PGP SIGNATURE----- ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
