Python logging has a WatchedFileHandler which will do the correct thing
for logrotate when copytruncate is not used. Do this to avoid having
multiple copies of the same log in place. Also, this should avoid a race
where log data is lost between copying and truncating done by logrotate.
Change-Id: Idbbc7869004a03b8f19cfbd81ad07f5584ce1964
We think we have useful logs now, so reduce the level just in case
all of the logging is exacerbating the problem.
Change-Id: I85e8e989976b452d73671089a5f66450c8e4743a
Python logrotate does not compress. Use logrotate utility to do log
rotation so that older logs can be compressed saving disk space.
Change python logging to use normal file handlers as it will no longer
be doing the rotation for us. Keep all the file names the same.
Change-Id: I7302e4b197e99fd49fd9d5678702333b17a46efa
To try to understand more about what would cause a zuul-geard
disconnect. Only keep 3 days of logs because they are BIG.
Change-Id: Iba9a8a9c21d82ab4e3323db8c561f8de8c18864f
(This is only used by zuul-dev currently.)
Remove co-hosted gearmand server (will require manual cleanup).
Also, listen for feature/gearman events in openstack-infra.
Change-Id: I2dd58e62ff79277f1ef5c79da54bcc7511f2ccee
Reviewed-on: https://review.openstack.org/30175
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: Monty Taylor <mordred@inaugust.com>
Approved: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
