Description of problem: The rdisc service does not start with default configuration. After commenting out the "PrivateUsers=yes" line in rdisc.service file and issuing this command "systemctl daemon-reload", the service starts successfully. Version-Release number of selected component (if applicable): iputils-20190515-5.fc32.x86_64 How reproducible: * always Steps to Reproduce: 1. get a Fedora 32 machine 2. start the rdisc service (via service or systemctl) 3. check if the service is running Actual results: systemd[1]: Started Network Router Discovery Daemon. rdisc[32930]: socket: Operation not permitted systemd[1]: rdisc.service: Main process exited, code=exited, status=5/NOTINSTALLED systemd[1]: rdisc.service: Failed with result 'exit-code'. Expected results: * the service is running
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
I don't see 'PrivateUsers=yes' in that service file? ✗ cat rdisc.service [Unit] Description=rdisc daemon which discovers routers on the local subnet After=network.target Documentation=man:rdisc [Service] Type=forking ExecStart=/sbin/rdisc -s [Install] WantedBy=multi-user.target Did you edit your copy perhaps?
# rpm -qf /usr/sbin/rdisc iputils-20200821-1.fc33.x86_64 # cat /usr/lib/systemd/system/rdisc.service [Unit] Description=Network Router Discovery Daemon Documentation=man:rdisc(8) Requires=network.target After=network.target [Service] EnvironmentFile=-/etc/sysconfig/rdisc ExecStart=/usr/sbin/rdisc -f -t $OPTIONS $SEND_ADDRESS $RECEIVE_ADDRESS AmbientCapabilities=CAP_NET_RAW PrivateTmp=yes PrivateUsers=yes ProtectSystem=strict ProtectHome=yes ProtectControlGroups=yes ProtectKernelTunables=yes ProtectKernelModules=yes MemoryDenyWriteExecute=yes RestrictRealtime=yes RestrictNamespaces=yes SystemCallArchitectures=native LockPersonality=yes NoNewPrivileges=yes [Install] WantedBy=multi-user.target #
The same picture is on both Fedora 32 and Fedora 33: # rpm -qf /usr/sbin/rdisc iputils-20190515-7.fc32.x86_64 # cat /usr/lib/systemd/system/rdisc.service [Unit] Description=Network Router Discovery Daemon Documentation=man:rdisc(8) Requires=network.target After=network.target [Service] EnvironmentFile=-/etc/sysconfig/rdisc ExecStart=/usr/sbin/rdisc -f -t $OPTIONS $SEND_ADDRESS $RECEIVE_ADDRESS AmbientCapabilities=CAP_NET_RAW PrivateTmp=yes PrivateUsers=yes ProtectSystem=strict ProtectHome=yes ProtectControlGroups=yes ProtectKernelTunables=yes ProtectKernelModules=yes MemoryDenyWriteExecute=yes RestrictRealtime=yes RestrictNamespaces=yes SystemCallArchitectures=native LockPersonality=yes NoNewPrivileges=yes [Install] WantedBy=multi-user.target # rpm -V iputils #
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 '32'. 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 32 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 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.