<html><head><style type="text/css"></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><DIV> I checked disk space df -h all had 20gb or more space wise, and then sudo to the acct and ran the following: [nagios@dprmisnag572 var]$ /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg [nagios@dprmisnag572 var]$ ps -A |grep nagios 11916 ? 00:00:00 nagios 11919 ? 00:00:00 nagios 11926 ? 00:00:00 nagios 11933 ? 00:00:00 nagios 11940 ? 00:00:00 nagio s 11947 ? 00:00:00 nagios 11954 ? 00:00:00 nagios 11961 ? 00:00:00 nagios 11968 ? 00:00:00 nagios 11975 ? 00:00:00 nagios 11982 ? 00:00:00 nagios 11989 ? 00:00:00 nagios 11996 ? 00:00:00 nagios 12066 ? 00:00:00 nagios 12187 ? 00:00:00 nagios 12333 ? 00:00:00 nagios 12334 ? 00:00:00 nagios [nagios@dprmisnag572 var]$ ps -A |grep nagios</DIV> <DIV>nothing returned then it dies with the foloowing in the nagios.log file </DIV> <DIV>[1234914856] Nagios 3.0.6 starting... (PID=11915) [1234914856] Local time is Tue Feb 17 17:54:16 CST 2009 [1234914856] LOG VERSION: 2.0 [1234914856] Warning: Host 'HVFSMTL01' has no services associated with it! [1234914856] Warning: Host 'MTSD0029' has no services associated with it! [1234914856] Warning: Host 'MTSD0031' has no services associated with it! [1234914856] Warning: Host 'MTSD0032' has no services associated with it! [1234914856] Warning: Host 'dfwftp' has no services associated with it! [1234914856] Finished daemonizing... (New PID=11916) [1234914856] HOST DOWNTIME ALERT: clovertech;STARTED; Host has entered a period of scheduled downtime </DIV> <DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif"> <DIV style="FONT-SIZE: 13px; FONT-FAMILY: arial, helvetica, sans-serif"> <HR SIZE=1> From: Marc Powell <marc@ena.com> To: Nagios Users <nagios-users@lists.sourceforge.net> Sent: Tuesday, February 17, 2009 4:06:52 PM Subject: Re: [Nagios-users] nagios 3.06 installed but died On Feb 17, 2009, at 2:53 PM, Rusty Hall wrote: > The first post went out beofre I was finished sorry > I have had nagios 3.x up and running on this server for awhile! I > noticed this morning nagios was not running > [XXXX@dprmisnag572 nagios-3.0.6]# service nagios status > nagios is not running > I tried to resta rt using the validation > /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg > and I get back: > > Things look okay - No serious problems were detected during the pre- > flight check > so I restart and get > Running configuration check...done. > Stopping nagios: /etc/init.d/nagios: line 67: kill: (397) - No such > process > done. > Starting nagios: done. > then I go in and do ps -A |grep nagios and it returns nothing for > nagios > The user interface shows a pid for the process, and the checks are > scheduled just nothing running > > I have no clue what has happened I have validated permisions as far > as I can any help would be greatly appreciated Did you run out of disk space perhaps? Does something different happen if you start nagios in the foreground - as the nagios user, run '/usr/ local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg'. -- Marc ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD <A href="http://p.sf.net/sfu/XcvMzF8H" target=_blank>http://p.sf.net/sfu/XcvMzF8H</A> _______________________________________________ Nagios-users mailing list <A href="mailto:Nagios-users@lists.sourceforge.net" ymailto="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</A> <A href="https://l ists.sourceforge.net/lists/listinfo/nagios-users" target=_blank>https://lists.sourceforge.net/lists/listinfo/nagios-users</A> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </DIV></DIV></div></body></html>