Package: man-db Version: 2.10.2-1 Severity: normal Tags: upstream Dear Maintainer,
I experienced this on an Ubuntu jammy system, but the current Debian unstable version is probably affected as well (based on the sources available on salsa.debian.org). Please consider these logs: 05:29:32 hn systemd[1]: Starting Cleanup of Temporary Directories... 05:29:32 hn systemd[1]: Starting Daily man-db regeneration... 05:29:32 hn find[31023]: /usr/bin/find: ‘/var/cache/man/de’: No such file or directory 05:29:32 hn find[31023]: /usr/bin/find: ‘/var/cache/man/pt’: No such file or directory [... bunch of similar error messages omitted ...] 05:29:32 hn systemd[1]: systemd-tmpfiles-clean.service: Succeeded. 05:29:32 hn systemd[1]: Finished Cleanup of Temporary Directories. 05:29:32 hn find[31023]: /usr/bin/find: ‘/var/cache/man/cat9’: No such file or directory 05:29:32 hn systemd[1]: man-db.service: Main process exited, code=exited, status=1/FAILURE 05:29:32 hn systemd[1]: man-db.service: Failed with result 'exit-code'. 05:29:32 hn systemd[1]: Failed to start Daily man-db regeneration. I suppose this happened because the cleanup prescribed by /usr/lib/tmpfiles.d/man-db.conf and the "manual" cleanup implemented by the find call in /lib/systemd/system/man-db.service ran concurrently. This results in man-db.service spuriously entering failed state, triggering false monitoring alarms. Please avoid this by choosing one cleanup method only (if the above analysis is correct). -- Thanks, Feri.
