Bug #14655: When Rudder is shut down because there isn't enough free space, it's not easy to know WHY it was shut down - Rudder - Issue Tracker

Actions

Copy link

Bug #14655

closed

When Rudder is shut down because there isn't enough free space, it's not easy to know WHY it was shut down

Added by Nicolas CHARLES over 5 years ago. Updated almost 3 years ago.

Status:

Resolved

Priority:

N/A

Assignee:

Category:

Agent

Target version:

6.1.19

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:

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

Copy link

Updated by François ARMAND over 5 years ago

Translation missing: en.field_tag_list set to community
Severity set to Major - prevents use of part of Rudder | no simple workaround
User visibility set to Operational - other Techniques | Rudder settings | Plugins
Priority changed from 0 to 52

I set level to "no simple workaround" because from user point of view, it looks like Rudder is broken and it's extremelly difficult to know why.

Actions

Copy link

Updated by Vincent MEMBRÉ over 5 years ago

Target version changed from 5.0.10 to 5.0.11

Actions

Copy link

Updated by Vincent MEMBRÉ over 5 years ago

Target version changed from 5.0.11 to 5.0.12
Priority changed from 52 to 51

Actions

Copy link

Updated by Vincent MEMBRÉ over 5 years ago

Target version changed from 5.0.12 to 5.0.13
Priority changed from 51 to 50

Actions

Copy link

Updated by Alexis Mousset over 5 years ago

Category set to Agent

Actions

Copy link

Updated by Vincent MEMBRÉ over 5 years ago

Target version changed from 5.0.13 to 5.0.14
Priority changed from 50 to 49

Actions

Copy link

Updated by Vincent MEMBRÉ about 5 years ago

Target version changed from 5.0.14 to 5.0.15
Priority changed from 49 to 48

Actions

Copy link

Updated by Benoît PECCATTE about 5 years ago

Priority changed from 48 to 47

It could be down in the 404/500 page since we don't shut down apache

Actions

Copy link

Updated by François ARMAND about 5 years ago

Effort required set to Very Small
Priority changed from 47 to 73

The webapp could look at a file (flag), or it could check for space available at startup using the same value than the promise and stop with a big message. If rudder doesn't start, people will look at webapp logs. Also possible to set a special apache error message in that case.

Actions

Copy link

#10