Unknow MySQL database

[Dan Hopkins]

Check the ownership and filemode of your resource.cfg. I had this effect on a root owned 0600 resource.cfg ...

--
Dan Hopkins


-----Original Message-----
From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-admin at lists.sourceforge.net]On Behalf Of Alex Curvers
Sent: 15 August 2004 11:23
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] Unknow MySQL database


Hi
 
I could use some help, I installed the nagios-mysql package on my debian system. I read the README.mysql and did what it said.  (creating database setting permissions and uncommenting setting the lines that define the mysql DB etc in resource.cfg and cgi.cfg.)
I veriefied MySQL was running and restarted nagios (nagios -d /etc/nagios/nagios.cfg), but I get these errors in the log.
Seems 
:
[1092563015] Error: Could not connect to MySQL database '' on host '' using username '' and password ''.  Retention data will not be processed or saved!
[1092563015] Error: Could not connect to MySQL database '' on host '' using username '' and password '' for comment data!
[1092563015] Error: Could not connect to MySQL database '' on host '' using username '' and password '' for downtime data!
[1092563020] Error: Could not lock status data tables in database ''
 
Seems still the database definition is not known to nagios. Im at a loss here could anyone help me futher ?
 
Regards 
Alex Curvers


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Nagios-users mailing list
Nagios-users at 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