-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
And indeed I read it and tested it carefully before setting the
options. Everything worked fine with the old version I had before.
Something changed with this version making it not accept the -h option
anymore.
I only have three other options set in
Hi Heiko
On Sun, Oct 15, 2017 at 07:16:24PM +0200, Heiko Richter wrote:
> You are indeed right, I set -h to receive human-readable numerals
> within the in logs. Just removed it and everything ran fine.
Okay. There is a reason why this part of the example config is prefixed
with:
| ## BE VERY C
Hi Peter
On Sun, Oct 15, 2017 at 05:00:51PM +, Peter Palfrader wrote:
> On Sun, 15 Oct 2017, Heiko Richter wrote:
> > Going through the logs I noticed ftpsync breakes after the second
> > stage. As I haven't changed anything it seems to be a bug in the
> > newest version of the ftpsync script.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I did not change anything in the script, just set the options in the
configuration file.
Line 601 in version 20170920 contains the following mathematical
operation:
total=$(( total + bytes ))
You are indeed right, I set -h to receive human-readab
Hi Heiko
On Sun, Oct 15, 2017 at 04:28:59PM +0200, Heiko Richter wrote:
> Going through the logs I noticed ftpsync breakes after the second
> stage. As I haven't changed anything it seems to be a bug in the
> newest version of the ftpsync script.
Did you change anything on the script?
> Here are
On Sun, 15 Oct 2017, Heiko Richter wrote:
> Going through the logs I noticed ftpsync breakes after the second
> stage. As I haven't changed anything it seems to be a bug in the
> newest version of the ftpsync script.
>
> Here are the logs:
> Oct 15 16:18:28 www ftpsync[39220]: Back from rsync wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Going through the logs I noticed ftpsync breakes after the second
stage. As I haven't changed anything it seems to be a bug in the
newest version of the ftpsync script.
Here are the logs:
Oct 15 16:18:28 www ftpsync[39220]: Back from rsync with retu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Everything is in order with my mirror except that the new ftpsync
creates a different trace file.
old filename: ftp.heikorichter.name
new filename: ftp.heikorichter.name.new
Obviously the new ftpsync version only updates the new file and leaves
the
ping.
On Tue, 10 Oct 2017, Peter Palfrader wrote:
> On Tue, 26 Sep 2017, Heiko Richter wrote:
>
> > Just found the error and fixed it. ftpsync is running right now, so the
> > mirror should be in sync again shortly.
>
> According to
> https://mirror-master.debian.org/status/mirror-info/ftp.hei
On Tue, 26 Sep 2017, Heiko Richter wrote:
> Just found the error and fixed it. ftpsync is running right now, so the
> mirror should be in sync again shortly.
According to
https://mirror-master.debian.org/status/mirror-info/ftp.heikorichter.name.html
your mirror hasn't successfully finished a run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
Just found the error and fixed it. ftpsync is running right now, so the
mirror should be in sync again shortly.
Heiko
Am 26.09.2017 um 10:37 schrieb Peter Palfrader:
> Package: mirrors
> User: mirr...@packages.debian.org
> Usertags: mirror-pr
Hi,
Thank you for your message. Strangely neither cron nor ftpmirror did not send
me any notices or errors.
I will look into it immediately.
Heiko
Am 26. September 2017 10:37:14 MESZ schrieb Peter Palfrader :
>Package: mirrors
>User: mirr...@packages.debian.org
>Usertags: mirror-probl
Package: mirrors
User: mirr...@packages.debian.org
Usertags: mirror-problem may-auto-close
Control: submitter -1 mirr...@debian.org
Hi,
I was checking some things in the Debian mirror universe and noticed
a problem with your mirror:
o Your mirror is out of date by almost a week
Status:
https
13 matches
Mail list logo
