Re: Initiator name missing
It worked IMMEDIATELY after removing those directories! Thanks a ton. At this point all I need to do is set up the shares and start cracking away at this render farm software. I appreciate the help! Jeff On Wed, Jan 9, 2013 at 10:28 PM, Mike Christie micha...@cs.wisc.edu wrote: Did you see my other mail? Previous mail: --- You have a older version. Just rm the old setup files: rm /etc/iscsi/nodes rm /etc/iscsi/send_targets or your version/distro might put it in /var/lib rm /var/lib/iscsi/nodes rm /var/lib/iscsisend_targets Also make sure that in iscsid.conf both the discovery username/password and node username/password settings are removed. - You can hand edit those files if you want, but we do not support that. They can change at any time. Where did you get your open-iscsi tools? Are they from the distro or open-iscsi.org? If you clear the username settings in iscsid.conf, then run the normal old iscsiadm discovery command it should have cleared out the old settings. On 01/09/2013 01:09 PM, Jeff Bye wrote: Hello again Mike / open-iscsi community, Any clue as to what might be missing for me? Is there a way to update by editing a file as opposed to typing in the commands? It seems so close to being figured out but I'm stumped! Thanks again Jeff On Fri, Jan 4, 2013 at 4:37 PM, Jeff Bye jeff...@gogoluckey.com mailto:jeff...@gogoluckey.com wrote: 2.0-871 is what I'm running Jeff On Fri, Jan 4, 2013 at 4:17 PM, Jeff Bye jeff...@gogoluckey.com mailto:jeff...@gogoluckey.com wrote: I tried all of the commands and none of them worked for me: *deadlineserver@deadlineserver ~ $ iscsiadm -m discoverydb -t st -p 10.10.0.1:3260 http://10.10.0.1:3260 -o delete* iscsiadm -m discovery [ -hV ] [ -d debug_level ] [-P printlevel] [ -t type -p ip:port -I ifaceN ... [ -l ] ] | [ -p ip:port ] [ -o operation ] [ -n name ] [ -v value ] iscsiadm -m node [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -L all,manual,automatic ] [ -U all,manual,automatic ] [ -S ] [ [ -T targetname -p ip:port -I ifaceN ] [ -l | -u | -R | -s] ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m session [ -hV ] [ -d debug_level ] [ -P printlevel] [ -r sessionid | sysfsdir [ -R | -u | -s ] [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m iface [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -I ifacename ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m fw [ -l ] iscsiadm -m host [ -P printlevel ] [ -H hostno ] iscsiadm -k priority *I checked man iscsiadm and found:* -m, --mode op specify the mode. op must be one of discovery, node, fw, host iface or session. If no other options are specified: for discovery and node, all of their respective records are displayed; for session, all active sessions and connections are displayed; for fw, all boot firmware values are displayed; for host, all iSCSI hosts are displayed; and for iface, all ifaces setup in /etc/iscsi/ifaces are displayed. Am I running the wrong version perhaps? Jeff On Thu, Jan 3, 2013 at 7:05 PM, Mike Christie micha...@cs.wisc.edu mailto:micha...@cs.wisc.edu wrote: The iscsid.conf values are the defaults one used to setup the port/node/target db. If you clear the iscsid.conf values, you would still need to update the db ones for it to take effect on existing targets you have already setup. For the discovery values you can either delete the old discovery record: iscsiadm -m discoverydb -t st -p ip -o delete When you run the discovery command next, then it will use the iscsid.conf settings to create the discovery record. or if your tools does not support that command you can clear the chap settings iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.username -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.password -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.authmethod -v none On 01/03/2013 01:46 PM, Jeff Bye wrote: Hey! I've been out of town for a couple of weeks. Hope you had a chance to take some time off as well :) It seems that the username and
Re: Initiator name missing
Hello again Mike / open-iscsi community, Any clue as to what might be missing for me? Is there a way to update by editing a file as opposed to typing in the commands? It seems so close to being figured out but I'm stumped! Thanks again Jeff On Fri, Jan 4, 2013 at 4:37 PM, Jeff Bye jeff...@gogoluckey.com wrote: 2.0-871 is what I'm running Jeff On Fri, Jan 4, 2013 at 4:17 PM, Jeff Bye jeff...@gogoluckey.com wrote: I tried all of the commands and none of them worked for me: *deadlineserver@deadlineserver ~ $ iscsiadm -m discoverydb -t st -p 10.10.0.1:3260 -o delete* iscsiadm -m discovery [ -hV ] [ -d debug_level ] [-P printlevel] [ -t type -p ip:port -I ifaceN ... [ -l ] ] | [ -p ip:port ] [ -o operation ] [ -n name ] [ -v value ] iscsiadm -m node [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -L all,manual,automatic ] [ -U all,manual,automatic ] [ -S ] [ [ -T targetname -p ip:port -I ifaceN ] [ -l | -u | -R | -s] ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m session [ -hV ] [ -d debug_level ] [ -P printlevel] [ -r sessionid | sysfsdir [ -R | -u | -s ] [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m iface [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -I ifacename ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m fw [ -l ] iscsiadm -m host [ -P printlevel ] [ -H hostno ] iscsiadm -k priority *I checked man iscsiadm and found:* -m, --mode op specify the mode. op must be one of discovery, node, fw, host iface or session. If no other options are specified: for discovery and node, all of their respective records are displayed; for session, all active sessions and connections are displayed; for fw, all boot firmware values are displayed; for host, all iSCSI hosts are displayed; and for iface, all ifaces setup in /etc/iscsi/ifaces are displayed. Am I running the wrong version perhaps? Jeff On Thu, Jan 3, 2013 at 7:05 PM, Mike Christie micha...@cs.wisc.eduwrote: The iscsid.conf values are the defaults one used to setup the port/node/target db. If you clear the iscsid.conf values, you would still need to update the db ones for it to take effect on existing targets you have already setup. For the discovery values you can either delete the old discovery record: iscsiadm -m discoverydb -t st -p ip -o delete When you run the discovery command next, then it will use the iscsid.conf settings to create the discovery record. or if your tools does not support that command you can clear the chap settings iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.username -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.password -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.authmethod -v none On 01/03/2013 01:46 PM, Jeff Bye wrote: Hey! I've been out of town for a couple of weeks. Hope you had a chance to take some time off as well :) It seems that the username and password I had initially set up is still being used, however in iscsid.conf CHAP is set to none and any other information has been commented. Does this only affect the target side? Jeff When I had it running on a windows machine (a temporary setup) we kept it open and On Fri, Dec 21, 2012 at 1:32 AM, Mike Christie micha...@cs.wisc.edu mailto:micha...@cs.wisc.edu wrote: On 12/20/2012 06:54 PM, GGL wrote: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target Yeah, this is a CHAP failure. Is it turned off on the target too? Could you run sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 -d 8 and send all the output? Also while running this command run: tcpdump -w iscsi.discovery.out -i your_eth_device and then send that iscsi.discovery.out file. It will show us what the target is sending on the wire too. Both of those files will have passwords in them if you have CHAP settings still being used, so send me them in private or edit out the values if you do not want them on the open. -- Jeff Bye Graphics Coordinator Liberty Post 12910 Culver Blvd. Suite G Los Angeles, CA 90066 (310) 314-3900 x247 -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- Jeff Bye Graphics Coordinator Liberty Post 12910 Culver Blvd. Suite G Los Angeles, CA 90066 (310) 314-3900 x247 -- Jeff Bye Graphics Coordinator Liberty Post 12910 Culver Blvd. Suite G
Re: Initiator name missing
Did you see my other mail? Previous mail: --- You have a older version. Just rm the old setup files: rm /etc/iscsi/nodes rm /etc/iscsi/send_targets or your version/distro might put it in /var/lib rm /var/lib/iscsi/nodes rm /var/lib/iscsisend_targets Also make sure that in iscsid.conf both the discovery username/password and node username/password settings are removed. - You can hand edit those files if you want, but we do not support that. They can change at any time. Where did you get your open-iscsi tools? Are they from the distro or open-iscsi.org? If you clear the username settings in iscsid.conf, then run the normal old iscsiadm discovery command it should have cleared out the old settings. On 01/09/2013 01:09 PM, Jeff Bye wrote: Hello again Mike / open-iscsi community, Any clue as to what might be missing for me? Is there a way to update by editing a file as opposed to typing in the commands? It seems so close to being figured out but I'm stumped! Thanks again Jeff On Fri, Jan 4, 2013 at 4:37 PM, Jeff Bye jeff...@gogoluckey.com mailto:jeff...@gogoluckey.com wrote: 2.0-871 is what I'm running Jeff On Fri, Jan 4, 2013 at 4:17 PM, Jeff Bye jeff...@gogoluckey.com mailto:jeff...@gogoluckey.com wrote: I tried all of the commands and none of them worked for me: *deadlineserver@deadlineserver ~ $ iscsiadm -m discoverydb -t st -p 10.10.0.1:3260 http://10.10.0.1:3260 -o delete* iscsiadm -m discovery [ -hV ] [ -d debug_level ] [-P printlevel] [ -t type -p ip:port -I ifaceN ... [ -l ] ] | [ -p ip:port ] [ -o operation ] [ -n name ] [ -v value ] iscsiadm -m node [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -L all,manual,automatic ] [ -U all,manual,automatic ] [ -S ] [ [ -T targetname -p ip:port -I ifaceN ] [ -l | -u | -R | -s] ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m session [ -hV ] [ -d debug_level ] [ -P printlevel] [ -r sessionid | sysfsdir [ -R | -u | -s ] [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m iface [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -I ifacename ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m fw [ -l ] iscsiadm -m host [ -P printlevel ] [ -H hostno ] iscsiadm -k priority *I checked man iscsiadm and found:* -m, --mode op specify the mode. op must be one of discovery, node, fw, host iface or session. If no other options are specified: for discovery and node, all of their respective records are displayed; for session, all active sessions and connections are displayed; for fw, all boot firmware values are displayed; for host, all iSCSI hosts are displayed; and for iface, all ifaces setup in /etc/iscsi/ifaces are displayed. Am I running the wrong version perhaps? Jeff On Thu, Jan 3, 2013 at 7:05 PM, Mike Christie micha...@cs.wisc.edu mailto:micha...@cs.wisc.edu wrote: The iscsid.conf values are the defaults one used to setup the port/node/target db. If you clear the iscsid.conf values, you would still need to update the db ones for it to take effect on existing targets you have already setup. For the discovery values you can either delete the old discovery record: iscsiadm -m discoverydb -t st -p ip -o delete When you run the discovery command next, then it will use the iscsid.conf settings to create the discovery record. or if your tools does not support that command you can clear the chap settings iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.username -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.password -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.authmethod -v none On 01/03/2013 01:46 PM, Jeff Bye wrote: Hey! I've been out of town for a couple of weeks. Hope you had a chance to take some time off as well :) It seems that the username and password I had initially set up is still being used, however in iscsid.conf CHAP is set to none and any other information has been commented. Does this only affect the target side? Jeff When I had it running on a windows machine (a temporary
Re: Initiator name missing
You have a older version. Just rm the old setup files: rm /etc/iscsi/nodes rm /etc/iscsi/send_targets or your version/distro might put it in /var/lib rm /var/lib/iscsi/nodes rm /var/lib/iscsisend_targets Also make sure that in iscsid.conf both the discovery username/password and node username/password settings are removed. On Jan 4, 2013, at 6:37 PM, Jeff Bye jeff...@gogoluckey.com wrote: 2.0-871 is what I'm running Jeff On Fri, Jan 4, 2013 at 4:17 PM, Jeff Bye jeff...@gogoluckey.com wrote: I tried all of the commands and none of them worked for me: deadlineserver@deadlineserver ~ $ iscsiadm -m discoverydb -t st -p 10.10.0.1:3260 -o delete iscsiadm -m discovery [ -hV ] [ -d debug_level ] [-P printlevel] [ -t type -p ip:port -I ifaceN ... [ -l ] ] | [ -p ip:port ] [ -o operation ] [ -n name ] [ -v value ] iscsiadm -m node [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -L all,manual,automatic ] [ -U all,manual,automatic ] [ -S ] [ [ -T targetname -p ip:port -I ifaceN ] [ -l | -u | -R | -s] ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m session [ -hV ] [ -d debug_level ] [ -P printlevel] [ -r sessionid | sysfsdir [ -R | -u | -s ] [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m iface [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -I ifacename ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m fw [ -l ] iscsiadm -m host [ -P printlevel ] [ -H hostno ] iscsiadm -k priority I checked man iscsiadm and found: -m, --mode op specify the mode. op must be one of discovery, node, fw, host iface or session. If no other options are specified: for discovery and node, all of their respective records are displayed; for session, all active sessions and connections are displayed; for fw, all boot firmware values are displayed; for host, all iSCSI hosts are displayed; and for iface, all ifaces setup in /etc/iscsi/ifaces are displayed. Am I running the wrong version perhaps? Jeff On Thu, Jan 3, 2013 at 7:05 PM, Mike Christie micha...@cs.wisc.edu wrote: The iscsid.conf values are the defaults one used to setup the port/node/target db. If you clear the iscsid.conf values, you would still need to update the db ones for it to take effect on existing targets you have already setup. For the discovery values you can either delete the old discovery record: iscsiadm -m discoverydb -t st -p ip -o delete When you run the discovery command next, then it will use the iscsid.conf settings to create the discovery record. or if your tools does not support that command you can clear the chap settings iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.username -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.password -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.authmethod -v none On 01/03/2013 01:46 PM, Jeff Bye wrote: Hey! I've been out of town for a couple of weeks. Hope you had a chance to take some time off as well :) It seems that the username and password I had initially set up is still being used, however in iscsid.conf CHAP is set to none and any other information has been commented. Does this only affect the target side? Jeff When I had it running on a windows machine (a temporary setup) we kept it open and On Fri, Dec 21, 2012 at 1:32 AM, Mike Christie micha...@cs.wisc.edu mailto:micha...@cs.wisc.edu wrote: On 12/20/2012 06:54 PM, GGL wrote: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target Yeah, this is a CHAP failure. Is it turned off on the target too? Could you run sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 -d 8 and send all the output? Also while running this command run: tcpdump -w iscsi.discovery.out -i your_eth_device and then send that iscsi.discovery.out file. It will show us what the target is sending on the wire too. Both of those files will have passwords in them if you have CHAP settings still being used, so send me them in private or edit out the values if you do not want them on the open. -- Jeff Bye Graphics Coordinator Liberty Post 12910 Culver Blvd. Suite G Los Angeles, CA 90066 (310) 314-3900 x247 -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- Jeff Bye Graphics Coordinator Liberty Post 12910 Culver Blvd. Suite G Los Angeles,
Re: Initiator name missing
I tried all of the commands and none of them worked for me: *deadlineserver@deadlineserver ~ $ iscsiadm -m discoverydb -t st -p 10.10.0.1:3260 -o delete* iscsiadm -m discovery [ -hV ] [ -d debug_level ] [-P printlevel] [ -t type -p ip:port -I ifaceN ... [ -l ] ] | [ -p ip:port ] [ -o operation ] [ -n name ] [ -v value ] iscsiadm -m node [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -L all,manual,automatic ] [ -U all,manual,automatic ] [ -S ] [ [ -T targetname -p ip:port -I ifaceN ] [ -l | -u | -R | -s] ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m session [ -hV ] [ -d debug_level ] [ -P printlevel] [ -r sessionid | sysfsdir [ -R | -u | -s ] [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m iface [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -I ifacename ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m fw [ -l ] iscsiadm -m host [ -P printlevel ] [ -H hostno ] iscsiadm -k priority *I checked man iscsiadm and found:* -m, --mode op specify the mode. op must be one of discovery, node, fw, host iface or session. If no other options are specified: for discovery and node, all of their respective records are displayed; for session, all active sessions and connections are displayed; for fw, all boot firmware values are displayed; for host, all iSCSI hosts are displayed; and for iface, all ifaces setup in /etc/iscsi/ifaces are displayed. Am I running the wrong version perhaps? Jeff On Thu, Jan 3, 2013 at 7:05 PM, Mike Christie micha...@cs.wisc.edu wrote: The iscsid.conf values are the defaults one used to setup the port/node/target db. If you clear the iscsid.conf values, you would still need to update the db ones for it to take effect on existing targets you have already setup. For the discovery values you can either delete the old discovery record: iscsiadm -m discoverydb -t st -p ip -o delete When you run the discovery command next, then it will use the iscsid.conf settings to create the discovery record. or if your tools does not support that command you can clear the chap settings iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.username -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.password -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.authmethod -v none On 01/03/2013 01:46 PM, Jeff Bye wrote: Hey! I've been out of town for a couple of weeks. Hope you had a chance to take some time off as well :) It seems that the username and password I had initially set up is still being used, however in iscsid.conf CHAP is set to none and any other information has been commented. Does this only affect the target side? Jeff When I had it running on a windows machine (a temporary setup) we kept it open and On Fri, Dec 21, 2012 at 1:32 AM, Mike Christie micha...@cs.wisc.edu mailto:micha...@cs.wisc.edu wrote: On 12/20/2012 06:54 PM, GGL wrote: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target Yeah, this is a CHAP failure. Is it turned off on the target too? Could you run sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 -d 8 and send all the output? Also while running this command run: tcpdump -w iscsi.discovery.out -i your_eth_device and then send that iscsi.discovery.out file. It will show us what the target is sending on the wire too. Both of those files will have passwords in them if you have CHAP settings still being used, so send me them in private or edit out the values if you do not want them on the open. -- Jeff Bye Graphics Coordinator Liberty Post 12910 Culver Blvd. Suite G Los Angeles, CA 90066 (310) 314-3900 x247 -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- Jeff Bye Graphics Coordinator Liberty Post 12910 Culver Blvd. Suite G Los Angeles, CA 90066 (310) 314-3900 x247 -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Initiator name missing
2.0-871 is what I'm running Jeff On Fri, Jan 4, 2013 at 4:17 PM, Jeff Bye jeff...@gogoluckey.com wrote: I tried all of the commands and none of them worked for me: *deadlineserver@deadlineserver ~ $ iscsiadm -m discoverydb -t st -p 10.10.0.1:3260 -o delete* iscsiadm -m discovery [ -hV ] [ -d debug_level ] [-P printlevel] [ -t type -p ip:port -I ifaceN ... [ -l ] ] | [ -p ip:port ] [ -o operation ] [ -n name ] [ -v value ] iscsiadm -m node [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -L all,manual,automatic ] [ -U all,manual,automatic ] [ -S ] [ [ -T targetname -p ip:port -I ifaceN ] [ -l | -u | -R | -s] ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m session [ -hV ] [ -d debug_level ] [ -P printlevel] [ -r sessionid | sysfsdir [ -R | -u | -s ] [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m iface [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -I ifacename ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m fw [ -l ] iscsiadm -m host [ -P printlevel ] [ -H hostno ] iscsiadm -k priority *I checked man iscsiadm and found:* -m, --mode op specify the mode. op must be one of discovery, node, fw, host iface or session. If no other options are specified: for discovery and node, all of their respective records are displayed; for session, all active sessions and connections are displayed; for fw, all boot firmware values are displayed; for host, all iSCSI hosts are displayed; and for iface, all ifaces setup in /etc/iscsi/ifaces are displayed. Am I running the wrong version perhaps? Jeff On Thu, Jan 3, 2013 at 7:05 PM, Mike Christie micha...@cs.wisc.eduwrote: The iscsid.conf values are the defaults one used to setup the port/node/target db. If you clear the iscsid.conf values, you would still need to update the db ones for it to take effect on existing targets you have already setup. For the discovery values you can either delete the old discovery record: iscsiadm -m discoverydb -t st -p ip -o delete When you run the discovery command next, then it will use the iscsid.conf settings to create the discovery record. or if your tools does not support that command you can clear the chap settings iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.username -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.password -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.authmethod -v none On 01/03/2013 01:46 PM, Jeff Bye wrote: Hey! I've been out of town for a couple of weeks. Hope you had a chance to take some time off as well :) It seems that the username and password I had initially set up is still being used, however in iscsid.conf CHAP is set to none and any other information has been commented. Does this only affect the target side? Jeff When I had it running on a windows machine (a temporary setup) we kept it open and On Fri, Dec 21, 2012 at 1:32 AM, Mike Christie micha...@cs.wisc.edu mailto:micha...@cs.wisc.edu wrote: On 12/20/2012 06:54 PM, GGL wrote: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target Yeah, this is a CHAP failure. Is it turned off on the target too? Could you run sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 -d 8 and send all the output? Also while running this command run: tcpdump -w iscsi.discovery.out -i your_eth_device and then send that iscsi.discovery.out file. It will show us what the target is sending on the wire too. Both of those files will have passwords in them if you have CHAP settings still being used, so send me them in private or edit out the values if you do not want them on the open. -- Jeff Bye Graphics Coordinator Liberty Post 12910 Culver Blvd. Suite G Los Angeles, CA 90066 (310) 314-3900 x247 -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- Jeff Bye Graphics Coordinator Liberty Post 12910 Culver Blvd. Suite G Los Angeles, CA 90066 (310) 314-3900 x247 -- Jeff Bye Graphics Coordinator Liberty Post 12910 Culver Blvd. Suite G Los Angeles, CA 90066 (310) 314-3900 x247 -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group
Re: Initiator name missing
Thank you for your response. Yes had to walk a bit. I do not use CHAP. Neither the purpose nor the proponent, I have it all off. 2013/1/3 Jeff Bye jeff...@gogoluckey.com Hey! I've been out of town for a couple of weeks. Hope you had a chance to take some time off as well :) It seems that the username and password I had initially set up is still being used, however in iscsid.conf CHAP is set to none and any other information has been commented. Does this only affect the target side? Jeff When I had it running on a windows machine (a temporary setup) we kept it open and On Fri, Dec 21, 2012 at 1:32 AM, Mike Christie micha...@cs.wisc.eduwrote: On 12/20/2012 06:54 PM, GGL wrote: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target Yeah, this is a CHAP failure. Is it turned off on the target too? Could you run sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 -d 8 and send all the output? Also while running this command run: tcpdump -w iscsi.discovery.out -i your_eth_device and then send that iscsi.discovery.out file. It will show us what the target is sending on the wire too. Both of those files will have passwords in them if you have CHAP settings still being used, so send me them in private or edit out the values if you do not want them on the open. -- Jeff Bye Graphics Coordinator Liberty Post 12910 Culver Blvd. Suite G Los Angeles, CA 90066 (310) 314-3900 x247 -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Initiator name missing
The iscsid.conf values are the defaults one used to setup the port/node/target db. If you clear the iscsid.conf values, you would still need to update the db ones for it to take effect on existing targets you have already setup. For the discovery values you can either delete the old discovery record: iscsiadm -m discoverydb -t st -p ip -o delete When you run the discovery command next, then it will use the iscsid.conf settings to create the discovery record. or if your tools does not support that command you can clear the chap settings iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.username -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.password -v iscsiadm -m discoverydb -t st -p ip -o update -n discovery.sendtargets.auth.authmethod -v none On 01/03/2013 01:46 PM, Jeff Bye wrote: Hey! I've been out of town for a couple of weeks. Hope you had a chance to take some time off as well :) It seems that the username and password I had initially set up is still being used, however in iscsid.conf CHAP is set to none and any other information has been commented. Does this only affect the target side? Jeff When I had it running on a windows machine (a temporary setup) we kept it open and On Fri, Dec 21, 2012 at 1:32 AM, Mike Christie micha...@cs.wisc.edu mailto:micha...@cs.wisc.edu wrote: On 12/20/2012 06:54 PM, GGL wrote: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target Yeah, this is a CHAP failure. Is it turned off on the target too? Could you run sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 -d 8 and send all the output? Also while running this command run: tcpdump -w iscsi.discovery.out -i your_eth_device and then send that iscsi.discovery.out file. It will show us what the target is sending on the wire too. Both of those files will have passwords in them if you have CHAP settings still being used, so send me them in private or edit out the values if you do not want them on the open. -- Jeff Bye Graphics Coordinator Liberty Post 12910 Culver Blvd. Suite G Los Angeles, CA 90066 (310) 314-3900 x247 -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Initiator name missing
On 12/20/2012 06:54 PM, GGL wrote: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target Yeah, this is a CHAP failure. Is it turned off on the target too? Could you run sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 -d 8 and send all the output? Also while running this command run: tcpdump -w iscsi.discovery.out -i your_eth_device and then send that iscsi.discovery.out file. It will show us what the target is sending on the wire too. Both of those files will have passwords in them if you have CHAP settings still being used, so send me them in private or edit out the values if you do not want them on the open. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Initiator name missing
Hey Mike, Here is a link to /var/log/messages (was disabled in this distro's conf, oddly enough) and /etc/init.d/open-iscsi - if you were local I'd have beer coming your way. I'm having trouble uploading files here so I opted to just host it elsewhere. http://www.sendspace.com/file/2iyali Here's what I've got: deadlineserver@deadlineserver ~ $ lsmod | grep iscsi_tcp iscsi_tcp 18587 0 libiscsi_tcp 25115 1 iscsi_tcp libiscsi 57546 3 ib_iser,iscsi_tcp,libiscsi_tcp scsi_transport_iscsi53735 4 ib_iser,iscsi_tcp,libiscsi *modprobe iscsi_tcp returns with nothing, even when verbose deadlineserver@deadlineserver ~ $ iscsid -d 8 -f [1] 2132 deadlineserver@deadlineserver ~ $ iscsid: sysfs_init: sysfs_path='/sys' iscsid: sysfs_attr_get_value: open '/module/scsi_transport_iscsi'/'version' iscsid: sysfs_attr_get_value: new uncached attribute '/sys/module/scsi_transport_iscsi/version' iscsid: sysfs_attr_get_value: add to cache '/sys/module/scsi_transport_iscsi/version' iscsid: sysfs_attr_get_value: cache '/sys/module/scsi_transport_iscsi/version' with attribute value '2.0-870' iscsid: transport class version 2.0-870. iscsid version 2.0-871 iscsid: Can not bind IPC socket iscsid: in ctldev_close Thanks! Jeff On Wednesday, December 19, 2012 5:37:17 PM UTC-8, Mike Christie wrote: I do not have access to that exact code. After the failure could you do lsmod | grep iscsi_tcp If that module is not loaded, could you do modprobe iscsi_tcp If that fails send the /var/log/messages output. Could you also send me the /etc/init.d/open-iscsi file? Could you also try maually starting the daemon. 1. modprobe iscsi_tcp 2. iscsid -d 8 -f // send all the output of the iscsid command above if that fails. On 12/19/2012 06:25 PM, GGL wrote: After checking the version and initiatorname.iscsi file I came up with the following: Version= open-iscsi/precise uptodate 2.0.871-0ubuntu9.12.04.1 initiatorname.iscsi file= InitiatorName=iqn.1993-08.org.debian:01:80d25ebdbe87 I've changed it to= InitiatorName=iqn.1993-08.org.deadlineserver: I'm surprised drobo doesn't have a more direct resource for this! Same error message is popping up when I attempt to start open-iscsi (initiatorname.iscsi missing) Thanks! Jeff On Wednesday, December 19, 2012 11:49:16 AM UTC-8, Mike Christie wrote: What version of open-iscsi is this? What is in the /etc/iscsi/initiatorname.iscsi file? cat /etc/iscsi/initiatorname.iscsi Is there something like InitiatorName=iqn.2001-12.somename.somethingelse ? If not then does your distro have a iscsiname or iscsi-iname tool? If not then just add a name to that file. The InitiatorName= is required. After that, add something like InitiatorName=iqn.2012-12.com.your_hostname:something_unique That name must be unique for each initiator you have. So every box you have iscsi installed on must have a different name. On 12/19/2012 12:01 PM, GGL wrote: Oops! I spaced on pasting that rather important part of the problem. The error comes when attempting to start: /etc/init.d/open-iscsi start * Starting iSCSI initiator service iscsid * Error: InitiatorName file /etc/iscsi/initiatorname.iscsi is missing! * The iSCSI driver has not been correctly installed and cannot start. Thanks again! It's much appreciated. Jeff On Tuesday, December 18, 2012 11:20:04 AM UTC-8, GGL wrote: Hi everyone, I'm having a few issues with the setup, specifically: InitiatorName file /etc/iscsi/initiatorname.iscsi is missing! *I'm able to see this file when I browse to /etc/iscsi/ so I'm a bit lost there. I found this to be an issue when troubleshooting the following message: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target iscsiadm: discovery login to 10.10.0.1 failed, giving up iscsiadm: Could not perform SendTargets discovery. My linux knowledge isn't the greatest as I work in entertainment industry post-production facilities generally, so my apologies in advance if I'm missing a rather obvious step. Jeff -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit
Re: Initiator name missing
On 12/18/2012 12:20 PM, GGL wrote: Hi everyone, I'm having a few issues with the setup, specifically: InitiatorName file /etc/iscsi/initiatorname.iscsi is missing! *I'm able to see this file when I browse to /etc/iscsi/ so I'm a bit lost there. I found this to be an issue when troubleshooting the following message: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target Hey, So many issues here :) So if you just run iscsid (without the extra arguments) does it work ok now? Are you just seeing the error above when you run that discovery command? That command above means that something is trying to use CHAP. Did you setup CHAP on the target or initiator side (set some sort of username or password to be able to access the target)? On the initiator side to setup chap you have to set the username/password and/or username_in/pasword_in settings in /etc/iscsid.conf. Maybe to make it simple start by not using CHAP. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Initiator name missing
Ahh right - I'm trying to keep this connection as open as possible as it will have many connections over a private network (using an iSCSI Drobo as storage for a render farm). I've commented any lines regarding CHAP and tried again: deadlineserver@deadlineserver ~ $ sudo /etc/init.d/open-iscsi start * Setting up iSCSI targets [ OK ] Good sign! Unfortunately I'm still getting the same result: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target iscsiadm: discovery login to 10.10.0.1 failed, giving up iscsiadm: Could not perform SendTargets discovery. I really appreciate the effort you've put into helping me as a total stranger so I'll understand if it becomes a bit too much. Jeff On Thursday, December 20, 2012 12:42:57 PM UTC-8, Mike Christie wrote: On 12/18/2012 12:20 PM, GGL wrote: Hi everyone, I'm having a few issues with the setup, specifically: InitiatorName file /etc/iscsi/initiatorname.iscsi is missing! *I'm able to see this file when I browse to /etc/iscsi/ so I'm a bit lost there. I found this to be an issue when troubleshooting the following message: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target Hey, So many issues here :) So if you just run iscsid (without the extra arguments) does it work ok now? Are you just seeing the error above when you run that discovery command? That command above means that something is trying to use CHAP. Did you setup CHAP on the target or initiator side (set some sort of username or password to be able to access the target)? On the initiator side to setup chap you have to set the username/password and/or username_in/pasword_in settings in /etc/iscsid.conf. Maybe to make it simple start by not using CHAP. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/z8nAakz0-scJ. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Initiator name missing
On 12/18/2012 12:20 PM, GGL wrote: Hi everyone, I'm having a few issues with the setup, specifically: InitiatorName file /etc/iscsi/initiatorname.iscsi is missing! *I'm able to see this file when I browse to /etc/iscsi/ so I'm a bit lost there. I found this to be an issue when troubleshooting the following message: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target iscsiadm: discovery login to 10.10.0.1 failed, giving up iscsiadm: Could not perform SendTargets discovery. Where are you seeing the initiatorname missing error? I think you just need to have iscsid started. That is started different in each distro. A lot of time you just need to do something like /etc/init.d/iscsid start or /etc/init.d/open-iscsi start then run the discovery command. In other distros running the iscsiadm command will start iscsid for you. Check that it is up before running the iscsiadm command ps -u root | grep iscsid -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Initiator name missing
Oops! I spaced on pasting that rather important part of the problem. The error comes when attempting to start: /etc/init.d/open-iscsi start * Starting iSCSI initiator service iscsid * Error: InitiatorName file /etc/iscsi/initiatorname.iscsi is missing! * The iSCSI driver has not been correctly installed and cannot start. Thanks again! It's much appreciated. Jeff On Tuesday, December 18, 2012 11:20:04 AM UTC-8, GGL wrote: Hi everyone, I'm having a few issues with the setup, specifically: InitiatorName file /etc/iscsi/initiatorname.iscsi is missing! *I'm able to see this file when I browse to /etc/iscsi/ so I'm a bit lost there. I found this to be an issue when troubleshooting the following message: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target iscsiadm: discovery login to 10.10.0.1 failed, giving up iscsiadm: Could not perform SendTargets discovery. My linux knowledge isn't the greatest as I work in entertainment industry post-production facilities generally, so my apologies in advance if I'm missing a rather obvious step. Jeff -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/CACdXLdcbzAJ. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Initiator name missing
After checking the version and initiatorname.iscsi file I came up with the following: Version= open-iscsi/precise uptodate 2.0.871-0ubuntu9.12.04.1 initiatorname.iscsi file= InitiatorName=iqn.1993-08.org.debian:01:80d25ebdbe87 I've changed it to= InitiatorName=iqn.1993-08.org.deadlineserver: I'm surprised drobo doesn't have a more direct resource for this! Same error message is popping up when I attempt to start open-iscsi (initiatorname.iscsi missing) Thanks! Jeff On Wednesday, December 19, 2012 11:49:16 AM UTC-8, Mike Christie wrote: What version of open-iscsi is this? What is in the /etc/iscsi/initiatorname.iscsi file? cat /etc/iscsi/initiatorname.iscsi Is there something like InitiatorName=iqn.2001-12.somename.somethingelse ? If not then does your distro have a iscsiname or iscsi-iname tool? If not then just add a name to that file. The InitiatorName= is required. After that, add something like InitiatorName=iqn.2012-12.com.your_hostname:something_unique That name must be unique for each initiator you have. So every box you have iscsi installed on must have a different name. On 12/19/2012 12:01 PM, GGL wrote: Oops! I spaced on pasting that rather important part of the problem. The error comes when attempting to start: /etc/init.d/open-iscsi start * Starting iSCSI initiator service iscsid * Error: InitiatorName file /etc/iscsi/initiatorname.iscsi is missing! * The iSCSI driver has not been correctly installed and cannot start. Thanks again! It's much appreciated. Jeff On Tuesday, December 18, 2012 11:20:04 AM UTC-8, GGL wrote: Hi everyone, I'm having a few issues with the setup, specifically: InitiatorName file /etc/iscsi/initiatorname.iscsi is missing! *I'm able to see this file when I browse to /etc/iscsi/ so I'm a bit lost there. I found this to be an issue when troubleshooting the following message: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target iscsiadm: discovery login to 10.10.0.1 failed, giving up iscsiadm: Could not perform SendTargets discovery. My linux knowledge isn't the greatest as I work in entertainment industry post-production facilities generally, so my apologies in advance if I'm missing a rather obvious step. Jeff -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/CACdXLdcbzAJ. To post to this group, send email to open-...@googlegroups.comjavascript:. To unsubscribe from this group, send email to open-iscsi+...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/rEc5T3EoZe0J. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Initiator name missing
I do not have access to that exact code. After the failure could you do lsmod | grep iscsi_tcp If that module is not loaded, could you do modprobe iscsi_tcp If that fails send the /var/log/messages output. Could you also send me the /etc/init.d/open-iscsi file? Could you also try maually starting the daemon. 1. modprobe iscsi_tcp 2. iscsid -d 8 -f // send all the output of the iscsid command above if that fails. On 12/19/2012 06:25 PM, GGL wrote: After checking the version and initiatorname.iscsi file I came up with the following: Version= open-iscsi/precise uptodate 2.0.871-0ubuntu9.12.04.1 initiatorname.iscsi file= InitiatorName=iqn.1993-08.org.debian:01:80d25ebdbe87 I've changed it to= InitiatorName=iqn.1993-08.org.deadlineserver: I'm surprised drobo doesn't have a more direct resource for this! Same error message is popping up when I attempt to start open-iscsi (initiatorname.iscsi missing) Thanks! Jeff On Wednesday, December 19, 2012 11:49:16 AM UTC-8, Mike Christie wrote: What version of open-iscsi is this? What is in the /etc/iscsi/initiatorname.iscsi file? cat /etc/iscsi/initiatorname.iscsi Is there something like InitiatorName=iqn.2001-12.somename.somethingelse ? If not then does your distro have a iscsiname or iscsi-iname tool? If not then just add a name to that file. The InitiatorName= is required. After that, add something like InitiatorName=iqn.2012-12.com.your_hostname:something_unique That name must be unique for each initiator you have. So every box you have iscsi installed on must have a different name. On 12/19/2012 12:01 PM, GGL wrote: Oops! I spaced on pasting that rather important part of the problem. The error comes when attempting to start: /etc/init.d/open-iscsi start * Starting iSCSI initiator service iscsid * Error: InitiatorName file /etc/iscsi/initiatorname.iscsi is missing! * The iSCSI driver has not been correctly installed and cannot start. Thanks again! It's much appreciated. Jeff On Tuesday, December 18, 2012 11:20:04 AM UTC-8, GGL wrote: Hi everyone, I'm having a few issues with the setup, specifically: InitiatorName file /etc/iscsi/initiatorname.iscsi is missing! *I'm able to see this file when I browse to /etc/iscsi/ so I'm a bit lost there. I found this to be an issue when troubleshooting the following message: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target iscsiadm: discovery login to 10.10.0.1 failed, giving up iscsiadm: Could not perform SendTargets discovery. My linux knowledge isn't the greatest as I work in entertainment industry post-production facilities generally, so my apologies in advance if I'm missing a rather obvious step. Jeff -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/CACdXLdcbzAJ https://groups.google.com/d/msg/open-iscsi/-/CACdXLdcbzAJ. To post to this group, send email to open-...@googlegroups.com javascript:. To unsubscribe from this group, send email to open-iscsi+...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en http://groups.google.com/group/open-iscsi?hl=en. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/rEc5T3EoZe0J. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Initiator name missing
Hi everyone, I'm having a few issues with the setup, specifically: InitiatorName file /etc/iscsi/initiatorname.iscsi is missing! *I'm able to see this file when I browse to /etc/iscsi/ so I'm a bit lost there. I found this to be an issue when troubleshooting the following message: deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 iscsiadm: Login authentication failed with target iscsiadm: discovery login to 10.10.0.1 failed, giving up iscsiadm: Could not perform SendTargets discovery. My linux knowledge isn't the greatest as I work in entertainment industry post-production facilities generally, so my apologies in advance if I'm missing a rather obvious step. Jeff -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/d4R529H7tJoJ. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
