Bug#358313: ftp.debian.org: Korean mirror unstable
Simon Paillard wrote: [...] > To ftp.kr.d.o (aka ftp.kaist.ac.kr) admins: > Could you investigate this issue ? Is there a limit concerning the > number of clients or something else ? I believe such errors were due to our poor machine at that moment. We switched to a much more powerful and stable hardware around April. Currently, connection limits do exist, but we've never seen the numbers reaching it. Our service must be stable these days. Thanks for your information anyway. :) Regards, J signature.asc Description: Digital signature
Bug#687969: ftp.debian.org: ftp.kr.debian.org began to develop Hash Sum errors.
Sorry about the confusion. However, you can confirm the upstream ones are fresh. ftp-master having Tue Oct 2 20:28:04 UTC 2012 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) 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? ~Jaeho On Tue, Oct 2, 2012 at 3:24 PM, Simon Paillard wrote: > Hi, > > On Mon, Oct 01, 2012 at 01:54:10AM -0700, Jaeho Shin wrote: > > Sorry for the delay. > > A few days ago, we have upgraded our ftpsync to a recent one, but forgot > to > > respond. > > > > This bug can be closed now, and we'll keep a better eye on the mailing > list > > in the future. > > No successful update occurred since 20th Sept ? > http://ftp.kr.debian.org/debian/project/trace/ > > Could you please check what is going on ? > > Do you receive ftpsync mails ? > > -- > Simon Paillard > >
Bug#687969: ftp.debian.org: ftp.kr.debian.org began to develop Hash Sum errors.
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 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 > 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 > >
Bug#687969: ftp.debian.org: ftp.kr.debian.org began to develop Hash Sum errors.
Hi Simon, Sorry for the delay. A few days ago, we have upgraded our ftpsync to a recent one, but forgot to respond. This bug can be closed now, and we'll keep a better eye on the mailing list in the future. ~Jaeho On Tue, Sep 18, 2012 at 3:07 AM, Simon Paillard wrote: > Hello Kaist admins, > > On Tue, Sep 18, 2012 at 02:18:31AM +0900, Hughe Chung wrote: > > Package: ftp.debian.org > > Severity: normal > > > > The Hash sum error during package update from the Debian official Korean > server > > has been found. I tried to fix it three different ways as below. All > methods failed. I > > checked it on a Squeeze system and it got exact same error. > > > > ftp.neowiz.com - unofficial Korean mirror site works fine like other > mirrors > > on foreign countries.. > > > > I began to experience this Hash Sum error one or two weeks ago. Replacing > > mirror worked out so I haven't spend time on it. I did troubleshoot it > today > > for two hours. > > > > W: Failed to fetch > > > > bzip2:/var/lib/apt/lists/partial/ftp.kr.debian.org_debian_dists_testing_main_i18n_Translation-en: > > Hash Sum mismatch > [..] > > Please upgrade your ftpsync version as advised on debian-mirrors-announce > mailing list. > > http://lists.debian.org/debian-mirrors-announce/2012/05/msg1.html > > Regards. > > -- > Simon Paillard > >
Bug#421333: mirror submission for ftp.kr.debian.org
Hi, (Sorry for late response, a little busy these days.) On Sat, 2007-04-28 at 11:28:53 +0200, Simon Paillard wrote: > Hello, > > On Fri, Apr 27, 2007 at 11:06:52PM +, KAIST FTP Operators wrote: > > Site: ftp.kr.debian.org > > Submission-Type: update > > Aliases: ftp.kaist.ac.kr > > Type: leaf > > Given your upstream mirror, I think that is still Push-Primary, isn't it ? Correct. We are waiting for push-triggers all the time. :) > > > Old-ftp: /debian-archive/ > > Old-http: /debian-archive/ > > Old-rsync: debian-archive/ > > Added. > > By the way : > > * you can delete http://ftp.kr.debian.org/debian-non-US/ that is now > obsolete. We will remove that soon. Thanks for your notice. > > * I don't know if you already use it, but you're advised to use > almost-atomic update scripts : > In the recent rsync versions, the --delay-updates and --delete-after > options combined with a two stages rsync allow to greatly reduce the > time a Debian mirror is not consistent and users cannot fetch packages. > > So every Debian mirror admin should use these new options. Be careful, > --delete-after is space consuming during the update ! > > We encourage you to use the official example script updated to use these > options: <http://www.debian.org/mirrors/anonftpsync> > > Please confirm that you switched to such a kind of script. [...] Yes, we are using a similar script tailored to our system. It is using those two options with the two stage rsyncs. After having a look at anonftpsync, I decided to merge some new tweaks, e.g. sync'ing only pool/ for the first phase. Thanks for pointing out those changes again. You may take a look of the script we are using if you want: http://ftp.kaist.ac.kr/pkgs/debian/sync Best regards, J -- 신재호 | Jaeho Shin <[EMAIL PROTECTED]> | http://netj.org/ signature.asc Description: Digital signature
Bug#596348: mirror listing update for ftp.kr.debian.org
Hi, Thanks for processing our issue so fast. 2010-09-11, 03:57, Simon Paillard 작성: > Hi, > > On Fri, Sep 10, 2010 at 03:52:43PM +, KAIST File Archive Operators wrote: >> Package: mirrors >> Severity: minor >> >> Submission-Type: update >> Site: ftp.kr.debian.org >> Aliases: ftp.kaist.ac.kr >> Type: leaf > [..] >> Volatile-ftp: /debian-volatile/ >> Volatile-http: /debian-volatile/ >> Volatile-rsync: debian-volatile/ >> Volatile-upstream: valente.debian.org > > Please make sure you sync from the role address > volatile-master.debian.org (which is *today* the same as valente > though). > Yes. That's where we actually sync from. The submission system was strangely rejecting the host volatile-master.d.o, so I looked up the FQDN of it and submitted it instead only to pass the system's check. >> CDImage-upstream: cdimage.debian.org >> Updates: push > > I know push is ok for archive, volatile, backports. > > Are you pushed for CDImage ? > Yes, we're actually a fully push triggered Debian mirror! (assuming there's no push for /debian-archive/ :) ~Jaeho -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
