[Bug 905863] New: lsinitrd - cat: write error: Broken pipe
http://bugzilla.opensuse.org/show_bug.cgi?id=905863 Bug ID: 905863 Summary: lsinitrd - cat: write error: Broken pipe Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: per@computer.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I noticed this error message when I did an "lsinitrd" on the initrd generated by a fresh 13.2 installation. The initrd can be found here: http://files.jessen.ch/office13-initrd-3.16.6-2-desktop (too big to attach directly) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905863 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com, | |sfalken@opensuse.org Assignee|bnc-team-screening@forge.pr |trenn@suse.com |ovo.novell.com | --- Comment #1 from Bernhard Wiedemann <bwiedemann@suse.com> --- I can not reproduce the error here, even with your initrd. Did you pipe the lsinitrd output somewhere (e.g. less or head)? Can you still reproduce the problem? IMHO it might not be a bad one anyway because "Broken pipe" only means that someone is writing but the output file-descriptor was already closed on the other end. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905863 --- Comment #2 from Per Jessen <per@computer.org> --- (In reply to Bernhard Wiedemann from comment #1)
I can not reproduce the error here, even with your initrd.
Did you pipe the lsinitrd output somewhere (e.g. less or head)?
No, just output to the console.
Can you still reproduce the problem?
I'm just reinstalling that system, I'll try it again later.
IMHO it might not be a bad one anyway because "Broken pipe" only means that someone is writing but the output file-descriptor was already closed on the other end.
Yeah, lsinitrd seems to work fine, it just looked odd to me. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905863 --- Comment #3 from Per Jessen <per@computer.org> --- (In reply to Per Jessen from comment #2)
Can you still reproduce the problem?
I'm just reinstalling that system, I'll try it again later.
Just now tried on a different 13.2 system, same message. with working dir = /boot, I run "lsinitrd initrd-3.16.6-2-desktop". lsinitrd is from dracut-037-17.6.1 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905863 Bjørn Lie <zaitor@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zaitor@opensuse.org --- Comment #4 from Bjørn Lie <zaitor@opensuse.org> --- Per: Are you by any chance using a scandinavian locale? I can reproduce too. I've been toying around in VM's trying different installoptions in order to hunt down an other bug ( https://bugzilla.opensuse.org/show_bug.cgi?id=890115 ) And in a minimal serverinstall, where I've not set regional data for root (under advanced in yast language) to yes, but kept the default just ctype I can not reproduce the error. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905863 --- Comment #5 from Per Jessen <per@computer.org> --- (In reply to Bjørn Lie from comment #4)
Per:
Are you by any chance using a scandinavian locale?
Hej Bjørn, haha, not a bad guess, but no, we're using en_GB.utf8. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905863 --- Comment #7 from Per Jessen <per@computer.org> --- I've got two systems being tested - 1) office12 - this is where the problem can be seen. It's running 13.2, but not current with updates. Running "lsinitrd <initrd>" produces this: Image: <name of imagefile> ================================= cat: write error: Broken pipe (the rest is fine). Oddly, I only see the problem when I'm on a physical console. When logged in via ssh, there is no problem. lsinitrd is from dracut-037-17.6.1.x86_64. 2) office31 - 13.2 current with updates. The issue cannot be reproduced here. lsinitrd is from dracut-037-17.9.1. The main difference between the two - office12 has root on NFS, office31 has local disk. I guess it would make sense to update office12 - if the problem disappears, fine - if not, we can continue? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905863 --- Comment #9 from Per Jessen <per@computer.org> --- (In reply to Julian Wolf from comment #8)
Yes, please, if it is possible update your system and let's see whether this still happens.
Okay, system was upgraded with all the latest updates. I now still see the "broken pipe" when I run "lsinitrd" - a) in a konsole window or b) on a virtual console. When logged in via ssh, I see no "broken pipe".
If that still happens after the update you could run lsinitrd with debugging options and provide the ouput so that we at least see at which point that happens:
bash -x lsinitrd $image
I'll attach the output in a minute. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905863 Per Jessen <per@computer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(per@computer.org) | --- Comment #10 from Per Jessen <per@computer.org> --- Created attachment 619968 --> http://bugzilla.opensuse.org/attachment.cgi?id=619968&action=edit bash -x lsinitrd $image -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905863 --- Comment #11 from Julian Wolf <juwolf@suse.com> --- Thank you for that. The problem in this case appears when extracting the early-microcode in the list_files() function: cat -- testinitrd | cpio --extract --verbose --quiet --list I assume cpio exits after reading the early-microcode (as the rest of the file is a xz archive) which then causes SIGPIPE to be delivered to cat. That's also exactly what I see when checking the exit-code of cat after running above command:
cat -- testinitrd | cpio --extract --verbose --quiet --list [...] echo ${PIPESTATUS[0]} ${PIPESTATUS[1]} 141 0
Exit code 141 (>128) is, afaik, pointing to 128 + Signal-Number, which gives in this case "13 SIGPIPE". Same exit code when running cat and killing it with SIGPIPE manually. So, in my opinion, SIGPIPE is absolutely okay here and the point is more about why the shell (bash?) does report that for you (when running it on a console). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905863 Giacomo Comes <comes@naic.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |comes@naic.edu --- Comment #12 from Giacomo Comes <comes@naic.edu> --- I'm having the same problem with lsinitrd. Here is what I have found so far. running: lsinitrd /boot/initrd >/dev/null gives this error message: cat: write error: Broken pipe this happens if: 1) you run the command on a console (ctrl alt F1-F6, tty is /dev/tty<n>) if you run the command in a terminal (xterm, konsole, etc, where tty is /dev/pts/<n>) then there is no error message AND 2) gnome-keyring-pam is installed. If gnome-keyring-pam is not installed then again there is no error message. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905863 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com