Hello Peter, * Peter Palfrader <wea...@debian.org> [2017-05-20 13:10]: > > Yes, the sync frequency isn't adapted yet after migrating the Debian > > mirrors to a new infrastructure. It's work in rogress, will be completed > > on Monday. I'll add the trace file at the same time. > Sounds good.
cronjobs are adapted, with */6 frequency. > By all means combine ftpsync with snapshots if you want, but please do > use ftpsync for the actual mirror run. That as well, I adapted our workflow to use ftpsync instead of direct rsync calls. https://mirror-master.debian.org/status/mirror-info/debian.mirrors.ovh.net.html seems to already have picked up this up. Our backend storage isn't currently reachable by rsync, I'll try to reach out to the mirror downstream of us to see what we can do. With this migration we also discontinued ftp services, but it seems as this hasn't been linked by d.o/mirror/list for more than a year now, so it shouldn't be a problem I believe. I monitored ftp logs over the last week and could mostly only see accesses to files that aren't mirrored anymore (squeeze and older) Meanwhile, I noticed that our debian-cd repository (http://debian.mirrors.ovh.net/debian-cd/) isn't listed at https://www.debian.org/CD/http-ftp/, and I'm not sure it ever was. Should I open a separate ticket to include it? And one more question, our new setup permits us to provide the same content at different geolocations, mainly France and Canada for now. Would you prefer keeping those under different DNS names? Or is it possible to list a mirror twice under the same name, but different locations? (for example replacing debian.bhs.mirrors.ovh.net) Thanks and best regards, Felix Krohn -- "I did a quick fix last time but it broke when we rebooted" (© developerexcuses.com)
