Bug 1267645 - nm-openconnect-service dies with SIGPIPE on writing to stderr
nm-openconnect-service dies with SIGPIPE on writing to stderr
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Lubomir Rintel
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-09-30 10:52 EDT by David Woodhouse
Modified: 2016-12-20 09:49 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 09:49:50 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Woodhouse 2015-09-30 10:52:46 EDT
4329  write(2, "\n** (nm-openconnect-service:4329): WARNING **: property 'cookie-flags' unknown\n", 79) = -1 EPIPE (Broken pipe)
4329  --- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=4329, si_uid=0} ---
4329  +++ killed by SIGPIPE +++

It's *always* given those messages. Why is stderr no longer connected?

If I run it from a terminal, of course it works fine.
Comment 1 Jirka Klimes 2015-10-01 07:31:16 EDT
nm-openconnect-service should inherit stderr from NetworkManager, that is probably directed to some systemd magic.


Would you run
$ sudo ls -l /proc/`pgrep -f nm-openconnect-service`/fd

and then
$ ss | grep <socket number> (or whatever fd 2 is linked to)
Comment 2 David Woodhouse 2015-12-01 15:03:47 EST
[root@i7 s2]# sudo ls -l /proc/`pgrep -f nm-openconnect-service`/fd
total 0
lr-x------. 1 root root 64 Dec  1 20:02 0 -> /dev/null
lrwx------. 1 root root 64 Dec  1 20:02 1 -> socket:[14848]
lrwx------. 1 root root 64 Dec  1 20:02 2 -> socket:[14848]
lrwx------. 1 root root 64 Dec  1 20:02 3 -> socket:[29618560]
lrwx------. 1 root root 64 Dec  1 20:02 4 -> anon_inode:[eventfd]
[root@i7 s2]# ss | grep 29618560
u_str  ESTAB      0      0       * 29618560              * 29828639             
u_str  ESTAB      0      0      /run/dbus/system_bus_socket 29828639              * 29618560
Comment 3 David Woodhouse 2015-12-01 15:05:51 EST
Sorry, wrong fd.

# ss | grep 14848
u_str  ESTAB      0      0       * 14848                 * 0
Comment 4 Fedora End Of Life 2016-11-24 07:39:58 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 5 Fedora End Of Life 2016-12-20 09:49:50 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.