User story #8438
closed
Log check-rudder-agent cron job output
Added by Alexis Mousset over 8 years ago.
Updated over 7 years ago.
Description
All messages are sent to stdout which is redirected to /dev/null in the cron line. We need a way to know what the script did, and be able to monitor it.
- Assignee set to Alexis Mousset
- Target version set to 2.11.23
We should add a log file for any "not normal" situations.
- Target version changed from 2.11.23 to 2.11.24
- Target version changed from 2.11.24 to 308
- Target version changed from 308 to 3.1.14
- Target version changed from 3.1.14 to 3.1.15
- Target version changed from 3.1.15 to 3.1.16
- Target version changed from 3.1.16 to 3.1.17
- Target version changed from 3.1.17 to 3.1.18
- Target version changed from 3.1.18 to 3.1.19
- Tracker changed from Bug to User story
- Subject changed from check-rudder-agent output is not logged to Log check-rudder-agent output
- Target version changed from 3.1.19 to 3.1.20
- Target version changed from 3.1.20 to 3.1.21
- Related to Bug #10771: check-rudder-agent doesn't purge the lmdb file when run via cron added
- Status changed from New to In progress
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- 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-techniques/pull/1151
- Status changed from Pending technical review to Pending release
- Subject changed from Log check-rudder-agent output to Log check-rudder-agent cron job output
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.21 which was released today.
Also available in: Atom
PDF
Updated by Jonathan CLARKE 
Updated by 
Updated by 
Updated by