[Check_mk (english)] notification trouble

MarsellusWallace · August 6, 2013, 11:20am

From debug: no notification will be sent

I’ll havw to test this for myself…

···

sent from my SGS3

Am 06.08.2013 12:20 schrieb “Presidio TI DLCI” presidio.ti.dlci@interno.it:

I'm so stupid! I didn't noticed that line on the global settings. I
believed that the config for email should have be done from nagios
config files. Anyway I’ve changed the command in “/usr/sbin/sendmail
-vt $CONTACTEMAIL$”, but I still can’t receive email. Making the
test I’ve the following in the debug:
 [1375784181.309122] [032.0] [pid=14943] ** Host Notification
Attempt ** Host: ‘capua1’, Type: 0, Options: 0, Current State: 1,
Last Notification: Mon Aug 5 17:31:06 2013
 [1375784181.309276] [032.1] [pid=14943] We shouldn't re-notify
contacts about this host problem.
 [1375784181.309308] [032.0] [pid=14943] Notification viability
test failed. No notification will be sent out.
 [1375784181.309351] [032.0] [pid=14943] ** Service Notification
Attempt ** Host: ‘capua1’, Service: ‘Check_MK’, Type: 0, Options:
0, Current State: 2, Last Notification: Thu Jan 1 01:00:00 1970
 [1375784181.309391] [032.1] [pid=14943] The host is either down or
unreachable, so we won’t notify contacts about this service.
 [1375784181.309421] [032.0] [pid=14943] Notification viability
test failed. No notification will be sent out.
 [1375784181.336258] [032.0] [pid=14943] ** Service Notification
Attempt ** Host: ‘capua1’, Service: ‘Check_MK’, Type: 99, Options:
0, Current State: 2, Last Notification: Thu Jan 1 01:00:00 1970
 [1375784181.336331] [032.0] [pid=14943] Notification viability
test passed.
 [1375784181.336361] [032.1] [pid=14943] Current notification
number: 0 (unchanged)
 [1375784181.336393] [032.1] [pid=14943] Service notification will
NOT be escalated.
 [1375784181.336427] [032.1] [pid=14943] Adding normal contacts for
service to notification list.
 [1375784182.135587] [032.0] [pid=14943] 1 contacts were notified.




 Il 06/08/2013 11:57, Marcel Schulte ha
scritto:

    So the problem changed, the initial one is solved.

Goog news!

    You can check the used command in WATO -> Global
settings → Notifications.
Try to execute that command as the user nagios runs as. Maybe
permissions must be chamged or similar.

sent from my SGS3

Am 06.08.2013 11:49 schrieb "Presidio TI > > DLCI" <presidio.ti.dlci@interno.it>:
 This is the
notification log:
 [1375782449.105267] [032.0] [pid=893] ** Host
Notification Attempt ** Host: ‘capua1’, Type: 0, Options:
0, Current State: 1, Last Notification: Mon Aug 5
17:31:06 2013
 [1375782449.105373] [032.1] [pid=893] We shouldn't
re-notify contacts about this host problem.
 [1375782449.105406] [032.0] [pid=893] Notification
viability test failed. No notification will be sent out.
 [1375782449.292236] [032.0] [pid=893] ** Host Notification
Attempt ** Host: ‘capua1’, Type: 99, Options: 0, Current
State: 1, Last Notification: Mon Aug 5 17:31:06 2013
 [1375782449.292311] [032.0] [pid=893] Notification
viability test passed.
 [1375782449.292342] [032.1] [pid=893] Current notification
number: 1 (unchanged)
 [1375782449.292373] [032.1] [pid=893] Host notification
will NOT be escalated.
 [1375782449.292402] [032.1] [pid=893] Adding normal
contacts for host to notification list.
 [1375782450.469510] [032.0] [pid=893] 1 contacts were
notified.
 This is messages:

 Aug 6 11:47:29 netmonitor4 nagios: EXTERNAL COMMAND:
SEND_CUSTOM_HOST_NOTIFICATION;capua1;0;nagiosadmin;TEST
 Aug 6 11:47:29 netmonitor4 nagios: HOST NOTIFICATION:
nagiosadmin;capua1;CUSTOM (DOWN);check-mk-notify;CRITICAL
172.25.3.252 : rta nan, lost
100%;nagiosadmin
 But I haven't received the email, does the check_mk plugin
use comman “mail” or “sendmail”? I’ve only the second.

Il 06/08/2013 11:42, Marcel Schulte ha scritto:


Thanks.
Hoped to see empty Host contactgroups ;-)
Did you try to send test notification after last changes? What does
the debug log (for notifications) say? At the beginning it said "no
contacts found for host").
2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:


Ah ok! Sorry!
Il 06/08/2013 11:28, Marcel Schulte ha scritto:


OK, maybe I wasn't specific enough (because that's the preferences
page again)...
Open this URL and send a shot:
http(s)://<url_to_you_multisite_ui>/view.py?host=capua1&view_name=hoststatus
2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:


Marcel I've sent it in a previous email, here you are in attachment
Il 06/08/2013 10:57, Marcel Schulte ha scritto:


One more. ;-)
I'm still waiting for the host's detail page...
2013/8/6 Marcel Schulte <schulte.marcel@gmail.com>:


Did you do that here:
WATO -> Host and service parameters -> Grouping -> Assignment of hosts
to contact groups
or here:
WATO -> Host and service parameters -> Grouping -> Assignment of
services to contact groups?
Your screenshot shows the rule of the second possibility - but that's
wrong, the first one would be right.
Don't forget to apply changes...
2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:


I've created the rule in grouping menu only for host like you suggested,
but nothing. what command the notification plugin use? The one specified
in the nagios config file (commands.cfg), associated in contact.cfg to
the user? Or it has its own?
Il 06/08/2013 10:43, Marcel Schulte ha scritto:


As mentioned: create your rule for the host, not the host's services.
2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:


Danny,
actually I've removed all filters, but I have the same problem.
Il 06/08/2013 10:04, Kip, Danny (CIV) ha scritto:


It's probably nothing, but I notice you mentioned you added 'capua_1' to the contact group, but the logging excerpt says 'capua1' without underscore.
If this is really the case, that would be a good explanation :)
//Danny.
-----Oorspronkelijk bericht-----
Van: Presidio TI DLCI [mailto:presidio.ti.dlci@interno.it]
Verzonden: maandag 5 augustus 2013 12:42
Aan: checkmk-en@lists.mathias-kettner.de
Onderwerp: [Check_mk (english)] notification trouble
Hi,
I have a problem with check_mk notification. I followed the wiki
([http://mathias-kettner.de/checkmk_flexible_notifications.html](http://mathias-kettner.de/checkmk_flexible_notifications.html)
) an I
have the attempted string in /var/log/messages after clicking the test
button. Manually using sendmail messages are delivered. From debug I
have the following text:
[1375698038.168104] [032.0] [pid=15374] Notification viability test passed.
[1375698038.168132] [032.1] [pid=15374] Current notification number: 1
(incremented)
[1375698038.168162] [032.1] [pid=15374] Host notification will NOT be
escalated.
[1375698038.168189] [032.1] [pid=15374] Adding normal contacts for host
to notification list.
[1375698038.168223] [032.0] [pid=15374] No contacts were found for
notification purposes. No notification was sent out.
[1375698038.168266] [032.0] [pid=15374] ** Service Notification Attempt
** Host: 'capua1', Service: 'Check_MK', Type: 0, Options: 0, Current
State: 2, Last Notification: Thu Jan 1 01:00:00 1970
The host capua_1 has been added properly to contact group and the
relative contact too.
Could you help me to reso
lve this problem?
Thank You for your attention

_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)

Kip_Danny_CIV · August 6, 2013, 11:45am

I think I noticed your notification period set to 15 hours in one of your screenshots.

So retesting within 15 hours will probably only give you this sort of logging:

[1375784181.309276] [032.1] [pid=14943] We shouldn’t re-notify contacts about this host problem.

[1375784181.309308] [032.0] [pid=14943] Notification viability test failed. No notification will be sent out.

···

Van: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Verzonden: dinsdag 6 augustus 2013 13:20
Aan: Presidio TI DLCI
CC: checkmk-en@lists.mathias-kettner.de
Onderwerp: Re: [Check_mk (english)] notification trouble

From debug: no notification will be sent

I’ll havw to test this for myself…

sent from my SGS3

Am 06.08.2013 12:20 schrieb “Presidio TI DLCI” presidio.ti.dlci@interno.it:

I’m so stupid! I didn’t noticed that line on the global settings. I believed that the config for email should have be done from nagios config
files. Anyway I’ve changed the command in “/usr/sbin/sendmail -vt $CONTACTEMAIL$”, but I still can’t receive email. Making the test I’ve the following in the debug:

[1375784181.309122] [032.0] [pid=14943] ** Host Notification Attempt ** Host: ‘capua1’, Type: 0, Options: 0, Current State: 1, Last Notification: Mon Aug 5 17:31:06 2013

[1375784181.309276] [032.1] [pid=14943] We shouldn’t re-notify contacts about this host problem.

[1375784181.309308] [032.0] [pid=14943] Notification viability test failed. No notification will be sent out.

[1375784181.309351] [032.0] [pid=14943] ** Service Notification Attempt ** Host: ‘capua1’, Service: ‘Check_MK’, Type: 0, Options: 0, Current State: 2, Last Notification: Thu Jan 1 01:00:00 1970

[1375784181.309391] [032.1] [pid=14943] The host is either down or unreachable, so we won’t notify contacts about this service.

[1375784181.309421] [032.0] [pid=14943] Notification viability test failed. No notification will be sent out.

[1375784181.336258] [032.0] [pid=14943] ** Service Notification Attempt ** Host: ‘capua1’, Service: ‘Check_MK’, Type: 99, Options: 0, Current State: 2, Last Notification: Thu Jan 1 01:00:00 1970

[1375784181.336331] [032.0] [pid=14943] Notification viability test passed.

[1375784181.336361] [032.1] [pid=14943] Current notification number: 0 (unchanged)

[1375784181.336393] [032.1] [pid=14943] Service notification will NOT be escalated.

[1375784181.336427] [032.1] [pid=14943] Adding normal contacts for service to notification list.

