Koozali.org formerly Contribs.org

Sorry - false alarm - yum update error

Sorry - false alarm - yum update error
« on: January 30, 2020, 11:05:03 PM »
Dear all,

not sure, if this is a bug. On *one* of my servers I'm trying to run a yum update. Other servers are updating fine. Here's what happens:

(only) info:
# uname -r
2.6.32-754.25.1.el6.x86_64

# yum clean all -v
Loading "fastestmirror" plugin
Loading "post-transaction-actions" plugin
Loading "smeserver" plugin
Config time: 0.014
Yum Version: 3.2.29
Cleaning repos: base smeaddons smeextras smeos smeupdates updates
Cleaning up Everything
Cleaning up list of fastest mirrors

# mv /home/e-smith/db/yum_repositories /home/e-smith/db/yum_repositories.old

# expand-template /etc/yum.smerepos.d/sme-base.repo

# /etc/e-smith/events/actions/initialize-default-databases
Migrating existing database backups
Migrating existing database yum_updates
Migrating existing database spamassassin
Migrating existing database yum_installed
Migrating existing database networks
Migrating existing database yum_repositories
Migrating existing database mailpatterns
Migrating existing database accounts
Migrating existing database hosts
Migrating existing database yum_available
Migrating existing database domains
Migrating existing database configuration

# signal-event yum-modify

# yum --enablerepo=* clean all

# yum update --enablerepo=smecontribs
Loaded plugins: fastestmirror, post-transaction-actions, smeserver
Setting up Update Process
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os error was
14: PYCURL ERROR 22 - "The requested URL returned error: 400 Bad Request"
Error: Cannot find a valid baseurl for repo: base

Server is behind a proxy. Therefore there's a custom-template:
# less 10main_proxy
{my $YumProxy = $yum{Proxy} || "none";$OUT = ($YumProxy eq "none") ? "" : "proxy=$YumProxy";}

# less yum_repositories shows:
# DO NOT MODIFY THIS FILE.
# This file is automatically maintained by the Mitel Networks SME Server
# configuration software.  Manually editing this file may put your
# system in an unknown state.
#
# updated: Thu Jan 30 22:55:31 2020
base=repository|EnableGroups|no|Exclude|initscripts,libgsf|GPGCheck|yes|MirrorList|http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os|Name|CentOS - os|Visible|yes|status|enabled
centosplus=repository|EnableGroups|no|GPGCheck|yes|MirrorList|http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus|Name|CentOS - centosplus|Visible|no|status|disabled
contrib=repository|EnableGroups|no|GPGCheck|yes|MirrorList|http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=contrib|Name|CentOS - contrib|Visible|no|status|disabled
extras=repository|EnableGroups|no|GPGCheck|yes|MirrorList|http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras|Name|CentOS - extras|Visible|no|status|disabled
fasttrack=repository|EnableGroups|no|GPGCheck|yes|MirrorList|http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=fasttrack|Name|CentOS - fasttrack|Visible|no|status|disabled
smeaddons=repository|EnableGroups|yes|GPGCheck|yes|MirrorList|http://mirrorlist.contribs.org/mirrorlist/smeaddons-9|Name|SME Server - addons|Visible|yes|status|enabled
smecontribs=repository|EnableGroups|yes|GPGCheck|yes|MirrorList|http://mirrorlist.contribs.org/mirrorlist/smecontribs-9|Name|SME Server - contribs|Visible|no|status|disabled
smedev=repository|EnableGroups|yes|GPGCheck|yes|MirrorList|http://mirrorlist.contribs.org/mirrorlist/smedev-9|Name|SME Server - dev|Visible|no|status|disabled
smeextras=repository|EnableGroups|yes|GPGCheck|yes|MirrorList|http://mirrorlist.contribs.org/mirrorlist/smeextras-9|Name|SME Server - extras|Visible|yes|status|enabled
smeos=repository|EnableGroups|yes|GPGCheck|yes|MirrorList|http://mirrorlist.contribs.org/mirrorlist/smeos-9|Name|SME Server - os|Visyum_repositories

Absolut no idea what's wrong. Any help would be greatly appreciated.

regards,
stefan
« Last Edit: January 31, 2020, 02:06:15 AM by SchulzStefan »
And then one day you find ten years have got behind you.

Time, 1973
(Mason, Waters, Wright, Gilmour)

Offline Jean-Philippe Pialasse

  • *
  • 1,573
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: yum update error
« Reply #1 on: January 30, 2020, 11:41:52 PM »
Url is good

