What my final solution is to disable the rcS.d and just call it in rc.local after a sleep 5. This was the only way to be 100% sure that no errors were present at the log. If I didn't do any sleep, it worked but there was still an error first, and then 2 seconds later everything was ok.
My VPS host told me that it's probably because the IPv6 address is received from network while the IPv4 address is manually specified. So it might take a few seconds to get the address. I guess the problem is either: 1. iscsi is testing for _any_ network connectivity, so when IPv4 is ready then it tries to connect even though the IPv6 isn't. A fix would be to test using the actual interface, not just using any network connectivity (might be hard to implement). 2. Or yes, an alternative fix might be to just increase the tryout number. 3. Or maybe what's happening is that since the interface doesn't exists it doesn't starts trying again, but terminates the whole process, since there was no interface at that time. I guess this was happening in my case. Also, there is a bug in the Debian package, `modprobe scsi_transport_iscsi` is missing, while the other 2 modprobes are present. It'll take some time for everyone trying to install iscsi to figure out that this modprobe is missing and you have to add it manually to /etc/modules. Also, making a change like this permanent in modules isn't really an elegant solution, so adding that line in the Deb 6 packages would be important. Are the maintainers present on this forum? Sending a bug report for Debian is such a hassle, I'd be happy if I could just reach them here. Regards, Zsolt On 8 January 2013 23:03, Mike Christie <[email protected]> wrote: > On 01/08/2013 05:39 AM, [email protected] wrote: > > I'm having problem configuring open-iscsi on Debian 6 to automatically > > start-up. I've configured everything and if I manually run *invoke-rc.d > > open-iscsi restart* then it runs fine! > > > > However after a simple reboot, nothing happens. This is the log in the > > daemon.log / syslog: > > > > Jan 8 11:31:51 ssdkvm iscsid: iSCSI logger with pid=1985 started! > > Jan 8 11:31:52 ssdkvm iscsid: transport class version 2.0-870. iscsid > > version 2.0-871 > > Jan 8 11:31:52 ssdkvm iscsid: iSCSI daemon with pid=1986 started! > > Jan 8 11:31:53 ssdkvm iscsid: connection1:0 is operational now > > ..... > > Jan 8 11:32:18 ssdkvm iscsid: transport class version 2.0-870. iscsid > > version 2.0-871 > > Jan 8 11:32:18 ssdkvm iscsid: iSCSI daemon with pid=929 started! > > *Jan 8 11:32:18 ssdkvm iscsid: cannot make a connection to 2a00:..... > > (-1,101)* > > * > > * > > Why is this happening? Is the network not up when this line is present? > > Probably. It might be coming up. 101 is ENETUNREACH "Network is > unreachable", so the networking might be coming up while is also > starting up. > > It might be that by the time you can log in and run commands, the > network is up so your invoke call then works. > > Does Your iscsid.conf have the setting initial_login_retry_max? You can > try increasing this. Make sure that you have disabled remove invalid > portals that are not going to come up or we will wait on them, and also > remember to run iscsiadm -o update.... to update the existing settings > with the new value or rerun the discovery command. > > > > (possibly because of IPv6?) How can I fix it? Remove the line from rcS.d > > and append *invoke-rc.d open-iscsi start *to rc.local? > > > > Regards, > > Zsolt > > > > > > > > > > > > > > > > -- > > 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/-/gMNaQs8I6lsJ. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
