Collect MCollective logs and Nailgun agent logs from target nodes
On master node:
run 'mco rpc rpcutil daemon_stats -v' and store the output.
Store the file: /var/log/
On target nodes put the next files into an archive:
/var/log/
/var/log/
It could be done on fuel-library side by setting rsyslog::imfile to track /var/log/
Once logs have arrived (continuously updated), any other tasks could be done on the Nailgun side
Blueprint information
- Status:
- Complete
- Approver:
- Bogdan Dobrelya
- Priority:
- Medium
- Drafter:
- Andrey Danin
- Direction:
- Approved
- Assignee:
- Bogdan Dobrelya
- Definition:
- Approved
- Series goal:
- Accepted for 5.0.x
- Implementation:
-
Implemented
- Milestone target:
-
5.0
- Started by
- Bogdan Dobrelya
- Completed by
- Bogdan Dobrelya
Related branches
Related bugs
Sprints
Whiteboard
Please tell us more why do we need to implement this? What is the purpose?
AndreyDanin: now we don't get these logs in a diagnostic snapshot. Wer need to understand what MC agengts are running at the slave nodes and what beheviour they are propagate. Also we should understand what errors oocur on slave modes while MC agent is running. And FuelMenu log also should be included into the diagnostic snapshot.
Gerrit topic: https:/
Addressed by: https:/
Send nailgun-agent logs to syslog as well
Addressed by: https:/
Send mcollective logs to syslog as well
