Hi,
On one of my VMs, running a server installation of Leap 15.3, I always get the following error:
# zypper ref repo-backports-update Repository 'Update repository of openSUSE Backports' is up to date. Building repository 'Update repository of openSUSE Backports' cache ..............................[error] Error building the cache: [|] Failed to cache repo (137). History: -
Skipping repository 'Update repository of openSUSE Backports' because of the above error. Could not refresh the repositories because of errors.
I don't understand what the underlying problem is.
This repository is the only one that's affected, the other 5 standard repositories have their caches built without issue. I also have several other VMs with a similar configuration, but none of them exhibit this error.
Neither "zypper clean" nor "rm -rf /var/cache/zypp/" helps.
Some more details:
# rpm -qf /etc/zypp/repos.d/repo-backports-update.repo openSUSE-release-15.3-lp1532.157.1.x86_64 # rpm -V zypper libzypp openSUSE-release S.5....T. c /etc/YaST2/control.xml
Here's the strace output of the failing command:
https://paste.opensuse.org/14766400
I would very much appreciate if someone with knowledge of how zypper works could take a look and explain what's going on. Maybe also describe what error code 137 is about?
Thanks, Olav
Hi Olav,
Am 20.11.21 um 11:42 schrieb Olav Reinert
Here's the strace output of the failing command:
https://paste.opensuse.org/14766400I would very much appreciate if someone with knowledge of how zypper works could take a look and explain what's going on. Maybe also describe what error code 137 is about?
Could you send me your zypper.log file ? The strace output does not help much. Alternatively you can also create a bug on https://bugzilla.suse.com/enter_bug.cgi?product=openSUSE%20Distribution.
You get the log from /var/log/zypper.log or if you have zypper-log installed you can get the log for a specific run via: zypper log <PID>
omitting the PID argument will list all zypper runs that are currently in the logfile.
Thanks,
Benjamin
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Content-ID: 7fab33cd-aede-fc35-6057-19d56558e9e9@Legolas.valinor
El 2021-11-23 a las 11:19 +0100, Benjamin Zeller escribió:
Hi Olav,
Am 20.11.21 um 11:42 schrieb Olav Reinert
You get the log from /var/log/zypper.log or if you have zypper-log installed you can get the log for a specific run via: zypper log <PID>
omitting the PID argument will list all zypper runs that are currently in the logfile.
Wow, thank you, that's a very interesting command to know :-)
- -- Cheers Carlos E. R.
(from openSUSE 15.2 (Legolas))
On Tue, 2021-11-23 at 11:19 +0100, Benjamin Zeller wrote:
Hi Olav,
Am 20.11.21 um 11:42 schrieb Olav Reinert
Here's the strace output of the failing command:
https://paste.opensuse.org/14766400I would very much appreciate if someone with knowledge of how zypper works could take a look and explain what's going on. Maybe also describe what error code 137 is about?
Could you send me your zypper.log file ? The strace output does not help much. Alternatively you can also create a bug on https://bugzilla.suse.com/enter_bug.cgi?product=openSUSE%20Distribution.
Thank you for following up on this.
I have created a bug report, and provided the requested zypper log as an attachment to it:
https://bugzilla.opensuse.org/show_bug.cgi?id=1193007
\Olav
-
Benjamin Zeller -
Carlos E. R. -
Olav Reinert