Lots of trouble with 3.5.1
Posted: Sun Dec 02, 2007 6:18 pm
He guy's from Rocket Division got some work for you 
First thing I see (and its been there in earlier versions) is that when I remove the default 'localhost:3260' connection in the GUI -> make a new connection instead -> exit the GUI and start it again the default connection is there again together with my own connection.
Second I'm using different control and iSCSI IP's. This is how I configured the relevant part of starwind.cfg:
<connections>
<!--Port number for iSCSI connectons (default 3260)-->
<Port value="3260"/>
<!--Interface to listen to. "0.0.0.0" corresponds to "listen to all interfaces".-->
<Interface value="192.168.11.17"/>
<!--Port number for Control connectons (default 3261)-->
<!-- <CtlPort value="3261"/> -->
<!--Interface to listen to Control connections. "0.0.0.0" corresponds to "listen to all interfaces".-->
<CtlInterface value="192.168.10.17"/>
</connections>
I am able to telnet into the control connection (see relevant part of the log):
12/2 19:18:52.684 6dc conf: Waiting for Control connections at 192.168.10.17:3261 ...
12/2 19:18:52.684 63c Srv: Waiting for iSCSI connections at 192.168.11.17:3260 ...
12/2 19:19:34.331 6dc conf: Accepted control connection from 192.168.10.17:1068.
12/2 19:19:37.828 71c conf: Control connection is closed.
However I'm unable to use the GUI to connect to the control port (192.168.10.17:3261). Here's the GUI log;
18:30:43:841 (144) App: Staring the application...
18:30:43:857 (144) App: Loaded 'English (United States)' resource dll.
18:30:44:029 (144) Doc: Loaded connection 'localhost:3260'.
18:30:48:344 (144) Doc: Removing connection 'localhost:3260'...
18:30:57:426 (144) Doc: Adding connection '192.168.10.17:3261' ...
18:30:59:349 (144) P: '192.168.10.17:3261' <<< login
18:30:59:365 (144) P: Connecting to '192.168.10.17:3261'...
18:31:00:459 (144) P: '192.168.10.17:3261' panic!
18:31:00:506 (144) P: '192.168.10.17:3261' <<< logoff
18:31:00:506 (144) P: '192.168.10.17:3261' panic!
18:31:00:506 (144) P: '192.168.10.17:3261' >>> logoff reply '105 '
18:31:00:506 (144) P: '192.168.10.17:3261' >>> logoff reply '105 '
18:31:00:506 (144) P: '192.168.10.17:3261' disconnecting...
18:31:00:506 (144) P: '192.168.10.17:3261' panic!
18:31:00:506 (144) P: Disconnect failed: An operation was attempted on something that is not a socket.
18:31:00:506 (144) P: '192.168.10.17:3261' panic!
B.t.w. there's a spelling error at line 1, should be 'Starting the application...'
And than the GUI crashes!
Now I swear that there was a time when I had this working. After all I was the guy that requested the possibility for a different IP address for the control channel.
Last issue is that I can see no difference between the different logging levels in the GUI, you know the tab 'Logging' on the 'StarWind Preferences' screen.
Best regards,
Han Valk.

First thing I see (and its been there in earlier versions) is that when I remove the default 'localhost:3260' connection in the GUI -> make a new connection instead -> exit the GUI and start it again the default connection is there again together with my own connection.
Second I'm using different control and iSCSI IP's. This is how I configured the relevant part of starwind.cfg:
<connections>
<!--Port number for iSCSI connectons (default 3260)-->
<Port value="3260"/>
<!--Interface to listen to. "0.0.0.0" corresponds to "listen to all interfaces".-->
<Interface value="192.168.11.17"/>
<!--Port number for Control connectons (default 3261)-->
<!-- <CtlPort value="3261"/> -->
<!--Interface to listen to Control connections. "0.0.0.0" corresponds to "listen to all interfaces".-->
<CtlInterface value="192.168.10.17"/>
</connections>
I am able to telnet into the control connection (see relevant part of the log):
12/2 19:18:52.684 6dc conf: Waiting for Control connections at 192.168.10.17:3261 ...
12/2 19:18:52.684 63c Srv: Waiting for iSCSI connections at 192.168.11.17:3260 ...
12/2 19:19:34.331 6dc conf: Accepted control connection from 192.168.10.17:1068.
12/2 19:19:37.828 71c conf: Control connection is closed.
However I'm unable to use the GUI to connect to the control port (192.168.10.17:3261). Here's the GUI log;
18:30:43:841 (144) App: Staring the application...
18:30:43:857 (144) App: Loaded 'English (United States)' resource dll.
18:30:44:029 (144) Doc: Loaded connection 'localhost:3260'.
18:30:48:344 (144) Doc: Removing connection 'localhost:3260'...
18:30:57:426 (144) Doc: Adding connection '192.168.10.17:3261' ...
18:30:59:349 (144) P: '192.168.10.17:3261' <<< login
18:30:59:365 (144) P: Connecting to '192.168.10.17:3261'...
18:31:00:459 (144) P: '192.168.10.17:3261' panic!
18:31:00:506 (144) P: '192.168.10.17:3261' <<< logoff
18:31:00:506 (144) P: '192.168.10.17:3261' panic!
18:31:00:506 (144) P: '192.168.10.17:3261' >>> logoff reply '105 '
18:31:00:506 (144) P: '192.168.10.17:3261' >>> logoff reply '105 '
18:31:00:506 (144) P: '192.168.10.17:3261' disconnecting...
18:31:00:506 (144) P: '192.168.10.17:3261' panic!
18:31:00:506 (144) P: Disconnect failed: An operation was attempted on something that is not a socket.
18:31:00:506 (144) P: '192.168.10.17:3261' panic!
B.t.w. there's a spelling error at line 1, should be 'Starting the application...'

And than the GUI crashes!
Now I swear that there was a time when I had this working. After all I was the guy that requested the possibility for a different IP address for the control channel.
Last issue is that I can see no difference between the different logging levels in the GUI, you know the tab 'Logging' on the 'StarWind Preferences' screen.
Best regards,
Han Valk.