Actions
action #96707
closedFailed systemd services alert for osd in session-c26076.scope
Description
There's failing session-XXX.scope units on osd. Still investigating as I'm filing this ticket. I don't see any obvious consequence so far, but assuming these are related to the database I'm treating them as important by default.
> systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● session-c26076.scope loaded failed failed Session c26076 of user postgres
● session-c26077.scope loaded failed failed Session c26077 of user postgres
Updated by livdywan over 3 years ago
- Status changed from Workable to In Progress
This is the concrete failure.
$ sudo journalctl -u session-c26076.scope
session-c26076.scope: Failed to add PIDs to scope's control group: No such process
Failed to start Session c26076 of user postgres.
Updated by mkittler over 3 years ago
- Assignee deleted (
mkittler)
I also don't know what caused these failing units. So far I've just reset the units (as we have bigger problems right now: #96710).
Updated by livdywan over 3 years ago
- Status changed from In Progress to Feedback
- Priority changed from High to Normal
Updated by okurz over 3 years ago
- Category set to Regressions/Crashes
- Status changed from Feedback to Resolved
- Assignee set to mkittler
then maybe it's nothing. Setting back to mkittler as the person doing an actual action.
Actions