log sizes

[rhclopes]

A new perfSONAR host admin reported recently that their host stopped working because /var reached 100% usage.

Things could be immediately improved if perfSONAR shipped with log rotation and compression for all perfsonar-tool kit logs. Presently,
the toolkit does ship a logrotate configuration that does not rotate nor compress old logs, except swamp logs.

It could be shipped with something like
'''
/var/log/perfsonar/*.log {
sharedscripts
size 100M
rotate 54
compress
compresscmd /bin/bzip2
delaycompress
notifempty
missingok
postrotate
/bin/kill -HUP cat /var/run/syslogd.pid 2> /dev/null 2> /dev/null || true
/bin/kill -HUP cat /var/run/rsyslogd.pid 2> /dev/null 2> /dev/null || true
endscript
}
'''

In addition the documentation could advise sites about using OS installs with separate /var partition with suitable size.

A 64GB partition should be suitable for most hosts if rotation with compression is deployed.

Raul

[mfeit-internet2]

The log rotation configurations installed by pScheduler and the bundles inherit the default behavior from whatever the OS installs. We can't dictate behavior for specific configurations because they'd end up not working for someone else's system or violating retention rules.

Treat this as a configuration issue and make configuring the defaults part of the system setup procedure.

I'll move this over to Toolkit for further discussion, if any.