[1375784182.135587] [032.0] [pid=14943] 1 contacts were notified.

Il 06/08/2013 11:57, Marcel Schulte ha scritto:

So the problem changed, the initial one is solved. Goog news!

You can check the used command in WATO → Global settings → Notifications.

Try to execute that command as the user nagios runs as. Maybe permissions must be chamged or similar.

sent from my SGS3

Am 06.08.2013 11:49 schrieb “Presidio TI DLCI” presidio.ti.dlci@interno.it:

This is the notification log:

[1375782449.105267] [032.0] [pid=893] ** Host Notification Attempt ** Host: ‘capua1’, Type: 0, Options: 0, Current State: 1, Last Notification: Mon Aug 5 17:31:06 2013

[1375782449.105373] [032.1] [pid=893] We shouldn’t re-notify contacts about this host problem.

[1375782449.105406] [032.0] [pid=893] Notification viability test failed. No notification will be sent out.

[1375782449.292236] [032.0] [pid=893] ** Host Notification Attempt ** Host: ‘capua1’, Type: 99, Options: 0, Current State: 1, Last Notification: Mon Aug 5 17:31:06 2013

[1375782449.292311] [032.0] [pid=893] Notification viability test passed.

[1375782449.292342] [032.1] [pid=893] Current notification number: 1 (unchanged)

[1375782449.292373] [032.1] [pid=893] Host notification will NOT be escalated.

[1375782449.292402] [032.1] [pid=893] Adding normal contacts for host to notification list.

[1375782450.469510] [032.0] [pid=893] 1 contacts were notified.

This is messages:
Aug 6 11:47:29 netmonitor4 nagios: EXTERNAL COMMAND: SEND_CUSTOM_HOST_NOTIFICATION;capua1;0;nagiosadmin;TEST

Aug 6 11:47:29 netmonitor4 nagios: HOST NOTIFICATION: nagiosadmin;capua1;CUSTOM (DOWN);check-mk-notify;CRITICAL -
172.25.3.252: rta nan, lost 100%;nagiosadmin

But I haven’t received the email, does the check_mk plugin use comman “mail” or “sendmail”? I’ve only the second.

Il 06/08/2013 11:42, Marcel Schulte ha scritto:

Thanks.

Hoped to see empty Host contactgroups ;-)

Did you try to send test notification after last changes? What does

the debug log (for notifications) say? At the beginning it said "no

contacts found for host").

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Ah ok! Sorry!

Il 06/08/2013 11:28, Marcel Schulte ha scritto:

OK, maybe I wasn't specific enough (because that's the preferences

page again)...

Open this URL and send a shot:

http(s)://<url_to_you_multisite_ui>/view.py?host=capua1&view_name=hoststatus

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Marcel I've sent it in a previous email, here you are in attachment

Il 06/08/2013 10:57, Marcel Schulte ha scritto:

One more. ;-)

I'm still waiting for the host's detail page...

2013/8/6 Marcel Schulte <schulte.marcel@gmail.com>:

Did you do that here:

WATO -> Host and service parameters -> Grouping -> Assignment of hosts

to contact groups

or here:

WATO -> Host and service parameters -> Grouping -> Assignment of

services to contact groups?

Your screenshot shows the rule of the second possibility - but that's

wrong, the first one would be right.

Don't forget to apply changes...

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

I've created the rule in grouping menu only for host like you suggested,

but nothing. what command the notification plugin use? The one specified

in the nagios config file (commands.cfg), associated in contact.cfg to

the user? Or it has its own?

Il 06/08/2013 10:43, Marcel Schulte ha scritto:

As mentioned: create your rule for the host, not the host's services.

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Danny,

actually I've removed all filters, but I have the same problem.

Il 06/08/2013 10:04, Kip, Danny (CIV) ha scritto:

It's probably nothing, but I notice you mentioned you added 'capua_1' to the contact group, but the logging excerpt says 'capua1' without underscore.

If this is really the case, that would be a good explanation :)

//Danny.

-----Oorspronkelijk bericht-----

Van: Presidio TI DLCI [mailto:presidio.ti.dlci@interno.it]

Verzonden: maandag 5 augustus 2013 12:42

Aan: checkmk-en@lists.mathias-kettner.de

Onderwerp: [Check_mk (english)] notification trouble

Hi,

I have a problem with check_mk notification. I followed the wiki

([http://mathias-kettner.de/checkmk_flexible_notifications.html](http://mathias-kettner.de/checkmk_flexible_notifications.html)) an I

have the attempted string in /var/log/messages after clicking the test

button. Manually using sendmail messages are delivered. From debug I

have the following text:

[1375698038.168104] [032.0] [pid=15374] Notification viability test passed.

[1375698038.168132] [032.1] [pid=15374] Current notification number: 1

(incremented)

[1375698038.168162] [032.1] [pid=15374] Host notification will NOT be

escalated.

[1375698038.168189] [032.1] [pid=15374] Adding normal contacts for host

to notification list.

[1375698038.168223] [032.0] [pid=15374] No contacts were found for

notification purposes.  No notification was sent out.

[1375698038.168266] [032.0] [pid=15374] ** Service Notification Attempt

** Host: 'capua1', Service: 'Check_MK', Type: 0, Options: 0, Current

State: 2, Last Notification: Thu Jan  1 01:00:00 1970

The host capua_1 has been added properly to contact group and the

relative contact too.

Could you help me to reso

lve this problem?

Thank You for your attention

_______________________________________________

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)

Presidio_TI_DLCI · August 6, 2013, 4:05pm

Hi,
the problem was in the notify.py script. The lack of a permission on
body.log stopped the script, preventing the mail to be send.

···

Il 06/08/2013 13:45, Kip, Danny (CIV)
ha scritto:

            I think I noticed your notification period
set to 15 hours in one of your screenshots.

            So retesting within 15 hours will probably

only give you this sort of logging:

            [1375784181.309276]
[032.1] [pid=14943] We shouldn’t re-notify contacts
about this host problem.
            [1375784181.309308] [032.0] [pid=14943] Notification
viability test failed. No notification will be sent
out.

Van: Marcel
Schulte
dinsdag 6 augustus 2013 13:20
Presidio TI DLCI
Re: [Check_mk (english)] notification trouble

            From debug: no notification

will be sent

mailto:schulte.marcel@gmail.com
Verzonden:
Aan:
**CC:**checkmk-en@lists.mathias-kettner.de
Onderwerp:

 -- -------------------------------------------------------------
Presidio Telecom Italia
Dip.to Libertà Civili e Immigrazione - Ministero dell'Interno
Tel: 06 465 25 775 / 06 69 000 190
E-mail: -------------------------------------------------------------

presidio.ti.dlci@interno.it

            I'll havw to test this for

myself…

sent from my SGS3

              Am 06.08.2013 12:20 schrieb "Presidio TI DLCI"

presidio.ti.dlci@interno.it:

                I'm so stupid! I didn't

noticed that line on the global settings. I believed
that the config for email should have be done from
nagios config files. Anyway I’ve changed the command
in “/usr/sbin/sendmail -vt $CONTACTEMAIL$”, but I
still can’t receive email. Making the test I’ve the
following in the debug:

                                  [1375784181.309122] [032.0]

[pid=14943] ** Host Notification Attempt ** Host:
‘capua1’, Type: 0, Options: 0, Current State: 1,
Last Notification: Mon Aug 5 17:31:06 2013

                [1375784181.309276] [032.1] [pid=14943] We shouldn't

re-notify contacts about this host problem.

                [1375784181.309308] [032.0] [pid=14943] Notification

viability test failed. No notification will be sent
out.

                [1375784181.309351] [032.0] [pid=14943] ** Service

Notification Attempt ** Host: ‘capua1’, Service:
‘Check_MK’, Type: 0, Options: 0, Current State: 2,
Last Notification: Thu Jan 1 01:00:00 1970

                [1375784181.309391] [032.1] [pid=14943] The host is

either down or unreachable, so we won’t notify
contacts about this service.

                [1375784181.309421] [032.0] [pid=14943] Notification

viability test failed. No notification will be sent
out.

                [1375784181.336258] [032.0] [pid=14943] ** Service

Notification Attempt ** Host: ‘capua1’, Service:
‘Check_MK’, Type: 99, Options: 0, Current State: 2,
Last Notification: Thu Jan 1 01:00:00 1970

                [1375784181.336331] [032.0] [pid=14943] Notification

viability test passed.

                [1375784181.336361] [032.1] [pid=14943] Current

notification number: 0 (unchanged)

                [1375784181.336393] [032.1] [pid=14943] Service

notification will NOT be escalated.

                [1375784181.336427] [032.1] [pid=14943] Adding

normal contacts for service to notification list.

                [1375784182.135587] [032.0] [pid=14943] 1 contacts

were notified.

                  Il 06/08/2013 11:57, Marcel Schulte ha

scritto:

                  So the problem changed,

the initial one is solved. Goog news!

                  You can check the used
command in WATO → Global settings →
Notifications.
                  Try to execute that command as the user nagios
runs as. Maybe permissions must be chamged or
similar.

sent from my SGS3

                    Am 06.08.2013 11:49 schrieb "Presidio TI

DLCI" presidio.ti.dlci@interno.it:

                      This is the
notification log:
                                              [1375782449.105267]
[032.0] [pid=893] ** Host Notification Attempt
** Host: ‘capua1’, Type: 0, Options: 0,
Current State: 1, Last Notification: Mon Aug
5 17:31:06 2013
                      [1375782449.105373] [032.1] [pid=893] We
shouldn’t re-notify contacts about this host
problem.
                      [1375782449.105406] [032.0] [pid=893]
Notification viability test failed. No
notification will be sent out.
                      [1375782449.292236] [032.0] [pid=893] ** Host
Notification Attempt ** Host: ‘capua1’, Type:
99, Options: 0, Current State: 1, Last
Notification: Mon Aug 5 17:31:06 2013
                      [1375782449.292311] [032.0] [pid=893]
Notification viability test passed.
                      [1375782449.292342] [032.1] [pid=893] Current
notification number: 1 (unchanged)
                      [1375782449.292373] [032.1] [pid=893] Host
notification will NOT be escalated.
                      [1375782449.292402] [032.1] [pid=893] Adding
normal contacts for host to notification list.
                      [1375782450.469510] [032.0] [pid=893] 1
contacts were notified.
                  This is messages:
                                            Aug 
6 11:47:29 netmonitor4 nagios: EXTERNAL
COMMAND:
SEND_CUSTOM_HOST_NOTIFICATION;capua1;0;nagiosadmin;TEST
                      Aug  6 11:47:29 netmonitor4 nagios: HOST
NOTIFICATION: nagiosadmin;capua1;CUSTOM
(DOWN);check-mk-notify;CRITICAL -
172.25.3.252 :
rta nan, lost 100%;nagiosadmin
                  But I haven't received the email, does the
check_mk plugin use comman “mail” or “sendmail”?
I’ve only the second.

                        Il 06/08/2013 11:42, Marcel Schulte

ha scritto:

Thanks.

Hoped to see empty Host contactgroups ;-)

