QA » openQA Project » openQA Infrastructure

Motivation¶

Our monitoring for failed systemd units triggered. The problematic unit in question shows the following:

openqa:~ # journalctl -u session-50177.scope
-- Logs begin at Tue 2021-09-28 01:30:09 CEST. --
Okt 12 12:47:54 openqa systemd[1]: session-50177.scope: Failed to add PIDs to scope's control group: No such process
Okt 12 12:47:54 openqa systemd[1]: Failed to start Session 50177 of user tjyrinki.
Okt 12 12:47:54 openqa systemd[1]: session-50177.scope: Unit entered failed state.

I asked Timo in slack if he experienced any issue. As he is currently away at the time of writing, I assume this was some automatic task.
Also looking up the issue in bugzilla and google did not yield any useful hint. "No such process" could mean something exited faster then the control group could take it (?).
We had a similar issue in the past, see poo#96707.

Suggestion¶

• Open a bugzilla ticket to request help from systemd developers
• Adjust monitoring script (systemd_failed.sh) to not monitor these scope units (if we follow the approach of https://progress.opensuse.org/issues/96707#note-6)