Actions
Bug #14655
closedWhen Rudder is shut down because there isn't enough free space, it's not easy to know WHY it was shut down
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
67
Name check:
Fix check:
Regression:
Description
Rudder shuts down if free space is lower than 2% on the Postgres or LDAP partition
During the archiving at night, it's possible to hit this limit - and so Rudder shuts down
If we don't look in the logs, there's no way to know why it was shut down, and why it restarts
It would be awesome if the agent or webapp could tell about this situation
Actions