-- Please reply above this line --
Hi Adrian,
I've seen that our mirror has been crawled now but it fails due to the
crawler timeout.
I added our rsync URL to MirrorManager and allowed the IP
209.132.181.102 (fedora's crawler IP in logs) to access it. Is that
the way on how to be crawled using the rsync protocol?
Thanks,
How would you rate my reply?
Great [1] Okay [2] Not Good [3]
--
Francis Roda
noc(a)rise.ph
Links:
------
[1]
On Tue, Jul 7, 2015 at 7:06 PM HKT, Rise NOC
<noc(a)rise.ph> wrote:
Hi Adrian,
Our mirror is now server the rsync protocol but for private use only.
May I know the IP block of the crawler to allow it to use the rsync?
Thanks
--
Francis Roda
noc(a)rise.ph
> On Mon, Jul 6, 2015 at 8:32 PM HKT, Adrian Reber <adrian(a)lisas.de>
wrote:
>
> The steps 1 and 2 has been done. Our mirror syncs from
>>
fedora-rsync.ftp.pub.2iij.net, a Tier 1 mirror. Then registered
> it in
>> mirror manager with a site name MIRROR.RISE.PH and run the
>> REPORT_MIRROR after sync.
>>
>> About the step 3, our mirror is not crawled yet. How did you
> check if
>> our files is up to date?
>
> Your mirror was disabled due to a bug in the web-interface which is
> now
> fixed. The other problem is that the crawler takes too long to scan
> your
> mirror and therefore your mirror will not be marked as up to date.
> The
> crawler takes more than 3 hours to scan your mirror and that is our
> current upper limit.
>
> The most efficient way for the crawler to scan a mirror is rsync,
> maybe
> you could enable rsync so that our crawler can scan you mirror
> faster.
>
> Adrian
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQIVAwUBVZp1aYLJN47TxJBqAQIqHQ/9En1X/uB+0aYREpW0KH414RM+KlG+Di7V
> 7AQowGdRwOS8Zjku7q7Lw1tDa2sHroMbMIpQGOY6tp7liEiGBjeDykUXkml4NBTh
> AMs5iaftbT9/epuPX64B9vSlLdRX6WL0g6PNlsj973dGh7nRcFApjLAN0PPrpHcm
> sw5Vq0x7qJjhp9ODQ56DQUKCWJu4EN2jqjn98Y33IQFoRmbv0NuM1HNT5BRLbvMW
> +39eKGfcdw/WwIkWttf+3KeZnPH4B5KXi6Ua+VcXJVBGLpJiVPGik1JALaoW/Rz9
> gK7Nz6QyrCoLawx7lgRacBIX6bqqCIFSCjpvPz+K4pg6yZkQCyLMQ3aYkZLFZm12
> ZUGAVQpKwKrxd/Pg1w+eMnsoDkhCZc5hgY5VNQrLsS6O2TZirl9zmqfPidewhrgv
> 3nIJQYBQ1J0u7oajUT3R6PQweYpeDB19Jw797xoB6ZF9Rz5AQYizQXxVmQtn+iQ8
> o3ZS9AYCx88cCsp0jlpEBK+P3YfKyo4Q6CSl7VoXX1D7qjqZWkPnFjc/1xg6bRb0
> uxTtMp2d5VuKCs89mDzaUvMX1B3z0oNzc8mhxxXX/KOoOABAaKHIMgVMdPXddA1k
> zrUh2QO5eyz889soBs/PEfGAnq6uYvNnyFH/JHWuS4biuZtvXeXgFiY2nirtZkQk
> 3iZTL+C8mcA=
> =IdiU
> -----END PGP SIGNATURE-----
>
>
>> On Mon, Jul 6, 2015 at 3:32 PM HKT, Rise NOC <noc(a)rise.ph> wrote:
>>
>> Hi Adrian,
>>
>> The steps 1 and 2 has been done. Our mirror syncs from
>>
fedora-rsync.ftp.pub.2iij.net, a Tier 1 mirror. Then registered it in
>> mirror manager with a site name MIRROR.RISE.PH and run the
>> REPORT_MIRROR after sync.
>>
>> About the step 3, our mirror is not crawled yet. How did you check if
>> our files is up to date?
>>
>> Thanks,
>>
>> --
>> Francis Roda
>> noc(a)rise.ph
>>
>>
>>
>>> On Fri, Jul 3, 2015 at 7:48 PM HKT, Adrian Reber
<adrian(a)lisas.de> wrote:
>>>
>>> We would like to support the distribution of Fedora and Fedora EPEL,
>>>> by being registered as an official mirror. Below are the
>>> details of
>>>> our mirror server:
>>>>
>>>> FEDORA
>>>> HTTP:
http://mirror.rise.ph/fedora/ [1] [1]
>>>> FTP: ftp://mirror.rise.ph/fedora/ [2] [2]
>>>>
>>>> FEDORA EPEL
>>>> HTTP:
http://mirror.rise.ph/fedora-epel/ [3] [3]
>>>> FTP: ftp://mirror.rise.ph/fedora-epel/ [4] [4]
>>>>
>>>> IP: 43.226.6.74
>>>> Sync schedule: Every 6 hrs
>>>> Bandwidth: 100Mbps CIR, 1Gbps PIR
>>>> Connectivity: We currently use Telstra (AS4637) as our transit
>>>> provider who connects directly to many other Phillipines
>>> networks.
>>>> Within the next couple of months we will also be present at
>>> PHOpenIX
>>>> in Manila, gathering most other ISPs.
>>>> Location: Cebu, Philippines
>>>> Admins: Dylan Clear, Francis Roda, Marcelito de Guzman
>>>> Email contact: noc(a)rise.ph [5] [5]
>>>>
>>>> Please advise if there is anything above you would like us to
>>> change
>>>> in order to match your policies, or if there are any further
>>> details
>>>> you would like us to provide.
>>>
>>> Please use a tier 1/2 mirror[1] close to you; create an account in
>>> the
>>> MirrorManager[2]; register your mirror in the mirror manager;
>>> enter your local netblocks in the mirror manager (if desired); run
>>> report_mirror[3] and as soon as you are listed in the database as up
>>> to
>>> date yum (and other clients) will be redirected to your mirror.
>>>
>>> All this information can be found in more details in the wiki at:
>>>
>>>
http://fedoraproject.org/wiki/Infrastructure/Mirroring [6]
>>>
>>> Thanks for supporting Fedora!
>>>
>>> If there are any more question do not hesitate to ask.
>>>
>>> Adrian
>>>
>>> [1]
http://fedoraproject.org/wiki/Infrastructure/Mirroring/Tiering
>>> [7]
>>> [2]
http://fedoraproject.org/wiki/Infrastructure/MirrorManager [8]
>>> [3]
http://fedoraproject.org/wiki/Infrastructure/Mirroring [9]
>>>
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1
>>>
>>> iQIVAwUBVZZ2mILJN47TxJBqAQIBSxAAvKn+KBgViYNEhr9vuzzEnxYn2l+BDALS
>>> E2liIMwyLckXLeL8YJ6wWuX04xp6pmcM68IGNqKEefinrJZ2502wj9HDvnoFtttC
>>> kKpcjUHfOKcd7ctFWxBFLrUV1wr3UzJfrssz5f3YRJjpJSGfh5dl2A5OIGgvcNGW
>>> KFRxZhVzi143X75GZV+8g6zpKfQJRuzX8M7ZQLM4jBO13JUYgiySNmE04E/+zQp7
>>> 65m2FnbiAi8gdIbaR9vwpPUzcNqDyG8l/bGlYLbQjMcE9UUmgd1c47UHRfpVYJkF
>>> 5qP5iD/L8LEwT5jZsnjqFeqNEADdEeq6t8MSK7NQBZa5IEZUaACBslKmF1tC3Vmh
>>> sVuSI+3CoAJawO8mxlKzzl8BhQqKB0Nfiegkd+PwmS4BPVtvCz3cpJl+a7+O2UGE
>>> QSNrPukTxONmgeKcOA7ClqDsVU3xtqC2I0oJvInpBaJqpVdmNT880JQNZ3df0QDH
>>> iDu6EgOUH8zzzMVCc6HD2/8jeZtEMNXGUTxwMT9hCu2oqo84MYd/K/G6/Yc3+eo5
>>> Z8kLhEXFXmcLxj1/CuWKRFhPE+SQj5hJtlw1swvW4a2ebTh3SSV1F2K8d9TFF6np
>>> C0qg+2R+ySDIPQvruX/tFRlOxYP5Tp1Jf7bRjKs+ilgaSnanlxCNJ7PQew/EGviQ
>>> sa4oZuVDfPs=
>>> =uDzU
>>> -----END PGP SIGNATURE-----
>>>
>>> Links:
>>> ------
>>> [1]
http://mirror.rise.ph/fedora/
>>> [2] /ftp://mirror.rise.ph/fedora/
>>> [3]
http://mirror.rise.ph/fedora-epel/
>>> [4] /ftp://mirror.rise.ph/fedora-epel/
>>> [5] mailto:noc@rise.ph
>>> [6]
http://fedoraproject.org/wiki/Infrastructure/Mirroring
>>> [7]
http://fedoraproject.org/wiki/Infrastructure/Mirroring/Tiering
>>> [8]
http://fedoraproject.org/wiki/Infrastructure/MirrorManager
>>> [9]
http://fedoraproject.org/wiki/Infrastructure/Mirroring
>>>
>>>
>>>
>>>> On Wed, Jul 1, 2015 at 1:58 PM HKT, Rise NOC <noc(a)rise.ph>
wrote:
>>>>
>>>> Hi,
>>>>
>>>> We would like to support the distribution of Fedora and Fedora EPEL,
>>>> by being registered as an official mirror. Below are the details of
>>>> our mirror server:
>>>>
>>>> FEDORA
>>>> HTTP:
http://mirror.rise.ph/fedora/ [1]
>>>> FTP: ftp://mirror.rise.ph/fedora/ [2]
>>>>
>>>> FEDORA EPEL
>>>> HTTP:
http://mirror.rise.ph/fedora-epel/ [3]
>>>> FTP: ftp://mirror.rise.ph/fedora-epel/ [4]
>>>>
>>>> IP: 43.226.6.74
>>>> Sync schedule: Every 6 hrs
>>>> Bandwidth: 100Mbps CIR, 1Gbps PIR
>>>> Connectivity: We currently use Telstra (AS4637) as our transit
>>>> provider who connects directly to many other Phillipines networks.
>>>> Within the next couple of months we will also be present at PHOpenIX
>>>> in Manila, gathering most other ISPs.
>>>> Location: Cebu, Philippines
>>>> Admins: Dylan Clear, Francis Roda, Marcelito de Guzman
>>>> Email contact: noc(a)rise.ph [5]
>>>>
>>>> Please advise if there is anything above you would like us to change
>>>> in order to match your policies, or if there are any further details
>>>> you would like us to provide.
>>>>
>>>>
>>>> Links:
>>>> ------
>>>> [1]
http://mirror.rise.ph/fedora/
>>>> [2] /ftp://mirror.rise.ph/fedora/
>>>> [3]
http://mirror.rise.ph/fedora-epel/
>>>> [4] /ftp://mirror.rise.ph/fedora-epel/
>>>> [5]
http://mailto:noc@rise.ph/
>>>>
>>>> --
>>>> Francis Roda
>>>> noc(a)rise.ph
>>>>
>>>>
>>>>
>>>>
>>>
>>
>