Re: "plumbing" problem during weekly update. [SOLVED]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/07/2018 02:56 PM, home user via users wrote:
> (replying to everyone)
> 
> (Rick)
>> "uname -r" will show you the currently running kernel:
> 
> (Joe)
>> uname -r
> 
> I get:
> -----
> bash.1[~]: uname -r
> 4.16.13-200.fc27.x86_64
> bash.2[~]:
> -----
> That matched the dnf log line, so apparently the update was successful;
> this is not a real problem.

If that's the kernel that the "broken pipe" error happened on and you've
rebooted into that kernel then yes, it worked and I wouldn't worry.

The thing is that sometimes there's a race condition caused by the
scriptlet where it may be sending data to, say, a logger, then shuts the
logger down while some data is still waiting to be written. When that
last bit of data tries to hit the pipe, it gets a broken pipe error
because there's nothing on the other end of the pipe to receive it.
It's minor, but annoying (and scary if you've never seen it).

You'd see a similar error if, for example, you ssh to a remote server
and then the remote server shuts down (or at least kills the ssh
daemon). Any time you try to shove data down a pipe with nothing on the
far end to receive it, you'll get that error.

> (Tom)
>> This has been happening for a while:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1497444
>> The bugzilla says it is fixed, but I guess not in f27.
> 
> In comment 17, Russell notes that the "plumbing" problem still occurs.
> This bug is "CLOSED RAWHIDE", but another bug was needed (1535458), and
> it's still in state "NEW".
> 
> Thank-you everyone for the help.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
- Millihelen (n): The amount of beauty required to launch one ship.  -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/FO35JIDUTKTCZXZ47TIZD2QG57GCQBI3/



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux