log sizes
@Rezi1999 is already working on this.
Since Jul 30, 2026.
- Dominant language
- JavaScript
- Stars
- 37
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.