rsyncd parent process hangs with 100% cpu usage
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| rsync (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: rsync
On our public free software mirror (also se.releases.u.c) we run amd64 hardy on the frontends. The rsyncd parent process quite often stops responding to new connections, and during this it seems to spin on cpu with 100% cpu usage. A quick check with strace on this process doesn't show any syscalls happening.
We currently have a script in cron.hourly that restarts rsyncd if there is nothing responding on localhost:: but even then the outages are frequent enough that it is a problem for our users (especially downstream mirrors). I would guesstimate at a couple of restarts every week.
We've observed this bug since dapper/sarge, but it seems to just get worse, so I'm finally getting around to reporting it. Any suggestions for tracking it down are most welcome, at least if they can be implemented transparently on a production system.
| Serge Hallyn (serge-hallyn) wrote | #1 |
| Changed in rsync (Ubuntu): | |
| status: | New → Invalid |
Please reply if this is still an issue on a supported release.