-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
TEST-60-MOUNT-RATELIMIT is unstable #23424
Copy link
Copy link
Closed
Labels
bug 🐛Programming errors, that need preferential fixingProgramming errors, that need preferential fixingpid1sd-event
Description
systemd version the issue has been seen with
latest main
Used distribution
Arch Linux
Since May 13th I've noticed several failed runs with TEST-60-MOUNT-RATELIMIT being the culprit:
[ 133.292006] testsuite-60.sh[446]: + journalctl -u init.scope
[ 133.292968] testsuite-60.sh[447]: + grep -q '(mount-monitor-dispatch) left rate limit'
[ 133.530574] testsuite-60.sh[239]: + sleep 5
[ 138.533647] testsuite-60.sh[449]: ++ date -u +%s
[ 138.536337] testsuite-60.sh[239]: + [[ 1652841000 -le 1652840999 ]]
[ 138.536785] testsuite-60.sh[239]: + '[' 0 = 0 ']'
[ 138.536916] testsuite-60.sh[239]: + exit 24
[ 138.538091] systemd[1]: systemd-journald.service: Received EPOLLHUP on stored fd 68 (stored), closing.
[ 138.538664] systemd[1]: Received SIGCHLD from PID 239 (bash).
[ 138.538779] systemd[1]: Child 239 (bash) died (code=exited, status=24/n/a)
[ 138.539026] systemd[1]: testsuite-60.service: Child 239 belongs to testsuite-60.service.
[ 138.539133] systemd[1]: testsuite-60.service: Main process exited, code=exited, status=24/n/a
[ 138.539293] systemd[1]: testsuite-60.service: Failed with result 'exit-code'.
[ 138.539395] systemd[1]: testsuite-60.service: Service will not restart (restart setting)
[ 138.541385] systemd[1]: testsuite-60.service: Changed start -> failed
[ 138.541492] systemd[1]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=643 reply_cookie=0 signa>
[ 138.569260] systemd[1]: testsuite-60.service: Failed to delete cgroup entry from LSM BPF map: No such file or directory
[ 138.569425] systemd[1]: testsuite-60.service: Job 167 testsuite-60.service/start finished, result=failed
[ 138.569521] systemd[1]: Failed to start TEST-60-MOUNT-RATELIMIT.
According to the logs it looks like the mount unit never leaves the rate limited state (or at least the respective log message is missing):
$ journalctl --file system.journal --no-hostname -o short-monotonic --grep mount-monitor-dispatch _PID=1
[ 17.198617] systemd[1]: Event source 0x55cbba456520 (mount-monitor-dispatch) entered rate limit state.
Some journals:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bug 🐛Programming errors, that need preferential fixingProgramming errors, that need preferential fixingpid1sd-event