Hi all,
I am trying to login to MirrorManager to make some changes but am unable to
do so. When I login, I get the above error (OpenID request was cancelled).
This is happening in Chrome and Firefox for me.
Anyone else having the same issue?
Hi, please add this server to your public Fedora Epel mirror list:
HTTP: http://repos.silknet.com/epel/
HTTPS: https://repos.silknet.com/epel/
Sync schedule: Every 6 hrs
Bandwidth: 1000Mb/s
Location: Georgia/Tbilisi
Sponsor: Silknet JSC
Sponsor URL: https://silknet.com/
IPv4 address to authorize: 213.131.32.179
Email contact: itavartkiladze(a)silknet.com<mailto:itavartkiladze@silknet.com>
Mirroring AltArch: no
Best regards,
Irakli Tavartkiladze
System Administrator
Silknet
E-mail: ITavartkiladze(a)silknet.com<mailto:ITavartkiladze@silknet.com>
Tel: +995 32 2100000 ext: 1505
+995 32 2770100 ext: 7634
3, Gotua str, Right Side of the River Mtkvari
0160, Tbilisi
www.silknet.com<http://www.silknet.com/>
[cid:image001.jpg@01D732B5.4C3F5F90]
This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. Silknet shall not be responsible nor liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Silknet does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference
I am sending this to identify myself according to the instructions on the
mirror-list subscription page. I do not have any knowledge or experience
about any related projects. I am just trying to follow the instructions
from the article at this url:
https://www.techrepublic.com/blog/linux-and-open-source/create-a-local-fedo…
I found this article while looking for a way to alleviate the very slow
times for the automatic repository refresh step when using dnf commands. I
am not sure I will have the time, resources, or proficiency to complete
more than the first few steps.
On Fri, May 07, 2021 at 09:15:42AM +0000, David Guo wrote:
> I'm on behalf of xTom GmbH, we recently hosted a Fedora mirror in Duesseldorf, Germany.
>
> Sync schedule: Every 4 hrs
> Bandwidth: 10Gbps
> Location: Duesseldorf, Germany
> Sponsor: xTom GmbH
> Sponsor URL: https://xtom.com/
>
> IPv4 address to authorize: 62.133.35.14
> IPv6 address to authorize: 2a09:0:8::14
>
> HTTP
> http://mirrors.xtom.de/fedora/
>
> HTTPS
> https://mirrors.xtom.de/fedora/
>
> RSYNC
> rsync://mirrors.xtom.de/fedora/
>
> AltArch HTTP: http://mirrors.xtom.de/fedora-altarch/
> AltArch HTTPS: https://mirrors.xtom.de/fedora-altarch/
> AltArch RSYNC: rsync://mirrors.xtom.de/fedora-altarch/
Please use a tier 1 mirror[1] close to you; create an account in the
MirrorManager[2]; register your mirror in our MirrorManager; enter your
local netblocks in the mirror manager and as soon as you are listed
in the database as up to date yum/dnf will be redirected to your mirror.
All this information can be found in more details in the wiki at:
https://fedoraproject.org/wiki/Infrastructure/Mirroring
Thanks for supporting Fedora. If you have any further questions do not
hesitate to ask.
It would help us a lot if you could provide rsync access for our
crawler. Our crawler checks the content of your mirror and using rsync
requires only one network connection in contrast to crawling via HTTP
which can take up one connection per directory/file on your mirror.
Adrian
[1] https://fedoraproject.org/wiki/Infrastructure/Mirroring/Tiering
[2] https://fedoraproject.org/wiki/Infrastructure/MirrorManager
We've been seeing this intermittently but with increasing frequency of late: the filelist provided does not match the contents of the mirror (kernel.org in our case) which results in a lot of "No such file or directory" errors spammed out from the quick-fedora-mirror script.
Is this something we should try to tune on our end or is there a sync issue upstream from us which needs to be looked into?