Hello Peter,
We have updated the ftpsync.conf, and have reconfigured the cronjob. I'll
check in a few hours to see if the sync has finished.
00 03 * * * /opt/debiansync/bin/ftpsync sync:all
00 06 * * * /opt/debiansync/bin/ftpsync sync:all
00 12 * * * /opt/debiansync/bin/ftpsync sync:all
00 21 * * * /opt/debiansync/bin/ftpsync sync:all
[root@MSRV001 log]# cat ../etc/ftpsync.conf
MIRRORNAME="mirrors.gigenet.com"
TO="/volume0/mirrors/debian"
RSYNC_PATH="debian"
RSYNC_HOST=debian.csail.mit.edu
LOGDIR="${BASEDIR}/log"
EXCLUDE=""
ARCH_INCLUDE="armhf source amd64 i386 all"
On Tue, Dec 18, 2018 at 4:09 AM Peter Palfrader <wea...@debian.org> wrote:
> ping?
>
> On Tue, 11 Dec 2018, Peter Palfrader wrote:
>
> > On Mon, 10 Dec 2018, Scott Ehas wrote:
> >
> > > We performed an entirely new sync, and I haven't found any errors
> within
> > > the ftpsync logs. Can you confirm everything is correct?
> >
> > http://mirrors.gigenet.com/debian/project/trace/mirrors.gigenet.com
> > says it's from Saturday, December 8.
> >
> > So the file has the right name now, but the sync is not happening
> > regularly (every 6 hours, 4 times a day).
> >
> > Further:
> > - looking at your arch list, you might want to move from an architecture
> > EXCLUDE configuration to an INCLUDE configuration.
> > - You should probably not sync off an ftp.*.debian.org alias and
> > probably not of a DNS rotation of several mirrors. Pick one upstream.
> >
> >
> > Also cf
> > -
> https://mirror-master.debian.org/status/mirror-info/mirrors.gigenet.com.html
> > Cheers,
> >
> > > > I started writing a new howto/guidelines in case that's helpful:
> > > > https://etherpad.wikimedia.org/p/debian-mirror
> > --
> > | .''`. ** Debian **
> > Peter Palfrader | : :' : The universal
> > https://www.palfrader.org/ | `. `' Operating System
> > | `- https://www.debian.org/
> >
>
> --
> | .''`. ** Debian **
> Peter Palfrader | : :' : The universal
> https://www.palfrader.org/ | `. `' Operating System
> | `- https://www.debian.org/
>