Did you try to send test notification after last changes? What does

the debug log (for notifications) say? At the beginning it said "no

contacts found for host").

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Ah ok! Sorry!

Il 06/08/2013 11:28, Marcel Schulte ha scritto:

OK, maybe I wasn't specific enough (because that's the preferences

page again)...

Open this URL and send a shot:

http(s)://<url_to_you_multisite_ui>/view.py?host=capua1&view_name=hoststatus

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Marcel I've sent it in a previous email, here you are in attachment

Il 06/08/2013 10:57, Marcel Schulte ha scritto:

One more. ;-)

I'm still waiting for the host's detail page...

2013/8/6 Marcel Schulte <schulte.marcel@gmail.com>:

Did you do that here:

WATO -> Host and service parameters -> Grouping -> Assignment of hosts

to contact groups

or here:

WATO -> Host and service parameters -> Grouping -> Assignment of

services to contact groups?

Your screenshot shows the rule of the second possibility - but that's

wrong, the first one would be right.

Don't forget to apply changes...

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

I've created the rule in grouping menu only for host like you suggested,

but nothing. what command the notification plugin use? The one specified

in the nagios config file (commands.cfg), associated in contact.cfg to

the user? Or it has its own?

Il 06/08/2013 10:43, Marcel Schulte ha scritto:

As mentioned: create your rule for the host, not the host's services.

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Danny,

actually I've removed all filters, but I have the same problem.

Il 06/08/2013 10:04, Kip, Danny (CIV) ha scritto:

It's probably nothing, but I notice you mentioned you added 'capua_1' to the contact group, but the logging excerpt says 'capua1' without underscore.

If this is really the case, that would be a good explanation :)

//Danny.

-----Oorspronkelijk bericht-----

Van: Presidio TI DLCI [mailto:presidio.ti.dlci@interno.it]

Verzonden: maandag 5 augustus 2013 12:42

Aan: checkmk-en@lists.mathias-kettner.de

Onderwerp: [Check_mk (english)] notification trouble

Hi,

I have a problem with check_mk notification. I followed the wiki

([http://mathias-kettner.de/checkmk_flexible_notifications.html](http://mathias-kettner.de/checkmk_flexible_notifications.html)) an I

have the attempted string in /var/log/messages after clicking the test

button. Manually using sendmail messages are delivered. From debug I

have the following text:

[1375698038.168104] [032.0] [pid=15374] Notification viability test passed.

[1375698038.168132] [032.1] [pid=15374] Current notification number: 1

(incremented)

[1375698038.168162] [032.1] [pid=15374] Host notification will NOT be

escalated.

[1375698038.168189] [032.1] [pid=15374] Adding normal contacts for host

to notification list.

[1375698038.168223] [032.0] [pid=15374] No contacts were found for

notification purposes.  No notification was sent out.

[1375698038.168266] [032.0] [pid=15374] ** Service Notification Attempt

** Host: 'capua1', Service: 'Check_MK', Type: 0, Options: 0, Current

State: 2, Last Notification: Thu Jan  1 01:00:00 1970

The host capua_1 has been added properly to contact group and the

relative contact too.

Could you help me to reso

lve this problem?

Thank You for your attention

_______________________________________________

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)

MarsellusWallace · August 6, 2013, 4:11pm

Cool, solved!

Nobody using OMD falls into these traps

···

sent from my SGS3

Am 06.08.2013 18:06 schrieb “Presidio TI DLCI” presidio.ti.dlci@interno.it:

Hi,
the problem was in the notify.py script. The lack of a permission on
body.log stopped the script, preventing the mail to be send.
  Il 06/08/2013 13:45, Kip, Danny (CIV) > ha scritto:

            I think I noticed your notification period
set to 15 hours in one of your screenshots.

            So retesting within 15 hours will probably

only give you this sort of logging:

            [1375784181.309276]
[032.1] [pid=14943] We shouldn’t re-notify contacts
about this host problem.
            [1375784181.309308] [032.0] [pid=14943] Notification
viability test failed. No notification will be sent
out.

Van: Marcel
Schulte [mailto:schulte.marcel@gmail.com ]
Verzonden:
dinsdag 6 augustus 2013 13:20
Aan:
Presidio TI DLCI
CC:
checkmk-en@lists.mathias-kettner.de
Onderwerp:
Re: [Check_mk (english)] notification trouble

            From debug: no notification

will be sent

 -- -------------------------------------------------------------
Presidio Telecom Italia
Dip.to Libertà Civili e Immigrazione - Ministero dell'Interno
Tel: 06 465 25 775 / 06 69 000 190
E-mail: presidio.ti.dlci@interno.it
  -------------------------------------------------------------

            I'll havw to test this for

myself…

sent from my SGS3

              Am 06.08.2013 12:20 schrieb "Presidio TI DLCI" > > <presidio.ti.dlci@interno.it>:

                I'm so stupid! I didn't
noticed that line on the global settings. I believed
that the config for email should have be done from
nagios config files. Anyway I’ve changed the command
in “/usr/sbin/sendmail -vt $CONTACTEMAIL$”, but I
still can’t receive email. Making the test I’ve the
following in the debug:
                                  [1375784181.309122] [032.0]
[pid=14943] ** Host Notification Attempt ** Host:
‘capua1’, Type: 0, Options: 0, Current State: 1,
Last Notification: Mon Aug 5 17:31:06 2013
                [1375784181.309276] [032.1] [pid=14943] We shouldn't
re-notify contacts about this host problem.
                [1375784181.309308] [032.0] [pid=14943] Notification
viability test failed. No notification will be sent
out.
                [1375784181.309351] [032.0] [pid=14943] ** Service
Notification Attempt ** Host: ‘capua1’, Service:
‘Check_MK’, Type: 0, Options: 0, Current State: 2,
Last Notification: Thu Jan 1 01:00:00 1970
                [1375784181.309391] [032.1] [pid=14943] The host is
either down or unreachable, so we won’t notify
contacts about this service.
                [1375784181.309421] [032.0] [pid=14943] Notification
viability test failed. No notification will be sent
out.
                [1375784181.336258] [032.0] [pid=14943] ** Service
Notification Attempt ** Host: ‘capua1’, Service:
‘Check_MK’, Type: 99, Options: 0, Current State: 2,
Last Notification: Thu Jan 1 01:00:00 1970
                [1375784181.336331] [032.0] [pid=14943] Notification
viability test passed.
                [1375784181.336361] [032.1] [pid=14943] Current
notification number: 0 (unchanged)
                [1375784181.336393] [032.1] [pid=14943] Service
notification will NOT be escalated.
                [1375784181.336427] [032.1] [pid=14943] Adding
normal contacts for service to notification list.
                [1375784182.135587] [032.0] [pid=14943] 1 contacts
were notified.

                  Il 06/08/2013 11:57, Marcel Schulte ha

scritto:

                  So the problem changed,

the initial one is solved. Goog news!

                  You can check the used
command in WATO → Global settings →
Notifications.
                  Try to execute that command as the user nagios
runs as. Maybe permissions must be chamged or
similar.

sent from my SGS3

                    Am 06.08.2013 11:49 schrieb "Presidio TI > > > DLCI" <presidio.ti.dlci@interno.it>:

                      This is the
notification log:
                                              [1375782449.105267]
[032.0] [pid=893] ** Host Notification Attempt
** Host: ‘capua1’, Type: 0, Options: 0,
Current State: 1, Last Notification: Mon Aug
5 17:31:06 2013
                      [1375782449.105373] [032.1] [pid=893] We
shouldn’t re-notify contacts about this host
problem.
                      [1375782449.105406] [032.0] [pid=893]
Notification viability test failed. No
notification will be sent out.
                      [1375782449.292236] [032.0] [pid=893] ** Host
Notification Attempt ** Host: ‘capua1’, Type:
99, Options: 0, Current State: 1, Last
Notification: Mon Aug 5 17:31:06 2013
                      [1375782449.292311] [032.0] [pid=893]
Notification viability test passed.
                      [1375782449.292342] [032.1] [pid=893] Current
notification number: 1 (unchanged)
                      [1375782449.292373] [032.1] [pid=893] Host
notification will NOT be escalated.
                      [1375782449.292402] [032.1] [pid=893] Adding
normal contacts for host to notification list.
                      [1375782450.469510] [032.0] [pid=893] 1
contacts were notified.
                  This is messages:
                                            Aug 
6 11:47:29 netmonitor4 nagios: EXTERNAL
COMMAND:
SEND_CUSTOM_HOST_NOTIFICATION;capua1;0;nagiosadmin;TEST
                      Aug  6 11:47:29 netmonitor4 nagios: HOST
NOTIFICATION: nagiosadmin;capua1;CUSTOM
(DOWN);check-mk-notify;CRITICAL -
172.25.3.252 :
rta nan, lost 100%;nagiosadmin
                  But I haven't received the email, does the
check_mk plugin use comman “mail” or “sendmail”?
I’ve only the second.

                        Il 06/08/2013 11:42, Marcel Schulte > > > ha scritto:

Thanks.

Hoped to see empty Host contactgroups ;-)

Did you try to send test notification after last changes? What does

the debug log (for notifications) say? At the beginning it said "no

contacts found for host").

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Ah ok! Sorry!

Il 06/08/2013 11:28, Marcel Schulte ha scritto:

