Hi, I switched idoutils from unix socket to tcp socket and back again, but quite frequently there is no ido process at all. I have "monit" looking for a process, and it restarts ido2db very often (sometimes every minute, sometimes it runs for hours).
>From /var/log/icinga/icinga.log: ---snip--- [1372675184] Event broker module '/usr/lib/icinga/idomod.so' deinitialized successfully. [1372675185] idomod: IDOMOD 1.9.2 (06-30-2013) Copyright(c) 2005-2008 Ethan Galstad, Copyright(c) 2009-2013 Icinga Development Team (https://www.icinga.org) [1372675185] idomod: Successfully connected to data sink. 52 queued items to flush. [1372675185] idomod: Successfully flushed 52 queued items to data sink. [1372675185] Event broker module 'IDOMOD' version '1.9.2' from '/usr/lib/icinga/idomod.so' initialized successfully. [1372675185] idomod: Error writing to data sink! Some output may get lost... [1372675185] idomod: Please check remote ido2db log, database connection or SSL Parameters [1372675203] idomod: Successfully reconnected to data sink! 0 items lost, 851 queued items to flush. [1372675203] idomod: Successfully flushed 851 queued items to data sink. [1372675205] idomod: Error writing to data sink! Some output may get lost... ---pins--- How can I debug this? In idomod.cfg, there is debug_level=-1 and debug_verbosity=2, and idomod.debug only has lines like ---snip--- [1370910856.084080] [001.2] [pid=12257] idomod_broker_data() end [1370910856.084096] [001.2] [pid=12257] idomod_broker_data() start [1370910856.084113] [001.2] [pid=12257] idomod_write_to_sink() start [1370910856.084130] [001.2] [pid=12257] idomod_write_to_sink( 203: 1=400 2=0 3=0 4=1370910856.84095 117=1370910856.84095 33=0.0 123=15 14=/usr/lib/nagios/plugins/eventhandlers/distributed-monitoring/ufz_obsessive_svc_handler vsap2hre '' '' 32=0 42=0.00000 110=0 95= 125= 999 ) [1372664965.971717] [001.2] [pid=31367] idomod_open_debug_log() [1372664989.738977] [001.2] [pid=32100] idomod_open_debug_log() [1372673870.742982] [001.2] [pid=21635] idomod_open_debug_log() [1372674310.286735] [001.2] [pid=24876] idomod_open_debug_log() [1372675185.539154] [001.2] [pid=30800] idomod_open_debug_log() ---pins--- In ido2db.debug, I see ---snip--- [1372676960.162207] [001.2] [pid=9936] [tid=140709814966016] ido2db_daemonize() start [1372676960.162381] [001.2] [pid=9936] [tid=140709814966016] ido2db_daemonize() parent process goes away [1372676960.162413] [001.2] [pid=9936] [tid=140709814966016] ido2db_free_program_memory() start [1372676960.162448] [001.2] [pid=9936] [tid=140709814966016] ido2db_free_program_memory() end [1372676960.162769] [001.2] [pid=9937] [tid=140709814966016] ido2db_daemonize() child forks again [1372676960.162943] [001.2] [pid=9937] [tid=140709814966016] ido2db_daemonize() first child process goes away [1372676960.162970] [001.2] [pid=9937] [tid=140709814966016] ido2db_free_program_memory() start [1372676960.162984] [001.2] [pid=9937] [tid=140709814966016] ido2db_free_program_memory() end [1372676960.163340] [001.2] [pid=9938] [tid=140709814966016] ido2db_daemonize() grandchild continues and becomes session leader [1372676960.163482] [001.2] [pid=9938] [tid=140709814966016] ido2db_daemonize() end ---pins--- All this is not a problem only with 1.9.2, it was there with 1.9.1 at least... Regards, Werner -- ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ icinga-users mailing list icinga-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/icinga-users
