Bug 1215741 - Warning/error message "Transport endpoint is not connected" in journald after cron job run by root
Summary: Warning/error message "Transport endpoint is not connected" in journald after...
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Leap 15.5
Hardware: x86-64 openSUSE Leap 15.5
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: Danilo Spinella
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-27 07:19 UTC by Claude Diderich
Modified: 2023-10-03 09:29 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Claude Diderich 2023-09-27 07:19:19 UTC 
After a cron job owned by root finishes, a warning + failure message is logged to the journal file:

Sep 27 00:15:12 jasper systemd[1]: user-runtime-dir@0.service: Failed with result 'exit-code'.
Sep 27 00:15:12 jasper systemd[1]: user-runtime-dir@0.service: Control process exited, code=exited, status=1/FAILURE
Sep 27 00:15:12 jasper systemd-user-runtime-dir[40960]: Failed to remove runtime directory /run/user/0 (after unmounting): Transport endpoint is not connected
Sep 27 00:15:01 jasper CRON[40871]: pam_unix(crond:session): session closed for user root
Sep 27 00:15:01 jasper CRON[40871]: (root) CMDEND (/usr/lib/cron/run-crons >/dev/null 2>&1)
Sep 27 00:15:01 jasper CRON[40912]: (root) CMD (/usr/lib/cron/run-crons >/dev/null 2>&1)

The cron job is executed correctly.
Comment 1 Claude Diderich 2023-09-27 09:52:11 UTC 
A little more details, i.e. output from systemctl status:

× user-runtime-dir@0.service - User Runtime Directory /run/user/0
     Loaded: loaded (/usr/lib/systemd/system/user-runtime-dir@.service; static)
     Active: failed (Result: exit-code) since Wed 2023-09-27 02:11:19 CEST; 9h ago
       Docs: man:user@.service(5)
    Process: 42199 ExecStart=/usr/lib/systemd/systemd-user-runtime-dir start 0 (code=exited, status=0/SUCCESS)
    Process: 42604 ExecStop=/usr/lib/systemd/systemd-user-runtime-dir stop 0 (code=exited, status=1/FAILURE)
   Main PID: 42199 (code=exited, status=0/SUCCESS)

Sep 27 02:11:19 jasper systemd-user-runtime-dir[42604]: Failed to remove runtime directory /run/user/0 (after unmounting): Transport endpoint is not connected
Sep 27 02:11:19 jasper systemd[1]: user-runtime-dir@0.service: Control process exited, code=exited, status=1/FAILURE
Sep 27 02:11:19 jasper systemd[1]: user-runtime-dir@0.service: Failed with result 'exit-code'.
Comment 2 Claude Diderich 2023-10-01 08:59:02 UTC 
Note: After installing the latest updates and rebooting the machine, the warning/error message disappeared.
Comment 3 Danilo Spinella 2023-10-03 09:29:22 UTC 
Hello Claude and thank you for the report. It seems to me it's related to systemd-user-runtime-dir and not directly to cron; for this reason and since it has been fixed with the latest update, I am closing this bug. If any issue appear again, feel free to reopen it and we'll look into it again.