OK, maybe I wasn't specific enough (because that's the preferences

page again)...

Open this URL and send a shot:

http(s)://<url_to_you_multisite_ui>/view.py?host=capua1&view_name=hoststatus

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Marcel I've sent it in a previous email, here you are in attachment

Il 06/08/2013 10:57, Marcel Schulte ha scritto:

One more. ;-)

I'm still waiting for the host's detail page...

2013/8/6 Marcel Schulte <schulte.marcel@gmail.com>:

Did you do that here:

WATO -> Host and service parameters -> Grouping -> Assignment of hosts

to contact groups

or here:

WATO -> Host and service parameters -> Grouping -> Assignment of

services to contact groups?

Your screenshot shows the rule of the second possibility - but that's

wrong, the first one would be right.

Don't forget to apply changes...

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

I've created the rule in grouping menu only for host like you suggested,

but nothing. what command the notification plugin use? The one specified

in the nagios config file (commands.cfg), associated in contact.cfg to

the user? Or it has its own?

Il 06/08/2013 10:43, Marcel Schulte ha scritto:

As mentioned: create your rule for the host, not the host's services.

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Danny,

actually I've removed all filters, but I have the same problem.

Il 06/08/2013 10:04, Kip, Danny (CIV) ha scritto:

It's probably nothing, but I notice you mentioned you added 'capua_1' to the contact group, but the logging excerpt says 'capua1' without underscore.

If this is really the case, that would be a good explanation :)

//Danny.

-----Oorspronkelijk bericht-----

Van: Presidio TI DLCI [mailto:presidio.ti.dlci@interno.it]

Verzonden: maandag 5 augustus 2013 12:42

Aan: checkmk-en@lists.mathias-kettner.de

Onderwerp: [Check_mk (english)] notification trouble

Hi,

I have a problem with check_mk notification. I followed the wiki

([http://mathias-kettner.de/checkmk_flexible_notifications.html](http://mathias-kettner.de/checkmk_flexible_notifications.html)) an I

have the attempted string in /var/log/messages after clicking the test

button. Manually using sendmail messages are delivered. From debug I

have the following text:

[1375698038.168104] [032.0] [pid=15374] Notification viability test passed.

[1375698038.168132] [032.1] [pid=15374] Current notification number: 1

(incremented)

[1375698038.168162] [032.1] [pid=15374] Host notification will NOT be

escalated.

[1375698038.168189] [032.1] [pid=15374] Adding normal contacts for host

to notification list.

[1375698038.168223] [032.0] [pid=15374] No contacts were found for

notification purposes.  No notification was sent out.

[1375698038.168266] [032.0] [pid=15374] ** Service Notification Attempt

** Host: 'capua1', Service: 'Check_MK', Type: 0, Options: 0, Current

State: 2, Last Notification: Thu Jan  1 01:00:00 1970

The host capua_1 has been added properly to contact group and the

relative contact too.

Could you help me to reso

lve this problem?

Thank You for your attention

_______________________________________________

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)

 

Presidio_TI_DLCI · August 6, 2013, 4:23pm

In general it seems that there are write permission problems with
logfiles. Now I can receive mail, but they are empty

···

Il 06/08/2013 18:11, Marcel Schulte ha
scritto:

Cool, solved!

Nobody using OMD falls into these traps

sent from my SGS3

    Am 06.08.2013 18:06 schrieb "Presidio TI
DLCI" presidio.ti.dlci@interno.it:
Hi,
        the problem was in the notify.py script. The lack of a
permission on body.log stopped the script, preventing the
mail to be send.

Il 06/08/2013 13:45, Kip, Danny (CIV) ha scritto:

                  I
think I noticed your notification period set to 15
hours in one of your screenshots.

                  So
retesting within 15 hours will probably only give
you this sort of logging:

                  [1375784181.309276]
[032.1] [pid=14943] We shouldn’t re-notify
contacts about this host problem.
                  [1375784181.309308] [032.0] [pid=14943]
Notification viability test failed. No
notification will be sent out.

Van:
Marcel Schulte [mailto:schulte.marcel@gmail.com ]
Verzonden:
dinsdag 6 augustus 2013 13:20
Aan:
Presidio TI DLCI
CC:
checkmk-en@lists.mathias-kettner.de
Onderwerp:
Re: [Check_mk (english)] notification trouble

                  From debug: no

notification will be sent

 -- -------------------------------------------------------------
Presidio Telecom Italia
Dip.to Libertà Civili e Immigrazione - Ministero dell'Interno
Tel: 06 465 25 775 / 06 69 000 190
E-mail: presidio.ti.dlci@interno.it
  -------------------------------------------------------------

                  I'll havw to test this

for myself…

sent from my SGS3

                    Am
06.08.2013 12:20 schrieb “Presidio TI DLCI” presidio.ti.dlci@interno.it:

                      I'm so stupid! I
didn’t noticed that line on the global
settings. I believed that the config for email
should have be done from nagios config files.
Anyway I’ve changed the command in
“/usr/sbin/sendmail -vt $CONTACTEMAIL$”, but I
still can’t receive email. Making the test
I’ve the following in the debug:
                                              [1375784181.309122]
[032.0] [pid=14943] ** Host Notification
Attempt ** Host: ‘capua1’, Type: 0, Options:
0, Current State: 1, Last Notification: Mon
Aug 5 17:31:06 2013
                      [1375784181.309276] [032.1] [pid=14943] We
shouldn’t re-notify contacts about this host
problem.
                      [1375784181.309308] [032.0] [pid=14943]
Notification viability test failed. No
notification will be sent out.
                      [1375784181.309351] [032.0] [pid=14943] **
Service Notification Attempt ** Host:
‘capua1’, Service: ‘Check_MK’, Type: 0,
Options: 0, Current State: 2, Last
Notification: Thu Jan 1 01:00:00 1970
                      [1375784181.309391] [032.1] [pid=14943] The
host is either down or unreachable, so we
won’t notify contacts about this service.
                      [1375784181.309421] [032.0] [pid=14943]
Notification viability test failed. No
notification will be sent out.
                      [1375784181.336258] [032.0] [pid=14943] **
Service Notification Attempt ** Host:
‘capua1’, Service: ‘Check_MK’, Type: 99,
Options: 0, Current State: 2, Last
Notification: Thu Jan 1 01:00:00 1970
                      [1375784181.336331] [032.0] [pid=14943]
Notification viability test passed.
                      [1375784181.336361] [032.1] [pid=14943]
Current notification number: 0 (unchanged)
                      [1375784181.336393] [032.1] [pid=14943]
Service notification will NOT be escalated.
                      [1375784181.336427] [032.1] [pid=14943] Adding
normal contacts for service to notification
list.
                      [1375784182.135587] [032.0] [pid=14943] 1
contacts were notified.

                        Il
06/08/2013 11:57, Marcel Schulte ha scritto:

                        So the problem
changed, the initial one is solved. Goog
news!

                        You can check the
used command in WATO → Global settings
→ Notifications.
                        Try to execute that command as the user
nagios runs as. Maybe permissions must be
chamged or similar.

sent from my SGS3

                          Am 06.08.2013
11:49 schrieb “Presidio TI DLCI” presidio.ti.dlci@interno.it:

                            This is the
notification log:
                            [1375782449.105267]
[032.0] [pid=893] ** Host Notification
Attempt ** Host: ‘capua1’, Type: 0,
Options: 0, Current State: 1, Last
Notification: Mon Aug 5 17:31:06 2013
                            [1375782449.105373] [032.1] [pid=893] We
shouldn’t re-notify contacts about this
host problem.
                            [1375782449.105406] [032.0] [pid=893]
Notification viability test failed. No
notification will be sent out.
                            [1375782449.292236] [032.0] [pid=893] **
Host Notification Attempt ** Host:
‘capua1’, Type: 99, Options: 0, Current
State: 1, Last Notification: Mon Aug 5
17:31:06 2013
                            [1375782449.292311] [032.0] [pid=893]
Notification viability test passed.
                            [1375782449.292342] [032.1] [pid=893]
Current notification number: 1
(unchanged)
                            [1375782449.292373] [032.1] [pid=893]
Host notification will NOT be escalated.
                            [1375782449.292402] [032.1] [pid=893]
Adding normal contacts for host to
notification list.
                            [1375782450.469510] [032.0] [pid=893] 1
contacts were notified.
                        This is messages:
                                                        Aug  6
11:47:29 netmonitor4 nagios: EXTERNAL
COMMAND:
SEND_CUSTOM_HOST_NOTIFICATION;capua1;0;nagiosadmin;TEST
                            Aug  6 11:47:29 netmonitor4 nagios: HOST
NOTIFICATION: nagiosadmin;capua1;CUSTOM
(DOWN);check-mk-notify;CRITICAL - 172.25.3.252 : rta
nan, lost 100%;nagiosadmin
                        But I haven't received the email, does the
check_mk plugin use comman “mail” or
“sendmail”? I’ve only the second.

                              Il 06/08/2013

11:42, Marcel Schulte ha scritto:

Thanks.

Hoped to see empty Host contactgroups ;-)

Did you try to send test notification after last changes? What does

the debug log (for notifications) say? At the beginning it said "no

contacts found for host").

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Ah ok! Sorry!

Il 06/08/2013 11:28, Marcel Schulte ha scritto:

OK, maybe I wasn't specific enough (because that's the preferences

page again)...

Open this URL and send a shot:

http(s)://<url_to_you_multisite_ui>/view.py?host=capua1&view_name=hoststatus

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Marcel I've sent it in a previous email, here you are in attachment

Il 06/08/2013 10:57, Marcel Schulte ha scritto:

One more. ;-)

I'm still waiting for the host's detail page...

2013/8/6 Marcel Schulte <schulte.marcel@gmail.com>:

Did you do that here:

WATO -> Host and service parameters -> Grouping -> Assignment of hosts

to contact groups

or here:

WATO -> Host and service parameters -> Grouping -> Assignment of

services to contact groups?

Your screenshot shows the rule of the second possibility - but that's

wrong, the first one would be right.

Don't forget to apply changes...

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

I've created the rule in grouping menu only for host like you suggested,

but nothing. what command the notification plugin use? The one specified

