This how-to will describe how to prepare and collect log data for naemon (nagios) and merlin, and supplying this data to op5 Support.
Doing this is often helpful in regards to decreasing the time to resolution for your support case, and it's especially useful in case you contact op5 Support regarding issues related to:
- Check execution
- Peers (load balanced setups)
- Pollers (distributed setups)
Log on as root to all your op5 Monitor nodes (masters, peers and pollers) via SSH, and make sure that the "op5 community" package repository and the "support tools" are installed.
Log on as root to one of your op5 Monitor master nodes via SSH (if you only have a single server, then that's the one), and execute the following command:
This tool will collect all naemon and merlin log data generated the last 30 days, from all your op5 Monitor nodes, and finally create a tarball containing this data, ready to be sent to op5 Support.
For a shorter or longer time period of log data, or to store the tarball at a specific location, start the command with argument
--helpfor more information.
If the log collection was successful, the output will look similar to this:
- As can be seen in the output above, the file /tmp/op5logcollect.1461324223.6124.6AQ6LG/op5-monitor-logs_2016-04-22_13.23.43.tgz was created.
Either download this file using scp/sftp (WinSCP is a nice tool if you're using Windows) and then attach to your support ticket, or send the file directly to op5 by scp via the op5 Monitor server command line (ask op5 Support for instructions).