On Tue, 12 Sep 2017, Agus Priyo wrote: > what is the meaning of score and ~#/d on > https://mirror-master.debian.org/status/mirror-status.html#mirror.poliwangi.ac.id > > what should i do to fix it?
It's a function of mirror status over time, and it's very new and experimental. If you look at https://mirror-master.debian.org/status/mirror-info/mirror.poliwangi.ac.id.html you will see it changing. It's a value between -100 and +100, and every run (every 10 minutes), a small value gets added it everything is OK, and a somewhat larger number is deducted if there are errors. Everything ok currently means: - sitetrace, and mastertrace exist and can be downloaded and parsed, and - the mirror is reasonable recent. > I already use the new ftpsync as you suggest. According to http://mirror.poliwangi.ac.id/debian/project/trace/mirror.poliwangi.ac.id you run quite an old version, 20150425. There have been releases in 2017, e.g. http://mirror.poliwangi.ac.id/debian/project/ftpsync/ftpsync-20170204.tar.gz > I sync mirrors from mirrors.pdx.kernel.org <http://mirrors.pdx.kernel.org>, > no longer to ftp.kaist.ac.kr <http://ftp.kaist.ac.kr> because of too long > access from my network. Ok, that's reasonable. > please tell me to fix problem it. I think things are looking a lot better already. Still, please update your ftpsync version. Also, how often do you update? We recommend four update runs a day (every six hours), synced with when your upstream finished their mirror run. You can check https://mirror-master.debian.org/status/mirror-info/mirrors.pdx.kernel.org.html to see when that is, and add a half hour, hour for good measure. An alternative is to do mirror runs ssh triggered by your upstream (some support that, but not many as it's some work to set up and maintain), or by monitoring the upstream trace file. Cheers, -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `- https://www.debian.org/