in the nagios config file (commands.cfg), associated in contact.cfg to

the user? Or it has its own?

Il 06/08/2013 10:43, Marcel Schulte ha scritto:

As mentioned: create your rule for the host, not the host's services.

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Danny,

actually I've removed all filters, but I have the same problem.

Il 06/08/2013 10:04, Kip, Danny (CIV) ha scritto:

It's probably nothing, but I notice you mentioned you added 'capua_1' to the contact group, but the logging excerpt says 'capua1' without underscore.

If this is really the case, that would be a good explanation :)

//Danny.

-----Oorspronkelijk bericht-----

Van: Presidio TI DLCI [mailto:presidio.ti.dlci@interno.it]

Verzonden: maandag 5 augustus 2013 12:42

Aan: checkmk-en@lists.mathias-kettner.de

Onderwerp: [Check_mk (english)] notification trouble

Hi,

I have a problem with check_mk notification. I followed the wiki

([http://mathias-kettner.de/checkmk_flexible_notifications.html](http://mathias-kettner.de/checkmk_flexible_notifications.html)) an I

have the attempted string in /var/log/messages after clicking the test

button. Manually using sendmail messages are delivered. From debug I

have the following text:

[1375698038.168104] [032.0] [pid=15374] Notification viability test passed.

[1375698038.168132] [032.1] [pid=15374] Current notification number: 1

(incremented)

[1375698038.168162] [032.1] [pid=15374] Host notification will NOT be

escalated.

[1375698038.168189] [032.1] [pid=15374] Adding normal contacts for host

to notification list.

[1375698038.168223] [032.0] [pid=15374] No contacts were found for

notification purposes.  No notification was sent out.

[1375698038.168266] [032.0] [pid=15374] ** Service Notification Attempt

** Host: 'capua1', Service: 'Check_MK', Type: 0, Options: 0, Current

State: 2, Last Notification: Thu Jan  1 01:00:00 1970

The host capua_1 has been added properly to contact group and the

relative contact too.

Could you help me to reso

lve this problem?

Thank You for your attention

_______________________________________________

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)

 

MarsellusWallace · August 6, 2013, 5:40pm

Sounds like another permission issue. Did you activate "debug
notifications" in WATO -> Global settings -> Notifications? Should
give you some hints what went wrong...

···

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

In general it seems that there are write permission problems with logfiles.
Now I can receive mail, but they are empty

Il 06/08/2013 18:11, Marcel Schulte ha scritto:

Cool, solved!

Nobody using OMD falls into these traps

sent from my SGS3

Am 06.08.2013 18:06 schrieb "Presidio TI DLCI" > <presidio.ti.dlci@interno.it>:

Hi,
the problem was in the notify.py script. The lack of a permission on
body.log stopped the script, preventing the mail to be send.

Il 06/08/2013 13:45, Kip, Danny (CIV) ha scritto:

I think I noticed your notification period set to 15 hours in one of your
screenshots.

So retesting within 15 hours will probably only give you this sort of
logging:

[1375784181.309276] [032.1] [pid=14943] We shouldn't re-notify contacts
about this host problem.
[1375784181.309308] [032.0] [pid=14943] Notification viability test
failed. No notification will be sent out.

________________________________

Van: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Verzonden: dinsdag 6 augustus 2013 13:20
Aan: Presidio TI DLCI
CC: checkmk-en@lists.mathias-kettner.de
Onderwerp: Re: [Check_mk (english)] notification trouble

From debug: no notification will be sent

--
-------------------------------------------------------------
 Presidio Telecom Italia
 Dip.to Libertà Civili e Immigrazione - Ministero dell'Interno
 Tel: 06 465 25 775 / 06 69 000 190
 E-mail: presidio.ti.dlci@interno.it
 -------------------------------------------------------------

I'll havw to test this for myself...

sent from my SGS3

Am 06.08.2013 12:20 schrieb "Presidio TI DLCI" >> <presidio.ti.dlci@interno.it>:

I'm so stupid! I didn't noticed that line on the global settings. I
believed that the config for email should have be done from nagios config
files. Anyway I've changed the command in "/usr/sbin/sendmail -vt
$CONTACTEMAIL$", but I still can't receive email. Making the test I've the
following in the debug:
[1375784181.309122] [032.0] [pid=14943] ** Host Notification Attempt **
Host: 'capua1', Type: 0, Options: 0, Current State: 1, Last Notification:
Mon Aug 5 17:31:06 2013
[1375784181.309276] [032.1] [pid=14943] We shouldn't re-notify contacts
about this host problem.
[1375784181.309308] [032.0] [pid=14943] Notification viability test
failed. No notification will be sent out.
[1375784181.309351] [032.0] [pid=14943] ** Service Notification Attempt **
Host: 'capua1', Service: 'Check_MK', Type: 0, Options: 0, Current State: 2,
Last Notification: Thu Jan 1 01:00:00 1970
[1375784181.309391] [032.1] [pid=14943] The host is either down or
unreachable, so we won't notify contacts about this service.
[1375784181.309421] [032.0] [pid=14943] Notification viability test
failed. No notification will be sent out.
[1375784181.336258] [032.0] [pid=14943] ** Service Notification Attempt **
Host: 'capua1', Service: 'Check_MK', Type: 99, Options: 0, Current State: 2,
Last Notification: Thu Jan 1 01:00:00 1970
[1375784181.336331] [032.0] [pid=14943] Notification viability test
passed.
[1375784181.336361] [032.1] [pid=14943] Current notification number: 0
(unchanged)
[1375784181.336393] [032.1] [pid=14943] Service notification will NOT be
escalated.
[1375784181.336427] [032.1] [pid=14943] Adding normal contacts for service
to notification list.
[1375784182.135587] [032.0] [pid=14943] 1 contacts were notified.

Il 06/08/2013 11:57, Marcel Schulte ha scritto:

So the problem changed, the initial one is solved. Goog news!

You can check the used command in WATO -> Global settings ->
Notifications.
Try to execute that command as the user nagios runs as. Maybe permissions
must be chamged or similar.

sent from my SGS3

Am 06.08.2013 11:49 schrieb "Presidio TI DLCI" >> <presidio.ti.dlci@interno.it>:

This is the notification log:
[1375782449.105267] [032.0] [pid=893] ** Host Notification Attempt **
Host: 'capua1', Type: 0, Options: 0, Current State: 1, Last Notification:
Mon Aug 5 17:31:06 2013
[1375782449.105373] [032.1] [pid=893] We shouldn't re-notify contacts
about this host problem.
[1375782449.105406] [032.0] [pid=893] Notification viability test failed.
No notification will be sent out.
[1375782449.292236] [032.0] [pid=893] ** Host Notification Attempt **
Host: 'capua1', Type: 99, Options: 0, Current State: 1, Last Notification:
Mon Aug 5 17:31:06 2013
[1375782449.292311] [032.0] [pid=893] Notification viability test passed.
[1375782449.292342] [032.1] [pid=893] Current notification number: 1
(unchanged)
[1375782449.292373] [032.1] [pid=893] Host notification will NOT be
escalated.
[1375782449.292402] [032.1] [pid=893] Adding normal contacts for host to
notification list.
[1375782450.469510] [032.0] [pid=893] 1 contacts were notified.

This is messages:
Aug 6 11:47:29 netmonitor4 nagios: EXTERNAL COMMAND:
SEND_CUSTOM_HOST_NOTIFICATION;capua1;0;nagiosadmin;TEST
Aug 6 11:47:29 netmonitor4 nagios: HOST NOTIFICATION:
nagiosadmin;capua1;CUSTOM (DOWN);check-mk-notify;CRITICAL - 172.25.3.252:
rta nan, lost 100%;nagiosadmin

But I haven't received the email, does the check_mk plugin use comman
"mail" or "sendmail"? I've only the second.

Il 06/08/2013 11:42, Marcel Schulte ha scritto:

Thanks.

Hoped to see empty Host contactgroups

Did you try to send test notification after last changes? What does

the debug log (for notifications) say? At the beginning it said "no

contacts found for host").

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Ah ok! Sorry!

Il 06/08/2013 11:28, Marcel Schulte ha scritto:

OK, maybe I wasn't specific enough (because that's the preferences

page again)...

Open this URL and send a shot:

http(s)://<url_to_you_multisite_ui>/view.py?host=capua1&view_name=hoststatus

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Marcel I've sent it in a previous email, here you are in attachment

Il 06/08/2013 10:57, Marcel Schulte ha scritto:

One more.

I'm still waiting for the host's detail page...

2013/8/6 Marcel Schulte <schulte.marcel@gmail.com>:

Did you do that here:

WATO -> Host and service parameters -> Grouping -> Assignment of hosts

to contact groups

or here:

WATO -> Host and service parameters -> Grouping -> Assignment of

services to contact groups?

Your screenshot shows the rule of the second possibility - but that's

wrong, the first one would be right.

Don't forget to apply changes...

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

I've created the rule in grouping menu only for host like you suggested,

but nothing. what command the notification plugin use? The one specified

in the nagios config file (commands.cfg), associated in contact.cfg to

the user? Or it has its own?

Il 06/08/2013 10:43, Marcel Schulte ha scritto:

As mentioned: create your rule for the host, not the host's services.

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Danny,

actually I've removed all filters, but I have the same problem.

Il 06/08/2013 10:04, Kip, Danny (CIV) ha scritto:

It's probably nothing, but I notice you mentioned you added 'capua_1' to
the contact group, but the logging excerpt says 'capua1' without underscore.

If this is really the case, that would be a good explanation

//Danny.

-----Oorspronkelijk bericht-----

Van: Presidio TI DLCI [mailto:presidio.ti.dlci@interno.it]

Verzonden: maandag 5 augustus 2013 12:42

Aan: checkmk-en@lists.mathias-kettner.de

Onderwerp: [Check_mk (english)] notification trouble

Hi,

I have a problem with check_mk notification. I followed the wiki

