I don't know what the problem is exactly, but I've been looking at it for days, i think it has to do with mysql support, or that xrddb stuff.. Here's the setup: I have 2 machines running nagios, but on one machine, obsess_over_services doesn't work (ocsd_command..). I tried swapping configs between the boxes, but that doesn't fix the problem, so I think it might actually be a bug somewhere in the nagios source.. I was playing with it, and i found out that if i build it with USE=-mysql on the problematic host, it suddenly works.. However, the doozy is that it works with USE=mysql on the other host already (this is nagios-core btw), so I am not sure what the problem is.. both have identical mysql configurations, and I can login to the nagios db on both machines.. I was thinking it could be related to mysq functionality, but I'm really note sure now.. Can anyone else verify this problem? Reproducible: Always Steps to Reproduce: 1. emerge nagios-core 2. try to use obsess_over_services=1 and an ocsd_command (that points to something in misccommands.cfg, and just doed like echo "fubar" >> /var/nagios/somefile 3. notice how it doesn't work perhaps.. then try to re-emerge with USE=-mysql on the WORKING machine (where USE=mysql has it working anyway) ortage 2.0.51-r3 (default-linux/x86/2004.3, gcc-3.3.4, glibc-2.3.4.20040 808-r1, 2.6.7-gentoo-r14 i686) ================================================================= System uname: 2.6.7-gentoo-r14 i686 Pentium III (Coppermine) Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux-headers-2.4.21-r1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig distlocks sandbox sfperms" GENTOO_MIRRORS="ftp://206.75.217.180/ ftp://206.75.217.205/ http://mir.zyrianes.net/gentoo/ ftp://mir.zyrianes.net/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 berkdb crypt curl doc gif innodb jpeg mysql ncurses nls pam pcre perl png python readline samba sasl spell ssl tcpd tiff truetype vhostsxml2 zlib" on the BROKEN machine (where USE==mysql is necessary): Portage 2.0.51-r3 (default-linux/x86/2004.3, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.7-gentoo-r14 i686) ================================================================= System uname: 2.6.7-gentoo-r14 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux-headers-2.4.21-r1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig distlocks sandbox sfperms" GENTOO_MIRRORS="http://151.204.184.67/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://localhost/gentoo-portage" USE="x86 berkdb crypt curl doc gif innodb jpeg mysql ncurses nls pam perl png python readline samba spell ssl tcpd tiff truetype vhosts xml2 zlib"
sounds and smells like a config problem to me. try building nagios with debug and follow the messages.
please attach debug info here and reopen.
I don't even have that machine/setup anymore. We moved to Nagios 2.0 at that company and haven't had any problems since then.