Failed unmounting Temporary Directory /tmp

humblebee · 2023-03-09 10:34:14

Hello all,

I know this is a topic that has been addressed before, but I wasn't able to find any satisfying answer to this problem (so far inconsequential by the way, as far as I can see).

This is what I'm getting from journalctl:

mars 09 07:14:47 humbleb systemd[1]: Unmounting Temporary Directory /tmp...
mars 09 07:14:48 humbleb umount[5946]: umount: /tmp: la cible est active.
mars 09 07:14:48 humbleb
systemd[1]: Failed unmounting Temporary Directory /tmp.

And here is the output of fuser -cv, either after startup or after I close my X session:

sudo fuser -cv /tmp/*
UTIL. PID ACCES COMMANDE
/tmp/dbus-hnYTV6kzRN:
root kernel mount /tmp
root 540 F.... dbus-daemon
/tmp/systemd-private-0aa8fd129db44528bf5b851b9825d816-systemd-logind.service-TAK7rS:
root kernel mount /tmp
root 540 F.... dbus-daemon
/tmp/systemd-private-0aa8fd129db44528bf5b851b9825d816-systemd-resolved.service-Y7twvh:
root kernel mount /tmp
root 540 F.... dbus-daemon

If I stop the dbus.service and dbus.socket whith systemctl stop before shutdown, the error occurs anyway.

I'm very new to archlinux (less than a week) and I don't have a clue what's happening here. I hope these informations will give enough food for thought to more experienced users.

Cheers,

Phil

(n.b. edited for better english...)

Last edited by humblebee (2023-03-09 10:37:58)

seth · 2023-03-09 11:51:45

https://bbs.archlinux.org/viewtopic.php?id=284071
You'll probably look at more of the shutdown sequence in the journal - the tail may tell you that, but doesn't hint at why the umount fails.

humblebee · 2023-03-09 14:45:20

Thank you Seth for your answer,

systemctl status dbus.service gives this:

dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Thu 2023-03-09 13:53:30 CET; 18min ago
TriggeredBy: ● dbus.socket
Docs: man:dbus-daemon(1)
Main PID: 394 (dbus-daemon)
Tasks: 1 (limit: 4671)
Memory: 2.3M
CPU: 381ms
CGroup: /system.slice/dbus.service
└─394 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
mars 09 14:03:51 humbleb dbus-daemon[394]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.70' (uid=0 pid=2323 comm="sudo systemctl status dbus.service")
mars 09 14:03:51 humbleb dbus-daemon[394]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mars 09 14:04:06 humbleb dbus-daemon[394]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.73' (uid=0 pid=2378 comm="sudo systemctl status dbus.socket")
mars 09 14:04:06 humbleb dbus-daemon[394]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mars 09 14:06:52 humbleb dbus-daemon[394]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.79' (uid=0 pid=2943 comm="sudo systemctl list-units")
mars 09 14:06:52 humbleb dbus-daemon[394]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.

journalctl | tail is quite flooded with pam messages mentionning the same Unit dbus-org.freedesktop.home1.service (not found), e.g.

mars 09 14:28:33 humbleb sudo[7972]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.

status pam_namespace.service reads:

○ pam_namespace.service - Make sure parent directories configured in /etc/security/namespace.conf for polyinstantiation exist
Loaded: loaded (/usr/lib/systemd/system/pam_namespace.service; static)
Active: inactive (dead)
Docs: man:pam_namespace(8)

Well, it seems to me that dbus-daemon is for some reason clinging to /tmp, maybe for some pam-related issues but all this is beyond me.

Anyway, apart from that oddity my new Archlinux box works for me pretty smoothly I think.

Thank you again,

Last edited by humblebee (2023-03-09 14:46:24)

seth · 2023-03-09 18:07:13

Please post your complete system journal for the previous boot:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

humblebee · 2023-03-09 18:21:37

Here it is.

seth · 2023-03-09 18:55:24

mars 09 15:23:28 humbleb systemd[1]: Unmounting /run/credentials/systemd-tmpfiles-setup.service...
mars 09 15:23:28 humbleb kernel: XFS (sda9): Unmounting Filesystem
mars 09 15:23:28 humbleb systemd[1]: Unmounting /run/credentials/systemd-tmpfiles-setup-dev.service...
mars 09 15:23:28 humbleb systemd[1]: Unmounting Temporary Directory /tmp...
mars 09 15:23:28 humbleb umount[4383]: umount: /run/credentials/systemd-tmpfiles-setup.service: Aucun point de montage indiqué.
mars 09 15:23:28 humbleb kernel: XFS (sda11): Unmounting Filesystem
mars 09 15:23:28 humbleb systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount: Mount process exited, code=exited, status=32/n/a
mars 09 15:23:28 humbleb systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount: Failed with result 'exit-code'.

1st off, you've networkd and dhcpcd active, pick one, disable the other.
Please also post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

And what is

mars 09 15:13:58 humbleb dbus-daemon[393]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.35' (uid=0 pid=1847 comm="sudo systemctl status pam_namespace.service")
mars 09 15:13:58 humbleb sudo[1847]:     phil : TTY=pts/0 ; PWD=/home/phil ; USER=root ; COMMAND=/usr/bin/systemctl status pam_namespace.service
mars 09 15:17:20 humbleb dbus-daemon[393]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.69' (uid=0 pid=3271 comm="sudo systemctl start pam_namespace.service")
mars 09 15:17:20 humbleb sudo[3271]:     phil : TTY=pts/0 ; PWD=/home/phil ; USER=root ; COMMAND=/usr/bin/systemctl start pam_namespace.service
mars 09 15:17:20 humbleb pam_namespace_helper[3276]: mkdir /tmp-inst/
mars 09 15:17:20 humbleb systemd[1]: pam_namespace.service: Deactivated successfully.
mars 09 15:17:25 humbleb dbus-daemon[393]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.71' (uid=0 pid=3304 comm="sudo systemctl status pam_namespace.service")
mars 09 15:17:25 humbleb sudo[3304]:     phil : TTY=pts/0 ; PWD=/home/phil ; USER=root ; COMMAND=/usr/bin/systemctl status pam_namespace.service
mars 09 15:20:41 humbleb dbus-daemon[393]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.80' (uid=0 pid=3997 comm="sudo systemctl restart pam_namespace.service")
mars 09 15:20:41 humbleb sudo[3997]:     phil : TTY=pts/0 ; PWD=/home/phil ; USER=root ; COMMAND=/usr/bin/systemctl restart pam_namespace.service
mars 09 15:20:41 humbleb systemd[1]: pam_namespace.service: Deactivated successfully.
mars 09 15:21:02 humbleb dbus-daemon[393]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.82' (uid=0 pid=4074 comm="sudo systemctl status pam_namespace.service")
mars 09 15:21:02 humbleb sudo[4074]:     phil : TTY=pts/0 ; PWD=/home/phil ; USER=root ; COMMAND=/usr/bin/systemctl status pam_namespace.service

about?

humblebee · 2023-03-09 20:04:14

I have disabled systemd-networkd.service (random choice between the two for now, I'll look at that later.

The output of the find command you asked for is :

dbus-org.freedesktop.home1.service | system
dbus-org.freedesktop.resolve1.service | system
dhcpcd.service | multi-user.target.wants
getty@tty1.service | getty.target.wants
gpm.service | multi-user.target.wants
p11-kit-server.socket | sockets.target.wants
pulseaudio.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
sshd.service | multi-user.target.wants
systemd-homed-activate.service | systemd-homed.service.wants
systemd-homed.service | multi-user.target.wants
systemd-resolved.service | sysinit.target.wants
systemd-userdbd.socket | sockets.target.wants
wg-quick@wg0.service | multi-user.target.wants

As for the "dbus-org.freedesktop.home1.service" and pam thing, I just don't know.

sudo systemctl status pam_namespace.service
○ pam_namespace.service - Make sure parent directories configured in /etc/security/namespace.conf for polyinstantiation exist
Loaded: loaded (/usr/lib/systemd/system/pam_namespace.service; static)
Active: inactive (dead)
Docs: man:pam_namespace(8)

seth · 2023-03-09 20:37:20

Do you intend to use https://wiki.archlinux.org/title/Systemd-homed ?
Was starting pam_namespace.service and enabling its services an attempt to "fix" the

mars 09 15:08:00 humbleb login[419]: pam_systemd_home(login:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.

"errors" systemd yells at you? You can ignore those, they're spam.

You're now running dhcpcd and resolved?

Unfortunately, there's no indication in the journal what might keep using /tmp
Other than homed, my next best guess would be wg-quick (but that's really just a guess w/o any supporting data)

humblebee · 2023-03-09 21:11:25

seth wrote:
Do you intend to use https://wiki.archlinux.org/title/Systemd-homed ?

No, I do not intend to use system-homed..

Was starting pam_namespace.service and enabling its services an attempt to "fix" the
mars 09 15:08:00 humbleb login[419]: pam_systemd_home(login:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
"errors" systemd yells at you? You can ignore those, they're spam.

Er, yes, I 've been fiddling with pam services to see what that did... roll

You're now running dhcpcd and resolved?

I first stopped and disabled systemd-networkd.service and then systemd-resolved.service when you pointed it out...

Unfortunately, there's no indication in the journal what might keep using /tmp
Other than homed, my next best guess would be wg-quick (but that's really just a guess w/o any supporting data)

Ok, I'll look into that upon next reboot.
Thank you very much, Seth

Last edited by humblebee (2023-03-09 21:36:10)

Arch Linux

#1 2023-03-09 10:34:14

Failed unmounting Temporary Directory /tmp

#2 2023-03-09 11:51:45

Re: Failed unmounting Temporary Directory /tmp

#3 2023-03-09 14:45:20

Re: Failed unmounting Temporary Directory /tmp

#4 2023-03-09 18:07:13

Re: Failed unmounting Temporary Directory /tmp

#5 2023-03-09 18:21:37

Re: Failed unmounting Temporary Directory /tmp

#6 2023-03-09 18:55:24

Re: Failed unmounting Temporary Directory /tmp

#7 2023-03-09 20:04:14

Re: Failed unmounting Temporary Directory /tmp

#8 2023-03-09 20:37:20

Re: Failed unmounting Temporary Directory /tmp

#9 2023-03-09 21:11:25

Re: Failed unmounting Temporary Directory /tmp

Board footer