(http://mathias-kettner.de/checkmk_flexible_notifications.html) an I

have the attempted string in /var/log/messages after clicking the test

button. Manually using sendmail messages are delivered. From debug I

have the following text:

[1375698038.168104] [032.0] [pid=15374] Notification viability test
passed.

[1375698038.168132] [032.1] [pid=15374] Current notification number: 1

(incremented)

[1375698038.168162] [032.1] [pid=15374] Host notification will NOT be

escalated.

[1375698038.168189] [032.1] [pid=15374] Adding normal contacts for host

to notification list.

[1375698038.168223] [032.0] [pid=15374] No contacts were found for

notification purposes. No notification was sent out.

[1375698038.168266] [032.0] [pid=15374] ** Service Notification Attempt

** Host: 'capua1', Service: 'Check_MK', Type: 0, Options: 0, Current

State: 2, Last Notification: Thu Jan 1 01:00:00 1970

The host capua_1 has been added properly to contact group and the

relative contact too.

Could you help me to reso

lve this problem?

Thank You for your attention

_______________________________________________

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Presidio_TI_DLCI · August 7, 2013, 6:57am

Yes, it crashed trying to write on body.log.

···

Il 06/08/2013 19:40, Marcel Schulte ha scritto:

Sounds like another permission issue. Did you activate "debug
notifications" in WATO -> Global settings -> Notifications? Should
give you some hints what went wrong...

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

In general it seems that there are write permission problems with logfiles.
Now I can receive mail, but they are empty

Il 06/08/2013 18:11, Marcel Schulte ha scritto:

Cool, solved!

Nobody using OMD falls into these traps

sent from my SGS3

Am 06.08.2013 18:06 schrieb "Presidio TI DLCI" >> <presidio.ti.dlci@interno.it>:

Hi,
the problem was in the notify.py script. The lack of a permission on
body.log stopped the script, preventing the mail to be send.

Il 06/08/2013 13:45, Kip, Danny (CIV) ha scritto:

I think I noticed your notification period set to 15 hours in one of your
screenshots.

So retesting within 15 hours will probably only give you this sort of
logging:

[1375784181.309276] [032.1] [pid=14943] We shouldn't re-notify contacts
about this host problem.
[1375784181.309308] [032.0] [pid=14943] Notification viability test
failed. No notification will be sent out.

________________________________

Van: Marcel Schulte [mailto:schulte.marcel@gmail.com]
Verzonden: dinsdag 6 augustus 2013 13:20
Aan: Presidio TI DLCI
CC: checkmk-en@lists.mathias-kettner.de
Onderwerp: Re: [Check_mk (english)] notification trouble

From debug: no notification will be sent

--
-------------------------------------------------------------
 Presidio Telecom Italia
 Dip.to Libert� Civili e Immigrazione - Ministero dell'Interno
 Tel: 06 465 25 775 / 06 69 000 190
 E-mail: presidio.ti.dlci@interno.it
 -------------------------------------------------------------

I'll havw to test this for myself...

sent from my SGS3

Am 06.08.2013 12:20 schrieb "Presidio TI DLCI" >>> <presidio.ti.dlci@interno.it>:

I'm so stupid! I didn't noticed that line on the global settings. I
believed that the config for email should have be done from nagios config
files. Anyway I've changed the command in "/usr/sbin/sendmail -vt
$CONTACTEMAIL$", but I still can't receive email. Making the test I've the
following in the debug:
[1375784181.309122] [032.0] [pid=14943] ** Host Notification Attempt **
Host: 'capua1', Type: 0, Options: 0, Current State: 1, Last Notification:
Mon Aug 5 17:31:06 2013
[1375784181.309276] [032.1] [pid=14943] We shouldn't re-notify contacts
about this host problem.
[1375784181.309308] [032.0] [pid=14943] Notification viability test
failed. No notification will be sent out.
[1375784181.309351] [032.0] [pid=14943] ** Service Notification Attempt **
Host: 'capua1', Service: 'Check_MK', Type: 0, Options: 0, Current State: 2,
Last Notification: Thu Jan 1 01:00:00 1970
[1375784181.309391] [032.1] [pid=14943] The host is either down or
unreachable, so we won't notify contacts about this service.
[1375784181.309421] [032.0] [pid=14943] Notification viability test
failed. No notification will be sent out.
[1375784181.336258] [032.0] [pid=14943] ** Service Notification Attempt **
Host: 'capua1', Service: 'Check_MK', Type: 99, Options: 0, Current State: 2,
Last Notification: Thu Jan 1 01:00:00 1970
[1375784181.336331] [032.0] [pid=14943] Notification viability test
passed.
[1375784181.336361] [032.1] [pid=14943] Current notification number: 0
(unchanged)
[1375784181.336393] [032.1] [pid=14943] Service notification will NOT be
escalated.
[1375784181.336427] [032.1] [pid=14943] Adding normal contacts for service
to notification list.
[1375784182.135587] [032.0] [pid=14943] 1 contacts were notified.

Il 06/08/2013 11:57, Marcel Schulte ha scritto:

So the problem changed, the initial one is solved. Goog news!

You can check the used command in WATO -> Global settings ->
Notifications.
Try to execute that command as the user nagios runs as. Maybe permissions
must be chamged or similar.

sent from my SGS3

Am 06.08.2013 11:49 schrieb "Presidio TI DLCI" >>> <presidio.ti.dlci@interno.it>:

This is the notification log:
[1375782449.105267] [032.0] [pid=893] ** Host Notification Attempt **
Host: 'capua1', Type: 0, Options: 0, Current State: 1, Last Notification:
Mon Aug 5 17:31:06 2013
[1375782449.105373] [032.1] [pid=893] We shouldn't re-notify contacts
about this host problem.
[1375782449.105406] [032.0] [pid=893] Notification viability test failed.
No notification will be sent out.
[1375782449.292236] [032.0] [pid=893] ** Host Notification Attempt **
Host: 'capua1', Type: 99, Options: 0, Current State: 1, Last Notification:
Mon Aug 5 17:31:06 2013
[1375782449.292311] [032.0] [pid=893] Notification viability test passed.
[1375782449.292342] [032.1] [pid=893] Current notification number: 1
(unchanged)
[1375782449.292373] [032.1] [pid=893] Host notification will NOT be
escalated.
[1375782449.292402] [032.1] [pid=893] Adding normal contacts for host to
notification list.
[1375782450.469510] [032.0] [pid=893] 1 contacts were notified.

This is messages:
Aug 6 11:47:29 netmonitor4 nagios: EXTERNAL COMMAND:
SEND_CUSTOM_HOST_NOTIFICATION;capua1;0;nagiosadmin;TEST
Aug 6 11:47:29 netmonitor4 nagios: HOST NOTIFICATION:
nagiosadmin;capua1;CUSTOM (DOWN);check-mk-notify;CRITICAL - 172.25.3.252:
rta nan, lost 100%;nagiosadmin

But I haven't received the email, does the check_mk plugin use comman
"mail" or "sendmail"? I've only the second.

Il 06/08/2013 11:42, Marcel Schulte ha scritto:

Thanks.

Hoped to see empty Host contactgroups

Did you try to send test notification after last changes? What does

the debug log (for notifications) say? At the beginning it said "no

contacts found for host").

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Ah ok! Sorry!

Il 06/08/2013 11:28, Marcel Schulte ha scritto:

OK, maybe I wasn't specific enough (because that's the preferences

page again)...

Open this URL and send a shot:

http(s)://<url_to_you_multisite_ui>/view.py?host=capua1&view_name=hoststatus

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Marcel I've sent it in a previous email, here you are in attachment

Il 06/08/2013 10:57, Marcel Schulte ha scritto:

One more.

I'm still waiting for the host's detail page...

2013/8/6 Marcel Schulte <schulte.marcel@gmail.com>:

Did you do that here:

WATO -> Host and service parameters -> Grouping -> Assignment of hosts

to contact groups

or here:

WATO -> Host and service parameters -> Grouping -> Assignment of

services to contact groups?

Your screenshot shows the rule of the second possibility - but that's

wrong, the first one would be right.

Don't forget to apply changes...

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

I've created the rule in grouping menu only for host like you suggested,

but nothing. what command the notification plugin use? The one specified

in the nagios config file (commands.cfg), associated in contact.cfg to

the user? Or it has its own?

Il 06/08/2013 10:43, Marcel Schulte ha scritto:

As mentioned: create your rule for the host, not the host's services.

2013/8/6 Presidio TI DLCI <presidio.ti.dlci@interno.it>:

Danny,

actually I've removed all filters, but I have the same problem.

Il 06/08/2013 10:04, Kip, Danny (CIV) ha scritto:

It's probably nothing, but I notice you mentioned you added 'capua_1' to
the contact group, but the logging excerpt says 'capua1' without underscore.

If this is really the case, that would be a good explanation

//Danny.

-----Oorspronkelijk bericht-----

Van: Presidio TI DLCI [mailto:presidio.ti.dlci@interno.it]

Verzonden: maandag 5 augustus 2013 12:42

Aan: checkmk-en@lists.mathias-kettner.de

Onderwerp: [Check_mk (english)] notification trouble

Hi,

I have a problem with check_mk notification. I followed the wiki

