Mirrorlist.sangoma.net down?


(Keithc) #1

Just installed freepbx image and tried a ‘yum update’ but getting the following

[root@freepbx ~]# yum update
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.sangoma.net/?release=7-8.2003.3.el7.sangoma&arch=x86_64&repo=os&dist=$dist&staging=$staging error was
12: Timeout on http://mirrorlist.sangoma.net/?release=7-8.2003.3.el7.sangoma&arch=x86_64&repo=os&dist=$dist&staging=$staging: (28, 'Connection timed out after 30000 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: sng-base/7-8.2003.3.el7.sangoma/x86_64

It is responding to ping. Am I missing something or has this changed?


(Lorne Gaetz) #2

No issues here and no reported outages. Look for common culprits, DNS?


(Keithc) #3

Thanks for verifying. Issue is on my side, looks like routing/firewall.