Bug ID 726622: Entropy start-up sentinel file is not cleared on successful start

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,

Fixed In:

Opened: Jul 03, 2018
Severity: 3-Major


When the entropy start-up fails, a file is created that will prevent a reboot loop. However, if the entropy start-up succeeds, the file remains.


The entropy start-up sentinel file is not cleared as it should be. If an entropy failure happens again, then all subsequent rebooting for a failed entropy is disabled. Should the entropy succeed and then later fail, the reboot to handle the failed entropy start-up will not happen.


Entropy start-up fails and then succeeds.


User can manually remove the start-up failure sentinel file using the following command: /bin/rm -f /.entropy_failure_sentinal_file

Fix Information

Now, if the entropy start-up succeeds, the system removes that file, so that subsequent failures reboot at least once. This is correct behavior.

Behavior Change