Fehler bei zypper up

Hallo,
seit einiger Zeit bekomme ich an meinem Laptop diese Meldungen bei “zypper up”:

Laptop-0025:~ # zypper up 
Retrieving repository 'Packman' metadata ......................................................................................................................................................................[done]
Building repository 'Packman' cache ...........................................................................................................................................................................[done]
Retrieving repository 'Update repository with updates from SUSE Linux Enterprise 15' metadata .................................................................................................................[done]
Building repository 'Update repository with updates from SUSE Linux Enterprise 15' cache ......................................................................................................................[done]
Retrieving repository 'security' metadata ------------------------------------------------------------------------------------------------------------------------------------------------------------------------\]
Warning: Digest verification failed for file 'f324205720a984cf1fc6e752ec9370e4984786195fca985eaa357fb1a3fd36a9-primary.xml.gz'
[/var/tmp/AP_0xviQmbX/repodata/f324205720a984cf1fc6e752ec9370e4984786195fca985eaa357fb1a3fd36a9-primary.xml.gz]

  expected f324205720a984cf1fc6e752ec9370e4984786195fca985eaa357fb1a3fd36a9
  but got  f19272f3ce7cf1978c4d896dd0b28cfb3a4efa1ff34acac5df604cbdc71d71a1

Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise.

However if you made certain that the file with checksum 'f192..' is secure, correct
and should be used within this operation, enter the first 4 characters of the checksum
to unblock using this file on your own risk. Empty input will discard the file.

