On Thu, 2019-08-01 at 16:49 +0300, Dokuchaev Ivan wrote: > There's also a ens19 interface, but it's management-only, and only > has > IP address assigned, no static routes/bonds/etc. Physically it's a VM > on > PVE hypervisor, all connected via virtual bridge to a router, and the > target is located on a MS Windows Server by another admin, and iSCSI > performs as expected on other initiators like the ones on Synology > DSM > and vmWare ESXi 6.x. > > Journalctl shows that iscsid has been started (iscsi.service unit is > not > present): > > jul 24 16:19:19 nfs-server iscsid[372]: iSCSI logger with pid=375 > started! > jul 24 16:19:19 nfs-server iscsid[375]: iSCSI daemon with pid=376 > started! > > But LUN is not mounted, requiring manual intervention with "iscsiadm > -m > node -L all && systemctl restart iscsid nfs-kernel-server" in order > to > drive to reappear. >
It is a stacked setup so it is hard to say where may lie the problem.
But the default Debian iSCSI setup works good.
root@debian-btrfs:~# systemctl status iscsi
● open-iscsi.service - Login to default iSCSI targets
Loaded: loaded (/lib/systemd/system/open-iscsi.service; enabled; vendor
preset: enabled)
Active: active (exited) since Thu 2019-08-01 20:50:41 IST; 2min 19s ago
Docs: man:iscsiadm(8)
man:iscsid(8)
Process: 407 ExecStartPre=/bin/systemctl --quiet is-active iscsid.service
(code=exited, status=0/SUCCESS)
Process: 408 ExecStart=/sbin/iscsiadm -m node --loginall=automatic
(code=exited, status=0/SUCCESS)
Process: 436 ExecStart=/lib/open-iscsi/activate-storage.sh (code=exited,
status=0/SUCCESS)
Main PID: 436 (code=exited, status=0/SUCCESS)
Aug 01 20:50:15 debian-btrfs systemd[1]: Starting Login to default iSCSI
targets...
Aug 01 20:50:41 debian-btrfs iscsiadm[408]: Logging in to [iface: default,
target: iqn.2003-01.org.linux-iscsi.debian.x8664, portal: 172.16.20.40,
Aug 01 20:50:41 debian-btrfs iscsiadm[408]: Logging in to [iface: default,
target: iqn.2003-01.org.linux-iscsi.debian.x8664, portal: 172.16.20.41,
Aug 01 20:50:41 debian-btrfs iscsiadm[408]: Logging in to [iface: default,
target: iqn.2003-01.org.linux-iscsi.debian.x8664, portal: 172.16.20.42,
Aug 01 20:50:41 debian-btrfs iscsiadm[408]: Logging in to [iface: default,
target: iqn.2003-01.org.linux-iscsi.debian.x8664, portal: 172.16.20.43,
Aug 01 20:50:41 debian-btrfs iscsiadm[408]: Login to [iface: default, target:
iqn.2003-01.org.linux-iscsi.debian.x8664, portal: 172.16.20.40,3260]
Aug 01 20:50:41 debian-btrfs iscsiadm[408]: Login to [iface: default, target:
iqn.2003-01.org.linux-iscsi.debian.x8664, portal: 172.16.20.41,3260]
Aug 01 20:50:41 debian-btrfs iscsiadm[408]: Login to [iface: default, target:
iqn.2003-01.org.linux-iscsi.debian.x8664, portal: 172.16.20.42,3260]
Aug 01 20:50:41 debian-btrfs iscsiadm[408]: Login to [iface: default, target:
iqn.2003-01.org.linux-iscsi.debian.x8664, portal: 172.16.20.43,3260]
Aug 01 20:50:41 debian-btrfs systemd[1]: Started Login to default iSCSI targets.
root@debian-btrfs:~# systemctl status iscsid
● iscsid.service - iSCSI initiator daemon (iscsid)
Loaded: loaded (/lib/systemd/system/iscsid.service; enabled; vendor preset:
enabled)
Active: active (running) since Thu 2019-08-01 20:50:15 IST; 2min 53s ago
Docs: man:iscsid(8)
Process: 400 ExecStartPre=/lib/open-iscsi/startup-checks.sh (code=exited,
status=0/SUCCESS)
Process: 403 ExecStart=/sbin/iscsid (code=exited, status=0/SUCCESS)
Main PID: 405 (iscsid)
Tasks: 2 (limit: 2353)
Memory: 4.9M
CGroup: /system.slice/iscsid.service
├─404 /sbin/iscsid
└─405 /sbin/iscsid
Aug 01 20:50:15 debian-btrfs systemd[1]: Starting iSCSI initiator daemon
(iscsid)...
Aug 01 20:50:15 debian-btrfs iscsid[403]: iSCSI logger with pid=404 started!
Aug 01 20:50:15 debian-btrfs systemd[1]: Started iSCSI initiator daemon
(iscsid).
Aug 01 20:50:16 debian-btrfs iscsid[404]: iSCSI daemon with pid=405 started!
Aug 01 20:50:41 debian-btrfs iscsid[404]: Connection2:0 to [target:
iqn.2003-01.org.linux-iscsi.debian.x8664, portal: 172.16.20.41,3260] through [
Aug 01 20:50:41 debian-btrfs iscsid[404]: Connection1:0 to [target:
iqn.2003-01.org.linux-iscsi.debian.x8664, portal: 172.16.20.40,3260] through [
Aug 01 20:50:41 debian-btrfs iscsid[404]: Connection4:0 to [target:
iqn.2003-01.org.linux-iscsi.debian.x8664, portal: 172.16.20.43,3260] through [
Aug 01 20:50:41 debian-btrfs iscsid[404]: Connection3:0 to [target:
iqn.2003-01.org.linux-iscsi.debian.x8664, portal: 172.16.20.42,3260] through [
> Configuration files haven't changed since initial bugreport, both
> iscsid.conf and default (inside /etc/iscsi/nodes/TARGETNAME/ADDRESS)
> have 'node.startup = automatic' and 'node.conn[0].startup =
> automatic'
> values in them.
>
> I don't know it it's related, but I can't simply reboot the service
> with
> an active iSCSI portal login, with a strange error:
>
> connection1:0: ping timeout of 5 secs expired, recv timeout 5, last
> rx
> 4355513531, last ping 4355514784, now 4355516096
> connection1:0: detected conn error (1022)
>
THat is not strange. Your network went out before the LUNs were
unmounted and the iSCSI sessions terminated. So iSCSI is simply
complaining about the network outage.
Please check your setup. Either of the service may be not enabled.
> Shouldn't systemd take care of logout from the portal, when the unit
> is
> stopping?
It does. And it does well.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
