I understand that you got the below error on the systemlogs from the instance that stopped working: "start request repeated too quickly for systemd-tmpfiles-clean.service”
If the service restart exceeds the value of StartLimitBurst within the time specified by the value of StartLimitInterval, the service startup will fail and lead to that error . Ensure that frequent restarts of your services/applications within a short period of time are the expected behaviour for hat service.When not, it is important to troubleshoot the reason for the frequent restarts of the service. This existing behaviour exists as a measure to prevent many repetitions of service restarts in a system. Once the service restart exceeds the value of StartLimitBurst within the time specified by the value of StartLimitInterval, the service startup will fail. StartLimitInterval is set to 10 seconds by default and StartLimitBurst is set to 5 by default. The problem can be avoided by disabling the restrictions, please be mindful of implications before disabling any system setting and please take note of any changes so they can be undone. To disable checking of service starts, please set StartLimitBurst to a value of 0.
Please see the commands below to troubleshoot the problem.
Check systemd's file with the following commands:  systemctl show -p FragmentPath systemd-tmpfiles-clean.service  cat /usr/lib/systemd/system/systemd-tmpfiles-clean.service
Write StartLimitBurst=0 in [Service] section:  vim /usr/lib/systemd/system/systemd-tmpfiles-clean.service ... StartLimitBurst=0
Re-load the modified systemd file:  systemctl daemon-reload
I hope the above information is helpful. Kindly let me know if you have additional concerns.
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 4 months ago
- EXPERTpublished a year ago