Problem Updating through MySQL

[Ricardo David Martins]

Hi,

i have been doing some more tests and i now realize that that the CGIs
alert history is NOT written in a mysql table. Instead this is done on
a file (var/nagios.log). I dont understand the reason for this. The
compilation
parameter referred mysql data base to all external data, just not objects.

How can i have all logged data on a mysql data base. What am i missing here?
I have read about PerfParse... does this do the trick?

Many thanks

-------------------------------
Ricardo David Martins


On Mon, 6 Sep 2004 10:52:50 -0500, Marc Powell <marc at ena.com> wrote:
> 
> 
> > -----Original Message-----
> > From: Ricardo David Martins [mailto:ricardo.martins at gmail.com]
> > Sent: Monday, September 06, 2004 9:30 AM
> > To: nagios-users at lists.sourceforge.net
> > Subject: [Nagios-users] Problem Updating through MySQL
> >
> > Hi,
> >
> > i was trying to change a service next schedule by updating directly on
> > a mysql client. It seems to produce no effect. Although it make the
> > changes and its visible on the CGI, in 3 seconds the value is restored
> > again!
> >
> > Can i make nagios to respond to my mysql UPDATE queries without the
> > external command file?
> 
> No, you cannot. Nagios maintains the primary reference points within its
> memory. The SQL values are simply for display by the CGI's only and/or
> retention, depending on the table you're trying to update. You'll need
> to send the change as an external command.
> 
> --
> Marc
> 
>


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&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