Package: systemd
Version: 231-4
Kernel version 4.6.0-1-amd64
I am currently running debian stretch/sid alpha 7, all up to date, no
testing repos or anything added. I have open-iscsi installed via apt
install open-iscsi. I have connected to an iSCSI share on my local
network, which is working
I believe this bug is actually in the open-iscsi package, with the
logout-all.sh script called at shutdown. I have submitted a bug report
for that package. I do not believe systemd is the cause of this, so I
feel confident this bug can be closed. Thank you!
as an issue with systemd and its ordering of shutdown scripts (possibly
killing the interface before the logout of iscsi session). That was
reported in bug# 838028 and I have updated this bug to reflect my
additional troubleshooting and findings. Any help with the appropriate
fix for this would be appreciated.
Colby Ross
].iscsi.IFMarker = No
node.conn[0].iscsi.OFMarker = No
# END RECORD
Colby
On 9/22/2016 05:31, Christian Seiler wrote:
Hi,
On 09/22/2016 03:06 AM, Colby Ross wrote:
So, it appears the command being issued is /bin/iscsiadm -m node
--logoutall=all. When I try that command, I get the same error as
when I try to
I ran the dpkg command to check config files:
root@debscsi:~# dpkg-query -f '${Conffiles}\n' -W open-iscsi | \
> awk '{printf("%s %s\n", $2, $1);}' | md5sum -c -
/etc/default/open-iscsi: OK
/etc/init.d/iscsid: OK
/etc/init.d/open-iscsi: OK
/etc/iscsi/iscsid.conf: FAILED
md5sum: WARNING: 1 co
Sorry, forgot to attach the modified file:
root@debscsi:~# cat /etc/iscsi/iscsid.conf
#
# Open-iSCSI default configuration.
# Could be located at /etc/iscsi/iscsid.conf or ~/.iscsid.conf
#
# Note: To set any of these values for a specific node/session run
# the iscsiadm --mode node --op command f
I think I figured out part of it. When its looking for the config file
on logout, its looking in 172.16.5.30,3260,257 -- that does not exist on
my system. However, 172.16.5.30,3260,1 does, but it doesn't check this.
When I manually create the folder it is looking for and copy the
"default" fil
Christian
Sorry I didn't mention this before. I thought I had.
I set up the iscsi share in virt-manager. I basically installed the
open-iscsi package and used virt-manager to attach to the share as a
storage pool. The share is nothing more than a pass through to a kvm guest.
Virt-manager I believ
Christian
It's also strange it's detecting portal group 257. It may be an issue with
freenas but I have the portal group ID set as 1 for my iscsi share in Free
NAS.
Colby
I'll give it a go and see what I find.
I can say I had no issues either Debian Jessie 8.5 with this same exact
setup.
Colby
Christian
Just an update -- iscsiadm's discover protocol detects the target portal
group tag as 257. Windows own iSCSI initiator does as well.
Colby
Also, not sure if it is relevant or not, but after the discovery command
was issued, it started attaching to the iSCSI share twice at boot. I had
to manually remove both entries in
/etc/iscsi/nodes/iqn.2015-12.org.cokenet.ctl:iscsi. After that, it
stopped attaching to it twice, and is back to a
12 matches
Mail list logo