Are you able to ping the host from this sme ?
Is your proxy correct ?
Is it up?

Re: yum update error
« Reply #2 on: January 30, 2020, 11:45:47 PM »
Bon soir Jean-Philippe,

thank's for joining in so fast. Let me hold the horses for a few minutes... I checked all logs and saw certificate errors. I fixed this. Right now the machine is rebooting. I'll be back in a second and will report.

regards,
stefan
And then one day you find ten years have got behind you.

Time, 1973
(Mason, Waters, Wright, Gilmour)

Re: yum update error
« Reply #3 on: January 31, 2020, 12:12:35 AM »
Url is good

Are you able to ping the host from this sme ?
Is your proxy correct ?
Is it up?

Here's what you've asked for:

# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=23.5 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=23.1 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=23.1 ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2045ms
rtt min/avg/max/mdev = 23.108/23.264/23.529/0.188 ms

# ping google.de
PING google.de (216.58.207.131) 56(84) bytes of data.
64 bytes from muc11s03-in-f3.1e100.net (216.58.207.131): icmp_seq=1 ttl=55 time=23.2 ms
64 bytes from muc11s03-in-f3.1e100.net (216.58.207.131): icmp_seq=2 ttl=55 time=23.0 ms
^C
--- google.de ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1964ms
rtt min/avg/max/mdev = 23.007/23.151/23.295/0.144 ms

# ping contribs.org
PING contribs.org (212.83.168.232) 56(84) bytes of data.
64 bytes from front.koozali.org (212.83.168.232): icmp_seq=1 ttl=54 time=47.0 ms
64 bytes from front.koozali.org (212.83.168.232): icmp_seq=2 ttl=54 time=46.4 ms
64 bytes from front.koozali.org (212.83.168.232): icmp_seq=3 ttl=54 time=46.8 ms
^C
--- contribs.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2101ms
rtt min/avg/max/mdev = 46.429/46.748/47.001/0.238 ms

# ping mirrorlist.centos.org
PING mirrorlist.centos.org (216.176.179.218) 56(84) bytes of data.
64 bytes from unlays-running.viewpoor.net (216.176.179.218): icmp_seq=1 ttl=51 time=187 ms
64 bytes from unlays-running.viewpoor.net (216.176.179.218): icmp_seq=2 ttl=51 time=186 ms
64 bytes from unlays-running.viewpoor.net (216.176.179.218): icmp_seq=3 ttl=51 time=186 ms
64 bytes from unlays-running.viewpoor.net (216.176.179.218): icmp_seq=4 ttl=51 time=190 ms

# yum update
Loaded plugins: fastestmirror, post-transaction-actions, smeserver
Setting up Update Process
Determining fastest mirrors
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os error was
14: PYCURL ERROR 22 - "The requested URL returned error: 400 Bad Request"
Error: Cannot find a valid baseurl for repo: base
« Last Edit: January 31, 2020, 12:31:19 AM by SchulzStefan »
And then one day you find ten years have got behind you.

Time, 1973
(Mason, Waters, Wright, Gilmour)

Re: yum update error
« Reply #4 on: January 31, 2020, 12:47:16 AM »
From another server in the same network:

# ping mirrorlist.centos.org
PING mirrorlist.centos.org (212.69.166.138) 56(84) bytes of data.
64 bytes from babylon.castlegem.co.uk (212.69.166.138): icmp_seq=1 ttl=52 time=52.1 ms
64 bytes from babylon.castlegem.co.uk (212.69.166.138): icmp_seq=2 ttl=52 time=51.5 ms
64 bytes from babylon.castlegem.co.uk (212.69.166.138): icmp_seq=3 ttl=52 time=51.6 ms
64 bytes from babylon.castlegem.co.uk (212.69.166.138): icmp_seq=4 ttl=52 time=51.4 ms
64 bytes from babylon.castlegem.co.uk (212.69.166.138): icmp_seq=5 ttl=52 time=51.0 ms
^C
--- mirrorlist.centos.org ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4492ms
rtt min/avg/max/mdev = 51.020/51.568/52.179/0.450 ms


# yum update
Geladene Plugins: fastestmirror, post-transaction-actions, smeserver
Einrichten des Aktualisierungsprozess
Loading mirror speeds from cached hostfile
 * base: ftp.agdsn.de
 * smeaddons: www.mirrorservice.org
 * smeextras: www.mirrorservice.org
 * smeos: www.mirrorservice.org
 * smeupdates: www.mirrorservice.org
 * updates: ftp.wrz.de
