Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#59867 - nfsidmap requires systemd-journald; silently crashing if not running

Attached to Project: Arch Linux
Opened by Daniel Laube (dlaube) - Wednesday, 29 August 2018, 20:49 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 29 August 2018, 22:38 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
We had a strange issue for a few qeeks now that i've tracked down yesterday. On our machines we use nfsv4/kerberos/ldap combo for providing user and group homes.
There was an issue that the devices stop working under normal workload (hanging windows, applications stop responding) after some amount of time.
We could track down the issue to folders with lots of files/directories with different user ownerships. It will hang there because idmapd has to translate a lot of usernames/kerberos principals. idmapd will translate fine but writes to /dev/log which is a symlink to a systemd-journald socket. At some point this socket buffer is full resulting in a hanging write syscall in idmapd.
Unmasking and restarting systemd-journald solved the issue but i really don't get why such an important daemon relies on logging functionality. That is why i think that this is some thing to work on.


Additional info:
nfs-utils 2.3.2-2


Steps to reproduce:
- Stop systemd-jorunald
- browse a kerberised nfsv4 directory with lots of files from different users
- after some time the device will lock up
This task depends upon

Closed by  Dave Reisner (falconindy)
Wednesday, 29 August 2018, 22:38 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Upstream systemd requires running journald.
Comment by Dave Reisner (falconindy) - Wednesday, 29 August 2018, 20:58 GMT
Something's not right here. journald is socket activated. Stopping it should be largely a no-op because anything that writes logs (stdout, stderr, syslog, native logs) will cause it to restart.
Comment by Daniel Laube (dlaube) - Wednesday, 29 August 2018, 21:11 GMT
I meant masking it. Masking it prevents it from starting, even if socket activated. No other service is complaining about that. It is just idmapd that fails silently.
Comment by Dave Reisner (falconindy) - Wednesday, 29 August 2018, 22:38 GMT
journald is a required service. Masking journald puts you well into unsupported territory.

Loading...