This repository was archived by the owner on Oct 1, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 1, 2025. It is now read-only.
Clearinghouse logs grow too quickly #169
Description
The clearinghouse logs seem to grow too quickly and not be culled or rotated.
These logs started 3 weeks (just over 21 days) before this snapshot, (AFAICT) involve no rapidly recurring errors or other anomalies, and occur on a very low traffic test clearinghouse accessible only on the .poly.edu network:
-rw-r--r-- 1 root root 2.9G Feb 19 11:12 transition_twopercent_to_twopercent.log
-rw-r--r-- 1 root root 1.4G Feb 19 11:12 transition_canonical_to_twopercent.log
-rw-r--r-- 1 root root 37M Feb 19 11:12 backend.log
-rw-r--r-- 1 root root 1.1G Feb 19 11:12 transition_donation_to_canonical.log
-rw-r--r-- 1 root root 23M Feb 19 11:12 check_active_db_nodes.log
-rw-r--r-- 1 root root 247M Feb 19 11:12 lockserver.log
-rw-r--r-- 1 root root 2.7G Feb 19 11:12 transition_onepercentmanyevents_to_canonical.log
Activity
awwad commentedon Feb 19, 2016
(Also, why are these logging as root...?)
awwad commentedon Feb 19, 2016
(
Ah...
While the script is being run as the clearinghouse user, the redirect is still technically as root. I suppose we could move that into the script. I suppose there's probably also some single-line-fu way of making the redirect happen as the clearinghouse user, instead of moving the logging into each of the scripts?
EDIT: Single-line-fu solutions exist in this thread. In short: 'tee' command, or explicitly starting a shell with -c (
sudo sh -c 'ls -hal /root/ > /root/test.out'))
awwad commentedon Feb 19, 2016
As for the original issue:
What ever happened to this issue? I don't see weekly log rotation anywhere (nor size-based).