| I want to say this is a FAQ, as I seem to recall seeing something about this behavior before, but I didn't find anything with a quick search, and I don't thing there was any real solution posted, so I'm going to ask now. I am running Nagios 3.2.0 on OpenBSD 4.6. I have found that from time to time nagios will simply stop updating. No errors will be produced, and the nagios log will show normal operation right up until it stops updating. After that, nothing. I have implemented a work around of a script that checks for this and restarts nagios if needed, but obviously this is a sub-optimal solution. Has anyone seen this behavior before that might have some idea how I can fix it? Or does anyone have a suggestion as to how I can go about debugging it? Thanks. ----------------------------------------------- Israel Brewster Computer Support Technician II Frontier Flying Service Inc. 5245 Airport Industrial Rd Fairbanks, AK 99709 (907) 450-7250 x293 ----------------------------------------------- |
BEGIN:VCARD VERSION:3.0 N:Brewster;Israel;;; FN:Israel Brewster ORG:Frontier Flying Service;MIS TITLE:PC Support Tech II EMAIL;type=INTERNET;type=WORK;type=pref:isr...@frontierflying.com TEL;type=WORK;type=pref:907-450-7293 item1.ADR;type=WORK;type=pref:;;5245 Airport Industrial Wy;Fairbanks;AK;99701; item1.X-ABADR:us CATEGORIES:General X-ABUID:36305438-95EA-4410-91AB-45D16CABCDDC\:ABPerson END:VCARD
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
