Actions
User story #7666
closed
Provide a command to monitor connection errors on the agent
Effort required:
Name check:
Fix check:
Regression:
Description
When there is a communication problem between the agent and the server, we cannot know it happened.
So we should provide an easy way for the user to monitor it.
Let's provide a "rudder agent nrpe" or similar that is compatible with nagios and returns an error if there were errors during the last connection to the server.
Things to look for in the logs are :
"FATAL:"
"Fatal :"
"Could not get an updated configuration"
Updated by Benoît PECCATTE almost 9 years ago
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
Updated by Benoît PECCATTE almost 9 years ago
- Target version changed from 4.0.0~rc2 to 3.2.0
Updated by Benoît PECCATTE almost 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-agent/pull/38
Updated by Benoît PECCATTE almost 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-agent|7495268f0bf91b98a0cccb3c0669f275bf4952a2.
Updated by Jonathan CLARKE almost 9 years ago
- Related to Bug #7763: Path error in rudder agent health added
Updated by Vincent MEMBRÉ almost 9 years ago
- Related to deleted (Bug #7763: Path error in rudder agent health)
Updated by Vincent MEMBRÉ almost 9 years ago
- Category changed from System integration to Agent
Updated by Vincent MEMBRÉ almost 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.2.0 which were released today.
Actions