User story #6847
open
Separate updating of failsafe.cf and update.cf
Added by Florian Heigl over 9 years ago.
Updated 2 months ago.
Description
Hi,
we've seen a common issue where agents lose their configuration due to cf-serverd problems during the policy download.
This is worsened by the fact that one of the lost pieces is the update.cf which should recover from this exact situation.
from one of my break&burn test I know the same can sometimes be triggered if you have a full filesystem for /var[/rudder]
They should be protected i.e. by being in a different directory than the rest.
Related issues
1 (1 open — 0 closed)
- Category set to Agent
- Target version set to 4.0.0~rc2
- Related to User story #5641: Make the agent policies update a state machine with integrity check added
- Target version changed from 4.0.0~rc2 to 4.1.0~beta1
- Target version changed from 4.1.0~beta1 to 4.1.0~beta2
- Target version changed from 4.1.0~beta2 to 4.1.0~beta3
- Target version changed from 4.1.0~beta3 to 4.1.0~rc1
- Target version changed from 4.1.0~rc1 to 4.2.0~beta1
- Target version changed from 4.2.0~beta1 to 4.2.0~beta2
- Target version changed from 4.2.0~beta2 to 4.2.0~beta3
- Target version changed from 4.2.0~beta3 to 4.2.0~rc1
- Target version changed from 4.2.0~rc1 to 4.2.0~rc2
- Target version changed from 4.2.0~rc2 to 4.2.0
- Target version changed from 4.2.0 to 4.2.1
- Target version changed from 4.2.1 to 4.2.2
- Target version changed from 4.2.2 to 4.2.3
- Target version changed from 4.2.3 to 4.2.4
- Target version changed from 4.2.4 to Ideas (not version specific)
- Priority changed from 5 (lowest) to N/A
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by