(http://mathias-kettner.de/checkmk_flexible_notifications.html) an I

have the attempted string in /var/log/messages after clicking the test

button. Manually using sendmail messages are delivered. From debug I

have the following text:

[1375698038.168104] [032.0] [pid=15374] Notification viability test
passed.

[1375698038.168132] [032.1] [pid=15374] Current notification number: 1

(incremented)

[1375698038.168162] [032.1] [pid=15374] Host notification will NOT be

escalated.

[1375698038.168189] [032.1] [pid=15374] Adding normal contacts for host

to notification list.

[1375698038.168223] [032.0] [pid=15374] No contacts were found for

notification purposes. No notification was sent out.

[1375698038.168266] [032.0] [pid=15374] ** Service Notification Attempt

** Host: 'capua1', Service: 'Check_MK', Type: 0, Options: 0, Current

State: 2, Last Notification: Thu Jan 1 01:00:00 1970

The host capua_1 has been added properly to contact group and the

relative contact too.

Could you help me to reso

lve this problem?

Thank You for your attention

_______________________________________________

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Presidio_TI_DLCI · August 7, 2013, 8:46am

Hi,
trying to send graphs in notification I had the following error in
notify.log:

              Output: Unable to fetch graph infos: Unable to locate

pnp4nagios index.php ().

I've followed what suggested

here:.
My code is a little diefferent and I’ve modified the path from
/share to /usr/local/pnp4nagios/share/:

···

http://lists.mathias-kettner.de/pipermail/checkmk-en/2013-April/008919.html

316 def fetch_pnp_data(context,
params):

317 try:

318 # Autodetect the path
in OMD environments

319 path =
“%s/usr/local/pnp4nagios/share/” % context[‘OMD_ROOT’]

320 except:

321 # Non-omd environment

use plugin argument 1

322 path =
context.get(‘PARAMETER_1’, ‘’)

323

324 if not
os.path.exists(path):

325 raise
GraphException(‘Unable to locate pnp4nagios index.php
(%s)’ % path)

326

327 return
os.popen(‘REMOTE_USER=“%s” php %s “%s”’ %
(context[‘CONTACTNAME’], path, params)).read()

  Il 07/08/2013 08:57, Presidio TI DLCI

ha scritto:


Yes, it crashed trying to write on body.log.
Il 06/08/2013 19:40, Marcel Schulte ha scritto:


Sounds like another permission issue. Did you activate "debug
notifications" in WATO -> Global settings -> Notifications? Should
give you some hints what went wrong...
2013/8/6 Presidio TI DLCI :


In general it seems that there are write permission problems with logfiles.
Now I can receive mail, but they are empty
Il 06/08/2013 18:11, Marcel Schulte ha scritto:
Cool, solved!
Nobody using OMD falls into these traps :-D
sent from my SGS3
Am 06.08.2013 18:06 schrieb "Presidio TI DLCI"
:


Hi,
the problem was in the notify.py script. The lack of a permission on
body.log stopped the script, preventing the mail to be send.
Il 06/08/2013 13:45, Kip, Danny (CIV) ha scritto:
I think I noticed your notification period set to 15 hours in one of your
screenshots.
So retesting within 15 hours will probably only give you this sort of
logging:
[1375784181.309276] [032.1] [pid=14943] We shouldn't re-notify contacts
about this host problem.
[1375784181.309308] [032.0] [pid=14943] Notification viability test
failed. No notification will be sent out.
________________________________
Van: Marcel Schulte []
Verzonden: dinsdag 6 augustus 2013 13:20
Aan: Presidio TI DLCI
CC: Onderwerp: Re: [Check_mk (english)] notification trouble
>From debug: no notification will be sent
--
-------------------------------------------------------------
Presidio Telecom Italia
Dip.to Libertà Civili e Immigrazione - Ministero dell'Interno
Tel: 06 465 25 775 / 06 69 000 190
E-mail: -------------------------------------------------------------
I'll havw to test this for myself...
sent from my SGS3
Am 06.08.2013 12:20 schrieb "Presidio TI DLCI"
:
I'm so stupid! I didn't noticed that line on the global settings. I
believed that the config for email should have be done from nagios config
files. Anyway I've changed the command in "/usr/sbin/sendmail -vt
$CONTACTEMAIL$", but I still can't receive email. Making the test I've the
following in the debug:
[1375784181.309122] [032.0] [pid=14943] ** Host Notification Attempt **
Host: 'capua1', Type: 0, Options: 0, Current State: 1, Last Notification:
Mon Aug 5 17:31:06 2013
[1375784181.309276] [032.1] [pid=14943] We shouldn't re-notify contacts
about this host problem.
[1375784181.309308] [032.0] [pid=14943] Notification viability test
failed. No notification will be sent out.
[1375784181.309351] [032.0] [pid=14943] ** Service Notification Attempt **
Host: 'capua1', Service: 'Check_MK', Type: 0, Options: 0, Current State: 2,
Last Notification: Thu Jan 1 01:00:00 1970
[1375784181.309391] [032.1] [pid=14943] The host is either down or
unreachable, so we won't notify contacts about this service.
[1375784181.309421] [032.0] [pid=14943] Notification viability test
failed. No notification will be sent out.
[1375784181.336258] [032.0] [pid=14943] ** Service Notification Attempt **
Host: 'capua1', Service: 'Check_MK', Type: 99, Options: 0, Current State: 2,
Last Notification: Thu Jan 1 01:00:00 1970
[1375784181.336331] [032.0] [pid=14943] Notification viability test
passed.
[1375784181.336361] [032.1] [pid=14943] Current notification number: 0
(unchanged)
[1375784181.336393] [032.1] [pid=14943] Service notification will NOT be
escalated.
[1375784181.336427] [032.1] [pid=14943] Adding normal contacts for service
to notification list.
[1375784182.135587] [032.0] [pid=14943] 1 contacts were notified.
Il 06/08/2013 11:57, Marcel Schulte ha scritto:
So the problem changed, the initial one is solved. Goog news!
You can check the used command in WATO -> Global settings ->
Notifications.
Try to execute that command as the user nagios runs as. Maybe permissions
must be chamged or similar.
sent from my SGS3
Am 06.08.2013 11:49 schrieb "Presidio TI DLCI"
:
This is the notification log:
[1375782449.105267] [032.0] [pid=893] ** Host Notification Attempt **
Host: 'capua1', Type: 0, Options: 0, Current State: 1, Last Notification:
Mon Aug 5 17:31:06 2013
[1375782449.105373] [032.1] [pid=893] We shouldn't re-notify contacts
about this host problem.
[1375782449.105406] [032.0] [pid=893] Notification viability test failed.
No notification will be sent out.
[1375782449.292236] [032.0] [pid=893] ** Host Notification Attempt **
Host: 'capua1', Type: 99, Options: 0, Current State: 1, Last Notification:
Mon Aug 5 17:31:06 2013
[1375782449.292311] [032.0] [pid=893] Notification viability test passed.
[1375782449.292342] [032.1] [pid=893] Current notification number: 1
(unchanged)
[1375782449.292373] [032.1] [pid=893] Host notification will NOT be
escalated.
[1375782449.292402] [032.1] [pid=893] Adding normal contacts for host to
notification list.
[1375782450.469510] [032.0] [pid=893] 1 contacts were notified.
This is messages:
Aug 6 11:47:29 netmonitor4 nagios: EXTERNAL COMMAND:
SEND_CUSTOM_HOST_NOTIFICATION;capua1;0;nagiosadmin;TEST
Aug 6 11:47:29 netmonitor4 nagios: HOST NOTIFICATION:
nagiosadmin;capua1;CUSTOM (DOWN);check-mk-notify;CRITICAL - 172.25.3.252:
rta nan, lost 100%;nagiosadmin
But I haven't received the email, does the check_mk plugin use comman
"mail" or "sendmail"? I've only the second.
Il 06/08/2013 11:42, Marcel Schulte ha scritto:
Thanks.
Hoped to see empty Host contactgroups ;-)
Did you try to send test notification after last changes? What does
the debug log (for notifications) say? At the beginning it said "no
contacts found for host").
2013/8/6 Presidio TI DLCI :
Ah ok! Sorry!
Il 06/08/2013 11:28, Marcel Schulte ha scritto:
OK, maybe I wasn't specific enough (because that's the preferences
page again)...
Open this URL and send a shot:
http(s)://<url_to_you_multisite_ui>/view.py?host=capua1&view_name=hoststatus
2013/8/6 Presidio TI DLCI :
Marcel I've sent it in a previous email, here you are in attachment
Il 06/08/2013 10:57, Marcel Schulte ha scritto:
One more. ;-)
I'm still waiting for the host's detail page...
2013/8/6 Marcel Schulte :
Did you do that here:
WATO -> Host and service parameters -> Grouping -> Assignment of hosts
to contact groups
or here:
WATO -> Host and service parameters -> Grouping -> Assignment of
services to contact groups?
Your screenshot shows the rule of the second possibility - but that's
wrong, the first one would be right.
Don't forget to apply changes...
2013/8/6 Presidio TI DLCI :
I've created the rule in grouping menu only for host like you suggested,
but nothing. what command the notification plugin use? The one specified
in the nagios config file (commands.cfg), associated in contact.cfg to
the user? Or it has its own?
Il 06/08/2013 10:43, Marcel Schulte ha scritto:
As mentioned: create your rule for the host, not the host's services.
2013/8/6 Presidio TI DLCI :
Danny,
actually I've removed all filters, but I have the same problem.
Il 06/08/2013 10:04, Kip, Danny (CIV) ha scritto:
It's probably nothing, but I notice you mentioned you added 'capua_1' to
the contact group, but the logging excerpt says 'capua1' without underscore.
If this is really the case, that would be a good explanation :)
//Danny.
-----Oorspronkelijk bericht-----
Van: Presidio TI DLCI []
Verzonden: maandag 5 augustus 2013 12:42
Aan: Onderwerp: [Check_mk (english)] notification trouble
Hi,
I have a problem with check_mk notification. I followed the wiki
() an I
have the attempted string in /var/log/messages after clicking the test
button. Manually using sendmail messages are delivered. From debug I
have the following text:
[1375698038.168104] [032.0] [pid=15374] Notification viability test
passed.
[1375698038.168132] [032.1] [pid=15374] Current notification number: 1
(incremented)
[1375698038.168162] [032.1] [pid=15374] Host notification will NOT be
escalated.
[1375698038.168189] [032.1] [pid=15374] Adding normal contacts for host
to notification list.
[1375698038.168223] [032.0] [pid=15374] No contacts were found for
notification purposes. No notification was sent out.
[1375698038.168266] [032.0] [pid=15374] ** Service Notification Attempt
** Host: 'capua1', Service: 'Check_MK', Type: 0, Options: 0, Current
State: 2, Last Notification: Thu Jan 1 01:00:00 1970
The host capua_1 has been added properly to contact group and the
relative contact too.
Could you help me to reso
lve this problem?
Thank You for your attention
_______________________________________________
checkmk-en mailing list

Presidio_TI_DLCI · August 7, 2013, 1:26pm

Solved,
I haven’t an OMD context, so I have to give the parameter from wato
in user&contacts->edit user->notificationframe->Plugin
Arguments (the pnp4nagios index.php path, in my case:
/usr/local/pnp4nagios/share/index.php). After, from
/var/lib/check_mk/notify/notify.log I’ve noticed what following:

