Hi,
We are running a Centos mirror mirrors.nayatel.com. We have noticed that that sometimes mirror status page of centos us shows our mirror as unreachable. The server is however up and serving content. The reason I could find is that TIME file under the mirror root directory goes blank after a mirror sync. On next sync the problem is typically fixed. We are using us-msync.centos.org for rsync mirror and following is the mirror script running 4 times a day. Need guidance how to address this issue.
#!/bin/bash if [ -f /var/lock/subsys/rsync_updates ]; then echo "Updates via rsync already running." exit 0 fi if [ -d /mirrors/centos ] ; then touch /var/lock/subsys/rsync_updates rsync -avzH --delete --delay-updates us-msync.centos.org::CentOS /mirrors/centos/ /bin/rm -f /var/lock/subsys/rsync_updates else echo "Target directory /mirrors/centos not present." fi
Regards
Jahanzeb
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 19/08/15 12:01, Jahanzeb Arshad wrote:
Hi,
We are running a Centos mirror mirrors.nayatel.com. We have noticed that that sometimes mirror status page of centos us shows our mirror as unreachable. The server is however up and serving content. The reason I could find is that TIME file under the mirror root directory goes blank after a mirror sync. On next sync the problem is typically fixed. We are using us-msync.centos.org for rsync mirror and following is the mirror script running 4 times a day. Need guidance how to address this issue.
Hmm, that issue with TIME would be interesting to investigate : I'll check on my side, but content of that file is monitored on our side on all msync nodes. What's the msync node from which you synced and saw that behaviour ? Assuming you have your rsync log, the fqdn of the server you're syncing from is in the rsyncd header.
Cheers,
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 08/19/2015 06:06 PM, Fabian Arrotin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 19/08/15 12:01, Jahanzeb Arshad wrote:
Hi,
We are running a Centos mirror mirrors.nayatel.com. We have noticed that that sometimes mirror status page of centos us shows our mirror as unreachable. The server is however up and serving content. The reason I could find is that TIME file under the mirror root directory goes blank after a mirror sync. On next sync the problem is typically fixed. We are using us-msync.centos.org for rsync mirror and following is the mirror script running 4 times a day. Need guidance how to address this issue.
Hmm, that issue with TIME would be interesting to investigate : I'll check on my side, but content of that file is monitored on our side on all msync nodes. What's the msync node from which you synced and saw that behaviour ? Assuming you have your rsync log, the fqdn of the server you're syncing from is in the rsyncd header.
Cheers,
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlXUf10ACgkQnVkHo1a+xU5KawCeKmYIyhhalbz7Tt/AgU+eN/lq KDoAnA9W5b2WgMcP+yMi9u/nua1f4L0G =IE8J -----END PGP SIGNATURE----- _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
We are using us-msync.centos.org for mirroring.
Regards
Jahanzeb
20.8.2015, 7.28, Jahanzeb Arshad kirjoitti:
On 08/19/2015 06:06 PM, Fabian Arrotin wrote:
Hmm, that issue with TIME would be interesting to investigate : I'll check on my side, but content of that file is monitored on our side on all msync nodes. What's the msync node from which you synced and saw that behaviour ? Assuming you have your rsync log, the fqdn of the server you're syncing from is in the rsyncd header.
We are using us-msync.centos.org for mirroring.
us-msync.centos.org is a round robin DNS entry for around 40 different servers. When you rsync, you will see the server's name in the greeting, centosn7 in this case:
$ rsync rsync://us-msync.centos.org/
msync.CentOS.org rsync service (centosn7) ...
If you keep logs of your rsync sessions, it would be useful to know from which server you synced from and ended up with an empty TIME file.
On 08/20/2015 12:17 PM, Anssi Johansson wrote:
20.8.2015, 7.28, Jahanzeb Arshad kirjoitti:
On 08/19/2015 06:06 PM, Fabian Arrotin wrote:
Hmm, that issue with TIME would be interesting to investigate : I'll check on my side, but content of that file is monitored on our side on all msync nodes. What's the msync node from which you synced and saw that behaviour ? Assuming you have your rsync log, the fqdn of the server you're syncing from is in the rsyncd header.
We are using us-msync.centos.org for mirroring.
us-msync.centos.org is a round robin DNS entry for around 40 different servers. When you rsync, you will see the server's name in the greeting, centosn7 in this case:
$ rsync rsync://us-msync.centos.org/
msync.CentOS.org rsync service (centosn7) ...
If you keep logs of your rsync sessions, it would be useful to know from which server you synced from and ended up with an empty TIME file. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
Okay. I was not keeping rsync logs before. Started doing it from now. Will share with you once I face the problem again. Current sync done from following and got proper TIME file.
msync.CentOS.org rsync service (centosc5)
Regards
Jahanzeb
On 08/20/2015 01:25 PM, Jahanzeb Arshad wrote:
On 08/20/2015 12:17 PM, Anssi Johansson wrote:
20.8.2015, 7.28, Jahanzeb Arshad kirjoitti:
On 08/19/2015 06:06 PM, Fabian Arrotin wrote:
Hmm, that issue with TIME would be interesting to investigate : I'll check on my side, but content of that file is monitored on our side on all msync nodes. What's the msync node from which you synced and saw that behaviour ? Assuming you have your rsync log, the fqdn of the server you're syncing from is in the rsyncd header.
We are using us-msync.centos.org for mirroring.
us-msync.centos.org is a round robin DNS entry for around 40 different servers. When you rsync, you will see the server's name in the greeting, centosn7 in this case:
$ rsync rsync://us-msync.centos.org/
msync.CentOS.org rsync service (centosn7) ...
If you keep logs of your rsync sessions, it would be useful to know from which server you synced from and ended up with an empty TIME file. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
Okay. I was not keeping rsync logs before. Started doing it from now. Will share with you once I face the problem again. Current sync done from following and got proper TIME file.
msync.CentOS.org rsync service (centosc5)
Regards
Jahanzeb _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
Okay faced the problem today. Following was the mirror server:
msync.CentOS.org rsync service (centost7)
Regards
Jahanzeb
On 08/25/2015 05:58 PM, Jahanzeb Arshad wrote:
On 08/20/2015 01:25 PM, Jahanzeb Arshad wrote:
On 08/20/2015 12:17 PM, Anssi Johansson wrote:
20.8.2015, 7.28, Jahanzeb Arshad kirjoitti:
On 08/19/2015 06:06 PM, Fabian Arrotin wrote:
Hmm, that issue with TIME would be interesting to investigate : I'll check on my side, but content of that file is monitored on our side on all msync nodes. What's the msync node from which you synced and saw that behaviour ? Assuming you have your rsync log, the fqdn of the server you're syncing from is in the rsyncd header.
We are using us-msync.centos.org for mirroring.
us-msync.centos.org is a round robin DNS entry for around 40 different servers. When you rsync, you will see the server's name in the greeting, centosn7 in this case:
$ rsync rsync://us-msync.centos.org/
msync.CentOS.org rsync service (centosn7) ...
If you keep logs of your rsync sessions, it would be useful to know from which server you synced from and ended up with an empty TIME file. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
Okay. I was not keeping rsync logs before. Started doing it from now. Will share with you once I face the problem again. Current sync done from following and got proper TIME file.
msync.CentOS.org rsync service (centosc5)
Regards
Jahanzeb _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
Okay faced the problem today. Following was the mirror server:
msync.CentOS.org rsync service (centost7)
Regards
Jahanzeb _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
Hi,
Our mirror is again shown down and the TIME file is blank. Following is the server from which last sync was done.
msync.CentOS.org rsync service (centosv)
Regards
Jahanzeb
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 26/08/15 07:06, Jahanzeb Arshad wrote:
On 08/25/2015 05:58 PM, Jahanzeb Arshad wrote:
<snip>
Hi,
Our mirror is again shown down and the TIME file is blank. Following is the server from which last sync was done.
msync.CentOS.org rsync service (centosv)
Regards
Jahanzeb
Hi,
So you had the issue with that centosv and centost7 servers, which have the correct TIME file when I checked. Let me try to see where that error would be located. Would be good to see if other people are seeing the same issue.
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
-
Anssi Johansson -
Fabian Arrotin -
Jahanzeb Arshad