Re: [Nagios-users] "No Route to Host" error - ssh-key exchange issue even if plugin checks work?
On Nov 10, 2010, at 12:13 PM, Jonathan Wiggins wrote: > I'm stuck troubleshooting an error message in the Service Status Details, > where a monitored host is being reported as "No Route to Host". > > I can do remote plugin tests from the Nagios server to the monitored node > without any problems, but referencing this page: > http://www.troubleshootingwiki.org/Troubleshooting_Nagios_3.0 I see a > paragraph about testing SSH key-exchange. > > Nagios Server = 10.0.100.130 > monitored node = 10.0.100.143 > > when I do an "ssh - 10.0.100.130" from the monitored node, it goes > straight through, no login prompt. When the reverse is attempted: "ssh - > 10.0.100.143" from Nagios box, I consistently get prompted for login. I was > recommended to use DSA instead of RSA, but that made no difference. > > I've appended the contents of both id_rsa.pub and id_dsa.pub to the > "authorized_keys" (and "known_hosts") files the exact same way to and from > each box respectively. Of course my tests on 2 test systems worked > perfectly, but I'm missing something with this setup. > > Additionally, if I do an NRPE check from Nagios > monitored node, it > completes successfully. > > /usr/local/nagios/libexec/check_tcp -H 10.0.100.143 -p 5666 > TCP OK - 0.000 second response time on port > 5666|time=0.000361s;0.00;0.00;0.00;10.00 > > checking logs on monitored node: > > grep nrpe /var/log/messages > > > /var/log/messages:Nov 10 12:01:26 monitorednode xinetd[5672]: START: nrpe > pid=8607 from=10.0.100.130 > /var/log/messages:Nov 10 12:01:26 monitorednode nrpe[8607]: Error: Could not > complete SSL handshake. 5 > /var/log/messages:Nov 10 12:01:26 monitorednode xinetd[5672]: EXIT: nrpe > status=0 pid=8607 duration=0(sec) > /var/log/messages:Nov 10 12:03:29 monitorednode xinetd[5672]: START: nrpe > pid=9220 from=10.0.100.130 > /var/log/messages:Nov 10 12:03:29 monitorednode nrpe[9220]: Error: Could not > complete SSL handshake. 5 > /var/log/messages:Nov 10 12:03:29 monitorednode xinetd[5672]: EXIT: nrpe > status=0 pid=9220 duration=0(sec) > > "Error could not complete SSL handshake" seems to confirm my suspicions > about the SSH key-exchange > > Ok, i've solved the SSH key-exchange part of my problem (criss-crossed id_rsa.pub keys or something) - so I have that piece figured out. But the "No Route to Host" message is still visible in Service Host Details for my monitored node. so.. am able to run the following against remote host: /usr/local/nagios/libexec/check_tcp -H 10.0.100.143 -p 5666 TCP OK - 0.000 second response time on port 5666|time=0.000361s;0.00;0.00;0.00;10.00 and this: ssh 10.0.100.143 /usr/local/nagios/libexec/check_procs PROCS OK: 603 processes I see this in the messages files: Nov 9 00:00:00 nagiosbox nagios: CURRENT SERVICE STATE: monitorednode;Home Page;CRITICAL;HARD;1;No route to host Nov 10 00:00:00 nagiosbox nagios: CURRENT HOST STATE: monitorednode;UP;HARD;1;PING OK - Packet loss = 0%, RTA = 0.21 ms Nov 10 00:00:00 nagiosbox nagios: CURRENT SERVICE STATE: monitorednode;Home Page;CRITICAL;HARD;1;No route to host which looks like there is no packet loss on the PING to the host, but then it shows No Route To Host Thanks again for the assistance. -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-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
Re: [Nagios-users] Nagios Notification State Issue
Thanks for the reply... I haven't changed any of the setting for retention since the system was deployed. I tried deleting the retention.dat and status.dat and restarting and the problem persists. I even tried different user perms on the file and no go... Here are my settings nagios.conf: retain_state_information=1 state_retention_file=/usr/local/nagios-3.2.1/var/retention.dat retention_update_interval=60 use_retained_program_state=1 use_retained_scheduling_info=1 retained_host_attribute_mask=0 retained_service_attribute_mask=0 retained_process_host_attribute_mask=0 retained_process_service_attribute_mask=0 retained_contact_host_attribute_mask=0 retained_contact_service_attribute_mask=0 If I am not mistaken I believe all of that is set by default... I don't see any status.sav files. Just the status.dat... On 11/10/10 6:00 AM, "Andreas Ericsson" wrote: On 11/10/2010 01:25 PM, Dale Wilhelm wrote: > ( this time with a proper subject ) > > Hello All... > > I am seeing an odd problem host status and retention after reloads > and I am wondering if anyone else has seen this and possibly knows of > a fix it... When I disable notifications for a host via the UI the > command completes and I see that notifications are indeed disabled, > notifications stop, etc... However when I reload Nagios the > notifications are re-enabled. This is only showing up with host > checks, service check state is retained after a reload. I can see the > status.dat file change however the retention.dat always stays the > same ( notifications_enabled=0 ). I am not even sure if that is it or > not, or if this is a permissions issue or some kind. Also, this has > worked with this build in the past. It stopped working a short time > ago... Any help would be greatly appreciated... > Have you disabled retention data lately but kept an old retention data file around? Normally, retention data should be saved in a file named status.sav. -- Andreas Ericsson andreas.erics...@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-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
[Nagios-users] "No Route to Host" error - ssh-key exchange issue even if plugin checks work?
I'm stuck troubleshooting an error message in the Service Status Details, where a monitored host is being reported as "No Route to Host". I can do remote plugin tests from the Nagios server to the monitored node without any problems, but referencing this page: http://www.troubleshootingwiki.org/Troubleshooting_Nagios_3.0 I see a paragraph about testing SSH key-exchange. Nagios Server = 10.0.100.130 monitored node = 10.0.100.143 when I do an "ssh - 10.0.100.130" from the monitored node, it goes straight through, no login prompt. When the reverse is attempted: "ssh - 10.0.100.143" from Nagios box, I consistently get prompted for login. I was recommended to use DSA instead of RSA, but that made no difference. I've appended the contents of both id_rsa.pub and id_dsa.pub to the "authorized_keys" (and "known_hosts") files the exact same way to and from each box respectively. Of course my tests on 2 test systems worked perfectly, but I'm missing something with this setup. Additionally, if I do an NRPE check from Nagios > monitored node, it completes successfully. /usr/local/nagios/libexec/check_tcp -H 10.0.100.143 -p 5666 TCP OK - 0.000 second response time on port 5666|time=0.000361s;0.00;0.00;0.00;10.00 checking logs on monitored node: grep nrpe /var/log/messages /var/log/messages:Nov 10 12:01:26 monitorednode xinetd[5672]: START: nrpe pid=8607 from=10.0.100.130 /var/log/messages:Nov 10 12:01:26 monitorednode nrpe[8607]: Error: Could not complete SSL handshake. 5 /var/log/messages:Nov 10 12:01:26 monitorednode xinetd[5672]: EXIT: nrpe status=0 pid=8607 duration=0(sec) /var/log/messages:Nov 10 12:03:29 monitorednode xinetd[5672]: START: nrpe pid=9220 from=10.0.100.130 /var/log/messages:Nov 10 12:03:29 monitorednode nrpe[9220]: Error: Could not complete SSL handshake. 5 /var/log/messages:Nov 10 12:03:29 monitorednode xinetd[5672]: EXIT: nrpe status=0 pid=9220 duration=0(sec) "Error could not complete SSL handshake" seems to confirm my suspicions about the SSH key-exchange i'm quite junior on this so I really appreciate everyones patience and thanks in advance-- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-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
Re: [Nagios-users] different notification_intervals by contact
Escalations are a little pesky to get working correctly.
Here is an example.
define serviceescalation{
host_name .*
service_description .*
first_notification 1
last_notification 0
notification_interval 60
contact_groups admins
escalation_period 24x7
escalation_options w,u,c,r
}
define serviceescalation{
host_name .*
servicegroup_name
disks,dns,firewall,load,mailq,processes,sendmail,ssh,time
first_notification 2
last_notification 2
notification_interval 60
contact_groups support
escalation_period 24x7
escalation_options w,u,c,r
}
define hostescalation{
host_name .*
first_notification 1
last_notification 0
notification_interval 60
contact_groups admins
escalation_period 24x7
escalation_options d,u,r
}
define hostescalation{
host_name .*
first_notification 2
last_notification 2
notification_interval 60
contact_groups support
escalation_period 24x7
escalation_options d,u,r
}
This alerts admins after the interval set on the host/service (5 mins) and
then every hour. On the second alert (5+60 mins) it will alert support (for
the services listed) just the once but then continue to alert admins every
hour.
At least that's what I think happens, I'm never sure with esculations!
For this to work I had to enable regular expressions and set up service
groups.
I have a feeling I also removed the following from my hosts definitions as
well.
contact_groups admins
notification_interval 30
notification_period 24x7
notification_options d,r
Hope that helps and gives you some ideas.
Duncan
From: Frost, Mark {PBC} [mailto:mark.fro...@pepsico.com]
Sent: 10 November 2010 17:26
To: 'Nagios Users List'
Subject: [Nagios-users] different notification_intervals by contact
So we're setting up some Nagios checks for a new team and they're asking for
something new that I'm not really sure we can do with Nagios. For any
production alerts they want to receive pager alerts every 15 minutes and
e-mail alerts every 60 minutes. Since each host/service definition has only
a single notification_interval setting and contact definitions don't allow a
notification_interval setting, I don't see how this can be done within that
context.
We don't currently use escalations for anything, but I've been staring at
them and trying to figure out how that might work for us. In terms of using
escalations to solve this problem I'm struck by several issues:
- I'd be trying to use escalations to setup an indefinite pattern, not a
system where there's an last_notification where everyone gets the
notifications.
- I have to do this for a lot of hosts/services and it doesn't look like I
can wildcard service_descriptions (tried it and it failed).
My other thought is to just have 2 checks for the same service where check A
has the 15-minute notification_interval and goes to pagers and check B has a
1-hour notification_interval and goes to e-mail. And that's for a lot of
services. I can't really do the duplicate checks on hosts. But either way,
you know, "yuck".
I keep thinking there's some easier more obvious solution that's eluding me
to this. Is something that anyone else has solved? I'm inclined to tell
them that we can't do this and get them to unify on one
notification_interval like everyone else, but before I do, I thought I'd
ask.
Thanks
Mark
--
This message has been scanned for viruses and
dangerous content by
[Nagios-users] different notification_intervals by contact
So we're setting up some Nagios checks for a new team and they're asking for something new that I'm not really sure we can do with Nagios. For any production alerts they want to receive pager alerts every 15 minutes and e-mail alerts every 60 minutes. Since each host/service definition has only a single notification_interval setting and contact definitions don't allow a notification_interval setting, I don't see how this can be done within that context. We don't currently use escalations for anything, but I've been staring at them and trying to figure out how that might work for us. In terms of using escalations to solve this problem I'm struck by several issues: - I'd be trying to use escalations to setup an indefinite pattern, not a system where there's an last_notification where everyone gets the notifications. - I have to do this for a lot of hosts/services and it doesn't look like I can wildcard service_descriptions (tried it and it failed). My other thought is to just have 2 checks for the same service where check A has the 15-minute notification_interval and goes to pagers and check B has a 1-hour notification_interval and goes to e-mail. And that's for a lot of services. I can't really do the duplicate checks on hosts. But either way, you know, "yuck". I keep thinking there's some easier more obvious solution that's eluding me to this. Is something that anyone else has solved? I'm inclined to tell them that we can't do this and get them to unify on one notification_interval like everyone else, but before I do, I thought I'd ask. Thanks Mark -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-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
Re: [Nagios-users] Time frame for Monitoring Performance?
Please don't hijack threads. It's terribly bad form. On 11/10/2010 04:27 PM, Paul M. Dubuc wrote: > I'm using Nagios 3.2.3. I'm wondering what time frame is used for the > measurements shown in the Monitoring Performance box on the Tactical Overview > display. In particular, are the execution times (min. max. avg.) measured > over the last hour, 10 minutes, or what? I can't find any information on this > in the documents. > The execution times are measured over the last executed check for each host and services. Latency is calculated the exact same way. -- Andreas Ericsson andreas.erics...@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-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
[Nagios-users] Time frame for Monitoring Performance?
I'm using Nagios 3.2.3. I'm wondering what time frame is used for the measurements shown in the Monitoring Performance box on the Tactical Overview display. In particular, are the execution times (min. max. avg.) measured over the last hour, 10 minutes, or what? I can't find any information on this in the documents. Thanks, Paul Dubuc -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-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
Re: [Nagios-users] Nagios Notification State Issue
On 11/10/2010 01:25 PM, Dale Wilhelm wrote: > ( this time with a proper subject ) > > Hello All... > > I am seeing an odd problem host status and retention after reloads > and I am wondering if anyone else has seen this and possibly knows of > a fix it... When I disable notifications for a host via the UI the > command completes and I see that notifications are indeed disabled, > notifications stop, etc... However when I reload Nagios the > notifications are re-enabled. This is only showing up with host > checks, service check state is retained after a reload. I can see the > status.dat file change however the retention.dat always stays the > same ( notifications_enabled=0 ). I am not even sure if that is it or > not, or if this is a permissions issue or some kind. Also, this has > worked with this build in the past. It stopped working a short time > ago... Any help would be greatly appreciated... > Have you disabled retention data lately but kept an old retention data file around? Normally, retention data should be saved in a file named status.sav. -- Andreas Ericsson andreas.erics...@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-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
Re: [Nagios-users] SMS Foxbox
Just a note about volume, that is standard for any sim based device as it is in effect the same as sending them via a phone and each message takes a few seconds to send. You could set up a bank of gsm modems like the maestro eco 100 with software of your choice to get round this (even your own software as it is pretty easy to do). As Mark points out an external gateway is a good alternative (like aql.com, clickatell), perhaps using that for most messages and using the fox box for messages when your internet connectivity fails. Duncan -Original Message- From: Mark Young [mailto:m...@zarzax.com] Sent: 10 November 2010 03:08 To: Nagios Users List Subject: Re: [Nagios-users] SMS Foxbox On Nov 5, 2010, at 4:44 AM, Rutger Blom wrote: > Hello list, > > I was wondering if any of you have experience with using the SMS Foxbox and Nagios? Are you satisfied with the product? Is there any other solution you would recommend instead? > > http://www.nagios.org/products/notification/foxbox/ > > /Rutger Hi Rutger, I originally demoed the SMS FoxBox while working at Nagios Enterprises in 2007. My original integration attempt was written up on the wiki http://wiki.nagios.org/index.php/ACME_SYSTEMS_SMSFoxBox. The device is a small embedded linux server that takes a SIM card and has a external antenna. *It is very important that it has cell (GSM) reception. Also my knowledge of the device is now a few years old. My experience was that it worked very well. It has the limitation that it can only send one message at a time (one GSM modem). My script from the wiki page used the web api, where you use a web address to send the message body and recipient. This was only able to handle a few requests before it overwhelmed the small web server. I later created another script that uploaded messages to a spool directory on the device (using SCP). This was able to handle a large number of messages but it takes a long time for the device to process messages. I would say if you have over 20 notification recipients you may want to look for an alternative. There are web services that handle these requests (AlarmTilt) or many people now use email addresses provided by cell providers that text phones (http://www.emailtextmessages.com/). I hope that this helps you out. Good luck in your quest! Mark Young -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-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 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-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
[Nagios-users]
Hello All... I am seeing an odd problem host status and retention after reloads and I am wondering if anyone else has seen this and possibly knows of a fix it... When I disable notifications for a host via the UI the command completes and I see that notifications are indeed disabled, notifications stop, etc... However when I reload Nagios the notifications are re-enabled. This is only showing up with host checks, service check state is retained after a reload. I can see the status.dat file change however the retention.dat always stays the same ( notifications_enabled=0 ). I am not even sure if that is it or not, or if this is a permissions issue or some kind. Also, this has worked with this build in the past. It stopped working a short time ago... Any help would be greatly appreciated... Nagios Version: 3.2.1 ( perms ) -rw--- 1 nagios nagios 1003961 2010-11-10 03:47 retention.dat -rw-r--r-- 1 nagios nagios 757630 2010-11-10 03:47 objects.cache -rw-r--r-- 1 nagios nagios 80887 2010-11-10 04:05 nagios.log -rw-rw-r-- 1 nagios nagios 1000332 2010-11-10 04:05 status.dat Regards, Dale -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-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
Re: [Nagios-users] SMS Foxbox
Thank you very much for the information. In our case we only have one SMS recipient so it should work fine. /Rutger On Wed, Nov 10, 2010 at 4:07 AM, Mark Young wrote: > On Nov 5, 2010, at 4:44 AM, Rutger Blom wrote: > > > Hello list, > > > > I was wondering if any of you have experience with using the SMS Foxbox > and Nagios? Are you satisfied with the product? Is there any other solution > you would recommend instead? > > > > http://www.nagios.org/products/notification/foxbox/ > > > > /Rutger > > Hi Rutger, > > I originally demoed the SMS FoxBox while working at Nagios Enterprises in > 2007. My original integration attempt was written up on the wiki > http://wiki.nagios.org/index.php/ACME_SYSTEMS_SMSFoxBox. The device is a > small embedded linux server that takes a SIM card and has a external > antenna. *It is very important that it has cell (GSM) reception. Also my > knowledge of the device is now a few years old. > > My experience was that it worked very well. It has the limitation that it > can only send one message at a time (one GSM modem). My script from the > wiki page used the web api, where you use a web address to send the message > body and recipient. This was only able to handle a few requests before it > overwhelmed the small web server. I later created another script that > uploaded messages to a spool directory on the device (using SCP). This was > able to handle a large number of messages but it takes a long time for the > device to process messages. I would say if you have over 20 notification > recipients you may want to look for an alternative. There are web services > that handle these requests (AlarmTilt) or many people now use email > addresses provided by cell providers that text phones ( > http://www.emailtextmessages.com/). > > I hope that this helps you out. Good luck in your quest! > > Mark Young > > > > > -- > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-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 > -- Rutger Blom Luzernvägen 14 227 38 LUND Sweden Tel. +46 763 46 99 44 www.rutgerblom.com about.me/rutgerblom -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-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
Re: [Nagios-users] SMS Foxbox
Title: Untitled Document Am 10.11.2010 10:09, schrieb Rutger Blom: Thank you very much for the information. In our case we only have one SMS recipient so it should work fine. Another option is to use a GSM modem (or old cellphone with serial cable) and the GPLed software "SMS server tools" ( http://smstools3.kekekasvi.com/ ) which gives you a nice SMS daemon. You can send messages then by dropping them in a spool directory. The message format is simple, containing phone number and text in a fixed format. This can be eaysily generated by a script you run when needing an alert. We found it quite easy o setup, only trick is to use a phone or modem that is well supported. I can give some details on request. Best regards, Jakob Curdes -- Jakob Curdes Anschrift: iS information systems oHG Postfach 3011 26020 Oldenburg Tel.: (0)441 - 84 53 1 Fax: (0)441 - 88 59 378 Sitz: Donnerschweer Str. 89-91 D 26123 Oldenburg Web: www.info-systems.de Firmierung und Handelsregisterangaben finden Sie unter diesem Link: Firmendaten. -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-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
[Nagios-users] Nagios Notification State Issue
( this time with a proper subject ) Hello All... I am seeing an odd problem host status and retention after reloads and I am wondering if anyone else has seen this and possibly knows of a fix it... When I disable notifications for a host via the UI the command completes and I see that notifications are indeed disabled, notifications stop, etc... However when I reload Nagios the notifications are re-enabled. This is only showing up with host checks, service check state is retained after a reload. I can see the status.dat file change however the retention.dat always stays the same ( notifications_enabled=0 ). I am not even sure if that is it or not, or if this is a permissions issue or some kind. Also, this has worked with this build in the past. It stopped working a short time ago... Any help would be greatly appreciated... Nagios Version: 3.2.1 ( perms ) -rw--- 1 nagios nagios 1003961 2010-11-10 03:47 retention.dat -rw-r--r-- 1 nagios nagios 757630 2010-11-10 03:47 objects.cache -rw-r--r-- 1 nagios nagios 80887 2010-11-10 04:05 nagios.log -rw-rw-r-- 1 nagios nagios 1000332 2010-11-10 04:05 status.dat Regards, Dale -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-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