session_start():
open(/var/lib/php/session/sess_44tojg5t2fqum7a2uje90aa6u5, O_RDWR)
failed: Permission denied (13)
The /var/lib/php/session/sess permission was 770, but
they must be changed in 777.

···

Il 07/08/2013 10:46, Presidio TI DLCI
ha scritto:

Hi,
  trying to send graphs in notification I had the following error in
notify.log:

Output: Unable to fetch graph infos: Unable to

locate pnp4nagios index.php ().
  I've followed what suggested here:.
My code is a little diefferent and I’ve modified the path from
/share to /usr/local/pnp4nagios/share/:
http://lists.mathias-kettner.de/pipermail/checkmk-en/2013-April/008919.html

316 def fetch_pnp_data(context,
params):

317 try:

318 # Autodetect the
path in OMD environments

319 path =
“%s/usr/local/pnp4nagios/share/” % context[‘OMD_ROOT’]

320 except:

321 # Non-omd
environment - use plugin argument 1

322 path =
context.get(‘PARAMETER_1’, ‘’)

323

324 if not
os.path.exists(path):

325 raise
GraphException(‘Unable to locate pnp4nagios index.php
(%s)’ % path)

326

327 return
os.popen(‘REMOTE_USER=“%s” php %s “%s”’ %
(context[‘CONTACTNAME’], path, params)).read()

    Il 07/08/2013 08:57, Presidio TI DLCI

ha scritto:


Yes, it crashed trying to write on body.log.
Il 06/08/2013 19:40, Marcel Schulte ha scritto:


Sounds like another permission issue. Did you activate "debug
notifications" in WATO -> Global settings -> Notifications? Should
give you some hints what went wrong...
2013/8/6 Presidio TI DLCI :


In general it seems that there are write permission problems with logfiles.
Now I can receive mail, but they are empty
Il 06/08/2013 18:11, Marcel Schulte ha scritto:
Cool, solved!
Nobody using OMD falls into these traps :-D
sent from my SGS3
Am 06.08.2013 18:06 schrieb "Presidio TI DLCI"
:


Hi,
the problem was in the notify.py script. The lack of a permission on
body.log stopped the script, preventing the mail to be send.
Il 06/08/2013 13:45, Kip, Danny (CIV) ha scritto:
I think I noticed your notification period set to 15 hours in one of your
screenshots.
So retesting within 15 hours will probably only give you this sort of
logging:
[1375784181.309276] [032.1] [pid=14943] We shouldn't re-notify contacts
about this host problem.
[1375784181.309308] [032.0] [pid=14943] Notification viability test
failed. No notification will be sent out.
________________________________
Van: Marcel Schulte []
Verzonden: dinsdag 6 augustus 2013 13:20
Aan: Presidio TI DLCI
CC: Onderwerp: Re: [Check_mk (english)] notification trouble
>From debug: no notification will be sent
--
-------------------------------------------------------------
Presidio Telecom Italia
Dip.to Libertà Civili e Immigrazione - Ministero dell'Interno
Tel: 06 465 25 775 / 06 69 000 190
E-mail: -------------------------------------------------------------
I'll havw to test this for myself...
sent from my SGS3
Am 06.08.2013 12:20 schrieb "Presidio TI DLCI"
:
I'm so stupid! I didn't noticed that line on the global settings. I
believed that the config for email should have be done from nagios config
files. Anyway I've changed the command in "/usr/sbin/sendmail -vt
$CONTACTEMAIL$", but I still can't receive email. Making the test I've the
following in the debug:
[1375784181.309122] [032.0] [pid=14943] ** Host Notification Attempt **
Host: 'capua1', Type: 0, Options: 0, Current State: 1, Last Notification:
Mon Aug 5 17:31:06 2013
[1375784181.309276] [032.1] [pid=14943] We shouldn't re-notify contacts
about this host problem.
[1375784181.309308] [032.0] [pid=14943] Notification viability test
failed. No notification will be sent out.
[1375784181.309351] [032.0] [pid=14943] ** Service Notification Attempt **
Host: 'capua1', Service: 'Check_MK', Type: 0, Options: 0, Current State: 2,
Last Notification: Thu Jan 1 01:00:00 1970
[1375784181.309391] [032.1] [pid=14943] The host is either down or
unreachable, so we won't notify contacts about this service.
[1375784181.309421] [032.0] [pid=14943] Notification viability test
failed. No notification will be sent out.
[1375784181.336258] [032.0] [pid=14943] ** Service Notification Attempt **
Host: 'capua1', Service: 'Check_MK', Type: 99, Options: 0, Current State: 2,
Last Notification: Thu Jan 1 01:00:00 1970
[1375784181.336331] [032.0] [pid=14943] Notification viability test
passed.
[1375784181.336361] [032.1] [pid=14943] Current notification number: 0
(unchanged)
[1375784181.336393] [032.1] [pid=14943] Service notification will NOT be
escalated.
[1375784181.336427] [032.1] [pid=14943] Adding normal contacts for service
to notification list.
[1375784182.135587] [032.0] [pid=14943] 1 contacts were notified.
Il 06/08/2013 11:57, Marcel Schulte ha scritto:
So the problem changed, the initial one is solved. Goog news!
You can check the used command in WATO -> Global settings ->
Notifications.
Try to execute that command as the user nagios runs as. Maybe permissions
must be chamged or similar.
sent from my SGS3
Am 06.08.2013 11:49 schrieb "Presidio TI DLCI"
:
This is the notification log:
[1375782449.105267] [032.0] [pid=893] ** Host Notification Attempt **
Host: 'capua1', Type: 0, Options: 0, Current State: 1, Last Notification:
Mon Aug 5 17:31:06 2013
[1375782449.105373] [032.1] [pid=893] We shouldn't re-notify contacts
about this host problem.
[1375782449.105406] [032.0] [pid=893] Notification viability test failed.
No notification will be sent out.
[1375782449.292236] [032.0] [pid=893] ** Host Notification Attempt **
Host: 'capua1', Type: 99, Options: 0, Current State: 1, Last Notification:
Mon Aug 5 17:31:06 2013
[1375782449.292311] [032.0] [pid=893] Notification viability test passed.
[1375782449.292342] [032.1] [pid=893] Current notification number: 1
(unchanged)
[1375782449.292373] [032.1] [pid=893] Host notification will NOT be
escalated.
[1375782449.292402] [032.1] [pid=893] Adding normal contacts for host to
notification list.
[1375782450.469510] [032.0] [pid=893] 1 contacts were notified.
This is messages:
Aug 6 11:47:29 netmonitor4 nagios: EXTERNAL COMMAND:
SEND_CUSTOM_HOST_NOTIFICATION;capua1;0;nagiosadmin;TEST
Aug 6 11:47:29 netmonitor4 nagios: HOST NOTIFICATION:
nagiosadmin;capua1;CUSTOM (DOWN);check-mk-notify;CRITICAL - 172.25.3.252:
rta nan, lost 100%;nagiosadmin
But I haven't received the email, does the check_mk plugin use comman
"mail" or "sendmail"? I've only the second.
Il 06/08/2013 11:42, Marcel Schulte ha scritto:
Thanks.
Hoped to see empty Host contactgroups ;-)
Did you try to send test notification after last changes? What does
the debug log (for notifications) say? At the beginning it said "no
contacts found for host").
2013/8/6 Presidio TI DLCI :
Ah ok! Sorry!
Il 06/08/2013 11:28, Marcel Schulte ha scritto:
OK, maybe I wasn't specific enough (because that's the preferences
page again)...
Open this URL and send a shot:
http(s)://<url_to_you_multisite_ui>/view.py?host=capua1&view_name=hoststatus
2013/8/6 Presidio TI DLCI :
Marcel I've sent it in a previous email, here you are in attachment
Il 06/08/2013 10:57, Marcel Schulte ha scritto:
One more. ;-)
I'm still waiting for the host's detail page...
2013/8/6 Marcel Schulte :
Did you do that here:
WATO -> Host and service parameters -> Grouping -> Assignment of hosts
to contact groups
or here:
WATO -> Host and service parameters -> Grouping -> Assignment of
services to contact groups?
Your screenshot shows the rule of the second possibility - but that's
wrong, the first one would be right.
Don't forget to apply changes...
2013/8/6 Presidio TI DLCI :
I've created the rule in grouping menu only for host like you suggested,
but nothing. what command the notification plugin use? The one specified
in the nagios config file (commands.cfg), associated in contact.cfg to
the user? Or it has its own?
Il 06/08/2013 10:43, Marcel Schulte ha scritto:
As mentioned: create your rule for the host, not the host's services.
2013/8/6 Presidio TI DLCI :
Danny,
actually I've removed all filters, but I have the same problem.
Il 06/08/2013 10:04, Kip, Danny (CIV) ha scritto:
It's probably nothing, but I notice you mentioned you added 'capua_1' to
the contact group, but the logging excerpt says 'capua1' without underscore.
If this is really the case, that would be a good explanation :)
//Danny.
-----Oorspronkelijk bericht-----
Van: Presidio TI DLCI []
Verzonden: maandag 5 augustus 2013 12:42
Aan: Onderwerp: [Check_mk (english)] notification trouble
Hi,
I have a problem with check_mk notification. I followed the wiki
() an I
have the attempted string in /var/log/messages after clicking the test
button. Manually using sendmail messages are delivered. From debug I
have the following text:
[1375698038.168104] [032.0] [pid=15374] Notification viability test
passed.
[1375698038.168132] [032.1] [pid=15374] Current notification number: 1
(incremented)
[1375698038.168162] [032.1] [pid=15374] Host notification will NOT be
escalated.
[1375698038.168189] [032.1] [pid=15374] Adding normal contacts for host
to notification list.
[1375698038.168223] [032.0] [pid=15374] No contacts were found for
notification purposes. No notification was sent out.
[1375698038.168266] [032.0] [pid=15374] ** Service Notification Attempt
** Host: 'capua1', Service: 'Check_MK', Type: 0, Options: 0, Current
State: 2, Last Notification: Thu Jan 1 01:00:00 1970
The host capua_1 has been added properly to contact group and the
relative contact too.
Could you help me to reso
lve this problem?
Thank You for your attention
_______________________________________________
checkmk-en mailing list