Red Hat Bugzilla – Bug 1464531
iscsi IPC qtask write failed: Broken pipe initiator reported error (8 - connection timed out)
Last modified: 2018-05-29 07:29:13 EDT
Description of problem:
iscsid fails to start
Version-Release number of selected component (if applicable):
iscsid version 126.96.36.1994
Steps to Reproduce:
iscsiadm: Could not login to [iface: default, target: iqn.1994-12.com.promise.c1.8c.188.8.131.52.0.20, portal: 10.0.10.2,3260].
iscsiadm: initiator reported error (8 - connection timed out)
iscsiadm: Could not log into all portals
Jun 23 12:30:24 curie iscsid: Connection-1:0 to [target: iqn.1994-12.com.promise.c1.8c.184.108.40.206.0.20, portal: 10.0.10.2,3260] through [iface: default] is shutdown.
Jun 23 12:30:24 curie iscsid: IPC qtask write failed: Broken pipe
iscsid: Connection-1:0 to [target: iqn.1994-12.com.promise.c1.8c.220.127.116.11.0.20, portal: 10.0.10.2,3260] through [iface: default] is shutdown.
iscsi starts correctly
4.11.6-300.fc26.i686+PAE #1 SMP Mon Jun 19 17:35:59 UTC 2017 i686 i686 i386 GNU/Linux
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: permissive
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 30
Sounds like this problem http://forums.fedoraforum.org/archive/index.php/t-306913.html
After reboot and disabling Selinux seeing this:
n 23 12:46:29 curie iscsid: Connection-1:0 to [target: iqn.1994-12.com.promise.c1.8c.18.104.22.168.0.20, portal: 10.0.10.2,3260] through [iface: default] is shutdown.
Jun 23 12:47:55 curie iscsid: iSCSI logger with pid=2210 started!
Jun 23 12:47:55 curie iscsid: Can not bind IPC socket
Jun 23 12:48:13 curie iscsid: semop down failed 22
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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'
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 26 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.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.