On Tue Sep 19 08:35:32 2017, ramereth wrote: > On Mon Sep 18 13:12:07 2017, ramereth wrote: > > I'm not sure what's causing this however they seem to be in sync as of right > > now. We've added nagios monitoring for the trace files on each host so we > > can hopefully have better insight into the issue. Please let us know if we > > start lagging behind again but I will do my best to check your mirror status > > site in the coming days. > > Very strange. I just got in the office and noticed that chi and nyc were > behind again so I went looking to compare the trace files. After I ran 'cat' > on the files, I went to look at the mirror report again and suddenly it > decides to resolve itself at that point. I'm starting to wonder if this might > be a filesystem issue and I need to run a fsck on the volume. I'm going to > keep an eye on it later today and see if it does it again.
Hi all, I finally got around to looking into this again. I've updated our ftpsync to version 20180513 and made a few other adjustments. I've been checking your mirror tracker [1][2][3] and it seems all three hosts are now keeping up normally. Can you please verify that on your end as well? I'm hoping this finally resolves the issue :) [1] https://mirror-master.debian.org/status/mirror-info/ftp-osl.osuosl.org.html [2] https://mirror-master.debian.org/status/mirror-info/ftp-nyc.osuosl.org.html [3] https://mirror-master.debian.org/status/mirror-info/ftp-chi.osuosl.org.html -- Lance Albertson Director Oregon State University | Open Source Lab
