Hi all,
It won't work with 1.0b6 for me either.
I have found that all versions I tried with would patch correctly.
I believe my problem is somewhere in the compiling or make process.
If anybody could send me his/her compile command for ver. 1.0b6 with xlogdb
that worked I'd really appreciate it.
Thank you all
Daniel
-----Original Message-----
From: Bryan Liles [mailto:[email protected]]
Sent: Monday, November 18, 2002 6:58 PM
To: Daniel Geske
Subject: Re: [Nagios-devel] Patch by Dougal Scott (MySQL History Log)
Problem Compiling
I can confirm your problems with the ./configure. I have it working
with 1.0b6, and I am diggin in the cvs configure.in right now to see
what the deal is.
On Mon, 18 Nov 2002 16:45:50 +0100
"Daniel Geske" wrote:
> Thanks, please let me know what you can find. I don't really know how
> to go on from here.
>
> Greetings
>
> Daniel
>
> -----Original Message-----
> From: Bryan Liles [mailto:[email protected]]
> Sent: Monday, November 18, 2002 4:37 PM
> To: 'Daniel Geske '; Bryan Liles; '[email protected]
> ' Subject: RE: [Nagios-devel] Patch by Dougal Scott (MySQL History
> Log) Problem Compiling
>
>
> interesting, I'll give it a try when I get into the office.
> -----Original Message-----
> From: Daniel Geske
> To: Bryan Liles; [email protected]
> Sent: 11/18/2002 10:31 AM
> Subject: RE: [Nagios-devel] Patch by Dougal Scott (MySQL History Log)
> Problem Compiling
> Yes, it went all the way through smoothly.
> Maybe a problem: I'm using the current CVS snapshot- not the 1.06b
> release.
> Greetings
> Daniel
> -----Original Message-----
> From: Bryan Liles [mailto:[email protected]]
> Sent: Monday, November 18, 2002 4:29 PM
> To: 'Daniel Geske '; '[email protected] '
> Subject: RE: [Nagios-devel] Patch by Dougal Scott (MySQL History Log)
> Problem Compiling
>
>
> Just curious, I have been using this patch with no problems at all.
> Did your patch apply cleanly?
> -----Original Message-----
> From: Daniel Geske
> To: Daniel Geske; [email protected]
> Sent: 11/18/2002 6:21 AM
> Subject: RE: [Nagios-devel] Patch by Dougal Scott (MySQL History Log)
> Problem Compiling
> Hi again,
> does anybody have an idea on how to fix this problem? Do you need more
> specific information (if yes, which) on it?
> Thank you all very much.
> Greetings
> Daniel
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Daniel
> Geske
> Sent: Monday, November 11, 2002 11:21 AM
> To: [email protected]
> Subject: [Nagios-devel] Patch by Dougal Scott (MySQL History Log)
> Problem Compiling
>
>
> Hi all,
> I'm trying to use Dougal Scott's patch to log nagios history info to
> mysql
> db.
> First off, I cvsed a fresh nagios. Applying the patch went OK, no
> problems.
> First thing I notice comes up when I run configure. It's supposed to
> echo
> "We'll use MySQL database routines (in xdata/xlogdb.*) for history
> log" between the lines for comment data and extended data, but
> doesn't. Then, of course, it doesn't show it's planning to use xlogdb
> in the configuration summary either. First line after "Web Interface
> Options" should be "History Log data: $XLOGCOMMENT". Instead, I get
> the normal"HTML
> URL: ..." There are no error messages. The first error I get in this
> procedure is when I run "make all". Maybe the output there can help.
> For all
> command outputs, please see below.
> I have checked wheather there it may use the wrong configure.in file,
> well
> there's only one in my nagios source dir (the patched file), so I
> assume it's using it, too.
> How can I compile nagios so it stores it's history logs in a MySQL DB
> now?
> I'm looking forward to hearing from you all. Thanks.
> Sincerely
> Daniel
>
>
> ///////////////////////////////
> $ ./configure [..] --with-mysql-historylog [..]
> [..]
> We'll use MySQL database routines (in xdata/xsddb.*) for status data
> I/O...
> We'll use MySQL database routines (in xdata/xcddb.*) fo
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: ryan Liles [mailto:[email protected]