Joerg, Great information! I changed the config to write to file and it works. After changing it back I still get the same error.
I checked and like you said I only see one ndo2db process. One thing I questioned was the DB PREFIX option. The default SQL import used a prefix of ndo_, but the default in the config file is to not use a prefix at all. I've tried using both configs with no luck so I guess that's probably not it. I really appreciate your help and ideas. Josh -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joerg Linge Sent: Thursday, May 25, 2006 7:50 AM To: [email protected] Subject: Re: [Nagios-users] NDOUtils 1.3.1 data sink error. Am Donnerstag 25 Mai 2006 14:38 schrieb Samba: > Thanks for your reply. I should have included that info: > .... > There are some timing options at the bottom, I don't think they're > important. These options are OK > I have verified tha the ndo.sock is nagios.nagios. I even tried changing > everything to TCPSocket and got the same errors. Hmmm If you make changes in ndomod.cfg, nagios must be restarted. > I manually connected to the DB as mysql/<password> with no problem. Ok, please check if ndo2db is running. If nagios (ndomod.o) connects to ndo2db ( Unix or tcp socket ) a new process is forked. So if you only see only one process, nagios can not connect to ndo2db. You can also check if ndomod.o is able to write the data to a file. Try to turn this feature on in ndomod.cfg But everything step by step. Jörg ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642 _______________________________________________ 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
