Greetings,
Are there any other masochists out there who run monitoring systems
on anything other than Intel kit atop some form of GNU operating
system? If so, I am specifically curious about the ido2db executable
and how well it behaves.
To set the stage, I'm running a Sun T1 105 with Solaris 10 Update 8,
gcc version 2.95.3, MySQL 5.0.51b, and Icinga 1.6.1. Basic Icinga
works like a charm, but when I try lighting off ido2db, the latter
segfaults. The debug output indicates that it's likely happening in
the ido2db_db_query() routine (note that I had to hack the source to
remove the reference to the instance name; a structure-passing issue
perhaps):
[1326578463.586885] [001.2] [pid=3049] [tid=1] ido2db_db_hello(25) conninfo_id
[1326578463.586973] [001.2] [pid=3049] [tid=1] ido2db_db_hello() get cached
object ids
[1326578463.587052] [001.2] [pid=3049] [tid=1] ido2db_get_cached_object_ids()
start
[1326578463.587179] [001.2] [pid=3049] [tid=1] ido2db_db_query() start
[1326578463.587593] [002.0] [pid=3049] [tid=1] SELECT object_id, objecttype_id,
name1, name2 FROM icinga_objects WHERE instance_id=0
[1326578463.608127] [001.2] [pid=3049] [tid=1] ido2db_child_sighandler() start
[1326578463.608253] [001.2] [pid=3049] [tid=1] Child caught signal '11' exiting
[1326578463.608463] [001.2] [pid=3049] [tid=1] ido2db_child_sighandler() end
The output in /var/log/userlog is slightly less than useful:
Jan 14 17:00:47 t1 ido2db[3049]: [ID 376905 user.info] IDO2DB 1.6.1
(12-02-2011) Copyright(c) 2005-2008 Ethan Galstad, Copyright(c) 2009-2011
Icinga Development Team (https://www.icinga.org)
Jan 14 17:00:47 t1 ido2db[3049]: [ID 255109 user.info] IDO2DB 1.6.1 starting...
(PID=3049)
Jan 14 17:01:03 t1 ido2db[3049]: [ID 973396 user.info] Client connected, data
available.
Jan 14 17:01:03 t1 ido2db[3049]: [ID 572053 user.info] Handling client
connection...
Jan 14 17:01:03 t1 ido2db[3049]: [ID 663190 user.info] Successfully connected
to mysql database
whereupon it conveniently dies. If I'm running ido2db as a daemon,
it restarts at a different PID, but the outcome remains the same.
The icinga.log proper merely shows that the database connection has
gone away.
The "icinga_instances" table does get populated, as does the
"icinga_conninfo" one, but nothing else.
I have not tried this on an Intel platform, but suspect that it all
"just works" there as other folks seem to be having luck with it. I
recall putting up a big fight with ndoutils-1.4b9, eventually getting
it to work, but the ido2db code looks like the problems I found in
ndoutils had been fixed.
Ideas? C code should "just work" no matter what platform it's
compiled on, so there may be hidden issues in the mix as well.
Cheers!
+------------------------------------------------+---------------------+
| Carl Richard Friend (UNIX Sysadmin) | West Boylston |
| Minicomputer Collector / Enthusiast | Massachusetts, USA |
| mailto:[email protected] +---------------------+
| http://users.rcn.com/crfriend/museum | ICBM: 42:22N 71:47W |
+------------------------------------------------+---------------------+
------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/icinga-users
