YUM update repository problems (from Russia)

curl -v -H ‘Host: mirrorlist.nethserver.org’ ‘http://packages.nethesis.it/7/nethserver?release=7&repo=nethforge&arch=x86_64

  • About to connect() to packages.nethesis.it port 80 (#0)
  • Trying 46.101.114.111…
  • Connected to packages.nethesis.it (46.101.114.111) port 80 (#0)

GET /7/nethserver?release=7&repo=nethforge&arch=x86_64 HTTP/1.1
User-Agent: curl/7.29.0
Accept: /
Host: mirrorlist.nethserver.org

< HTTP/1.1 200 OK
< Date: Fri, 11 May 2018 10:31:23 GMT
< Server: Apache/2.4.6 (CentOS) PHP/5.4.16
< X-Powered-By: PHP/5.4.16
< Content-Length: 773
< Content-Type: text/plain; charset=UTF-8
<
http://mirror.nethserver.org/nethserver/7/nethforge/x86_64/
http://mirror1.nethserver.org/nethserver/7/nethforge/x86_64/
http://mirror2.nethserver.org/nethserver/7/nethforge/x86_64/
https://mirror.nethesis.it/nethserver/7/nethforge/x86_64/
http://nethserver.de-labrusse.fr/7/nethforge/x86_64/
http://mirror.framassa.org/nethserver/7/nethforge/x86_64/
http://mirror.nordest.systems/nethserver/7/nethforge/x86_64/
https://mirror.alpix.eu/nethserver/7/nethforge/x86_64/
http://mrmarkuz.goip.de/mirror/nethserver/7/nethforge/x86_64/
http://mirror.pcxlan.es/nethserver/7/nethforge/x86_64/
https://markusneuberger.at/mirror/nethserver/7/nethforge/x86_64/
http://buck.goip.de/nethserver/7/nethforge/x86_64/
http://nethserver.globalcortex.net/mirror/nethserver/7/nethforge/x86_64/

  • Connection #0 to host packages.nethesis.it left intact
    13:31:23 root@ms jobs:0 cmd:187 /root

ping 46.101.114.111

PING 46.101.114.111 (46.101.114.111) 56(84) bytes of data.
64 bytes from 46.101.114.111: icmp_seq=1 ttl=57 time=46.6 ms
64 bytes from 46.101.114.111: icmp_seq=2 ttl=57 time=49.7 ms
64 bytes from 46.101.114.111: icmp_seq=3 ttl=57 time=46.7 ms
^C
— 46.101.114.111 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 46.605/47.693/49.766/1.477 ms

2 Likes

yum clean all && rm -rf /var/cache/yum && yum -y update
Loaded plugins: changelog, fastestmirror, nethserver_events
Cleaning repos: base centos-sclo-rh centos-sclo-sclo collaboraoffice.com_repos_CollaboraOnline_CODE-centos7 epel
: extras nethforge nethserver-base nethserver-updates remi-php56 remi-safe updates veeam
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos
Cleaning up list of fastest mirrors
Loaded plugins: changelog, fastestmirror, nethserver_events
Determining fastest mirrors
epel/x86_64/metalink | 13 kB 00:00:00
Could not retrieve mirrorlist http://mirrorlist.nethserver.org/7/nethserver?release=7&repo=nethforge&arch=x86_64 error was
12: Timeout on http://mirrorlist.nethserver.org/7/nethserver?release=7&repo=nethforge&arch=x86_64: (28, ‘Connection timed out after 30001 milliseconds’)

One of the configured repositories failed (Unknown),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work “fix” this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=<repoid> ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable <repoid>
    or
        subscription-manager repos --disable=<repoid>

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: nethforge/7/x86_64

But it does not find non-package updates

Did you set it?

Yes.

yum clean all && rm -rf /var/cache/yum && yum -y update
Loaded plugins: changelog, fastestmirror, nethserver_events
Cleaning repos: base centos-sclo-rh centos-sclo-sclo collaboraoffice.com_repos_CollaboraOnline_CODE-centos7 epel extras
: nethforge nethserver-base nethserver-updates remi-php56 remi-safe updates veeam
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos
Cleaning up list of fastest mirrors
Loaded plugins: changelog, fastestmirror, nethserver_events
Determining fastest mirrors
epel/x86_64/metalink | 13 kB 00:00:00

https://wiki.centos.org/yum-errors

If above article doesn’t help to resolve this issue please use https://bugs.centos.org/.

One of the configured repositories failed (NethServer-7 - Base),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work “fix” this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=nethserver-base ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable nethserver-base
    or
        subscription-manager repos --disable=nethserver-base

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=nethserver-base.skip_if_unavailable=true

failure: repodata/repomd.xml from nethserver-base: [Errno 256] No more mirrors to try.
http://docs.readthedocs.org/en/latest/canonical.html/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

Maybe some repositories IP are in Russian block list too?

ping mirrorlist.nethserver.org
PING mirrorlist.nethserver.org (46.101.114.111) 56(84) bytes of data.
64 bytes from mirrorlist.nethserver.org (46.101.114.111): icmp_seq=1 ttl=57 time=47.3 ms
64 bytes from mirrorlist.nethserver.org (46.101.114.111): icmp_seq=2 ttl=57 time=49.3 ms
64 bytes from mirrorlist.nethserver.org (46.101.114.111): icmp_seq=3 ttl=57 time=46.8 ms
64 bytes from mirrorlist.nethserver.org (46.101.114.111): icmp_seq=4 ttl=57 time=49.5 ms
64 bytes from mirrorlist.nethserver.org (46.101.114.111): icmp_seq=5 ttl=57 time=47.8 ms
64 bytes from mirrorlist.nethserver.org (46.101.114.111): icmp_seq=6 ttl=57 time=47.6 ms
64 bytes from mirrorlist.nethserver.org (46.101.114.111): icmp_seq=7 ttl=57 time=52.3 ms
64 bytes from mirrorlist.nethserver.org (46.101.114.111): icmp_seq=8 ttl=57 time=46.4 ms
64 bytes from mirrorlist.nethserver.org (46.101.114.111): icmp_seq=9 ttl=57 time=47.5 ms
64 bytes from mirrorlist.nethserver.org (46.101.114.111): icmp_seq=10 ttl=57 time=49.5 ms
^C

ping packages.nethserver.org
PING packages.nethserver.org (159.89.233.254) 56(84) bytes of data.
^C
packages.nethserver.org ping statistics —
7 packets transmitted, 0 received, 100% packet loss, time 5999ms

In the inside network http://packages.nethserver.org/ open, the server is not pingback

Do you use your NethServer as DNS server on your local network?
And if so, is it listed as first or second DNS server? (I remember a glitch in NethSevrer DNS settings that the secondary listed DNS server was used prior to the 1st DNS server listed… see Nethserver DNS primary and secondary server entries have mixed priorities in dnsmasq?

It looks like the DNS setting is not (yet) propagated to your clients.

Yes use

Primary DNS 77.88.8.8

Inside the network everything open, from the NS open not go!!!

ping packages.nethserver.org
PING packages.nethserver.org (159.89.233.254) 56(84) bytes of data.
^C
packages.nethserver.org ping statistics —
17 packets transmitted, 0 received, 100% packet loss, time 15999ms

It seems that IP of packages.nethserver.org is the same as mirrorlist.nethserver.org

@davidep: can you confirm that this should work?:

* go to DNS page and set an override for packages.nethserver.org pointing to 46.101.114.111 too

No, it can’t work. I think @kelevra must comment out mirrorlist= lines in *.repo files and configure the corresponding baseurl= to reachable mirrors.

Do not prompt, what I need to adjust the mirror?
It’s amazing that the mirrors were working yesterday before the update and suddenly blocked after the update. As we have seen, the IPS does not block the server. Therefore it is not in the lock, then locks himself NethServer.

Look at the .repo files in /etc/yum.repos.d directory. You can comment out the mirrorlist= line and have your own baseurl= line with the mirror site of your choice. You can list multiple sites if you wish.

https://www.centos.org/forums/viewtopic.php?t=11668

1 Like

Заблокировано в России

Добрый всем день!
IP зеркала заблокированы провайдерами интернета в России. Попали под раздачу наверно при блокировки Telegram. Есть другие варианты или иные зеркала для стабильной установки и обновления?

Good day everyone!
IP mirrors are blocked by Internet providers in Russia. Got under the hand, probably at a blocking Telegram. Are there other options or other mirrors for a stable installation and upgrade?

Let’s write an Howto! The idea is to create a local override of mirrorlist.nethserver.org

With a local override, no modification of YUM config is required. It’s like not having IP blocks…

1 Like

I started process of unbloking IP 159.89.233.254 (http://mirrorlist.nethserver.org/). Maybe it will be successful.

4 Likes

Now in Russia again blocked mirrorlist.nethserver.org and partly community.nethserver.org.

You may publish other ip addresses for mirrorlist.nethserver.org ?

1 Like

Sorry, but we don’t have another machine running the mirrorlist service.

I suggest you to disable the mirrorlist from the Nethserver.repo configuration file, then enable the baseurl option selecting a mirror from this list http://mirror-status.nethserver.org/

2 Likes

Thank you!

1 Like

For reference
you can configure the proxy on the server with one command
it works for me
through a proxy updated server

Use the following syntax to configure traffic types such as http, https, and ftp from the command line:
export ftp_proxy=»http://proxy-server:port»
export http_proxy=»http://proxy-server:port»
export https_proxy=»https://proxy-server:port»

Use the following syntax if the proxy server requires authentication:
export http_proxy=»http://user:pass@proxy-server:port»
export https_proxy=»https://user:pass@proxy-server:port»
export ftp_proxy=»http://user:pass@proxy-server:port»