Löse Abhängigkeiten auf
--> Führe Transaktionsprüfung aus
---> Package kernel.x86_64 0:2.6.32-754.27.1.el6 will be installiert
---> Package kernel-firmware.noarch 0:2.6.32-754.25.1.el6 will be aktualisiert
---> Package kernel-firmware.noarch 0:2.6.32-754.27.1.el6 will be an update
---> Package kernel-headers.x86_64 0:2.6.32-754.25.1.el6 will be aktualisiert
---> Package kernel-headers.x86_64 0:2.6.32-754.27.1.el6 will be an update
--> Abhängigkeitsauflösung beendet
--> Führe Transaktionsprüfung aus
---> Package kernel.x86_64 0:2.6.32-754.23.1.el6 will be gelöscht
--> Abhängigkeitsauflösung beendet

Abhängigkeiten aufgelöst

========================================================================================================
 Paket                     Arch             Version                          Repository           Grösse
========================================================================================================
Installieren:
 kernel                    x86_64           2.6.32-754.27.1.el6              smeupdates            32 M
Aktualisieren:
 kernel-firmware           noarch           2.6.32-754.27.1.el6              smeupdates            29 M
 kernel-headers            x86_64           2.6.32-754.27.1.el6              smeupdates           4.6 M
Entfernen:
 kernel                    x86_64           2.6.32-754.23.1.el6              @updates             133 M

Vorgangsübersicht
========================================================================================================
Install       1 Package(s)
Upgrade       2 Package(s)
Remove        1 Package(s)

Gesamte Downloadgrösse: 66 M
Ist dies in Ordnung? [j/N] :

Seems to be a mirror problem?
And then one day you find ten years have got behind you.

Time, 1973
(Mason, Waters, Wright, Gilmour)

Re: yum update error
« Reply #5 on: January 31, 2020, 12:57:33 AM »
The question is why is yum not switching to another mirror if this one does not work?
And then one day you find ten years have got behind you.

Time, 1973
(Mason, Waters, Wright, Gilmour)

Re: yum update error
« Reply #6 on: January 31, 2020, 02:02:22 AM »
Good news - no bug, all this has got nothing to do with SME 9.2 I'm sorry for bothering.

It's a firewall issue. I have to check what happened since the last update of my OPNsense. It seems to be a web-proxy problem. *All* servers are whitelisted to bypass the proxy. At this moment it's difficult to understand why one server allows yumming and the other not. It's too late (or early) for today to investigate more. At least the update went through, so far everything is fine.

Again sorry for wasting time of Jean-Philippe and who else followed.

regards,
stefan
And then one day you find ten years have got behind you.

Time, 1973
(Mason, Waters, Wright, Gilmour)

Offline TerryF

  • grumpy old man
  • *
  • 1,322
Re: Sorry - false alarm - yum update error
« Reply #7 on: January 31, 2020, 02:24:37 AM »
Dont worry, all adds to the knowledge tree :-) I also experience that irregularly, new VMs and old installs..more to do with my location I think :-)
--
qui scribit bis legit

Offline janet

  • ****
  • 4,812
Re: Sorry - false alarm - yum update error
« Reply #8 on: January 31, 2020, 03:35:58 AM »
TerryF & all

Yes I just had a very similar error after moving server box.
I plugged the Ethernet cable into wrong NIC socket on SME server, resulting in no network access & subsequent update errors.
Switched the lead & all OK now.
Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Offline TerryF

  • grumpy old man
  • *
  • 1,322
Re: Sorry - false alarm - yum update error
« Reply #9 on: January 31, 2020, 05:33:47 AM »
I plugged the Ethernet cable into wrong NIC socket on SME server, resulting in no network access & subsequent update errors.

 :lol: :lol: :lol: :lol:
--
qui scribit bis legit

Offline ReetP

  • *
  • 2,792
Re: Sorry - false alarm - yum update error
« Reply #10 on: January 31, 2020, 12:59:40 PM »
I plugged the Ethernet cable into wrong NIC socket on SME server, resulting in no network access & subsequent update errors.

:lol: :lol: :lol: :lol:

There but for the grace go I !!!!
...
1. Read the Manual
2. Read the Wiki
3. Don't ask for support on Unsupported versions of software
4. I have a job, wife, and kids and do this in my spare time. If you want something fixed, please help.

Bugs are easier than you think: http://wiki.contribs.org/Bugzilla_Help

If you love SME and don't want to lose it, join in: http://wiki.contribs.org/Koozali_Foundation