Discussion:
[Check_mk (english)] CMK raw 1.5.p2 won't "activate" after adding periodic notifications for services.
Fernando CMK
2018-09-10 10:14:10 UTC
Permalink
Hi everyone

I have one cmk raw 1.5p2 where I'm currently monitoring about 100 hosts,
3400+ services. It's running on top of centos 7.

The problem comes when we tried to add periodic notifications for both
hosts and services.

First we enabled notifications for hosts, and that went ok. However, when
we tried adding notifications for services problems (that is, we want cmk
will renotify of a service critical every X minutes), then cmk won't
activate the changes.

I tried on a "clean" new site I created, and on that mostly empty new site,
it worked (that is, we haven't actually tried to have that cmk renotify on
an issue, but at least it activated the changed. WE can try to see if it
actually works if it helps) . I did a backup of the system, took it to
another server, restored it, and in there, it has the same behavior: cmk
won't activate the changes after adding the periodic service notifications.

I then tried adding on main.mk the following (haven't tried only services
though but both host and services):

extra_host_conf.setdefault('notification_interval', [])

extra_host_conf['notification_interval'] = [
( 10.0, [], ALL_HOSTS, {'description': u'resend host notifications every
10 minutes'} ),
] + extra_host_conf['notification_interval']


extra_service_conf.setdefault('notification_interval', [])

extra_service_conf['notification_interval'] = [
( 10.0, [], ALL_HOSTS, ALL_SERVICES, {'description': u'resend service
notifications every 10 minutes'} ),
] + extra_service_conf['notification_interval']


And then, after making another change on the config, not related to this,
then cmk won't activate (it just goes after the 10 seconds general figures,
and stays there saying "Activating").

Is there anything in particular I should be looking for regarding this
issue or that we might've done wrong?

TIA, Fer.
Arno Wijnhoven
2018-10-12 10:38:51 UTC
Permalink
I’ve got the same issue, I’m currently on 1.5.0p5 (but I’ve got the error at least since 1.5.0p3).
It looks like there’s also an amount of hosts involved. If I remove some hosts on a particular monitoring server, I can activate again (after stopping/starting OMD on that host).
If I’m <302 hosts on this server it works, even with periodic notifications enabled. If I add another host, activation will fail.

Did you find a solution for this?

Arno Wijnhoven

From: checkmk-en [mailto:checkmk-en-***@lists.mathias-kettner.de] On Behalf Of Fernando CMK
Sent: maandag 10 september 2018 12:14
To: checkmk-***@lists.mathias-kettner.de
Subject: [Check_mk (english)] CMK raw 1.5.p2 won't "activate" after adding periodic notifications for services.

Hi everyone

I have one cmk raw 1.5p2 where I'm currently monitoring about 100 hosts, 3400+ services. It's running on top of centos 7.

The problem comes when we tried to add periodic notifications for both hosts and services.

First we enabled notifications for hosts, and that went ok. However, when we tried adding notifications for services problems (that is, we want cmk will renotify of a service critical every X minutes), then cmk won't activate the changes.

I tried on a "clean" new site I created, and on that mostly empty new site, it worked (that is, we haven't actually tried to have that cmk renotify on an issue, but at least it activated the changed. WE can try to see if it actually works if it helps) . I did a backup of the system, took it to another server, restored it, and in there, it has the same behavior: cmk won't activate the changes after adding the periodic service notifications.

I then tried adding on main.mk<http://main.mk> the following (haven't tried only services though but both host and services):

extra_host_conf.setdefault('notification_interval', [])

extra_host_conf['notification_interval'] = [
( 10.0, [], ALL_HOSTS, {'description': u'resend host notifications every 10 minutes'} ),
] + extra_host_conf['notification_interval']


extra_service_conf.setdefault('notification_interval', [])

extra_service_conf['notification_interval'] = [
( 10.0, [], ALL_HOSTS, ALL_SERVICES, {'description': u'resend service notifications every 10 minutes'} ),
] + extra_service_conf['notification_interval']


And then, after making another change on the config, not related to this, then cmk won't activate (it just goes after the 10 seconds general figures, and stays there saying "Activating").

Is there anything in particular I should be looking for regarding this issue or that we might've done wrong?

TIA, Fer.
Arno Wijnhoven
2018-10-12 10:54:10 UTC
Permalink
Addition: it also seems to matter what time I set. With 60 minutes, it’s 302 hosts max (not sure about services, sorry).
With 600 minutes, I can still activate with more hosts. This is really strange.

I tried a fresh install (so, clean install 1.5.0p5) and an upgrade from 1.2.8p20 --> 1.4.0p35 -> 1.5.0p5.
Both have the same issue.

Arno Wijnhoven
T: 2580

From: checkmk-en [mailto:checkmk-en-***@lists.mathias-kettner.de] On Behalf Of Arno Wijnhoven
Sent: vrijdag 12 oktober 2018 12:39
To: Fernando CMK <***@gmail.com>; checkmk-***@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] CMK raw 1.5.p2 won't "activate" after adding periodic notifications for services.

I’ve got the same issue, I’m currently on 1.5.0p5 (but I’ve got the error at least since 1.5.0p3).
It looks like there’s also an amount of hosts involved. If I remove some hosts on a particular monitoring server, I can activate again (after stopping/starting OMD on that host).
If I’m <302 hosts on this server it works, even with periodic notifications enabled. If I add another host, activation will fail.

Did you find a solution for this?

Arno Wijnhoven

From: checkmk-en [mailto:checkmk-en-***@lists.mathias-kettner.de] On Behalf Of Fernando CMK
Sent: maandag 10 september 2018 12:14
To: checkmk-***@lists.mathias-kettner.de<mailto:checkmk-***@lists.mathias-kettner.de>
Subject: [Check_mk (english)] CMK raw 1.5.p2 won't "activate" after adding periodic notifications for services.

Hi everyone

I have one cmk raw 1.5p2 where I'm currently monitoring about 100 hosts, 3400+ services. It's running on top of centos 7.

The problem comes when we tried to add periodic notifications for both hosts and services.

First we enabled notifications for hosts, and that went ok. However, when we tried adding notifications for services problems (that is, we want cmk will renotify of a service critical every X minutes), then cmk won't activate the changes.

I tried on a "clean" new site I created, and on that mostly empty new site, it worked (that is, we haven't actually tried to have that cmk renotify on an issue, but at least it activated the changed. WE can try to see if it actually works if it helps) . I did a backup of the system, took it to another server, restored it, and in there, it has the same behavior: cmk won't activate the changes after adding the periodic service notifications.

I then tried adding on main.mk<http://main.mk> the following (haven't tried only services though but both host and services):

extra_host_conf.setdefault('notification_interval', [])

extra_host_conf['notification_interval'] = [
( 10.0, [], ALL_HOSTS, {'description': u'resend host notifications every 10 minutes'} ),
] + extra_host_conf['notification_interval']


extra_service_conf.setdefault('notification_interval', [])

extra_service_conf['notification_interval'] = [
( 10.0, [], ALL_HOSTS, ALL_SERVICES, {'description': u'resend service notifications every 10 minutes'} ),
] + extra_service_conf['notification_interval']


And then, after making another change on the config, not related to this, then cmk won't activate (it just goes after the 10 seconds general figures, and stays there saying "Activating").

Is there anything in particular I should be looking for regarding this issue or that we might've done wrong?

TIA, Fer.
Arno Wijnhoven
2018-10-12 11:15:13 UTC
Permalink
Ok, with the setting to 60 minutes I can’t activate.
However, with the setting at 120 minutes I can.

@Fernando, if it’s possible for you: change the time to a higher value for a temporary workaround.
Seems to work for me.

Arno Wijnhoven

From: Arno Wijnhoven
Sent: vrijdag 12 oktober 2018 12:54
To: Arno Wijnhoven <***@vsnsystemen.nl>; Fernando CMK <***@gmail.com>; checkmk-***@lists.mathias-kettner.de
Subject: RE: [Check_mk (english)] CMK raw 1.5.p2 won't "activate" after adding periodic notifications for services.

Addition: it also seems to matter what time I set. With 60 minutes, it’s 302 hosts max (not sure about services, sorry).
With 600 minutes, I can still activate with more hosts. This is really strange.

I tried a fresh install (so, clean install 1.5.0p5) and an upgrade from 1.2.8p20 --> 1.4.0p35 -> 1.5.0p5.
Both have the same issue.

Arno Wijnhoven
T: 2580

From: checkmk-en [mailto:checkmk-en-***@lists.mathias-kettner.de] On Behalf Of Arno Wijnhoven
Sent: vrijdag 12 oktober 2018 12:39
To: Fernando CMK <***@gmail.com<mailto:***@gmail.com>>; checkmk-***@lists.mathias-kettner.de<mailto:checkmk-***@lists.mathias-kettner.de>
Subject: Re: [Check_mk (english)] CMK raw 1.5.p2 won't "activate" after adding periodic notifications for services.

I’ve got the same issue, I’m currently on 1.5.0p5 (but I’ve got the error at least since 1.5.0p3).
It looks like there’s also an amount of hosts involved. If I remove some hosts on a particular monitoring server, I can activate again (after stopping/starting OMD on that host).
If I’m <302 hosts on this server it works, even with periodic notifications enabled. If I add another host, activation will fail.

Did you find a solution for this?

Arno Wijnhoven

From: checkmk-en [mailto:checkmk-en-***@lists.mathias-kettner.de] On Behalf Of Fernando CMK
Sent: maandag 10 september 2018 12:14
To: checkmk-***@lists.mathias-kettner.de<mailto:checkmk-***@lists.mathias-kettner.de>
Subject: [Check_mk (english)] CMK raw 1.5.p2 won't "activate" after adding periodic notifications for services.

Hi everyone

I have one cmk raw 1.5p2 where I'm currently monitoring about 100 hosts, 3400+ services. It's running on top of centos 7.

The problem comes when we tried to add periodic notifications for both hosts and services.

First we enabled notifications for hosts, and that went ok. However, when we tried adding notifications for services problems (that is, we want cmk will renotify of a service critical every X minutes), then cmk won't activate the changes.

I tried on a "clean" new site I created, and on that mostly empty new site, it worked (that is, we haven't actually tried to have that cmk renotify on an issue, but at least it activated the changed. WE can try to see if it actually works if it helps) . I did a backup of the system, took it to another server, restored it, and in there, it has the same behavior: cmk won't activate the changes after adding the periodic service notifications.

I then tried adding on main.mk<http://main.mk> the following (haven't tried only services though but both host and services):

extra_host_conf.setdefault('notification_interval', [])

extra_host_conf['notification_interval'] = [
( 10.0, [], ALL_HOSTS, {'description': u'resend host notifications every 10 minutes'} ),
] + extra_host_conf['notification_interval']


extra_service_conf.setdefault('notification_interval', [])

extra_service_conf['notification_interval'] = [
( 10.0, [], ALL_HOSTS, ALL_SERVICES, {'description': u'resend service notifications every 10 minutes'} ),
] + extra_service_conf['notification_interval']


And then, after making another change on the config, not related to this, then cmk won't activate (it just goes after the 10 seconds general figures, and stays there saying "Activating").

Is there anything in particular I should be looking for regarding this issue or that we might've done wrong?

TIA, Fer.

Loading...