I appreciate your interest, and I've attached a text file which I hope
is responsive to your request.
R
On Wed, Jun 26, 2019 at 8:55 AM The Lee-Man <[email protected]> wrote:
>
> On Tuesday, June 25, 2019 at 11:31:03 AM UTC-4, Randy Broman wrote:
>>
>> Thanks for your response. I'm using Kubuntu 19.04. I disabled the iscsi
>> service and in fact the boot was much faster:
>>
>>
> I'm not understanding what's going on with your system. I suspect there's
> more than just an unused open-iscsi initiator involved here.
>
> Do you have any iscsi targets set up? Existing sessions?
>
> I downloaded kunbuntu, and open-iscsi.service is enabled by default. Can you
> give me the systemctl status for open-iscsi.service, iscsid.socket, and
> iscsid.service? Also, an "ls" of /etc/iscsi/nodes and
> /sys/class/iscsi_session?
>
> And please don't assume that the numbers that "systemd-analyze blame" show --
> they don't always mean what you think. Can you just please time the boot (or
> reboot) sequence yourself, using the log files?
>
> On my test VM, I have iscsid.socket, iscsid.service, and open-iscsi.service
> at their default settings, but I have never discovered any targets, so I
> don't have any history of nodes or sessions. And when I run "systemd-analyze
> blame", iscsi does not show up at all.
>
> --
> You received this message because you are subscribed to a topic in the Google
> Groups "open-iscsi" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/open-iscsi/NK2sBOEzSQE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/open-iscsi.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/open-iscsi/8fe010f4-fc0f-4021-a20e-9d7bdfaf0a76%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/open-iscsi.
To view this discussion on the web visit
https://groups.google.com/d/msgid/open-iscsi/CAAixNYGu7RLUwvYZvFV8LzuorUcAXpwjXbuA6PqoeZmDL1rX1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
> I'm not understanding what's going on with your system. I suspect there's
> more than just an unused open-iscsi initiator involved
> here.
Requested info is below, hopefully I collected the right stuff, if not let me
know. I see messages like "no route to host" and "could not log in" (to
target), which don't make sense to me, as the QNAP target NAS is continually
running, ping-able, and should thus be available, and thus it seems like the
initiator is correctly configured as the connection does succeed eventually.
Maybe the delay is in the QNAP needing time to wake up upon the requests by the
initiator upon it's boot????
(QNAP uses their own variant of linux, and I can ssh into it and collect info
on the QNAP/targets if you can give me guidance on what to collect)
> Do you have any iscsi targets set up? Existing sessions?
There's one target:
$ sudo iscsiadm -m session -P 3
iSCSI Transport Class version 2.0-870
version 2.0-874
Target: iqn.2004-04.com.qnap:ts-473:iscsi.qnapiscsilu.2356fd (non-flash)
Current Portal: 192.168.1.30:3260,1
Persistent Portal: 192.168.1.30:3260,1
**********
Interface:
**********
Iface Name: default
Iface Transport: tcp
Iface Initiatorname: iqn.2015-06.world.server:www.server.world
Iface IPaddress: 192.168.1.17
Iface HWaddress: <empty>
Iface Netdev: <empty>
SID: 1
iSCSI Connection State: LOGGED IN
iSCSI Session State: LOGGED_IN
Internal iscsid Session State: NO CHANGE
*********
Timeouts:
*********
Recovery Timeout: 15
Target Reset Timeout: 30
LUN Reset Timeout: 30
Abort Timeout: 15
*****
CHAP:
*****
username: <empty>
password: ********
username_in: <empty>
password_in: ********
************************
Negotiated iSCSI params:
************************
HeaderDigest: None
DataDigest: None
MaxRecvDataSegmentLength: 262144
MaxXmitDataSegmentLength: 262144
FirstBurstLength: 65536
MaxBurstLength: 262144
ImmediateData: Yes
InitialR2T: Yes
MaxOutstandingR2T: 1
************************
Attached SCSI devices:
************************
Host Number: 5 State: running
scsi5 Channel 00 Id 0 Lun: 0
Attached scsi disk sdh State: running
> I downloaded kunbuntu, and open-iscsi.service is enabled by default. Can you
> give me the systemctl status for open-iscsi.service, > iscsid.socket, and
> iscsid.service? Also, an "ls" of /etc/iscsi/nodes and
> /sys/class/iscsi_session?
# systemctl status open-iscsi.service
● open-iscsi.service - Login to default iSCSI targets
Loaded: loaded (/lib/systemd/system/open-iscsi.service; disabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-06-27 07:23:51 PDT; 48min
ago
Docs: man:iscsiadm(8)
man:iscsid(8)
Process: 4231 ExecStartPre=/bin/systemctl --quiet is-active iscsid.service
(code=exited, status=0/SUCCESS)
Process: 4240 ExecStart=/sbin/iscsiadm -m node --loginall=automatic
(code=exited, status=8)
Main PID: 4240 (code=exited, status=8)
Jun 27 07:21:45 Jboat17 systemd[1]: Starting Login to default iSCSI targets...
Jun 27 07:23:51 Jboat17 iscsiadm[4240]: iscsiadm: Could not login to [iface:
default, target: iqn.2004-04.com.qnap:ts-473:iscsi.qnapiscsilu.2356fd, portal:
192.168.1.31,3260].
Jun 27 07:23:51 Jboat17 iscsiadm[4240]: iscsiadm: initiator reported error (8 -
connection timed out)
Jun 27 07:23:51 Jboat17 iscsiadm[4240]: iscsiadm: Could not log into all portals
Jun 27 07:23:51 Jboat17 iscsiadm[4240]: Logging in to [iface: default, target:
iqn.2004-04.com.qnap:ts-473:iscsi.qnapiscsilu.2356fd, portal:
192.168.1.31,3260] (multiple)
Jun 27 07:23:51 Jboat17 iscsiadm[4240]: Logging in to [iface: default, target:
iqn.2004-04.com.qnap:ts-473:iscsi.qnapiscsilu.2356fd, portal:
192.168.1.30,3260] (multiple)
Jun 27 07:23:51 Jboat17 iscsiadm[4240]: Login to [iface: default, target:
iqn.2004-04.com.qnap:ts-473:iscsi.qnapiscsilu.2356fd, portal:
192.168.1.30,3260] successful.
Jun 27 07:23:51 Jboat17 systemd[1]: open-iscsi.service: Main process exited,
code=exited, status=8/n/a
Jun 27 07:23:51 Jboat17 systemd[1]: open-iscsi.service: Failed with result
'exit-code'.
Jun 27 07:23:51 Jboat17 systemd[1]: Failed to start Login to default iSCSI
targets.
# systemctl status iscsid.socket
Unit iscsid.socket could not be found.
# systemctl status iscsid.service
● iscsid.service - iSCSI initiator daemon (iscsid)
Loaded: loaded (/lib/systemd/system/iscsid.service; enabled; vendor preset:
enabled)
Active: active (running) since Thu 2019-06-27 07:18:54 PDT; 58min ago
Docs: man:iscsid(8)
Process: 1898 ExecStartPre=/lib/open-iscsi/startup-checks.sh (code=exited,
status=0/SUCCESS)
Process: 1913 ExecStart=/sbin/iscsid (code=exited, status=0/SUCCESS)
Main PID: 1918 (iscsid)
Tasks: 2 (limit: 4915)
Memory: 4.9M
CGroup: /system.slice/iscsid.service
├─1917 /sbin/iscsid
└─1918 /sbin/iscsid
Jun 27 07:22:53 Jboat17 iscsid[1917]: connect to 192.168.1.31:3260 failed (No
route to host)
Jun 27 07:23:00 Jboat17 iscsid[1917]: connect to 192.168.1.31:3260 failed (No
route to host)
Jun 27 07:23:07 Jboat17 iscsid[1917]: connect to 192.168.1.31:3260 failed (No
route to host)
Jun 27 07:23:14 Jboat17 iscsid[1917]: connect to 192.168.1.31:3260 failed (No
route to host)
Jun 27 07:23:21 Jboat17 iscsid[1917]: connect to 192.168.1.31:3260 failed (No
route to host)
Jun 27 07:23:28 Jboat17 iscsid[1917]: connect to 192.168.1.31:3260 failed (No
route to host)
Jun 27 07:23:35 Jboat17 iscsid[1917]: connect to 192.168.1.31:3260 failed (No
route to host)
Jun 27 07:23:42 Jboat17 iscsid[1917]: connect to 192.168.1.31:3260 failed (No
route to host)
Jun 27 07:23:49 Jboat17 iscsid[1917]: connect to 192.168.1.31:3260 failed (No
route to host)
Jun 27 07:23:52 Jboat17 iscsid[1917]: Connection-1:0 to [target:
iqn.2004-04.com.qnap:ts-473:iscsi.qnapiscsilu.2356fd, portal:
192.168.1.31,3260] through [iface: default] is shutdown
ls -l /etc/iscsi/nodes
total 4
drw------- 7 root root 4096 Jun 27 08:06
iqn.2004-04.com.qnap:ts-473:iscsi.qnapiscsilu.2356fd
# ls -l /sys/class/iscsi_session
total 0
lrwxrwxrwx 1 root root 0 Jun 27 07:21 session1 ->
../../devices/platform/host5/session1/iscsi_session/session1
> And please don't assume that the numbers that "systemd-analyze blame" show --
> they don't always mean what you think. Can you just > please time the boot
> (or reboot) sequence yourself, using the log files?
# cat /var/log/syslog | grep iscsi
Jun 27 07:18:54 Jboat17 systemd[1]: Starting iSCSI initiator daemon (iscsid)...
Jun 27 07:18:54 Jboat17 iscsid: iSCSI logger with pid=1917 started!
Jun 27 07:18:54 Jboat17 systemd[1]: Started iSCSI initiator daemon (iscsid).
Jun 27 07:18:54 Jboat17 iscsid: iSCSI daemon with pid=1918 started!
Jun 27 07:21:46 Jboat17 iscsid: Connection1:0 to [target:
iqn.2004-04.com.qnap:ts-473:iscsi.qnapiscsilu.2356fd, portal:
192.168.1.30,3260] through [iface: default] is operational now
Jun 27 07:21:50 Jboat17 iscsid: connect to 192.168.1.31:3260 failed (No route
to host)
Jun 27 07:22:04 Jboat17 iscsid: message repeated 2 times: [ connect to
192.168.1.31:3260 failed (No route to host)]
Jun 27 07:22:11 Jboat17 iscsid: connect to 192.168.1.31:3260 failed (No route
to host)
Jun 27 07:23:42 Jboat17 iscsid: message repeated 13 times: [ connect to
192.168.1.31:3260 failed (No route to host)]
Jun 27 07:23:49 Jboat17 iscsid: connect to 192.168.1.31:3260 failed (No route
to host)
Jun 27 07:23:51 Jboat17 iscsiadm[4240]: iscsiadm: Could not login to [iface:
default, target: iqn.2004-04.com.qnap:ts-473:iscsi.qnapiscsilu.2356fd, portal:
192.168.1.31,3260].
Jun 27 07:23:51 Jboat17 iscsiadm[4240]: iscsiadm: initiator reported error (8 -
connection timed out)
Jun 27 07:23:51 Jboat17 iscsiadm[4240]: iscsiadm: Could not log into all portals
Jun 27 07:23:51 Jboat17 iscsiadm[4240]: Logging in to [iface: default, target:
iqn.2004-04.com.qnap:ts-473:iscsi.qnapiscsilu.2356fd, portal:
192.168.1.31,3260] (multiple)
Jun 27 07:23:51 Jboat17 iscsiadm[4240]: Logging in to [iface: default, target:
iqn.2004-04.com.qnap:ts-473:iscsi.qnapiscsilu.2356fd, portal:
192.168.1.30,3260] (multiple)
Jun 27 07:23:51 Jboat17 iscsiadm[4240]: Login to [iface: default, target:
iqn.2004-04.com.qnap:ts-473:iscsi.qnapiscsilu.2356fd, portal:
192.168.1.30,3260] successful.
Jun 27 07:23:51 Jboat17 systemd[1]: open-iscsi.service: Main process exited,
code=exited, status=8/n/a
Jun 27 07:23:51 Jboat17 systemd[1]: open-iscsi.service: Failed with result
'exit-code'.
Jun 27 07:23:52 Jboat17 iscsid: Connection-1:0 to [target:
iqn.2004-04.com.qnap:ts-473:iscsi.qnapiscsilu.2356fd, portal:
192.168.1.31,3260] through [iface: default] is shutdown.
> On my test VM, I have iscsid.socket, iscsid.service, and open-iscsi.service
> at their default settings, but I have never discovered > any targets, so I
> don't have any history of nodes or sessions. And when I run "systemd-analyze
> blame", iscsi does not show up at
> all.
