Search found 10 matches
- Thu Mar 13, 2014 11:46 am
- Forum: Open Source Nagios Projects
- Topic: Timeout without warning?
- Replies: 6
- Views: 3245
Re: Timeout without warning?
I think you can - thank you for your help!!!
- Thu Mar 13, 2014 1:30 am
- Forum: Open Source Nagios Projects
- Topic: Timeout without warning?
- Replies: 6
- Views: 3245
Re: Timeout without warning?
As I have written the grep -i timeout output it has become reasonable for me service_check_timeout=90 and a ... -t 99 could not work together very well... (and now the "but" :) ) but until 4.0.3 this raised no problems. I will lower the -t value, it is more logical in the way 4.0.3 handles...
- Wed Mar 12, 2014 2:46 pm
- Forum: Open Source Nagios Projects
- Topic: Timeout without warning?
- Replies: 6
- Views: 3245
Re: Timeout without warning?
here you go 
lg
Martin
Code: Select all
root@nagios:/opt/nagios/etc# grep -i timeout nagios.cfg
# TIMEOUT VALUES
service_check_timeout=90
host_check_timeout=30
event_handler_timeout=240
notification_timeout=120
ocsp_timeout=5
perfdata_timeout=5
Martin
- Wed Mar 12, 2014 5:16 am
- Forum: Open Source Nagios Projects
- Topic: Timeout without warning?
- Replies: 6
- Views: 3245
Timeout without warning?
Hi! [12-03-2014 09:50:07] wproc: Core Worker 4124: job 95209 (pid=18245): Dormant child reaped Informational Message[12-03-2014 09:50:02] wproc: Core Worker 4124: Failed to reap child with pid 18245. Next attempt @ 1394614207.572255 Informational Message[12-03-2014 09:50:02] wproc: Core Worker 4124:...
- Wed Mar 12, 2014 1:30 am
- Forum: Open Source Nagios Projects
- Topic: Nagios & Apache problem
- Replies: 11
- Views: 5565
Re: Nagios & Apache problem
Hi! Where are using the 4.0.3 Core version. I tested the floating intervals define service{ use switch_general_template,graphed-service host_name switch418 service_description Switch418_10_416 check_interval 0.3 check_command check_hpinterface!10.254.4.18!10!1024!90!95 } and they were working, the l...
- Tue Mar 11, 2014 2:44 pm
- Forum: Open Source Nagios Projects
- Topic: Nagios & Apache problem
- Replies: 11
- Views: 5565
Re: Nagios & Apache problem
Good point - but its not very simple for the administrator that nagios itself is running but the webinterface not (with a not very useful message) - maybe make a "strong" warning while checking the nagios config during startup that floating values could lead to web-interface problems... We...
- Tue Mar 11, 2014 2:15 pm
- Forum: Open Source Nagios Projects
- Topic: Nagios & Apache problem
- Replies: 11
- Views: 5565
Re: Nagios & Apache problem
I have found the solution - it is possibly a bug in nagios itself: (and ... its reproducable) I found the same "error" on my old nagios system and on a completly new system - when i change the parameter retry_check_interval from integer to float (in my case 1 to 0.5) define service{ use ge...
- Mon Feb 10, 2014 12:19 pm
- Forum: Open Source Nagios Projects
- Topic: Nagios & Apache problem
- Replies: 11
- Views: 5565
Re: Nagios & Apache problem
Hi, yes I restarted nagios, i have restarted the whole server too. I installed nagios from scretch, I actived a backup from last week, i checked the user and the usergroups (www-data group and user). no effect. There are no hints in the log - i tested the status.cgi and tac.cgi with the www-data use...
- Mon Feb 10, 2014 11:31 am
- Forum: Open Source Nagios Projects
- Topic: Nagios & Apache problem
- Replies: 11
- Views: 5565
Re: Nagios & Apache problem
Thank you for the answer -
as i posted ... yes nagios is running (its collecting data, sending warning mails/sms, etc) ...
as i posted ... yes nagios is running (its collecting data, sending warning mails/sms, etc) ...
- Mon Feb 10, 2014 9:02 am
- Forum: Open Source Nagios Projects
- Topic: Nagios & Apache problem
- Replies: 11
- Views: 5565
Nagios & Apache problem
Hi! I am using nagios 4.02 on an Ubuntu 12.04 - both were running for a longer period of time without any issues. Todays restart of nagios and apache2 (i configured a new iftraffic check) made nagios running and apache2 running, but each cgi called from the web interface ends up in: Error: Could not...