Hi Donald, 1) Can you point me in right direction for clarifying that? debian.mirror.ba has an A record pointing to our server.
~ dig debian.mirror.ba > ; <<>> DiG 9.8.3-P1 <<>> debian.mirror.ba > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58440 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 > ;; QUESTION SECTION: > ;debian.mirror.ba. IN A > ;; ANSWER SECTION: > debian.mirror.ba. 90 IN A 80.65.85.94 2) I've downloaded and set up ftpsync. The files should be all up-to-date now. 3) Rsync is fixed now. 4) I've set the EXTENDEDTRACE="full" in ftpsync.conf but it still didn't generate anything more. http://debian.mirror.ba/project/trace/mirror.ba Can you give me a hand with this? On Sun, Apr 24, 2016 at 8:16 PM, Donald Norwood <dnorw...@portalus.com> wrote: > Hi Emir, > > My apologies I did not see your email response. > > 1) Alias issues: > > The alias debian.mirror.ba points to mirror.ba. > The mirror.ba page then links to debian.mirror.ba > > 2) /debian-cd/ not current: > > The /debian-cd/ directory is not current, your mirror has 8.2.0 and > 8.2.0-live and not 8.4. Which your upstream is providing. Please check > your configuration. Are you using the ftpsync script[1] we suggest? > > 3) Rsync does not work: > > rsync rsync://mirror.ba > rsync: failed to connect to mirror.ba (80.65.85.94): Connection refused > (111) > > Please check this configuration. > > > > Also the rsync works now. How do you check if the mirror has been > updated? > > > I can see it has, but you say it hasn't :) > > I look at the /project/trace/ directory which holds the files that the > mirror script generates. The trace file tells us which upstream mirror > you are using, the time your mirror updated, and what the mirror is > carrying. Your tracefile only provides the date but a longer tracefile > (option EXTENDEDTRACE="full" in the ftpsync.conf file) would provide > information such as: > > Sun Apr 24 16:17:57 UTC 2016 > Date: Sun, 24 Apr 2016 16:17:57 +0000 > Date-Started: Sun, 24 Apr 2016 16:04:59 +0000 > Archive serial: 2016042403 > Used ftpsync version: 20160306 > Running on host: intrepid.portalus.net > Architectures: GUESSED:{ source amd64 i386} > Upstream-mirror: ftp.halifax.rwth-aachen.de > SSL: false > Total bytes received in rsync: 365271190 > Total time spent in stage1 rsync: 417 > Total time spent in stage2 rsync: 359 > Total time spent in rsync: 776 > Average rate: 470710 B/s > > Hope that helps. :) > > If you have further questions please reach out I'll do my best to walk > you through the process. > > > [1]ftp://ftp.us.debian.org/debian/project/ftpsync/ftpsync-current.tar.gz > Best regards, > > Donald Norwood > -Debian Mirrors Team > > > On Tue, 12 Apr 2016 08:14:48 +0000 Emir Beganovic > <beganovic.e...@gmail.com> wrote: > > Hi, > > > > Any news on this? > > > > Thanks > > > > On Thu, Apr 7, 2016 at 1:55 AM Emir Beganovic <beganovic.e...@gmail.com> > > wrote: > > > > > Hi Donald, > > > > > > I did the changes as you said. > > > > > > I've removed /debian and left only the /debian-cd. > > > > > > Also the rsync works now. How do you check if the mirror has been > updated? > > > I can see it has, but you say it hasn't :) > > > > > > I was using debian.sil.at but it seems old (2 days at least). I've > > > switched to LeaseWeb's mirror (mirror.de.leaseweb.net) and updated the > > > mirror. > > > > > > Hope it looks good now! > > > > > > Regards > > > > > > > > > On Tue, Apr 5, 2016 at 10:36 PM Donald Norwood <dnorw...@portalus.com> > > > wrote: > > > > > >> Hi Emir, > > >> > > >> Do you change the mirror structure? I swear I accessed this > differently > > >> yesterday. > > >> > > >> The alias listed: debian.mirror.ba no longer works. It does not have > to > > >> be included and is only a minor fix. > > >> > > >> The /debian-cd/ directory has not updated yet. Please check your > > >> upstream provider if you are syncing and it has not updated. > > >> > > >> The rsync mechanism fails: > > >> rsync rsync://mirror.ba/debian-cd > > >> @ERROR: chroot failed > > >> > > >> It would be ideal to remove the /debian/ directory to avoid user > > >> confusion as it appears on your http and ftp listings. > > >> > > >> Best regards, > > >> > > >> Donald Norwood > > >> -Debian Mirrors Team > > >> > > >> > > >> > > >> On Tue, 05 Apr 2016 11:59:58 +0000 Emir Beganovic > > >> <beganovic.e...@gmail.com> wrote: > > >> > Hi Donald, > > >> > > > >> > Our application might have been mistaken a little bit - we're > applying > >
