Forums

Resolved
0 votes
Hello,

I have a fresh install of ClearOS, in a VM for testing purposes. I have direct access to the internet and works inside the VM, I tried using both NAT and Bridged in VMware Workstation.
Whenever I try to install anything from the marketplace I get the error:

Exception: Cannot find a valid baseurl for repo: clearos-centos-verified

I get the same using yum update on the console.

I found a few, very, old posts on similar problems and tried various things I found there. "Yum clean all" even up to editing the repo files, trying other mirrors.

Any idea what I need to do to be able to install updates?

Thanks in advance

Chris
Tuesday, September 15 2020, 08:37 PM
Share this post:
Responses (9)
  • Accepted Answer

    Wednesday, September 16 2020, 10:44 AM - #Permalink
    Resolved
    0 votes
    Sorry - don't have an email error sample as they are deleted after being read, and Trash has been emptied. Do remember "baseurl" being mentioned and a particular repository being unavailable with hints to try to work-around the error. The same for all ClearOS systems. Enabled automatic updates and ran /etc/cron.d/app-software-updates. Two lines were added to /var/log/system.

    Sep 16 20:27:24 emma software-updates: starting update
    Sep 16 20:28:22 emma software-updates: no updates required

    My script produces much more useful information...

    Loaded plugins: clearcenter-marketplace, fastestmirror, verify
    ClearCenter Marketplace: fetching repositories...
    Cleaning repos: clearos clearos-centos clearos-centos-sclo-rh clearos-centos-updates clearos-contribs clearos-epel clearos-fast-updates clearos-infra clearos-paid clearos-updates
    Cleaning up list of fastest mirrors
    Loaded plugins: clearcenter-marketplace, fastestmirror, verify
    ClearCenter Marketplace: fetching repositories...
    Determining fastest mirrors
    * clearos: mirror1-sanfrancisco.clearos.com
    * clearos-centos: download2.clearsdn.com
    * clearos-centos-sclo-rh: download2.clearsdn.com
    * clearos-centos-updates: download2.clearsdn.com
    * clearos-contribs: mirror1-sanfrancisco.clearos.com
    * clearos-epel: download2.clearsdn.com
    * clearos-fast-updates: download2.clearsdn.com
    * clearos-infra: mirror1-sanfrancisco.clearos.com
    * clearos-paid: mirror1-sanfrancisco.clearos.com
    * clearos-updates: mirror1-sanfrancisco.clearos.com
    clearos | 3.7 kB 00:00:00
    clearos-centos | 3.6 kB 00:00:00
    clearos-centos-sclo-rh | 3.0 kB 00:00:00
    clearos-centos-updates | 2.9 kB 00:00:00
    clearos-contribs | 3.5 kB 00:00:00
    clearos-epel | 2.9 kB 00:00:00
    clearos-fast-updates | 3.0 kB 00:00:00
    clearos-infra | 3.5 kB 00:00:00
    clearos-updates | 3.5 kB 00:00:00
    (1/14): clearos/7/group_gz | 1.6 kB 00:00:01
    (2/14): clearos-centos/x86_64/group_gz | 153 kB 00:00:01
    (3/14): clearos-contribs/7/updateinfo | 96 B 00:00:00
    (4/14): clearos-contribs/7/primary_db | 66 kB 00:00:00
    (5/14): clearos-centos-sclo-rh/x86_64/primary_db | 2.8 MB 00:00:05
    (6/14): clearos-fast-updates/x86_64/primary_db | 10 kB 00:00:00
    (7/14): clearos-infra/7/updateinfo | 96 B 00:00:00
    (8/14): clearos-infra/7/primary_db | 11 kB 00:00:00
    (9/14): clearos-updates/7/updateinfo | 96 B 00:00:00
    (10/14): clearos-updates/7/primary_db | 176 kB 00:00:01
    (11/14): clearos-centos/x86_64/primary_db | 6.1 MB 00:00:10
    (12/14): clearos/7/primary_db | 1.0 MB 00:00:10
    (13/14): clearos-centos-updates/x86_64/primary_db | 4.3 MB 00:00:12
    (14/14): clearos-epel/7/x86_64/primary_db | 11 MB 00:00:15
    clearos-paid | 3.5 kB 00:00:00
    clearos-paid/updateinfo | 96 B 00:00:00
    clearos-paid/primary_db | 115 kB 00:00:00
    No packages marked for update

    As part of my installs always disable auto system updates - far too dangerous. Retrying later in the day got the app-base and clearos-release updates on a test system OK.

    EDIT: When are ClearOS going to fix their code tags and introduce a horizontal scroll-bar and stop breaking long lines. Other sites do, hopeless....
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 16 2020, 09:34 AM - #Permalink
    Resolved
    0 votes
    OK. The nightly job /etc/cron.d/app-software-updates produces similar output in the system log and I can see no lines mentioning either baseurl or Exception over the last 10 weeks. Something different (PHP error) went wrong last night which I am trying to track down.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 16 2020, 09:08 AM - #Permalink
    Resolved
    0 votes
    Nick - just the script as shown below run during the night (aussie time) and piped into an email sent to my admin email address for all systems. Check them in the morning. Dead simple... Advantage being the update(s) are already on the machine if wanted, saving time...

    #!/bin/bash
    yum clean all
    rm -rf /var/cache/yum
    yum update -y --downloadonly

    Should be surprised, no - should be astounded, if ClearOS were not monitoring the respositories. Sadly though, it wouldn't be a surprise... Do the same using appropriate code for other distributions which use yum, dnf, apt-get etc

    EDIT. Unclear about the reference to webconfigs - I very rarely use webconfig. Neither do I edit any contents of /etc/yum.repos.d - it's whatever ClearOS has put in there.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 16 2020, 08:40 AM - #Permalink
    Resolved
    0 votes
    Yesterday was a bad day as we had a problem with all Digital Ocean servers but was fixed so should clear. It is odd as I am not seeing these issues. Do you have an automatic way of spotting the problem or do you go into each of your servers to check? If you have an automatic way, it would be great if I could use it. I have a number of servers running at the moment for various testing configurations both here and in the US but I don't often visit the webconfigs.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 16 2020, 08:16 AM - #Permalink
    Resolved
    0 votes
    Nick - the error was evident on all my ClearOS (community) 7.x machines. OK now. In fact I see this type of error every every few weeks and just wait another day if I require something, then try again. I have machines running several disributions, ClearOS repositories, for me, are the most unreliable. All my mchines run a 'downlod only' update each night sending an email report with details, so I am aware every day of any new updates, and how reliable the various respositories are.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 16 2020, 08:00 AM - #Permalink
    Resolved
    0 votes
    There was a general repo issue issue yesterday which was fixed at about 18h00 UTC+1 but I somehow doubt if it would have affected you. Is your DNS working OK? Can you ping google.com from ClearOS?

    A "yum clean all" won't work on the verified repos. Instead can you do an:
    rm -rf /var/cache/yum/
    And try again.

    If that does not work please do the following:
    wget https://mirror2-newyork.clearos.com/clearos/7/updates/x86_64/RPMS/app-base-2.9.3-1.v7.noarch.rpm
    wget https://mirror2-newyork.clearos.com/clearos/7/updates/x86_64/RPMS/app-base-core-2.9.3-1.v7.noarch.rpm
    wget https://mirror2-newyork.clearos.com/clearos/7/updates/x86_64/RPMS/clearos-release-7-8.2.v7.x86_64.rpm
    yum update app-base* clearos-release* --disablerepo=*
    yum update
    Then try again?
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, September 15 2020, 10:05 PM - #Permalink
    Resolved
    0 votes
    The NIC is marked as external.
    I am quite sure there is no proxy, but to make sure I just connected using my phone as hotspot and I get the same error.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, September 15 2020, 09:07 PM - #Permalink
    Resolved
    0 votes
    The other thing to check is if you have a proxy upstream from ClearOS. In that case you also need to set the proxy settings in the IP Settings for the NIC.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, September 15 2020, 09:03 PM - #Permalink
    Resolved
    0 votes
    I think this happens when your internet-facing NIC is not set as External (even if it is on your LAN). Please can you check? This applies to both Standalone and Gateway installations.
    The reply is currently minimized Show
Your Reply