Unblock or discard? [f192/...? shows all options] (discard): 
Retrieving repository 'security' metadata ....................................................................................................................................................................[error]
Repository 'security' is invalid.
[security|http://download.opensuse.org/repositories/security/openSUSE_Leap_15.3/] Valid metadata not found at specified URL
History:
 - f324205720a984cf1fc6e752ec9370e4984786195fca985eaa357fb1a3fd36a9-primary.xml.gz has wrong checksum
 - Can't provide ./repodata/f324205720a984cf1fc6e752ec9370e4984786195fca985eaa357fb1a3fd36a9-primary.xml.gz

Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'security' because of the above error.
Retrieving repository 'vivaldi' metadata ......................................................................................................................................................................[done]
Building repository 'vivaldi' cache ...........................................................................................................................................................................[done]
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...

The following 10 package updates will NOT be installed:
  libbox2d2 libixion-0_16-0 libmetalink3 liborcus-0_16-0 libsox3 openslp publicsuffix sox telnet vlan

The following 4 packages are going to be upgraded:
  libmariadbd19 mariadb mariadb-client mariadb-errormessages

4 packages to upgrade.
Overall download size: 27.5 MiB. Already cached: 0 B. After the operation, additional 330.6 KiB will be used.
Continue? [y/n/v/...? shows all options] (y): 
Retrieving package mariadb-errormessages-10.5.16-150300.3.18.1.noarch                                                                                                           (1/4), 269.5 KiB (  2.6 MiB unpacked)
Retrieving delta: ./noarch/mariadb-errormessages-10.5.15_10.5.16-150300.3.15.1_150300.3.18.1.noarch.drpm, 114.4 KiB
Retrieving: mariadb-errormessages-10.5.15_10.5.16-150300.3.15.1_150300.3.18.1.noarch.drpm .....................................................................................................................[done]
Applying delta: ./mariadb-errormessages-10.5.15_10.5.16-150300.3.15.1_150300.3.18.1.noarch.drpm ...............................................................................................................[done]
Retrieving package mariadb-client-10.5.16-150300.3.18.1.x86_64                                                                                                                  (2/4),   1.1 MiB ( 26.4 MiB unpacked)
Retrieving delta: ./x86_64/mariadb-client-10.5.15_10.5.16-150300.3.15.1_150300.3.18.1.x86_64.drpm, 180.1 KiB
Retrieving: mariadb-client-10.5.15_10.5.16-150300.3.15.1_150300.3.18.1.x86_64.drpm ............................................................................................................................[done]

Warning: Digest verification failed for file 'mariadb-client-10.5.15_10.5.16-150300.3.15.1_150300.3.18.1.x86_64.drpm'
[/var/tmp/AP_0x9NitPX/x86_64/mariadb-client-10.5.15_10.5.16-150300.3.15.1_150300.3.18.1.x86_64.drpm]

  expected 8b42da979e06f35930eca692b33056db63052789297207a67ca8bf88cc5a3ac0
  but got  93b27f778e891bd29c3cf34b57b3e0e88302720488530ec07c31358add4342f1

Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise.

However if you made certain that the file with checksum '93b2..' is secure, correct
and should be used within this operation, enter the first 4 characters of the checksum
to unblock using this file on your own risk. Empty input will discard the file.

Unblock or discard? [93b2/...? shows all options] (discard): 
mariadb-client-10.5.15_10.5.16-150300.3.15.1_150300.3.18.1.x86_64.drpm has wrong checksum
History:                                                                                                                                                                                                             
 - Can't provide ./x86_64/mariadb-client-10.5.15_10.5.16-150300.3.15.1_150300.3.18.1.x86_64.drpm                                                                                                                     

Retrieving: mariadb-client-10.5.16-150300.3.18.1.x86_64.rpm ...................................................................................................................................................[done]

Warning: Digest verification failed for file 'mariadb-client-10.5.16-150300.3.18.1.x86_64.rpm'
[/var/tmp/AP_0x9NitPX/x86_64/mariadb-client-10.5.16-150300.3.18.1.x86_64.rpm]

  expected c0f38c995d5bffc0c7b35ab35867f1d82e92392b1dacaf7f03b61ed686ee7b37
  but got  c52bfc0c7c1600b9eaf545010d259e2963009abf3bbbd65fd31d5bbe1100c507

Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise.

However if you made certain that the file with checksum 'c52b..' is secure, correct
and should be used within this operation, enter the first 4 characters of the checksum
to unblock using this file on your own risk. Empty input will discard the file.

Unblock or discard? [c52b/...? shows all options] (discard): 
Package mariadb-client-10.5.16-150300.3.18.1.x86_64 (Update repository with updates from SUSE Linux Enterprise 15) seems to be corrupted during transfer. Do you want to retry retrieval?
Abort, retry, ignore? [a/r/i] (a): 
Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.                                                                                                                                                                           
Please see the above error message for a hint.

Dabei sind aber immer andere Repos betroffen. Meine Repos:



[FONT=monospace][FONT=monospace]#  | Alias                 | Name                                                         | Enabled | GPG Check | Refresh | Priority | URI 
---+-----------------------+--------------------------------------------------------------+---------+-----------+---------+----------+--------------------------------------------------------------------------------- 
 1 | Firefox               | Firefox                                                      | Yes     | (r ) Yes  | Yes     |   90     | https://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/ 
 2 | KDE:Extra             | KDE:Extra                                                    | Yes     | (r ) Yes  | Yes     |   90     | http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Leap_15.3/ 
 3 | LibreOffice           | LibreOffice                                                  | Yes     | (r ) Yes  | Yes     |   80     | http://download.opensuse.org/repositories/LibreOffice:/7.3/openSUSE_Leap_15.3/ 
 4 | OSS_Update            | OSS_Update                                                   | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/update/leap/15.3/oss/ 
 5 | Packman               | Packman                                                      | Yes     | (r ) Yes  | Yes     |   99     | http://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Leap_15.3/ 
 6 | home:ecsos            | home:ecsos                                                   | No      | ----      | ----    |   99     | https://download.opensuse.org/repositories/home:/ecsos/openSUSE_Leap_15.3/ 
 7 | network_utilities     | network_utilities                                            | Yes     | (r ) Yes  | Yes     |   60     | http://download.opensuse.org/repositories/network:/utilities/openSUSE_Leap_15.3/ 
 8 | repo-backports-update | Update repository of openSUSE Backports                      | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/update/leap/15.3/backports/ 
 9 | repo-non-oss          | Non-OSS                                                      | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/ 
10 | repo-oss              | OSS                                                          | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/distribution/leap/15.3/repo/oss/ 
11 | repo-sle-update       | Update repository with updates from SUSE Linux Enterprise 15 | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/update/leap/15.3/sle/ 
12 | repo-source           | Source Repository                                            | No      | ----      | ----    |   99     | http://download.opensuse.org/source/distribution/leap/15.3/repo/oss/ 
13 | repo-source-non-oss   | Source Repository (Non-OSS)                                  | No      | ----      | ----    |   99     | http://download.opensuse.org/source/distribution/leap/15.3/repo/non-oss/ 
14 | repo-update-non-oss   | Non-Oss Update                                               | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/update/leap/15.3/non-oss/ 
15 | security              | security                                                     | Yes     | (r ) Yes  | Yes     |   60     | http://download.opensuse.org/repositories/security/openSUSE_Leap_15.3/ 
16 | virtualbox            | VirtualBox                                                   | Yes     | (r ) Yes  | Yes     |  120     | http://download.virtualbox.org/virtualbox/rpm/opensuse/15.0/x86_64/ 
17 | vivaldi               | vivaldi                                                      | Yes     | (r ) Yes  | Yes     |   90     | https://repo.vivaldi.com/archive/rpm/x86_64
[/FONT] [/FONT]

Es war schon das LibreOffice-Repos, mal das SLE-Repo, heute nun das security-Repo :frowning: Gerstern klappte das Update - heute wieder nicht.

Versucht habe ich “[FONT=monospace][FONT=monospace][FONT=monospace][FONT=tahoma]zypper clean -a && zypper ref” und danach “zypper up” - das selbe wieder.
Kann es wirklich sein, dass ich immer gerade zum Erneuerungszeitpunkt ein Update versuche?

VG
[/FONT][/FONT][/FONT][/FONT]

Ich habe von Mirrorbrain auf Mirrorcache umgestellt: https://forums.opensuse.org/showthread.php/569863-Issues-downloading-stable-opensuse-repo?p=3128546#post3128546

Und das heißt jetzt was für mich?

Mach mal als root:


zypper clean -a && rpm --rebuilddb && zypper ref

Mach ich morgen, weil ich jetzt nicht mehr an meinem Arbeits-Laptop bin.

Irgendwann kam der Fehler nur noch für “libmariadbd19”, welches ich mir darauf manuell heruntergeladen und ins Zypper-Cache geschafft habe.
Dann lief “zypper up” ohne Fehler durch.

Probier es aus. Ich habe es auch ausprobiert und entdeckt, dass Mirrorcache stabiler ist.

https://en.opensuse.org/MirrorCache

Bei “zypper ref” gehts wieder los :frowning:

Laptop-0025:~ # zypper refRetrieving repository 'Firefox' metadata ............................................................................................................................[done]
Building repository 'Firefox' cache .................................................................................................................................[done]
Retrieving repository 'KDE:Extra' metadata -----------------------------------------------------------------------------------------------------------------------------\]
Warning: Digest verification failed for file '51401f628d1931d33eba31be840375b9205991e425b01ed53df09f76ac169dd2-primary.xml.gz'
[/var/tmp/AP_0xLkG3AC/repodata/51401f628d1931d33eba31be840375b9205991e425b01ed53df09f76ac169dd2-primary.xml.gz]


  expected 51401f628d1931d33eba31be840375b9205991e425b01ed53df09f76ac169dd2
  but got  2ec1540086b4b7710a301c69b84ae438d914966cda50b1849573f6b5404352a6


Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise.


