Sorry for having this conversation with myself online but I felt it was important to document my problem so everyone could benefit.
My problem ended up being rooted in ndo2db. It is hardcoded to look for the mysql.sock file in /var/lib/mysql/mysql.sock. Mine was located in /tmp/mysql.sock. To resolve the issue I created a sym link to where it was looking for the mysql.lock, resarted nagios and things are working now. Thanks to Joerg for your help !!! Josh -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joerg Linge Sent: Thursday, May 25, 2006 8:09 AM To: [email protected] Subject: Re: [Nagios-users] NDOUtils 1.3.1 data sink error. Am Donnerstag 25 Mai 2006 14:59 schrieb Samba: > Joerg, Hi Josh > 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. OK, let me test this on my devel box. I will try to reproduxe this error. > 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. db_prefix must set to ndo_ if you use the default sheme. can your db user write to the database ? Please test this again, i have done the same mistakes by using a wrong db user. > I really appreciate your help and ideas. Give me 5 minutes.... ------------------------------------------------------- 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
