Project

General

Profile

Actions
Copy link

Bug #11125

closed

When we have a /var full, Rudder LDAP or Postgres can be corrupted

Added by Nicolas CHARLES almost 7 years ago. Updated over 6 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
System integration
Target version:
3.1.25
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
71
Name check:
Fix check:
Regression:

Description

When there's no space left on /var, ldap and/or postgres are at risk of failing hard - and not restart
Process to repair and restore is quite hard, so we need to prevent this situation (could be stop component before its too late, or something else...)

Subtasks 4 (0 open — 4 closed)

User story #11731: Add a new reason why rudder might not be loadedReleasedAlexis MoussetActions
Bug #11739: When we have a /var full, Rudder LDAP or Postgres can be corruptedReleasedAlexis MoussetActions
Bug #11740: When we have a /var full, Rudder LDAP or Postgres can be corruptedReleasedAlexis MoussetActions
Bug #11747: When we have a /var full, Rudder LDAP or Postgres can be corruptedReleasedAlexis MoussetActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES almost 7 years ago

  • Subject changed from When we have a /var full, Rudder LDAP or Postgres can be corrupded to When we have a /var full, Rudder LDAP or Postgres can be corrupted
  • Description updated (diff)
  • Category set to System integration
  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
Actions
Copy link
 #2

Updated by Benoît PECCATTE over 6 years ago

  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 0 to 76

We can manage the simple case: if /var is almost full, stop rudder, slapd and postgresql

Actions
Copy link
 #3

Updated by Benoît PECCATTE over 6 years ago

  • Assignee set to Benoît PECCATTE

This could be added to rudder agent check.

Actions
Copy link
 #4

Updated by Benoît PECCATTE over 6 years ago

  • Target version set to 3.1.24
  • Priority changed from 76 to 73
Actions
Copy link
 #5

Updated by Benoît PECCATTE over 6 years ago

  • Status changed from New to In progress
Actions
Copy link
 #6

Updated by Benoît PECCATTE over 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/1391
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions
Copy link
 #8

Updated by Benoît PECCATTE over 6 years ago

  • Priority changed from 73 to 72
Actions
Copy link
 #9

Updated by Benoît PECCATTE over 6 years ago

  • Assignee changed from Alexis Mousset to Benoît PECCATTE
Actions
Copy link
 #10

Updated by Benoît PECCATTE over 6 years ago

  • Assignee changed from Benoît PECCATTE to Alexis Mousset
Actions
Copy link
 #11

Updated by Benoît PECCATTE over 6 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Pending release to Released
  • Priority changed from 72 to 71

This bug has been fixed in Rudder 3.1.25, 4.1.9 and 4.2.3 which were released today.

Actions
Copy link

Also available in: Atom PDF