CheckMK Appliances - static service failed (user@999)

[cg1603 (Christian Gehrig)]

**CMK version:2.3.P6
**OS version:1.7.1

**Error message:static service failed (user@999)

Hello Forum

I recently got this status from a check that is run directly on the CheckMK appliance.

• Systemd Service Summary
• Total: 113, Disabled: 4, Failed: 1, 1 static service failed (user@999)
  Total: 113
  Disabled: 4
  Failed: 1
  1 static service failed (user@999)

In the Systemctl Service view it is displayed like this

• ● user@999.service loaded failed failed User Manager for UID 999

What could this be and how can I fix it?

There seems to be a fix for this but I already installed this version 2.3.p6
Fix failed systemd units user@999.service when creating sites (checkmk.com)

[Dirk]

I’m not 100 % sure but I think these user@NUMBER services appear when a session for a user is created (when a user logs in, for example) and when checkmk fetches the data in that exact moment, the service is not yet up and running. Something like that.

I’d create a rule to just ignore them:

Systemd Service Summary Help

Yes, these user@NUMBER services appear from time to time. I suggest adding a rule Systemd Services Summary to ignore those units like so: [image] The \d+ is a regular expression and means “any number” so the rule will ignore units with these names. See also Systemd Service summary issues with check_mk

---

If you don’t want to ignore these services, then reset the failed state in the appliance like so:

sudo systemctl reset-failed user@999.service

But it may reappear then.

[cg1603 (Christian Gehrig)]

Hi Dirk,

ok i start the service with “sudo systemctl reset-failed user@999.service”…
and there is not longer in the service list?!
I’ll see if it comes back

Thanks!

[robin.gierse]

While @Dirk pointed out how to ignore or mask the issue for the time being, it does not solve it.
We are aware and understand the issue. To our knowledge, it has no impact on functionality whatsoever and we are already working on a permanent fix.

[DaveS (Dave)]

Hi Robin,

Do you know what version this is/will be fixed in? Is there a way for us to track this, if it’s not already fixed?

Thanks.

[robin.gierse]

It will be included in 1.7.6 with Werk 9601, which is on the brink of being released. Probably beginning of next week.
The changes necessary where a bit more complex than we initially thought, hence we took a little extra time to make sure the change landed safely.