Bug in syslogd-listfiles causing insane log rotation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sysklogd (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Binary package hint: sysklogd
** First some background information:
About a year ago I enabled syslog to listen on my private LAN so I could forward syslog message from my OpenWTR (linux) NAT router and save it on my workstation (to debug an intermittent problem with the ADSL PPPoE handshake). To make sure I'd get all logs from the router in a single place I added the following line in syslog.conf:
*.* /var/log/
** The first side effects of the bug:
A few months ago I started having login issues, both with local (console and GUI) login and ssh. I added a bare root shell (no login) on tty12 to debug when it happens and I finally found out timeouts were occurring while reading /var/log. It turned out I had millions of files with a few random .0, .2, .3, .4 or .gz extentions and logins were timing out while trying to read that folder (probably somewhere in the pam/logging code.
I knew it was something with the log rotation scripts but didn't had time to find the culprit until now. I was working around it with a periodic:
rm -f /var/log/
** The root cause:
It turns out /etc/cron.
I quickly looked at /usr/sbin/
Given the impact this bug can have on the system (causing login timeouts) and the little work required to fix it I believe it should be treated as urgent.
Changed in sysklogd (Ubuntu): | |
status: | Incomplete → New |
Changed in sysklogd (Ubuntu): | |
status: | New → Confirmed |
Is this symptom still reproducible in 8.10 or 9.04?