We've moved to a new support system!

The Nagios Answer Hub is a place where you can get help with technical questions from our experts. There, you can quickly open tickets and join discussion boards.

Request Nagios Answer Hub access here: https://info.nagios.com/answer-hub-access-new-users

After completing the access form, you will be given access to a portal where new tickets can be created. We will keep the old customer forum sections and ticket system available for current cases to be resolved.

Go to the Answer Hub

[Nagios-devel] CVS compile failing to run

Engage with the community of users including those using the open source solutions.
Includes Nagios Core, Plugins, and NCPA

[Nagios-devel] CVS compile failing to run

Postby Guest » Thu May 23, 2002 11:12 am

Hi,

I noticed that my compiles of the recent CVS code (last week or so)
compiles fine now, but fails to run as a daemon. The -v check runs fine,
but when I try to startup Nagios, I'm getting a SIGEGV fault.=20

What are some good debuggers that I could use to determine where in the
code Nagios is giving me the finger? Here's the particulars on the CVS
compile:


Running this command:
/usr/local/nagios/bin/nagios usr/local/nagios/etc/nagios.cfg

seems to generate the proper response, but still stops after reviewing
the schedules. However, if I try it as a daemon (-d), the last messages
I get are:

Completed circular path checks
Completed circular service dependency checks
Completed global event handler command checks
Completed obsessive compulsive service processor command check
[root@tempserver bin]#=20

Followed by this message in the log file:

[1022180415] Finished daemonizing... (New PID=3D6666)
[1022180415] Caught SIGSEGV, shutting down...

This is all on a RH 7.3 system, using the MySQL options. My configure
options look like this:

./configure --with-mysql-lib=3D/usr/lib/mysql \
--with-mysql-inc=3D/usr/include/mysql --with-mysql-xdata \
--with-template-objects --with-template-extinfo --enable-DEBUG1

The 1.0b1 code compiles, installs, and runs fine with the same set of
.cfg files.

Strangeness indeed. Is it possible there's been a schema change or some
database corruption that is causing problems (although I've dropped the
database and recreated)?

Regards,

--- Gavin





This post was automatically imported from historical nagios-devel mailing list archives
Original poster: gadams@promisant.com
Guest
 

Return to Community Support

Who is online

Users browsing this forum: No registered users and 15 guests