Problems with Nagios 3.0rc1 and NDOMOD 1.4b7

[Diego Saavedra]

Hello!
Sorry for my bad English. I have installed Nagios Version 3.0rc1 and NDOMOD
1.4b7. When I restart Nagios occurs as follows:


[08-27-2008 09:05:39] Nagios 3.0rc1 starting... (PID=13053)
[08-27-2008 09:05:39] Local time is Wed Aug 27 09:05:39 ART 2008
[08-27-2008 09:05:39] LOG VERSION: 2.0
[08-27-2008 09:05:39] ndomod: NDOMOD 1.4b7 (10-31-2007) Copyright (c)
2005-2007 Ethan Galstad (nagios at nagios.org)
[08-27-2008 09:05:39] ndomod: Successfully connected to data sink. 2 queued
items to flush.
[08-27-2008 09:05:39] ndomod: Successfully flushed 2 queued items to data
sink.
[08-27-2008 09:05:39] Event broker module
'/usr/local/nagios/bin/ndomod-3x.o' initialized successfully.
[08-27-2008 09:05:39] Finished daemonizing... (New PID=13055)

The problem is that not write anything on the MYSQL database. I read that it
might be a problem of compatibility of versions but I do not believe that.

Thanks in advance.

Greetings.

---------------------------------------------
Lic. Diego Saavedra
Operador NOC
ARIU - Red de Interconexion Universitaria
Buenos Aires - Argentina
---------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080827/9aa4e766/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
-------------- next part --------------
_______________________________________________
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