FW: Notifications question

[Bruno Martins]

Hello guys,

No ideas about the problem below?

Thanks!

Best regards,

Bruno Martins

-----Original Message-----
From: Bruno Martins [mailto:bruno.martins at gruporumos.com] 
Sent: sexta-feira, 2 de Novembro de 2012 12:42
To: Nagios Users List
Subject: Re: [Nagios-users] Notifications question

Hi,

I have changed enable_environment_macros variable to 0 with no luck.
I have also cleared all services I had on service groups and still no luck.

Now I've changed debug level in Nagios to be in Notifications level, and I get this on /var/log/nagios/nagios.debug:

[1351859880.332512] [032.0] [pid=15799] ** Service Notification Attempt ** Host: 'RUMOSSRV_flxis01', Service: 'CPU Load', Type: 99, Options: 0, Current State: 0, Last Notification: Thu Jan  1 01:00:00 1970 [1351859880.335799] [032.0] [pid=15799] Notification viability test passed.
[1351859880.335845] [032.1] [pid=15799] Current notification number: 0 (unchanged) [1351859880.335884] [032.2] [pid=15799] Creating list of contacts to be notified.
[1351859880.335914] [032.1] [pid=15799] Service notification will NOT be escalated.
[1351859880.335942] [032.1] [pid=15799] Adding normal contacts for service to notification list.
[1351859880.335968] [032.2] [pid=15799] Adding members of contact group 'WISESRV-critical' for service to notification list.
[1351859880.336003] [032.2] [pid=15799] ** Checking service notification viability for contact 'helpdesk'...
[1351859880.350829] [032.2] [pid=15799] Adding contact 'helpdesk' to notification list.
[1351859880.353521] [032.2] [pid=15799] ** Notifying contact 'helpdesk'
[1351859880.353595] [032.2] [pid=15799] Raw notification command: my notification command [1351859880.353730] [032.2] [pid=15799] Processed notification command: my notification command [1351859880.555686] [032.0] [pid=15799] 1 contacts were notified.

And I get this on the /var/log/Nagios/Nagios.log:

[1351859880] EXTERNAL COMMAND: SEND_CUSTOM_SVC_NOTIFICATION;RUMOSSRV_flxis01;CPU Load;0;Helpdesk User;teste [1351859880] SERVICE NOTIFICATION: helpdesk;RUMOSSRV_flxis01;CPU Load;CUSTOM (OK);notify-by-email;CPU Load 2% (5 min average);Helpdesk User;teste

Best regards,

Bruno Martins

-----Original Message-----
From: Andreas Ericsson [mailto:ae at op5.se]
Sent: sexta-feira, 2 de Novembro de 2012 12:16
To: Nagios Users List
Cc: Bruno Martins
Subject: Re: [Nagios-users] Notifications question

On 11/02/2012 12:53 PM, Bruno Martins wrote:
> Ok, I see that nothing appears on the log file.
> 
> Now, why? The command is the same for both services.
> 

Remove environment macros and get rid of SERVICEGROUP_NAMES and SERVICEGROUP_MEMBERS macros in the output. Also grep for 'Warning: '
in nagios.log.


------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Nagios-users mailing list
Nagios-users at 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

------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Nagios-users mailing list
Nagios-users at 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