Simon, you were right. Our mirror was not getting past stage1 for a while, but now it's fixed. After our ssh port got blocked, we were invoking ftpsync from crontab, but too excessively. Invoking ftpsync while another one was running touched the update-required file, and this made ftpsync loop in stage1 so it never proceeded to the rest of the sync.
We learned we should be careful not to invoke ftpsync too frequently when doing it manually, and our mirror is now (really) in sync. I also made some internal changes, so we can use ftpsync without any modification. Previously, we added a hook to the cleanup part of ftpsync. I'll contact you privately (and perhaps mirrors@) to get our push triggers back via a non-standard ssh port. Thanks, and sorry for the mess we made, ~Jaeho On Wed, Oct 3, 2012 at 1:54 AM, Simon Paillard <spaill...@debian.org> wrote: > Hi, > > On Tue, Oct 02, 2012 at 05:50:33PM -0700, Jaeho Shin wrote: > > On Tue, Oct 2, 2012 at 3:24 PM, Simon Paillard <spaill...@debian.org> > wrote: > > > On Mon, Oct 01, 2012 at 01:54:10AM -0700, Jaeho Shin wrote: > > > No successful update occurred since 20th Sept ? > > > http://ftp.kr.debian.org/debian/project/trace/ > > > > Sorry about the confusion. However, you can confirm the upstream ones > are > > fresh. > > > > ftp-master having Tue Oct 2 20:28:04 UTC 2012 > > It's misleading, it can happen you have synchronized trace files and part > of > the mirror, but the sync is not properly finished so local trace file not > generated. > > > Seems like the upgrade wasn't smooth and our timestamps aren't being > > generated since then. We are hooking some of our pre/post scripts into > > ftpsync, but that must have gone wrong. We'll fix it soon. > > > > Yes we do receive the mails, and despite seeing some connection timeouts > > for a few days, it seems to be keeping in sync. (except our trace > timestamp) > > You may disable the hook for the moment so that 1 full sync is performed > including trace file. > > > We're also working on opening a ssh port for receiving push triggers from > > you. Our campus network policy became very strict a while ago and most > of > > the known service ports have been closed. > > > Is it possible to receive ssh triggers on a non-standard port BTW? > > Yes. > > > -- > Simon Paillard > >
