[Bug 1024392] New: Warnings about OSS Out of date
http://bugzilla.suse.com/show_bug.cgi?id=1024392 Bug ID: 1024392 Summary: Warnings about OSS Out of date Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers@forge.provo.novell.com Reporter: hkuehnemund@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- This is what I'm currently experiencing with Leap 42.2 running inside WSL: root@X230:/home/hkuehnemund# date Wed Feb 8 20:17:50 UTC 2017 root@X230:/home/hkuehnemund# zypper ref Repository 'NON-OSS' is up to date. Repository 'OSS' is up to date. Retrieving repository 'OSS Update' metadata ....................................................................................[done] Retrieving repository 'Update Non-Oss' metadata ................................................................................[done] All repositories have been refreshed. root@X230:/home/hkuehnemund# date Wed Feb 8 20:18:03 UTC 2017 root@X230:/home/hkuehnemund# zypper up Retrieving repository 'OSS Update' metadata ....................................................................................[done] Retrieving repository 'Update Non-Oss' metadata ................................................................................[done] Loading repository data... Warning: Repository 'OSS Update' appears to be outdated. Consider using a different mirror or server. Reading installed packages... Nothing to do. root@X230:/home/hkuehnemund# date Wed Feb 8 20:18:19 UTC 2017 root@X230:/home/hkuehnemund# How can zypper ref says that all is ok, when zypper up 20 seconds later gives a warning? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c2
--- Comment #2 from Marcus Meissner
http://bugzilla.suse.com/show_bug.cgi?id=1024392
Marcus Meissner
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c3
--- Comment #3 from Hannes Kühnemund
what is the url of the repository?
root@X230:/home/hkuehnemund# cat /etc/zypp/repos.d/oss-update.repo [oss-update] name=OSS Update enabled=1 autorefresh=1 baseurl=http://download.opensuse.org/update/42.2/ path=/ type=rpm-md keeppackages=0 root@X230:/home/hkuehnemund# -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c4
--- Comment #4 from Marcus Meissner
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c5
--- Comment #5 from Hannes Kühnemund
This is weird. is that the real download.opensuse.org server,
I do not know. Looking up de.opensuse.org/Paket_Repositorys there is a difference: #/etc/zypp/repos.d/oss-update.repo http://download.opensuse.org/update/42.2/ #https://de.opensuse.org/Paket_Repositorys http://download.opensuse.org/update/leap/42.2/oss/ Though: root@X230:/var/log# ls -la /etc/zypp/repos.d/oss-update.repo -rw-r--r-- 1 root root 137 Oct 12 07:51 /etc/zypp/repos.d/oss-update.repo So that hasn't changed recently.
can you also attach zypper.log ?
Sure. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c6
--- Comment #6 from Hannes Kühnemund
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c7
--- Comment #7 from Marcus Meissner
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c8
--- Comment #8 from Marcus Meissner
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c9
--- Comment #9 from Hannes Kühnemund
can youy check this directory if there are bad permission or mount flags or so?
root@X230:/var/cache/zypp# ls -la total 8 drwxr-xr-x 2 root root 0 Jan 5 10:24 . drwxr-xr-x 2 root root 0 Jan 16 09:12 .. drwxr-xr-x 2 root root 0 Feb 8 20:39 packages drwxr-xr-x 2 root root 0 Feb 9 07:38 raw drwxr-xr-x 2 root root 0 Jan 5 10:24 solv root@X230:/var/cache/zypp# cd raw root@X230:/var/cache/zypp/raw# ls -la total 12 drwxr-xr-x 2 root root 0 Feb 9 07:38 . drwxr-xr-x 2 root root 0 Jan 5 10:24 .. drwxr-xr-x 2 root root 0 Jan 5 10:23 non-oss drwxr-xr-x 2 root root 0 Jan 5 10:23 oss drwxr-xr-x 2 root root 0 Jan 5 10:23 oss-update drwxr-xr-x 2 root root 0 Jan 5 10:24 update-non-oss root@X230:/var/cache/zypp/raw# ls -la oss-update/ total 8 drwxr-xr-x 2 root root 0 Jan 5 10:23 . drwxr-xr-x 2 root root 0 Feb 9 07:38 .. drwxr-xr-x 2 root root 0 Jan 5 10:24 repodata lrwxrwxrwx 1 root root 6 Jan 5 10:23 .repo_gpgcheck -> ./true root@X230:/var/cache/zypp/raw# touch oss-update/testfile root@X230:/var/cache/zypp/raw# ls -la oss-update/testfile -rw-r--r-- 1 root root 0 Feb 9 07:54 oss-update/testfile root@X230:/var/cache/zypp/raw# rm oss-update/testfile root@X230:/var/cache/zypp/raw# touch ./test root@X230:/var/cache/zypp/raw# ls -la ./test -rw-r--r-- 1 root root 0 Feb 9 07:56 ./test root@X230:/var/cache/zypp/raw# rm ./test root@X230:/var/cache/zypp/raw# Is zypper using dbus by any chance? I'm encountering dbus related issues in this environment (see my email on the Linux mailing list). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c10
--- Comment #10 from Marcus Meissner
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c11
--- Comment #11 from Hannes Kühnemund
does "mv" work? is this partition full?
root@X230:/var/cache/zypp/raw# l non-oss/ oss/ oss-update/ update-non-oss/ root@X230:/var/cache/zypp/raw# touch /tmp/1 root@X230:/var/cache/zypp/raw# mv /tmp/1 . root@X230:/var/cache/zypp/raw# mv 1 oss-update/ root@X230:/var/cache/zypp/raw# ll oss-update/ total 8 drwxr-xr-x 2 root root 0 Feb 9 08:12 ./ drwxr-xr-x 2 root root 0 Feb 9 08:12 ../ -rw-r--r-- 1 root root 0 Feb 9 08:11 1 drwxr-xr-x 2 root root 0 Jan 5 10:24 repodata/ lrwxrwxrwx 1 root root 6 Jan 5 10:23 .repo_gpgcheck -> ./true root@X230:/var/cache/zypp/raw# df . Filesystem 1K-blocks Used Available Use% Mounted on rootfs 101813920 36788364 65025556 37% /
is it a weird fs?
Well, this is Leap 42.2 in WSL (see https://www.suse.com/communities/blog/make-windows-green-part-1/). Also, here is a pretty good explanation on how this works: https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subsystem-for-linux-... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c12
--- Comment #12 from Marcus Meissner
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c13
--- Comment #13 from Hannes Kühnemund
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c14
--- Comment #14 from Hannes Kühnemund
OK, here is the logfile. Before using zypper via strace it gave the warning. When running strace it didn't and now the warning disappeared. Maybe an issue with the repo afterall?
Nah, my mistake, 'ref' doesn't show the warning, 'up' does (and still does). Let me add the strace of "zypper update" too ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c15
--- Comment #15 from Hannes Kühnemund
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c16
Michael Andres
<suseinfo xmlns="http://linux.duke.edu/metadata/repo"> <expire>2592000</expire> </suseinfo>
This means the server promises to regenerate the meatdata index at least every 2592000 seconds. If the repo metadata we get are older, we suspect a lazy mirror. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c17
Marcus Meissner
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c18
Michael Andres
grep -A 1 exchange zypper.log -- 2017-01-05 10:24:08 <1> X230(6) [zypp] PathInfo.cc(exchange):737 exchange /var/cache/zypp/raw/update-non-ossLGDZMV <-> /var/cache/zypp/raw/update-non-oss 2017-01-05 10:24:08 <1> X230(6) [zypp] PathInfo.cc(recursive_rmdir):426 recursive_rmdir /var/cache/zypp/raw/update-non-ossLGDZMV -- 2017-01-09 11:27:37 <1> X230(7) [zypp] PathInfo.cc(exchange):730 exchange /var/cache/zypp/raw/oss-updateVyB0oH <-> /var/cache/zypp/raw/oss-update 2017-01-09 11:27:37 <2> X230(7) [zypp] PathInfo.cc(doLogResult):295 FAILED: (2)No such file or directory --
The log shows that exchanging directories -with or without more than 8 leading chars in common- worked last on 2017-01-05. Since 2017-01-09 all exchange calls fail. To me it looks like a corrupted filesystem. @Hannes: You can check /varlib/zypp/history to see which packages were added/removed in between. Maybe it reveals something. If you can, try to do a filesystem check and aferwards remove /var/cache/zypp completely. A 'zypper ref' will recreate the cache and we'll see whether it still suffers the same problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c19
Hannes Kühnemund
Since 2017-01-09 all exchange calls fail. To me it looks like a corrupted filesystem.
@Hannes: You can check /varlib/zypp/history to see which packages were added/removed in between. Maybe it reveals something.
/var/log/zypp/history shows: 2017-01-05 10:24:54|install|gpm|1.20.7-9.53| 2017-01-05 10:24:54|install|libglib-2_0-0 2017-01-05 10:24:55|install|libpython2_7-1_0|2.7.12-24.1 2017-01-05 10:24:55|install|libslang2|2.2.4-12.5 2017-01-05 10:24:56|install|libgmodule-2_0-0|2.48.2-1.10 2017-01-05 10:25:07|install|python-base and then 2017-01-05 10:25:08|install|mc|4.8.15-6.1 2017-01-09 11:47:17|install|libX11-data|1.6.3-7.1 2017-01-09 11:47:17|install|xbitmaps|1.1.1-13.2 2017-01-09 11:47:18|install|libICE6|1.0.9-4.4 2017-01-09 11:47:18|install|libXau6|1.0.8-7.4 2017-01-09 11:47:18|install|libdb-4_8|4.8.30-31.51 2017-01-09 11:47:18|install|libgdbm4|1.10-4.52 2017-01-09 11:47:19|install|libpng16-16|1.6.8-8.1 2017-01-09 11:47:19|install|luit|20141204-2.4 2017-01-09 11:47:19|install|ncurses-utils|5.9-54.48 2017-01-09 11:47:19|install|libSM6|1.2.2-6.3 2017-01-09 11:47:19|install|libxcb1|1.11.1-2.25 2017-01-09 11:47:25|install|perl|5.18.2-5.6 2017-01-09 11:47:25|install|libfreetype6
If you can, try to do a filesystem check and aferwards remove /var/cache/zypp completely. A 'zypper ref' will recreate the cache and we'll see whether it still suffers the same problem.
Yepp, that definitely helped - no more errors. I'm wondering if zypper could surface such information via message on the command line. Sth like that (in [] brackets] root@X230:/home/hkuehnemund# zypper up Retrieving repository 'OSS Update' metadata .....................[done] Retrieving repository 'Update Non-Oss' metadata .................[done] Loading repository data... Warning: Repository 'OSS Update' appears to be outdated. Consider using a different mirror or server. [You might want to delete /var/cache/zypp entirely and try again] Reading installed packages... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c20
Michael Andres
http://bugzilla.suse.com/show_bug.cgi?id=1024392
http://bugzilla.suse.com/show_bug.cgi?id=1024392#c21
Tomáš Chvátal
participants (1)
-
bugzilla_noreply@novell.com