Systemd services CRIT after update to 2.3.0p26

Troubleshooting
1

After installing the update, I see some problem regarding service alive checks on Linux hosts (check_mk-systemd_units_ services summary and check_mk-systemd_units sockets _summary).

The output is no longer “readable” as only the count of failed services is shown, but not the actually names of failed services:

“Total: 186, Disabled: 9, Failed: 1 CRIT”

I have an enterprise version, so the agents should update automatically. But even when doing a manual update of the agent, the problem persists.

I think even the number of failed services is “false positive”.

2

I moved your post to a dedicated thread, to not spam the release thread. :slight_smile:

I cannot reproduce this issue. Can you elaborate on what service(s) and port(s) fail exactly? Are you sure, this worked before?

3

Hi,

I think i face a similar situation on my Check-MK instance.
I upgraded it from “Checkmk Raw Edition 2.3.0p23” to “Checkmk Raw Edition 2.3.0p27”.

After the upgrade to version 2.3.0p27 some of the monitored Linux servers shows the following information:
Systemd Service Summary Total: 169, Disabled: 9, Failed: 2CRIT

What i found out is the following:
All affected server have a “Exclude units matching provided regex patterns” rule to ignore failed services. Now it seems that the rule is not working anymore. It recognizes the excluded service (that’s why the name of the failed service isn’t shown), but it states the service as critical and trigger an alert instead of ignoring it.

I hope this information will help to fix this bug.

I used the rules several month before upgrading to 2.3.0p27 and it always worked fine.

If you want a I can send you some screenshots from my system (as a new user I’m not allowed to upload files directly to this post)

4

Hi,

i just found another topic for this bug:

In the last post you can read that it should be fixed in p28.

1 Like
5

This is a known problem - discussed in the p27 release post.
There is also a solution for the problem with a small mkp available here.

2 Likes
6

Thanks for the information.
I prefer to wait for a bug fix in one of the next releases :slight_smile:

7

The mkp is an “official” bugfix until the next release.

1 Like
8

I can acknowledge, that the latest version of the .mkp works like a charm.

3 Likes
9

Hello!

If one of the answers helped you solve your question, please mark it as the solution. This way, you thank the person who helped you and also indicate that the question has been resolved. This, in turn, helps others who come across the same question.

Solution

Thank you!

10

Hello everyone!

Just wanted to let you know that the fix will be available with version p28.

Here you can find more information - [Release] Checkmk stable release 2.3.0p27 - #33 by lracic

Thanks for the help!

Best,
Luka

1 Like