Re: spurious Archive-Update-in-Progress-syncproxy.wna.debian.org
On Wed, Nov 25, 2009 at 05:41:20PM -0200, Carlos Carvalho wrote:
> syncproxy.wna "leaked" the update-in-progress above. We've been
> triggered by it, so that file should have already been removed. It's a
> config error or a bug in ftpsync. This isn't the first time; such
> leaks happen occasionally.
Seems to be a bug in ftpsync: cleanup function (which removes the
"lock") seems trapped on exit, so *after* push signal is sent to
mirrors.
There is no conequence of this, except the archive update itself is
actually finished at the moment the push of 2nd stage / all stages is
triggered, so the ftpsync lock file should be already removed IMO.
> BTW, the last push we got was this one, so there are already 3
> consecutive updates missing.
Triggers at 10 AM UTC and 16 PM happened in a weird way from
ftp-masters, some files where generated (or at least available in the
tree) when sync from syncproxy.wna.d.o started.
rsync: send_files failed to open "/dists/squeeze/main/source/Sources.bz2.new" (in debian): Permission denied (13)
rsync: send_files failed to open "/dists/squeeze/main/source/Sources.gz.new" (in debian): Permission denied (13)
Because of this failure, the push didn't happen.
--
Simon Paillard
Reply to: