nagios-db problems

[Joubin Moshrefzadeh]

I'm having some challenges getting nagios-db working properly.

I've installed Nagios 2.0b2, and nagios-db-0.91 on a Debian box, plus mysql-4.1.9 through apt, and using the minimal config shipped with version 2.0.

For some reason I keep getting the following message in the nagios log when I start the process:

[1109693638] Nagios 2.0b2 starting... (PID=1957)
[1109693638] LOG VERSION: 2.0
[1109693638] initializing nagios-db mysql inserter...
[1109693638] nagios-db: inserter locked into db
[1109693638] Event broker module '/usr/local/nagios/modules/inserter_mysql.o' initialized successfully.
[1109693638] nagios-db: configured 0 hosts
[1109693638] nagios-db: configured 0 services
[1109693638] nagios-db: loaded 0 hostgroups
[1109693638] nagios-db: configuration complete. Registering for status notifications...
[1109693638] Finished daemonizing... (New PID=1959)
[1109693639] Can't find record in 'host_history' 1032 INSERT INTO host_history (hostid,started,lasted,soft_state,hard_state,current_attempt,plugin_output) VALUES (@hostid, at time,null,0,0,1,'PING OK - Packet loss = 0%, RTA = 0.38 ms') ON DUPLICATE KEY UPDATE current_attempt=VALUES(current_attempt),plugin_output=VALUES(plugin_output)
[1109693648] nagios-db: inserter unloading...


Then looking at the services/hosts status using the UI, all checks remain in a pending state... any thoughts on what I should be checking/changing?





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
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