Re: [Nagios-users] Fwd: Problem with recovery notification
I found this in source code : /* ADDED IF STATEMENT 01-17-05 EG */ /* 01-17-05: Services in hard problem states before hosts went down would sometimes come back as soft problem states after */ /* the hosts recovered. This caused problems, so hopefully this will fix it */ if(temp_service->state_type==SOFT_STATE) temp_service->current_attempt=1; } "so hopefully this will fix it" => Perhaps this patch does not work ... Samuel Mutel. - Mail Original - De: "samuel mutel" À: nagios-users@lists.sourceforge.net Envoyé: Jeudi 18 Février 2010 09:21:41 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: [Nagios-users] Fwd: Problem with recovery notification Hello, Anybody ? I don't understand the Hard and soft logic in Service Alert of server 1 : CRITICAL;SOFT;1 CRITICAL;SOFT;2 CRITICAL;HARD;3 CRITICAL;SOFT;1 => Why I don't have after CRITICAL;HARD;3 and before CRITICAL;SOFT;1 : OK;HARD;3. Questions : 1) The flapping mode can explain this behaviour ? 2) If the node is down the service state (hard or soft) is set to soft ? Regards, Thanks. - Mail transféré - De: "Samuel Mutel" À: nagios-users@lists.sourceforge.net Envoyé: Mardi 16 Février 2010 21:05:54 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Problem with recovery notification Hello, I have two Nagios servers that monitor the same equipement. This two nagios send the result of check by notification to another monitoring system (OpenNMS). I use Nagios 3.2. I received the recovery notification from server 2 but I did not received recovery notification from server 1. Why ? I think that SOFT and HARD states are the problem but I am not sur. In the second server 2 the status of service is HARD - OK so the notification is sent but on server 1, the service is SOFT - OK !!! Here is the log of Nagios : Service Alert of server 1 : [1266299592] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;1;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at 'https://ip_address/sdk/vimService.wsdl' [1266299885] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;2;CHECK_ESX3.PL CRITICAL - Error connecting to server at 'https://ip_address/sdk/webService': Perhaps host is not a Virtual Center or ESX server [1266299925] SERVICE ALERT: test-server;CPU;CRITICAL;HARD;3;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at 'https://ip_address/sdk/vimService.wsdl' [1266303080] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;1;CHECK_ESX3.PL CRITICAL - Error connecting to server at 'https://ip_address/sdk/webService': Perhaps host is not a Virtual Center or ESX server [1266303380] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;2;CHECK_ESX3.PL CRITICAL - Error connecting to server at 'https://ip_address/sdk/webService': Perhaps host is not a Virtual Center or ESX server [1266308485] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;1;(Service Check Timed Out) [1266308500] SERVICE ALERT: test-server;CPU;OK;SOFT;2;CHECK_ESX3.PL OK - "test-server" cpu usage=2.29 % Service Notification of server 1 : [1266299925] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at https://ip_address/sdk/vimService.wsdl [1266300645] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at https://ip_address/sdk/vimService.wsdl [1266301385] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at https://ip_address/sdk/vimService.wsdl [1266301720] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at https://ip_address/sdk/vimService.wsdl [1266303575] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error connecting to server at https://ip_address/sdk/webService: Perhaps host is not a Virtual Center or ESX server [1266304175] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error connecting to server at https://ip_address/sdk/webService: Perhaps host is not a Virtual Center or ESX server [1266304810] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at https://ip_address/sdk/vimService.wsdl [1266305270] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at https://ip_address/sdk/vimService.wsdl [1266305975] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_
Re: [Nagios-users] Fwd: Problem with recovery notification
samuel.mu...@free.fr wrote: > Hello, > > Anybody ? > I don't understand the Hard and soft logic in Service Alert of server 1 : > > CRITICAL;SOFT;1 > CRITICAL;SOFT;2 > CRITICAL;HARD;3 > CRITICAL;SOFT;1 > > => Why I don't have after CRITICAL;HARD;3 and before CRITICAL;SOFT;1 : > OK;HARD;3. > > Questions : > 1) The flapping mode can explain this behaviour ? > 2) If the node is down the service state (hard or soft) is set to soft ? > Flap detection only inhibits notifications. It would not effect hard/soft states. Several things could cause this, but it appears you've stripped all context out of the logs. Was Nagios restarted between the " CRITICAL;HARD;3" and the "CRITICAL;SOFT;1," maybe? Im not 100% sure, but the service state count may also be reset (I'd be a bit surprised if it isn't) if the host is determined to be down. -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ 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] Fwd: Problem with recovery notification
Hello, Anybody ? I don't understand the Hard and soft logic in Service Alert of server 1 : CRITICAL;SOFT;1 CRITICAL;SOFT;2 CRITICAL;HARD;3 CRITICAL;SOFT;1 => Why I don't have after CRITICAL;HARD;3 and before CRITICAL;SOFT;1 : OK;HARD;3. Questions : 1) The flapping mode can explain this behaviour ? 2) If the node is down the service state (hard or soft) is set to soft ? Regards, Thanks. - Mail transféré - De: "Samuel Mutel" À: nagios-users@lists.sourceforge.net Envoyé: Mardi 16 Février 2010 21:05:54 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Problem with recovery notification Hello, I have two Nagios servers that monitor the same equipement. This two nagios send the result of check by notification to another monitoring system (OpenNMS). I use Nagios 3.2. I received the recovery notification from server 2 but I did not received recovery notification from server 1. Why ? I think that SOFT and HARD states are the problem but I am not sur. In the second server 2 the status of service is HARD - OK so the notification is sent but on server 1, the service is SOFT - OK !!! Here is the log of Nagios : Service Alert of server 1 : [1266299592] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;1;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at 'https://ip_address/sdk/vimService.wsdl' [1266299885] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;2;CHECK_ESX3.PL CRITICAL - Error connecting to server at 'https://ip_address/sdk/webService': Perhaps host is not a Virtual Center or ESX server [1266299925] SERVICE ALERT: test-server;CPU;CRITICAL;HARD;3;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at 'https://ip_address/sdk/vimService.wsdl' [1266303080] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;1;CHECK_ESX3.PL CRITICAL - Error connecting to server at 'https://ip_address/sdk/webService': Perhaps host is not a Virtual Center or ESX server [1266303380] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;2;CHECK_ESX3.PL CRITICAL - Error connecting to server at 'https://ip_address/sdk/webService': Perhaps host is not a Virtual Center or ESX server [1266308485] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;1;(Service Check Timed Out) [1266308500] SERVICE ALERT: test-server;CPU;OK;SOFT;2;CHECK_ESX3.PL OK - "test-server" cpu usage=2.29 % Service Notification of server 1 : [1266299925] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at https://ip_address/sdk/vimService.wsdl [1266300645] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at https://ip_address/sdk/vimService.wsdl [1266301385] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at https://ip_address/sdk/vimService.wsdl [1266301720] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at https://ip_address/sdk/vimService.wsdl [1266303575] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error connecting to server at https://ip_address/sdk/webService: Perhaps host is not a Virtual Center or ESX server [1266304175] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error connecting to server at https://ip_address/sdk/webService: Perhaps host is not a Virtual Center or ESX server [1266304810] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at https://ip_address/sdk/vimService.wsdl [1266305270] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at https://ip_address/sdk/vimService.wsdl [1266305975] SERVICE NOTIFICATION: onms_prod;test-server;CPU;CRITICAL;send_service_trap_to_onms_prod;CHECK_ESX3.PL CRITICAL - Error connecting to server at https://ip_address/sdk/webService: Perhaps host is not a Virtual Center or ESX server Service Alert of server 2 : [1266299856] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;1;(Service Check Timed Out) [1266300161] SERVICE ALERT: test-server;CPU;CRITICAL;HARD;1;(Service Check Timed Out) [1266300516] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;1;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at 'https://ip_address/sdk/vimService.wsdl' [1266301481] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;1;(Service Check Timed Out) [1266301512] SERVICE ALERT: test-server;CPU;CRITICAL;SOFT;2;CHECK_ESX3.PL CRITICAL - Error: Server version unavailable at 'https://ip_address/sdk/vimService.wsdl' [1266304201] SERVICE ALERT: test-
