Mirrorlist.sangoma.net unavailable

Unable to connect to the repo:

# yum update

Loaded plugins: fastestmirror

Could not retrieve mirrorlist http://mirrorlist.sangoma.net/?release=7&arch=x86_64&repo=os&dist=$dist error was

12: Timeout on http://mirrorlist.sangoma.net/?release=7&arch=x86_64&repo=os&dist=$dist: (28, 'Connection timed out after 30001 milliseconds')
1 Like

Received the below email from several servers.

This is an automatic notification from your FreePBX (VoIP Server) server.

Could not retrieve mirrorlist
error was
12: Timeout on
(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>
 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

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

Cannot find a valid baseurl for repo: sng-base/7/x86_64

Submitted https://issues.freepbx.org/browse/FREEPBX-20112


Receiving the same error on a system that was at Asterisk 13.26 so I can’t change asterisk versions. Odd thing is this system wasn’t at 13.26 so I don’t know how it made that jump.

I’m getting yum errors as well. In addition, I can no longer access my PBX using Firefox today, only Chrome. It was fine Friday.
yum-config-manager --save --setopt=.skip_if_unavailable=true

That is not related to this in anyway. Have you tried clearing your Firefox cache and seeing if that helps?

Same here on several production servers

Unfortunately I do not know how to raise this concern so that someone will see it. The bug tracker is just that, meant for bugs and not for incident reports. The support system will not let me raise the issue without buying credits. The status page shows no incidents/outages: https://status.sangoma.com

I am experiencing the same issue with yum. It would seem this actually is a bug. Though, after grappling with this issue for the past hour, I must say it’s gratifying that I am not alone.


I’m prepping a distro upgrade and the following is also down.

yum -y install http://package1.sangoma.net/distro-upgrade-1807-2.sng7.noarch.rpm

Loaded plugins: fastestmirror, kmod, refresh-packagekit
Setting up Install Process
Cannot open: http://package1.sangoma.net/distro-upgrade-1807-2.sng7.noarch.rpm. Skipping.
Error: Nothing to do

So i’m guessing Sangoma is having some vm problems.

I reported it to Bill in sales as we were already talking about licensing and he said he reported to someone internally.

There is a bad switch being replaced/fixed/something. Sangoma is aware and working on it per Sangoma on IRC.

That is why we are fully network and power redundant in our Headends.

1 Like

I have alerted the Calvary I will update shortly


Thanks James

After reviewing the list of services at https://status.sangoma.com it appears that the SangomaOS dist repo is not included in any of them which is why there is no report of it being down. I would like to request that the repos be added to this status screen.

1 Like

It looks like there is a known issue. Our internal team is aware of it and working on a resolution. There is currently no ETA.

@billsimon I have sent a message about that as well

Yes, cleared cache, restarted Firefox too. I don’t want to hijack this thread. I only posted it in a case that was in some way related. I’ll post a new question on the Firefox thing later so as not to pollute the topic. Thank you.

This is server side

Any progress on a fix?

I am staying on top of them… Squeaky wheel :slight_smile: nothing yet.

1 Like