Description of problem: The rngd service : [ 6.669072] systemd[1]: rngd.service: Current command vanished from the unit file, execution of the command list won't be resumed. Version-Release number of selected component (if applicable): How reproducible: Restart computer or restart service Steps to Reproduce: 1.restart computer 2.dmesg check rngd : [ 6.669072] systemd[1]: rngd.service: Current command vanished from the unit file, execution of the command list won't be resumed. 3. systemctl status rngd.service 4. check $RNGD_ARGS variable but it does not return anything Actual results: ● rngd.service - Hardware RNG Entropy Gatherer Daemon Loaded: loaded (/usr/lib/systemd/system/rngd.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2021-10-09 10:23:04 CEST; 17min ago Main PID: 2970 (rngd) Tasks: 5 (limit: 38339) Memory: 2.4M CPU: 20.163s CGroup: /system.slice/rngd.service └─2970 /usr/sbin/rngd -f -x pkcs11 -x nist oct. 09 10:23:04 xx.localdomain rngd[2970]: Disabling 7: PKCS11 Entropy generator (pkcs11) oct. 09 10:23:04 xx.localdomain rngd[2970]: Disabling 5: NIST Network Entropy Beacon (nist) oct. 09 10:23:04 xx.localdomain rngd[2970]: Initializing available sources oct. 09 10:23:04 xx.localdomain rngd[2970]: [hwrng ]: Initialized oct. 09 10:23:04 xx.localdomain rngd[2970]: [rdrand]: Enabling RDSEED rng support oct. 09 10:23:04 xx.localdomain rngd[2970]: [rdrand]: Initialized oct. 09 10:23:04 xx.localdomain rngd[2970]: [jitter]: Initializing AES buffer oct. 09 10:23:05 xx.localdomain rngd[2970]: [jitter]: Enabling JITTER rng support oct. 09 10:23:05 xx.localdomain rngd[2970]: [jitter]: Initialized oct. 09 10:23:05 xx.localdomain rngd[2970]: [rtlsdr]: Initialization Failed Expected results: [root@xx ~]# systemctl status rngd.service ● rngd.service - Hardware RNG Entropy Gatherer Daemon Loaded: loaded (/usr/lib/systemd/system/rngd.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2021-10-09 10:44:31 CEST; 1s ago Main PID: 42338 (rngd) Tasks: 5 (limit: 38339) Memory: 1.9M CPU: 7.622s CGroup: /system.slice/rngd.service └─42338 /usr/sbin/rngd -f -r /dev/hwrng oct. 09 10:44:31 xx.localdomain systemd[1]: Started Hardware RNG Entropy Gatherer Daemon. oct. 09 10:44:31 xx.localdomain rngd[42338]: Initializing available sources oct. 09 10:44:31 xx.localdomain rngd[42338]: [hwrng ]: Initialized oct. 09 10:44:31 xx.localdomain rngd[42338]: [rdrand]: Enabling RDSEED rng support oct. 09 10:44:31 xx.localdomain rngd[42338]: [rdrand]: Initialized oct. 09 10:44:31 xx.localdomain rngd[42338]: [jitter]: Initializing AES buffer Additional info: If I modify the file : /usr/lib/systemd/system/rngd.service If I replace : ExecStart=/usr/sbin/rngd -f $RNGD_ARGS by ExecStart=/usr/sbin/rngd -f -r /dev/hwrng The service start correctly Is this normal? Thanks in advance Sylvain
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.