Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: rpc-statd crashes during startup. Version-Release number of selected component (if applicable): nfs-utils-2.4.1-0.rc1.fc30.x86_64 How reproducible: Always Steps to Reproduce: 1.(Re-boot) 2.systemctl status rpc-statd Actual results: systemctl shows rpc-statd is crashed (SIGSEGV) Expected results: rpc-statd should be running. Additional info: Once the system is fully booted starting rpc-statd doesn't crash anymore. There is no coredump nor backtrace. systemctl -b shows: rpc.statd[2107]: Version 2.3.4 starting rpc.statd[2107]: Flags: TI-RPC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rpc-statd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' audit[2107]: ANOM_ABEND auid=4294967295 uid=29 gid=29 ses=4294967295 pid=2107 comm="rpc.statd" exe="/usr/sbin/rpc.statd" sig=11 res=1 kernel: rpc.statd[2107]: segfault at 10 ip 00005617d5ac59cd sp 00007ffe988f4790 error 6 in rpc.statd[5617d5ac3000+f000] systemd[1]: rpc-statd.service: Main process exited, code=killed, status=11/SEGV systemd[1]: rpc-statd.service: Failed with result 'signal'. audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rpc-statd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' It seems to be a start-up ordering issue, adding an After=nfs-server.service stanza to rpc-statd.service seems to fix the issue.
Given that this is a crash of a vital system service, why has it not even been triaged yet?
While adding After=nfs-server.service stanza to rpc-statd.service might be a workaround, ultimately this is a segfault and a segfault is without argument a bug.
> It seems to be a start-up ordering issue, adding an After=nfs-server.service stanza to rpc-statd.service seems to fix the issue. This creates a circular dependency in the latest Fedora 31: Jan 14 07:03:46 pc.example.com systemd[1]: rpc-statd.service: Found ordering cycle on nfs-server.service/stop Jan 14 07:03:46 pc.example.com systemd[1]: rpc-statd.service: Found dependency on rpc-statd.service/stop Jan 14 07:03:46 pc.example.com systemd[1]: rpc-statd.service: Job nfs-server.service/stop deleted to break ordering cycle starting with rpc-statd.service/stop Jan 14 07:03:47 pc.example.com systemd[1]: Stopping NFS status monitor for NFSv2/3 locking.... Jan 14 07:03:47 pc.example.com systemd[1]: rpc-statd.service: Succeeded. Jan 14 07:03:47 pc.example.com systemd[1]: Stopped NFS status monitor for NFSv2/3 locking.. But again, I would ask why this ticket has not even been triaged when it crashes on every reboot: Dec 25 21:21:20 pc.example.com systemd[1]: rpc-statd.service: Main process exited, code=killed, status=11/SEGV Jan 05 06:29:43 pc.example.com systemd[1]: rpc-statd.service: Main process exited, code=killed, status=11/SEGV Jan 06 21:03:53 pc.example.com systemd[1]: rpc-statd.service: Main process exited, code=killed, status=11/SEGV Jan 06 21:04:06 pc.example.com systemd[1]: rpc-statd.service: Main process exited, code=killed, status=11/SEGV Jan 08 06:52:30 pc.example.com systemd[1]: rpc-statd.service: Main process exited, code=killed, status=11/SEGV Jan 08 11:16:23 pc.example.com systemd[1]: rpc-statd.service: Main process exited, code=killed, status=11/SEGV Unfortunately there is never an abrt report filed for it, so maybe resolving that is the first step in resolving this issue.
I have created bug 1790972 for the lack of abrt report.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.