However if you made certain that the file with checksum '2ec1..' is secure, correct
and should be used within this operation, enter the first 4 characters of the checksum
to unblock using this file on your own risk. Empty input will discard the file.


Unblock or discard? [2ec1/...? shows all options] (discard):

:frowning:

Ich hab mal alle Repos gelöscht und völlig neu hinzugefügt - mit “clean” und “ref” dazwischen natürlich.
Aber das Ergebnis blieb das Selbe - irgendein Repo (meist ist es KDE_Extra oder LibreOffice) meckert.

Jetzt alles auf mirrorcache-eu umgestellt - und es lief das “zypper ref” sauber durch und ein “zypper up” tut auch gerade :smiley:
Danke @karlmistelberger für den Tipp.

Laptop-0025:~ # zypper refRetrieving repository ‘Firefox’ metadata

Nur mal als Info:
Ich hatte eigentlich nur 1 Zeile gepostet, die man ausführen sollte und nicht jeden Befehl einzeln…

zypper clean -a && rpm --rebuilddb && zypper ref

&& bedeutet:
wenn vorausgegangener Befehl erfolgreich war, mit nächstem Befehl weitermachen.

https://wiki.ubuntuusers.de/Shell/Operatoren/

Sorry, aber ich weiß sehr wohl was das bedeutet und wenn ich die Befehle einzeln ausführe, dann macht das keinen Unterschied, wenn die vorherigen erfolgreich waren und das waren sie.
Sonst hätte ich nicht weitergemacht :wink:

Ich kann das aber aus den Ausgaben nicht nachvollziehen…

Vielen Dank für die Rückmeldung. Ich bin gerade nach Art der Zweitausender Jahre mit dem Internet verbunden. Bandbreite (Senden/Empfangen): [kbps/kbps]: 773 / 8.741

Anders als mit “download” klappt es mit “mirrorcache-eu” immer einwandfrei, z.B. heute Nachmittag:

  • openSUSE Tumbleweed 20220607-0 -> 20220608-0, 24 Pakete, Gesamtgröße des Downloads: 190,3 MiB.
  • Download: Consumed 27.215s CPU time.
  • Install: Consumed 1min 13.046s CPU time.

Das stimmt natürlich :frowning:
Die ersten beiden Teile liefen aber wirklich ohne Fehler, ohne irgendeine Meldung durch.

Gerne.
Bevor ich aber euphorisch werde, warte ich ein paar Tage ab :wink: