Description of problem: The daemon won't start Version-Release number of selected component (if applicable): rasdaemon-0.6.7-2.fc35.x86_64 How reproducible: Always Steps to Reproduce: Upgrade to FC35 Actual results: Daemon did not start Expected results: Daemon should start Additional info: https://github.com/mchehab/rasdaemon/commit/455aaac394ca18b2f404a2f37f04cb48d4d890e5 added the SYSCONFDEFDIR configure parameter The /usr/lib/systemd/system/rasdaemon.service file has this now: [Service] EnvironmentFile=/rasdaemon So it could not find the file /rasdaemon and the daemon won't start.
The service always fails to start. root@msft-t490s:~# systemctl status rasdaemon.service × rasdaemon.service - RAS daemon to log the RAS events Loaded: loaded (/usr/lib/systemd/system/rasdaemon.service; enabled; vendor preset: disabled) Active: failed (Result: resources) CPU: 0 ott 13 23:20:25 msft-t490s systemd[1]: rasdaemon.service: Failed to load environment files: No such file or directory ott 13 23:20:25 msft-t490s systemd[1]: rasdaemon.service: Failed to run 'start' task: No such file or directory ott 13 23:20:25 msft-t490s systemd[1]: rasdaemon.service: Failed with result 'resources'. ott 13 23:20:25 msft-t490s systemd[1]: Failed to start RAS daemon to log the RAS events. I think that the unit is wrong: root@msft-t490s:~# cat /usr/lib/systemd/system/rasdaemon.service [Unit] Description=RAS daemon to log the RAS events After=syslog.target [Service] EnvironmentFile=/rasdaemon ExecStart=/usr/sbin/rasdaemon -f -r ExecStartPost=/usr/sbin/rasdaemon --enable ExecStop=/usr/sbin/rasdaemon --disable Restart=on-abort [Install] WantedBy=multi-user.target "/rasdaemon" seems a wrong path to me.
The unit file template is at: https://github.com/mchehab/rasdaemon/blob/master/misc/rasdaemon.service.in [Service] EnvironmentFile=@SYSCONFDEFDIR@/rasdaemon Obviously SYSCONFDEFDIR is empty during configure
I have the same problem upon upgrading to Fedora 35.
As stated in comment #2. The package provides an invalid systemd service file, but also /etc/sysconfig/rasdaemon file is missing. Its content should be fro here: https://github.com/mchehab/rasdaemon/blob/master/misc/rasdaemon.env The configuration scripts for building this package have been fixed the the version tagged with 0.6.7.
0.6.7-2.fc35.x86_64 still having this issue. I used comment #4 to get this working on my machine. Idk what I am doing, don't flame me. Thank you for what you do!
Interesting bug... The package's build logic is working fine when manually build it, as it does: $ rm misc/rasdaemon.service && make distclean && autoreconf -vfi $ ./configure --enable-sqlite3 --enable-aer --enable-mce --enable-extlog --enable-devlink --enable-diskerror --enable-abrt-report --enable-non-standard --enable-arm --enable-hisi-ns-decode --prefix /usr && make ... sed -e s,\@sbindir\@,/usr/sbin,g -e s,\@SYSCONFDEFDIR\@,/etc/sysconfig,g misc/rasdaemon.service.in > misc/rasdaemon.service sed -e s,\@sbindir\@,/usr/sbin,g -e s,\@SYSCONFDEFDIR\@,/etc/sysconfig,g misc/ras-mc-ctl.service.in > misc/ras-mc-ctl.service ... And the output is correct: $ more misc/rasdaemon.service [Unit] Description=RAS daemon to log the RAS events # only needed when not running in foreground (--foreground | -f) #After=syslog.target [Service] EnvironmentFile=/etc/sysconfig/rasdaemon ExecStart=/usr/sbin/rasdaemon -f -r ExecStartPost=/usr/sbin/rasdaemon --enable ExecStop=/usr/sbin/rasdaemon --disable Restart=on-abort [Install] WantedBy=multi-user.target Yet, somehow the package generated from rasdaemon.spec has issues. I'll do some tests here in order to identify why this is happening.
There were several issues related to it, including the lack of a /etc/sysconfig/rasdaemon. I fixed the package and pushed to testing: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f690d319b3 Please let me know if it fixes the issue.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.