Actions
Bug #7763
closed
User story #7666: Provide a command to monitor connection errors on the agent
Path error in rudder agent health
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
# rudder agent health grep: /var/rudder/cfengine-community/output/previous: No such file or directory Connection errors in Rudder agent last run See /var/rudder/cfengine-community/output/previous for more details
the name is /outputs/ and not /output/.
Furthermore, the error check of the log file is incorrect, the return code of egrep
when no connection error occurred is 1 and not 0.
EXIT STATUS
Normally the exit status is 0 if a line is selected, 1 if no lines were selected, and 2 if an error occurred.
Updated by Alexis Mousset almost 9 years ago
- Status changed from New to In progress
Updated by Alexis Mousset almost 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-agent/pull/42
Updated by Jonathan CLARKE almost 9 years ago
- Related to User story #7666: Provide a command to monitor connection errors on the agent added
Updated by Alexis Mousset almost 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-agent|7482f3a49af88b26915d9147969ad765c60d44b0.
Updated by Vincent MEMBRÉ almost 9 years ago
- Related to deleted (User story #7666: Provide a command to monitor connection errors on the 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