Package: rasdaemon Version: 0.6.0-1.2 Severity: important File: /lib/systemd/system/rasdaemon.service Tags: patch
Dear Maintainer, I often found rasdaemon.service inactive (exited) after a fresh boot. There were no obvious errors, except this: Aug 04 17:04:13 host rasdaemon[549]: rasdaemon: Can't open trace_clock Aug 04 17:04:13 host rasdaemon[549]: rasdaemon: Can't select a timestamp for tracing After some digging, I found that /sys/kernel/debug/tracing was not yet mounted at the time rasdaemon.service was started, and rasdaemon needs this to function. Please find attached a patch to correct this situation. -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages rasdaemon depends on: ii libc6 2.28-10 ii libdbd-sqlite3-perl 1.62-3 ii libsqlite3-0 3.27.2-3 ii perl 5.28.1-6 ii sqlite3 3.27.2-3 ii systemd 241-5 rasdaemon recommends no packages. rasdaemon suggests no packages. -- no debconf information
--- /lib/systemd/system/rasdaemon.service 2018-05-09 07:46:47.000000000 -0700 +++ rasdaemon.service 2019-08-04 17:15:26.336126160 -0700 @@ -1,5 +1,6 @@ [Unit] Description=RAS daemon to log the RAS events +RequiresMountsFor=/sys/kernel/debug/tracing [Service] ExecStart=/usr/sbin/rasdaemon -f -r
