[Nagios-users] Graph url being changed.
I have installed Fedora 17 and copied my Fedora 15 configuration files over. Nagios works, data is collected. However, when I click the icon to display pnp4nagios graph I find my url has been changed and of course it can't find what it is suppose to display. Below you can see under Fedroa 17 label that the next line has changed. Under Fedora 15 label, it is unchanged. I can image something in configuration has changed, but what? I am using the same nagios.conf in httpd/conf.d/. FEDORA 17 172.23.93.249 - nagios [08/Jun/2012:14:01:26 -0600] GET /nagios/pnp4nagios/index.php?host=comcastsrv=Packet%20Loss HTTP/1.1 302 90 http://172.23.93.6/nagios/cgi-bin//status.cgi?host=all; Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 172.23.93.249 - nagios [08/Jun/2012:14:01:26 -0600] GET /nagios/pnp4nagios/graph HTTP/1.1 404 298 http://172.23.93.6/nagios/cgi-bin//status.cgi?host=all; Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 FEDORA 15 172.23.93.249 - nagios [08/Jun/2012:14:01:29 -0600] GET /nagios/pnp4nagios/index.php?host=comcastsrv=Packet%20Loss HTTP/1.1 200 12319 http://172.23.93.7/nagios/cgi-bin//status.cgi?host=all; Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 172.23.93.249 - nagios [08/Jun/2012:14:01:30 -0600] GET /nagios/pnp4nagios/index.php?host=comcastsrv=Packet_Losssource=2view=2end=1339185689display=image HTTP/1.1 200 12938 http://172.23.93.7/nagios/pnp4nagios/index.php?host=comcastsrv=Packet%20Loss Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Thank you, Durwin This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient(s), please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message.-- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ 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
[Nagios-users] Retry issue fail to notify
I have the notifications using a script calling festival. My initial
configuration work and festival voice was heard. But I wanted to change
it so it would retry 3 times before reporting.
This worked. I heard festival for each change it state.
max_check_attempts 1
normal_check_interval 2
retry_interval 0
This did *not* work. I never heard festival.
max_check_attempts 3
normal_check_interval 2
retry_interval 15s
What is wrong with the way I did it?
define service{
namegeneric-service ; The
'name' of this service template
active_checks_enabled 1 ; Active
service checks are enabled
passive_checks_enabled 1 ; Passive
service checks are enabled/accepted
parallelize_check 1 ; Active
service checks should be parallelized (disabling this can lead to major
performance problems)
obsess_over_service 1 ; We
should obsess over this service (if necessary)
check_freshness 0 ; Default
is to NOT check service 'freshness'
event_handler_enabled 1 ; Service
event handler is enabled
event_handler service-notify
flap_detection_enabled 1 ; Flap
detection is enabled
failure_prediction_enabled 1 ; Failure
prediction is enabled
process_perf_data 1 ; Process
performance data
retain_status_information 1 ; Retain
status information across program restarts
retain_nonstatus_information1 ; Retain
non-status information across program restarts
is_volatile 0 ; The
service is not volatile
check_period24x7; The
service can be checked at any time of the day
max_check_attempts 3 ; Re-check
the service up to 1 times in order to determine its final (hard) state
normal_check_interval 2 ; Check
the service every 2 minutes under normal conditions
retry_interval 15s ; Re-check
the service every minute until a hard state can be determined
contact_groups festival;
Notifications get sent out to everyone in the 'admins' group
notifications_enabled 1 ; Service
notifications are enabled
notification_optionsw,u,c,r ; Send
notifications about warning, unknown, critical, and recovery events
notification_interval 1 ;
Re-notify about service problems every hour
notification_period 24x7;
Notifications can be sent out at any time
register0 ; DONT
REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
}
Durwin F. De La Rue
Management Sciences, Inc.
6022 Constitution Ave. NE
Albuquerque, NM 87110
Phone (505) 255-8611
This email message and any attachments are for the sole use of the
intended recipient(s) and may contain proprietary and/or confidential
information which may be privileged or otherwise protected from
disclosure. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient(s), please contact the
sender by reply email and destroy the original message and any copies of
the message as well as any attachments to the original message.--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb___
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
Re: [Nagios-users] Retry issue fail to notify
Jim Avery j...@jimavery.me.uk wrote on 02/18/2011 12:13:30 PM: Jim Avery j...@jimavery.me.uk 02/18/2011 12:13 PM Please respond to Nagios Users List nagios-users@lists.sourceforge.net To Nagios Users List nagios-users@lists.sourceforge.net cc Subject Re: [Nagios-users] Retry issue fail to notify On 18 February 2011 14:31, dur...@mgtsciences.com wrote: I have the notifications using a script calling festival. My initial configuration work and festival voice was heard. But I wanted to change it so it would retry 3 times before reporting. This worked. I heard festival for each change it state. max_check_attempts 1 normal_check_interval 2 retry_interval 0 This did *not* work. I never heard festival. max_check_attempts 3 normal_check_interval 2 retry_interval 15s What is wrong with the way I did it? I don't know for certain without testing, but does it work if you change 15s to 1. Also, do you see the service go from a soft state to a hard state after the 3rd check? Take a look at the alert history screen for that service to see better what has (or hasn't) happened. Also if you look at the notification history screen does it tell you a notification was sent? Changing 15s to 1 does work. I see a soft state during the first check. It goes to hard state and I get festivals notification after 3 check (3 minutes later). So this brings me to ask the question, is there no way to reduce the retry_interval units to seconds? Other configuration settings have that option. I see no need to wait long for a retry (at least no longer then a timeout takes)? Thank you for your reply, Durwin This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient(s), please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message.-- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ 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
