The Qube! supervisor and workers communicate between themselves in order to coordinate the dispatch and running of jobs, and log this communication in the supelog and workerlog files respectively. Over time, these logs may become very large, can consume an inordinate amount of disk space, and can be unwieldy to should they need to be read for troubleshooting purposes.
Automated log rotation on the supervisor and workers is available via a Windows Scheduled Task, launchctl on OS X, and a cron job on Linux.
Setup and configuration
Linux
Setup
Configuration
logrotated
, and is specified in /etc/logrotate.d/supervisor
. See the man pages for logrotated
if you wish to customize the rotation policies.Rotation Policy
OS X
Setup
Rotation Policy
Configuration
/Library/LaunchDaemons/com.pipelinefx.logrotate.worker.plist
Both of these plists call /Applications/pfx/qube/utils/logrotate.py;
see The logrotate.py script
Windows
Setup
Configuration
%QBDIR%/pfx/qube/utils/logrotate.py,
with only the path to the log as an argument. Rotation Policy
Verifying that log rotation is occurring
- Linux:
/var/log/
- OS X:
/var/log
- Windows Vista, 7, Server 2008:
C:\ProgramData\Pfx\qube\logs
You will see at least on workerlog or supelog file. When rotation occurs, these logs are renamed and/or zipped/compressed.
- supelog -> supelog.1
- supelog.1 --> supelog.2.zip
- supelog.2.zip --> supelog.3.zip
- supelog.3.zip --> supelog.4.zip
- supelog.4.zip is deleted
You will only see supelog and supelog.1 the first time the rotation occurs. The other files will appear when additional log rotation cycles occur as time passes.