Message-ID: <1612435351.8173.1711625466553.JavaMail.confluence@host3.pipelinefx.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8172_1870950675.1711625466553" ------=_Part_8172_1870950675.1711625466553 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Qube! supervisor and workers communicate between themselves = in order to coordinate the dispatch and running of jobs, and log this commu= nication 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 troubleshooti= ng 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.
logrotated
=20
, and is specified in =20
/etc/logrotate.d/supervisor
=20
. See the man pages for =20
logrotated
=20
if you wish to customize the rotation policies.
Both of these plists call /App=
lications/pfx/qube/utils/logrotate.py;
see The logrotate.py script
%QBDIR%/pfx/qube/utils/logrotate.py,
with only the =
path to the log as an argument.
/var/log/
=
/v=
ar/log
C:\ProgramData\Pfx\qube\log=
s
You will see at least on workerlog or supelog file. When rotation = occurs, these logs are renamed and/or zipped/compressed.
You will only see supelog and supelog.1 the first time the rotation occu= rs. The other files will appear when additional log rotation cycles o= ccur as time passes.