On 08/05/2013 04:09 PM, Daniel Petersen wrote: > On 08/05/2013 03:54 PM, Michael Friedrich wrote: >> On 05.08.2013 15:47, Daniel Petersen wrote: >>> On 08/05/2013 03:19 PM, Michael Friedrich wrote: >>>> On 05.08.2013 15:11, Daniel Petersen wrote: >>>>>> >>>>>> filesystem full? >>>>>> >>>>> Not this time:-) Plenty of space on the /tmp partition, and all the >>>>> others as well >>>> >>>> inode problem? >>> No, all the filesystems are down around 1% inode usage. >>> >>> any clean job for /tmp by an external application running? >>> >>> No, we only clean out /tmp on reboot. >> >> ok, one more guess - multiple icinga daemons running? >> >> to verify - # service icinga stop ; ps aux | grep icinga >> >>>> >>>> btw - which icinga core version? >>> >>> 1.9.1-1~ppa1~precise (ubuntu package) >>>> >>>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Get your SQL database under version control now! >>> Version control is standard for application code, but databases havent >>> caught up. So what steps can you take to put your SQL databases under >>> version control? Why should you start doing it? Read more to find out. >>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> icinga-users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/icinga-users >> >> > #service icinga stop ; ps aux | grep icinga > * Stopping icinga monitoring daemon icinga > Waiting for icinga daemon to die.. > [ OK ] > nagios 2892 0.0 0.0 107560 796 ? Ss Aug01 1:18 > /usr/sbin/ido2db -c /etc/icinga/ido2db.cfg > root 44164 0.0 0.0 12112 912 pts/1 S+ 16:04 0:00 grep icinga > > and then starting back up I get: > > # service icinga start > * Starting icinga monitoring daemon icinga > > > [ OK ] > root@radar:/etc/apt# ps aux | grep icinga > nagios 2892 0.0 0.0 107560 4596 ? Ssl Aug01 1:18 > /usr/sbin/ido2db -c /etc/icinga/ido2db.cfg > nagios 44243 26.5 0.0 121600 4428 ? Rl 16:06 0:01 > /usr/sbin/ido2db -c /etc/icinga/ido2db.cfg > nagios 44246 15.2 0.0 88528 20472 ? SNsl 16:06 0:00 > /usr/sbin/icinga -d /etc/icinga/icinga.cfg > nagios 44273 0.0 0.0 54104 10236 ? SN 16:06 0:00 > /usr/sbin/icinga -d /etc/icinga/icinga.cfg > nagios 44323 0.0 0.0 62604 10280 ? SN 16:06 0:00 > /usr/sbin/icinga -d /etc/icinga/icinga.cfg > root 44491 0.0 0.0 12112 908 pts/1 S+ 16:06 0:00 grep icinga > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > icinga-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/icinga-users > so it look like when the icinga service is running, there were in this instance 3 icinga processes and 2 ido2db processes.
I know with some servers, such as httpd for example, it's normal for many processes to launch, but is this expected behavior for icinga? ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ icinga-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/icinga-users
