Systemd process running as a user job
Bug #1861525 reported by
Ryan Farrell
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Neutron Gateway Charm |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Somehow we are in a state where there is a systemd process installed and running as a user job.
Syslog is being spammed with messages similar to:
Jan 31 15:31:26 HOSTNAME systemd[1002797]: Failed to canonicalize path /home/ubuntu/
root@HOSTNAME:~# ps aux | grep 1002797
root 445115 0.0 0.0 13148 1156 pts/4 S+ 19:29 0:00 grep --color=auto 1002797
ubuntu 1002797 0.0 0.0 78592 9572 ? Ss Jan29 0:02 /lib/systemd/
Note that ubuntu is the user on that proc and that /home/ubuntu/
| Changed in charm-neutron-gateway: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
Revision history for this message
| Steve Dodd (anarchetic) wrote | #1 |
To post a comment you must log in.
Wondered in here randomly, but .. it is normal for there to be a per-user systemd process on interactive systems - it manages jobs for that user when logged in. If there is no user logged in, it may still exist if 'loginctl enable-linger' has been called for that user - it allows the per-user systemd to start and monitor background services for the user (things that in the old days we might have started from cron, or using nohup.)
The permission denied error message normally occurs when one or more of the path components /home/ubuntu/