[BlueOnyx:20643] errors with yum and admin GUI

[Richard Barker]

Only happens on one vps

Get this error when logged in to the admin GUI

*This page would usually display the newsfeed about updates and other 
important anouncements from the www.blueonyx.it website. However, your 
server apparently cannot resolve the domain name www.blueonyx.it, or 
access to that domain is currently not possible for other reasons. This 
has no impact on the functionality of this server, although you also may 
be unable to get YUM updates as long as this problem persists.*

Also get this error when doing a yum update

yum update
Loaded plugins: blueonyx, fastestmirror
BlueOnyx-5209R | 3.0 kB  00:00:00
http://bbone.smd.net/avspamv5/BlueOnyx/5209R/CentOS7/avs6/x86_64/repodata/repomd.xml: 
[Errno 12] Timeout on 
http://bbone.smd.net/avspamv5/BlueOnyx/5209R/CentOS7/avs6/x86_64/repodata/repomd.xml: 
(28, 'Connection timed out after 30000 milliseconds')
Trying other mirror.
Solarspeed.net-AVSPAM-v6 | 2.5 kB  00:00:00
Could not retrieve mirrorlist 
http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock 
error was
14: curl#7 - "Failed to connect to 2607:f8f8:700:12::10: Network is 
unreachable"


  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: base/7/x86_64


-- 

/*Richard C. Barker Sr.
CEO & President
1-813-873-8942
ProBass Networks Inc. */
www.probassnetworks.net <http://www.probassnetworks.net>
www.probass.net <http://www.probass.net>
***************************************
DISCLAIMER : -
This e-mail is confidential and intended only for the use
of the individual or entity named above and may contain
information that is privileged. If you are not the intended
recipient, you are notified that any dissemination, distribution
or copying of this e-mail is strictly prohibited. If you have
received this email in error, please notify us immediately
by return email or telephone and destroy the original message.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20170211/ed427da3/attachment.html>