Dear Christian, Thanks for your quick and educational reply. Here is the result of dpkg :
root@control:~# dpkg -l open-iscsi Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-========================-=================-=================-====================================================== ii open-iscsi 2.0.873-3.13.2014 amd64 High performance, transport independent iSCSI implemen I generated a new initiatorname and received the following : InitiatorName=iqn.2005-03.org.open-iscsi:9b96ddaa68f4 So, I tried again to connect and failed. I put the intitator name and IP into the target again, reset tgtd, but no change : root@control:~# iscsiadm -m discovery -t st -p 192.168.0.10:3260 iscsiadm: Cannot perform discovery. Invalid Initiatorname. iscsiadm: Could not perform SendTargets discovery: invalid parameter So, this thing still hates us ... On Fri, Mar 25, 2016 at 5:39 AM, Christian Seiler <[email protected] > wrote: > Hi, > > (I'm one of the current Debian maintainers of open-iscsi.) > > On 03/25/2016 04:37 AM, ZER0SEN wrote: > > root@control:~# cat /etc/iscsi/initiatorname.iscsi > > GenerateName=yes > > This was specific to Debian up to very recently: the default configuration > file initiatorname.iscsi contained GenerateName=yes and the startup script > for open-iscsi would detect that and generate a name on the fly. We've > changed that in recent versions, so that the initiator name is now > generated at package installation time, but older versions still had that. > > Now the thing is, that I've recently added systemd support in Debian and > refactored a lot of the startup logic - and during a short period of time, > the startup logic for generating the initiator name was broken (regardless > of init system) because of a bug. This was fixed (even before we moved the > generation logic to package installation time), but if Univention grabbed > the Debian package from the Debian unstable distribution during that > period where it was buggy, it would explain why you see this. (Or, > maybe they have an extremely old version that had a similar bug.) > > To check, could you please do: > > dpkg -l open-iscsi > > and tell me what version of open-iscsi is running on your system? > > To solve your immediate problem: you generate a unique initiator name by > doing (as root): > > echo "InitiatorName=$(iscsi-iname)" > /etc/iscsi/initiatorname.iscsi > > Then look at the contents of the file and that is your unique initiator > name (which you can use in the target's access control, for example). > > Regards, > Christian > > -- > 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/oG4ByBK6Y6w/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. > 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. For more options, visit https://groups.google.com/d/optout.
