[Bug 1190008] New: Failure of replacing filesystem package version 15.5-40.1 by 84.87-2.1
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 Bug ID: 1190008 Summary: Failure of replacing filesystem package version 15.5-40.1 by 84.87-2.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: Markus.Elfring@web.de QA Contact: jsrain@suse.com Found By: --- Blocker: --- I came along the need to try a software repair out again by the means of the image ���openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20210829-Media.iso���. Unfortunately, I stumbled on the following YaST2 message after the installation of some packages. Subprocess failed. Error: RPM failed: error: lua script failed: [string "%prein(filesystem-84.87-2.1.x86_64)"]:15: No such file or directory error: filesystem-84.87-2.1.x86_64: install failed error: filesystem-15.5-40.1.x86_64: erase skipped Will the chances grow to fix remaining open issues in such a system configuration area? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 Markus Elfring <Markus.Elfring@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1029961 Severity|Normal |Major -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c3 Markus Elfring <Markus.Elfring@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Markus.Elfring@we | |b.de) | --- Comment #3 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #2)
Can you reproduce the issue?
Theoretically, yes. But I got the impression that the debug log storage requirements trigger also undesirable software run time characteristics here. How will your chances evolve to improve the affected software by any other means as it seems that mentioned (and known) changes trigger some unwanted technical difficulties? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c4 --- Comment #4 from Ludwig Nussel <lnussel@suse.com> --- Not sure what you mean? The known problems with usrmerge are listed here: https://en.opensuse.org/openSUSE:Usr_merge#State_in_openSUSE Without logs I can't figure out whether you hit an existing or a new issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c5 --- Comment #5 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #4)
The known problems with usrmerge are listed here: https://en.opensuse.org/openSUSE:Usr_merge#State_in_openSUSE
Would you like to fix any typos in this document?
Without logs I can't figure out whether you hit an existing or a new issue.
I imagine that other approaches can eventually be also considered for desirable solutions besides sharing the complete debug log data from the beginning of another Linux software distribution installation attempt. I would find it nicer if the clarification can be concentrated more on the remaining open issues for the mentioned components (without questionable run time characteristics). Can you eventually check any other test systems which contain still the software package ���filesystem 15.5-40.1��� (as it was working under ���special circumstances��� for a while)? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c6 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #6 from Ludwig Nussel <lnussel@suse.com> --- (In reply to Markus Elfring from comment #5)
(In reply to Ludwig Nussel from comment #4)
The known problems with usrmerge are listed here: https://en.opensuse.org/openSUSE:Usr_merge#State_in_openSUSE
Would you like to fix any typos in this document?
It's a wiki, go ahead.
Without logs I can't figure out whether you hit an existing or a new issue.
I imagine that other approaches can eventually be also considered for desirable solutions besides sharing the complete debug log data from the beginning of another Linux software distribution installation attempt. I would find it nicer if the clarification can be concentrated more on the remaining open issues for the mentioned components (without questionable run time characteristics).
Can you eventually check any other test systems which contain still the software package ���filesystem 15.5-40.1��� (as it was working under ���special circumstances��� for a while)?
All my test systems work fine. I need to know what's different in your setup to be able to debug. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c7 Markus Elfring <Markus.Elfring@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME |--- --- Comment #7 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #6)
All my test systems work fine.
It seems that a corresponding test can need another adjustment.
I need to know what's different in your setup to be able to debug.
* Can we work a bit more with the information that the software component ���convertfs��� would be involved here? * Can the error reporting be improved only for the affected function calls? * How are chances to reduce the generated debug data? * Are any log parts eventually be reusable from attachments according to previous bug reports? Execution failure for ���grub2-editenv��� (from snapshot 20210615?) https://bugzilla.opensuse.org/attachment.cgi?id=850381 YaST2 crashes when analyzing fstab files of systems to upgrade with no entries https://bugzilla.opensuse.org/attachment.cgi?id=850102 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c8 --- Comment #8 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #4)
Without logs I can't figure out ���
How do you think about possibilities to reproduce the reported error situation by the means of virtual machines (or container software)? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c10 Markus Elfring <Markus.Elfring@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Markus.Elfring@we | |b.de) | --- Comment #10 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Fabian Vogt from comment #9)
For analysis, it's necessary to have the logs for the particular failure.
I suggest to consider additional options for the desired error analysis. Will another code review trigger any more helpful insights? https://build.opensuse.org/package/view_file/openSUSE:Factory/filesystem/fil...
"try a software repair out" isn't one of the common tasks.
How relevant is it that fixing software can be a common task (or not)?
Did you boot the live CD and used it to "upgrade" an existing system,
Yes.
or install a new one on top?
Not for the reported situation.
In any case, the needed log files can be collected by running "save_y2logs" after the error message appeared.
Can the corresponding storage requirements look a bit special from the discussed Live system? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c12 Markus Elfring <Markus.Elfring@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Markus.Elfring@we | |b.de) | --- Comment #12 from Markus Elfring <Markus.Elfring@web.de> --- Created attachment 852535 --> http://bugzilla.opensuse.org/attachment.cgi?id=852535&action=edit error logs as background information for another questionable software upgrade attempt (In reply to Fabian Vogt from comment #11)
Without those logs there will likely not be any progress, I'm afraid.
I hope that this view can eventually be adjusted. I tried the software repair out again by the means of the image ���openSUSE-Tumbleweed-NET-x86_64-Snapshot20210913-Media.iso���. Unfortunately, I stumbled on YaST2 error messages once more after the installation of some packages.
A similar setup is tested by openQA, but using 42.3, 15.0 and 15.2, which also run through usrmerge migration. Those all work fine.
Will the software test approaches be accordingly extended for openSUSE Tumbleweed systems (besides my experience reports)? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c13 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(Markus.Elfring@we | |b.de) --- Comment #13 from Ludwig Nussel <lnussel@suse.com> --- Could it be that the system suffers from a half done usrmerge? So the error message is probably due to a failure to run /bin/bash in the target system. The setup is quite complex with lvm and multiple volumes so I suppose you can't just use the rescue image to mount your volumes? If that's the case you could start the upgrade like you did indeed. When the error appears switch to a text console with shell or press ctrl-alt-shift-x to get an xterm. In that shell look at /mnt. That should have your system and "chroot /mnt" should work. I guess it doesn't. So there's probably either /lib64/ld-linux.so.2 or /bin/bash missing. Could be that /bin or /lib64 are still directories or the symlinks are missing. Either way try to fix the situation with symlinks. Once you got chroot working, go again go back to yast and retry. If that's not the issue I'd be interested in ls -al /mnt, rpm -Va --root /mnt -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c14 --- Comment #14 from Ludwig Nussel <lnussel@suse.com> --- if chroot works, you may also try to run /usr/libexec/convertfs in the chroot manually -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c15 Markus Elfring <Markus.Elfring@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Markus.Elfring@we | |b.de) | --- Comment #15 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #13)
Could it be that the system suffers from a half done usrmerge?
It seems so after the questionable software updates were published.
The setup is quite complex with lvm and multiple volumes so I suppose you can't just use the rescue image to mount your volumes?
I can mount all available partitions (on demand) with various (Live) systems here. (In reply to Ludwig Nussel from comment #14)
if chroot works,
I am too unsure about this approach.
you may also try to run /usr/libexec/convertfs in the chroot manually
Will any software package fix the mess (file system inconsistencies) automatically? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c16 --- Comment #16 from Ludwig Nussel <lnussel@suse.com> --- if convertfs succeeds your system should be back operational and zypper dup can proceed. That will then fix the inconsistencies, yes. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c17 --- Comment #17 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #16)
if convertfs succeeds your system should be back operational and zypper dup can proceed. That will then fix the inconsistencies, yes.
Would you point any more specific commands out which might help to determine if the chroot approach can ever work after broken file system dependencies? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c18 --- Comment #18 from Ludwig Nussel <lnussel@suse.com> --- see comment#13 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c19 --- Comment #19 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #13)
That should have your system and "chroot /mnt" should work.
I took another look by the means of the image ���openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20210914-Media.iso���. linux@bw-wst021:~> sudo chroot /mnt ��� chroot: failed to run command ���/bin/bash���: No such file or directory
Either way try to fix the situation with symlinks.
* Would you like to influence the questionable situation any more by improved software repair scripts? * Do any of the mentioned conversion tools need special system dependencies?
If that's not the issue I'd be interested in ls -al /mnt, rpm -Va --root /mnt
linux@bw-wst021:~> ls -al /mnt && rpm -Va --root /mnt total 4 dr-xr-xr-x 2 root root 4096 Sep 15 10:34 . drwxr-xr-x 1 root root 160 Sep 17 10:16 .. error: cannot open Packages database in /mnt/usr/lib/sysimage/rpm -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c20 --- Comment #20 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #13)
When the error appears ��� press ctrl-alt-shift-x to get an xterm.
Subprocess failed. Error: RPM failed: error: lua script failed: [string "%prein(filesystem-84.87-2.1.x86_64)"]:15: No such file or directory error: filesystem-84.87-2.1.x86_64: install failed error: filesystem-15.5-40.1.x86_64: erase skipped bw-wst021:/home/linux # ls -al /mnt total 120 drwxr-xr-x 26 root root 4096 Sep 17 10:43 . drwxr-xr-x 1 root root 180 Sep 17 10:16 .. drwxr-xr-x 2 root root 4096 Feb 20 2021 B dr-xr-xr-x 6 root root 4096 May 20 18:30 bin dr-xr-xr-x 8 root root 4096 May 25 07:49 boot drwx------ 2 107 107 4096 Feb 7 2021 .cache drwx------ 2 systemd-resolve systemd-resolve 4096 Nov 26 2020 .config drwxr-xr-x 20 root root 4440 Sep 17 12:06 dev drwxr-xr-x 184 root root 12288 Sep 17 10:35 etc drwxr-xr-x 2 systemd-resolve systemd-resolve 4096 Nov 26 2020 .fonts dr-xr-xr-x 5 root root 4096 Sep 14 10:52 home -rw-r--r-- 1 systemd-resolve systemd-resolve 599 Oct 22 2020 .i18n dr-xr-xr-x 7 root root 4096 May 20 18:30 lib dr-xr-xr-x 5 root root 4096 Jun 2 08:54 lib64 drwx------ 2 systemd-resolve systemd-resolve 4096 Nov 26 2020 .local drwx------ 2 root root 16384 Feb 4 2021 lost+found dr-xr-xr-x 2 root root 4096 May 20 18:30 mnt dr-xr-xr-x 6 root root 4096 Sep 14 15:26 opt dr-xr-xr-x 509 root root 0 Sep 17 10:35 proc drwx------ 13 root root 4096 Jun 2 09:00 root drwxr-xr-x 35 root root 980 Sep 17 10:34 run dr-xr-xr-x 6 root root 12288 Jun 2 08:54 sbin dr-xr-xr-x 6 root root 4096 May 20 18:30 srv dr-xr-xr-x 13 root root 0 Sep 17 10:45 sys drwxrwxrwt 4 root root 4096 Feb 20 2021 tmp drwxr-xr-x 14 root root 4096 Jun 2 08:54 usr drwxr-xr-x 15 root root 4096 Sep 15 14:18 var -rw-r--r-- 1 systemd-resolve systemd-resolve 1951 Oct 22 2020 .xim.template
If that's not the issue I'd be interested in ls -al /mnt, rpm -Va --root /mnt
bw-wst021:/home/linux # rpm -Va --root /mnt .M....... /usr/bin/readcd error: failed to exec scriptlet interpreter /bin/sh: No such file or directory error: %verify(readcd-3.02~a10-40.1.x86_64) scriptlet failed, exit status 127 missing /var/spool/atjobs missing /var/spool/atjobs/.SEQ missing /var/spool/atspool error: failed to exec scriptlet interpreter /bin/sh: No such file or directory error: %verify(at-3.2.1-1.5.x86_64) scriptlet failed, exit status 127 .M....... /var/lib/AccountsService/icons missing /var/log/krb5 missing /var/lib/lifecycle missing /var/lib/dpkg/methods missing /var/lib/dpkg/methods/disk missing /var/lib/dpkg/methods/ftp missing /var/lib/dpkg/methods/mnt missing /var/lib/dpkg/methods/multicd Unsatisfied dependencies for incidenceeditor-lang-21.04.1-1.2.noarch: incidenceeditor = 21.04.1 is needed by (installed) incidenceeditor-lang-21.04.1-1.2.noarch ��� How do you think about to limit the verification to selected software packages? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c21 --- Comment #21 from Ludwig Nussel <lnussel@suse.com> --- The usrmerge there is not complete. Unclear why. Usually means the linker and/or glibc are moved to /usr and deleted from /lib64 before replacing /lib64 with a link: https://en.opensuse.org/openSUSE:Usr_merge#In_the_middle_of_the_upgrade.2C_n... You can try "ln -s /usr/lib64/ld-linux-x86-64.so.2 /mnt/lib64/ld-linux-x86-64.so.2" then call convertfs. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c22 --- Comment #22 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #21)
The usrmerge there is not complete. Unclear why.
Will any more clarity be achieved for this issue?
You can try "ln -s /usr/lib64/ld-linux-x86-64.so.2 /mnt/lib64/ld-linux-x86-64.so.2" then call convertfs.
Should such a symbolic link eventually be automatically performed for the discussed file system conversion? Do any more software dependencies matter here? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c23 --- Comment #23 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #21) I tried the suggested adjustment out by the means of the image ���openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20210916-Media.iso���. bw-wst021:/home/linux # ln -s /usr/lib64/ld-linux-x86-64.so.2 /mnt/lib64/ld-linux-x86-64.so.2 bw-wst021:/home/linux # ls -l /usr/lib64/ld-linux-x86-64.so.2 /mnt/lib64/ld-linux-x86-64.so.2 lrwxrwxrwx 1 root root 31 Sep 20 11:54 /mnt/lib64/ld-linux-x86-64.so.2 -> /usr/lib64/ld-linux-x86-64.so.2 lrwxrwxrwx 1 root root 10 Jun 20 18:52 /usr/lib64/ld-linux-x86-64.so.2 -> ld-2.33.so Where are the required file system conversion tools stored so far? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c24 --- Comment #24 from Ludwig Nussel <lnussel@suse.com> --- chroot /mnt /usr/libexec/convertfs -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c25 --- Comment #25 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #24)
chroot /mnt /usr/libexec/convertfs
Should I know anything more about this file system conversion tool? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c26 --- Comment #26 from Ludwig Nussel <lnussel@suse.com> --- It's a shell script, just look into it if you are interested :) What the script does is also documented: https://en.opensuse.org/openSUSE:Usr_merge#How_the_conversion_works_technica... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c27 --- Comment #27 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #24)
chroot /mnt /usr/libexec/convertfs
The execution succeeded for this shell script a moment ago. But I am still looking for further solution approaches according to the following information from a YaST2 error message for my software distribution upgrade attempt. Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /var/mail: cpio: File from package already exists as a directory in system error: filesystem-84.87-2.1.x86_64: install failed error: filesystem-15.5-40.1.x86_64: erase skipped -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c28 --- Comment #28 from Ludwig Nussel <lnussel@suse.com> --- /var/mail is not something usrmerge touches. Maybe move it away. If "chroot /mnt" works now in the rescue system the upgrade should be able to proceed from a usrmerge perspective. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c29 --- Comment #29 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #28)
/var/mail is not something usrmerge touches.
Should this software area be accordingly adjusted by the published package updates?
Maybe move it away.
Why?
If "chroot /mnt" works now in the rescue system
It seems that this command did not complain for the convertfs script execution.
the upgrade should be able to proceed from a usrmerge perspective.
I have got another opposite impression a moment ago. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c30 --- Comment #30 from Ludwig Nussel <lnussel@suse.com> --- /var/mail has been a link for 20 years already. If it's a directory in your system it's probably a local modification you have there. That's unrelated to usrmerge. Rename the directory /var/mail to something else so the filesystem package installation can add it as symlink again. Anyway does your system work again now? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c31 --- Comment #31 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #30)
/var/mail has been a link for 20 years already. If it's a directory in your system it's probably a local modification you have there.
Are there any differences to consider between software distributions for the E-Mail configuration? https://help.ubuntu.com/lts/installation-guide/armhf/ch08s05.html
Anyway does your system work again now?
Partly. * I noticed by boot messages that start attempts failed for an authorization manager. * I can login into a graphical user session (in principle). Unfortunately, internet access was broken there. It seems that the desired software update is still incomplete for the questionable openSUSE Tumbleweed instance at the moment. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c32 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(Markus.Elfring@we | |b.de) --- Comment #32 from Ludwig Nussel <lnussel@suse.com> --- (In reply to Markus Elfring from comment #31)
(In reply to Ludwig Nussel from comment #30)
/var/mail has been a link for 20 years already. If it's a directory in your system it's probably a local modification you have there.
Are there any differences to consider between software distributions for the E-Mail configuration? https://help.ubuntu.com/lts/installation-guide/armhf/ch08s05.html
Not sure why you are phrasing that as question. Are you saying you did replace /var/mail with a directory following the article? If so I'd tell you don't do that :-) Mail is kept in /var/spool/mail and /var/mail is a link so you can access mail via both paths.
* I noticed by boot messages that start attempts failed for an authorization manager. * I can login into a graphical user session (in principle). Unfortunately, internet access was broken there.
It seems that the desired software update is still incomplete for the questionable openSUSE Tumbleweed instance at the moment.
Different issues, maybe for different bug reports. I'm still interested how you originally got into the broken state. Did you run zypper dup and then it was broken and then you used the live image or what happened exactly? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c33 Markus Elfring <Markus.Elfring@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Markus.Elfring@we | |b.de) | --- Comment #33 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #32)
Are you saying you did replace /var/mail with a directory following the article?
It depends on the views. I performed also another Ubuntu 21.04 installation on 2021-09-14.
Mail is kept in /var/spool/mail and /var/mail is a link so you can access mail via both paths.
I have picked this idea up here.
Different issues, maybe for different bug reports.
I am curious how corresponding development views will evolve further.
I'm still interested how you originally got into the broken state. Did you run zypper dup and then it was broken
A software distribution upgrade damaged a working system.
and then you used the live image or what happened exactly?
I was occasionally using Live systems for my needs for a while. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c34 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(Markus.Elfring@we | |b.de) --- Comment #34 from Ludwig Nussel <lnussel@suse.com> --- please attach /var/log/zypp/history -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c35 Markus Elfring <Markus.Elfring@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Markus.Elfring@we | |b.de) | --- Comment #35 from Markus Elfring <Markus.Elfring@web.de> --- Created attachment 852670 --> http://bugzilla.opensuse.org/attachment.cgi?id=852670&action=edit /var/log/zypp/history from 2021-09-20 (In reply to Ludwig Nussel from comment #34) Does this log file point any remaining open issues out? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c36 --- Comment #36 from Ludwig Nussel <lnussel@suse.com> --- Unfortuantely not. The log is not complete. It starts at "2021-09-15 14:21:20" but the system was already broken at that point. I need the entries from the start. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c37 --- Comment #37 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #36)
I need the entries from the start.
These log records are not available any more here. I assume that the software update attempt according to the ���snapshot 20210829��� triggered this. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c38 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #38 from Ludwig Nussel <lnussel@suse.com> --- Ok so we won't find out how this happened then. At least the system seems to work again. Closing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c39 Markus Elfring <Markus.Elfring@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #39 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #38)
Ok so we won't find out how this happened then.
I wonder about such a feedback. The search for possible solutions is challenging as usual.
At least the system seems to work again.
The mentioned openSUSE Tumbleweed instance can still not be updated (or upgraded) by the installation tool (or package) version from current Live images as expected. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c40 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #40 from Ludwig Nussel <lnussel@suse.com> --- Please understand that Bugzilla is not a support forum but a bug tracking tool. There is probably a bug that broke your system but since the log is truncated the information to figure out what happened is missing. The /var/mail directory is not something any official package creates. IMO remove that, disable all extra repos and get zypper dup to work. You really have to help yourself from here. Maybe the mailinglists or forums can provide more guidance. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c41 Markus Elfring <Markus.Elfring@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #41 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #40)
Please understand that Bugzilla is not a support forum but a bug tracking tool.
I would like to get remaining open issues fixed somehow.
There is probably a bug that broke your system but since the log is truncated the information to figure out what happened is missing. The /var/mail directory is not something any official package creates.
It seems that this detail can occasionally look a bit different (if you might take also views into account which would be related to Debian / Ubuntu settings).
You really have to help yourself from here. Maybe the mailing lists or forums can provide more guidance.
I hope then that other developers, system administrators or supporters can increase the desire to improve the questionable situation in significant ways. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c42 --- Comment #42 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #40)
There is probably a bug that broke your system
Various factors influenced this event as usual.
but since the log is truncated
Do installation tools from openSUSE Live system versions overwrite the file ���/var/log/zypp/history��� during software update/upgrade attempts?
the information to figure out what happened is missing.
I suggest to reconsider such a view once more. * Can the initial error situation be restored (or reproduced) by any other means? * How do you think about to work with the currently questionable software status in more constructive ways? + Can the installation tool be executed by an other running Linux system instead of using the version from the openSUSE Tumbleweed Live system? + Is there a need to configure another ���special chroot environment��� with desirable settings so that the error messages which are reported by installation commands here so far can be better clarified (according to the software package ���filesystem 84.87-2.1���? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c43 --- Comment #43 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #24)
chroot /mnt /usr/libexec/convertfs
A few symbolic links were configured. Now I would like to activate another chroot environment for my needs. But I stumbled on the following information. markus-elfring@bw-wst-linux1:~/root-Alternative$ ls -l $(find . -maxdepth 1 -type l) && LANG=C ls -l -d -L * lrwxrwxrwx 1 root root 7 Aug 3 22:50 ./bin -> usr/bin ��� ls: cannot access 'bin': No such file or directory ��� Should the link targets be reconsidered any further? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c44 --- Comment #44 from Markus Elfring <Markus.Elfring@web.de> --- I took another look also by the means of the image ���openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20210926-Media.iso���. bw-wst021:/mnt # ls -l $(find . -maxdepth 1 -type l) && du -h -s usr lrwxrwxrwx 1 root root 7 Sep 18 12:23 ./bin -> usr/bin lrwxrwxrwx 1 root root 7 Sep 18 12:23 ./lib -> usr/lib lrwxrwxrwx 1 root root 9 Sep 18 12:23 ./lib64 -> usr/lib64 lrwxrwxrwx 1 root root 8 Sep 18 12:23 ./sbin -> usr/sbin 50G usr Would you like to share any more helpful system configuration ideas for this issue? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c45 --- Comment #45 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to comment #43)
Should the link targets be reconsidered any further?
Unfortunately, I overlooked to mount also my LVM partitions for the selected chroot environment yesterday. I adjusted this setting then. Now I am looking for further advices according to the following information. markus-elfring@bw-wst-linux1:~/root-Alternative$ sudo chroot ${chr} bw-wst-linux1:/ # zypper info zypper ��� Problem retrieving files from 'Haupt-Repository (OSS)'. Download (curl) error for 'http://download.opensuse.org/tumbleweed/repo/oss/repodata/repomd.xml': Error code: Connection failed Error message: Could not resolve host: download.opensuse.org Please see the above error message for a hint. Warning: Skipping repository 'Haupt-Repository (OSS)' because of the above error. ��� Information for package zypper: ��� Version : 1.14.44-1.1 ��� One of my internet browsers could successfully retrieve the referenced XML files from within an Ubuntu 21.04 session. How will remaining open issues become resolvable? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c46 --- Comment #46 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to comment #42)
+ Is there a need to configure another ���special chroot environment��� with desirable settings so that the error messages which are reported by installation commands here so far can be better clarified ���?
markus-elfring@bw-wst-linux1:~/root-Alternative$ sudo chroot ${chr} bw-wst-linux1:/ # zypper update filesystem ��� Some of the repositories have not been refreshed because of an error. Loading repository data... Reading installed packages... Resolving package dependencies... The following package is going to be upgraded: filesystem 1 package to upgrade. Overall download size: 0 B. Already cached: 66.5 KiB. After the operation, additional 31.0 B will be used. Continue? [y/n/v/...? shows all options] (y): In cache filesystem-84.87-2.2.x86_64.rpm (1/1), 66.5 KiB ( 584 B unpacked) Checking for file conflicts: ..........................................................................................................................................................[done] (1/1) Installing: filesystem-84.87-2.2.x86_64 ........................................................................................................................................[error] Installation of filesystem-84.87-2.2.x86_64 failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /var/spool/mail: cpio: lstat failed - Invalid argument error: filesystem-84.87-2.2.x86_64: install failed error: filesystem-15.5-40.1.x86_64: erase skipped Abort, retry, ignore? [a/r/i] (a): 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. Would you like to contribute further solution ideas accordingly? https://forums.opensuse.org/showthread.php/555033-Fixing-software-package-up... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c47 --- Comment #47 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #30)
/var/mail has been a link for 20 years already. If it's a directory in your system it's probably a local modification you have there.
bw-wst021:/ # ls -l /var/spool/mail lrwxrwxrwx 1 root root 7 Sep 14 11:44 /var/spool/mail -> ../mail
That's unrelated to usrmerge. Rename the directory /var/mail to something else
I have tried this suggestion out in a configured chroot environment a moment ago. bw-wst021:/ # mv /var/spool/mail /var/spool/mail-20210914 bw-wst021:/ # zypper update filesystem ��� Loading repository data... Reading installed packages... Resolving package dependencies... The following package is going to be upgraded: filesystem 1 package to upgrade. Overall download size: 0 B. Already cached: 66.5 KiB. After the operation, additional 31.0 B will be used. Continue? [y/n/v/...? shows all options] (y): In cache filesystem-84.87-2.2.x86_64.rpm (1/1), 66.5 KiB ( 584 B unpacked) Checking for file conflicts: ..........................................................................................................................................................[done] (1/1) Installing: filesystem-84.87-2.2.x86_64 .........................................................................................................................................[done]
so the filesystem package installation can add it as symlink again.
bw-wst021:/ # ls -l /var/spool/mail total 0 Will this system configuration detail trigger any further adjustments? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c48 --- Comment #48 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Ludwig Nussel from comment #30)
Anyway does your system work again now?
Mostly, yes. Today a lot of software updates succeeded as expected finally. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190008 http://bugzilla.opensuse.org/show_bug.cgi?id=1190008#c49 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #49 from Ludwig Nussel <lnussel@suse.com> --- closing as fixed then -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com