CentOS 7.4.1708 + iscsi-initiator-utils-6.2.0.874-4.el7: Could not insert module . Kmod error -38

295 views
Skip to first unread message

vladimir...@gmail.com

unread,
Oct 3, 2017, 1:00:31 PM10/3/17
to open-iscsi
Hi,

I'm experiencing the following issue, an iSCSI initiator fails to connect to iSCSI target.

# journalctl _SYSTEMD_UNIT=iscsid.service
..
Oct 03 15:02:43 myhost iscsid[3366]: Could not insert module . Kmod error -38
..

# systemctl status iscsid 
● iscsid.service - Open-iSCSI
   Loaded: loaded (/usr/lib/systemd/system/iscsid.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2017-09-14 15:33:32 CEST; 2 weeks 5 days ago
     Docs: man:iscsid(8)
           man:iscsiadm(8)
 Main PID: 3408 (iscsid)
   Memory: 2.5M
   CGroup: /system.slice/iscsid.service
           ├─3406 /usr/sbin/iscsid
           └─3408 /usr/sbin/iscsid

Oct 03 16:52:44 myhost  iscsid[3406]: IPC qtask write failed: Broken pipe

The same host could successfully mount from the same target. I also noticed that according to https://github.com/vishvananda/open-iscsi/blob/9fe0fab2975eb102d5019696dc090379f7eca66c/usr/transport.c#L197 it should print out "transport_name" in the error message, however it doesn't do so in my case.

# systemctl restart iscsid fixes it.

Any ideas maybe?

Vladimir Zhigulin

unread,
Oct 4, 2017, 3:59:01 AM10/4/17
to open-iscsi
I even think it was

# systemctl restart iscsid.socket

that fixed the issue.

Vladimir Zhigulin

unread,
Oct 24, 2017, 3:02:57 PM10/24/17
to open-iscsi
I also noticed that things seem to be piling up on @ISCSIADM_ABSTRACT_NAMESPACE socket, I see many lines in "CONNECTING" status via "netstat -na"
Reply all
Reply to author
Forward
0 new messages