Hi all, Recently I have installed Nagios 3.1.2 and NDOUtils 1.4b8 on a Solaris 9 system with MySQL 5.0.67. Nagios is running fine, but while I start ndo2db daemon for retriving and sending Nagios data to MySQL, ndo2db started and then stoped soon....with no error message.
Part of nagios.log is as following: [1247834612] ndomod: Successfully reconnected to data sink! 0 items lost, 4840 queued items to flush. [1247834612] ndomod: Error writing to data sink! Some output may get lost. 4604 queued items to flush. [1247834628] ndomod: Still unable to reconnect to data sink. 0 items lost, 4694 queued items to flush. [1247834644] ndomod: Still unable to reconnect to data sink. 0 items lost, 4770 queued items to flush. [1247834660] ndomod: Still unable to reconnect to data sink. 0 items lost, 4862 queued items to flush. [1247834676] ndomod: Still unable to reconnect to data sink. 0 items lost, 4938 queued items to flush. [1247834692] ndomod: Still unable to reconnect to data sink. 27 items lost, 5000 queued items to flush. [1247834708] ndomod: Still unable to reconnect to data sink. 107 items lost, 5000 queued items to flush. The first line with "Successfully ....." is the moment while ndo2db was started, it seems at that time ndomod can send data to ndo2db socket. After that ndo2db stoped adnormal and ndomod can't find the socket to write. Any help will be appreciated, thank in advance. ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
