3.5.3 crashes on server 2008.

bfuchs · Wed Mar 26, 2008 10:38 am

Hi.

Have installed StarWind 3.5.3 on a server 2008 and are having an issue where the service is crashing.
It seems to crash when the ESX servers are loosing their network connection and have to connect again.

The Log file Shows.

3/25 21:46:22.795 f80 Params: <<< String param 'TargetName': received 'vi3-raid5', accepted 'vi3-raid5'
3/25 21:46:22.795 f80 Params: <<< Enum param 'SessionType': received 'Normal', accepted 'Normal'
3/25 21:46:22.795 f80 Params: <<< Enum param 'AuthMethod': received 'CHAP,None', accepted 'CHAP'
3/25 21:46:22.795 524 debug: The program encountered a serious error and may be closed. Crash dump will be created.
3/25 21:46:22.795 524 debug: Please, send this log file and the crash dump to 'support@starwind.com'.
3/25 21:46:22.795 f80 Tgt: : open 'vi3-raid5': 2 session(s) opened, 65534 more allowed.
3/25 21:46:22.795 f80 Params: <<< Enum param 'AuthMethod': received 'CHAP,None', accepted 'CHAP'
3/25 21:46:22.795 f80 T[1]: CHAP authentication selected.
3/25 21:46:22.795 f80 Params: >>> AuthMethod=CHAP.
3/25 21:46:22.795 f80 Params: >>> TargetPortalGroupTag=1.
3/25 21:46:22.795 f80 Params: <<< Enum param 'CHAP_A': received '5', accepted '5'
3/25 21:46:22.795 f80 Params: >>> CHAP_A=5.
3/25 21:46:22.795 f80 Params: >>> CHAP_I=2.
3/25 21:46:22.795 f80 Params: >>> CHAP_C=0bR7jeiy/1HWSEFiNG509+2UW5aniVA7ekuh+nsi/SjbY=.
3/25 21:46:22.795 f80 Params: <<< String param 'CHAP_N': received 'vi3rawdevice', accepted 'vi3rawdevice'
3/25 21:46:22.795 f80 Params: <<< String param 'CHAP_R': received '0x4b91165a193dc0467197570c6f582f07', accepted '0x4b91165a193dc0467197570c6f582f07'
3/25 21:46:22.795 150 T[1]: session 0x8, connection 0x8 : end of stage 0, next stage 1.
3/25 21:46:22.795 f80 Params: <<< Enum param 'HeaderDigest': received 'None,CRC32C', accepted 'None'
3/25 21:46:22.795 f80 Params: <<< Enum param 'DataDigest': received 'None,CRC32C', accepted 'None'
3/25 21:46:22.795 f80 Params: <<< Numeric param 'MaxRecvDataSegmentLength': received 131072, accepted 131072
3/25 21:46:22.795 f80 Params: <<< Numeric param 'DefaultTime2Wait': received 0, accepted 0
3/25 21:46:22.795 f80 Params: <<< Numeric param 'DefaultTime2Retain': received 0, accepted 0
3/25 21:46:22.795 f80 Params: <<< Numeric param 'ErrorRecoveryLevel': received 0, accepted 0
3/25 21:46:22.795 f80 Params: <<< Boolean param 'IFMarker': received No, accepted 0
3/25 21:46:22.795 f80 Params: <<< Boolean param 'OFMarker': received No, accepted 0
3/25 21:46:22.795 f80 Params: <<< Boolean param 'InitialR2T': received No, accepted 0
3/25 21:46:22.795 f80 Params: <<< Boolean param 'ImmediateData': received Yes, accepted 1
3/25 21:46:22.795 f80 Params: <<< Numeric param 'MaxBurstLength': received 16776192, accepted 262144
3/25 21:46:22.795 f80 Params: <<< Numeric param 'FirstBurstLength': received 262144, accepted 262144
3/25 21:46:22.795 f80 Params: <<< Numeric param 'MaxOutstandingR2T': received 1, accepted 1
3/25 21:46:22.795 f80 Params: <<< Numeric param 'MaxConnections': received 1, accepted 1
3/25 21:46:22.795 f80 Params: <<< Boolean param 'DataPDUInOrder': received Yes, accepted 1
3/25 21:46:22.795 f80 Params: <<< Boolean param 'DataSequenceInOrder': received Yes, accepted 1
3/25 21:46:22.795 f80 Params: <<< Unknown key 'X-com.cisco.PingTimeout' with value: '5'
3/25 21:46:22.795 f80 Params: <<< Unknown key 'X-com.cisco.sendAsyncText' with value: 'No'
3/25 21:46:22.795 f80 Params: <<< Unknown key 'X-com.cisco.protocol' with value: 'draft20'
3/25 21:46:22.795 f80 Params: >>> ErrorRecoveryLevel=0.
3/25 21:46:22.795 f80 Params: >>> MaxConnections=1.
3/25 21:46:22.795 f80 Params: >>> HeaderDigest=None.
3/25 21:46:22.795 f80 Params: >>> DataDigest=None.
3/25 21:46:22.795 f80 Params: >>> OFMarker=No.
3/25 21:46:22.795 f80 Params: >>> IFMarker=No.
3/25 21:46:22.795 f80 Params: >>> InitialR2T=No.
3/25 21:46:22.795 f80 Params: >>> ImmediateData=Yes.
3/25 21:46:22.795 f80 Params: >>> MaxRecvDataSegmentLength=262144.
3/25 21:46:22.795 f80 Params: >>> MaxBurstLength=262144.
3/25 21:46:22.795 f80 Params: >>> FirstBurstLength=262144.
3/25 21:46:22.795 f80 Params: >>> DefaultTime2Wait=0.
3/25 21:46:22.795 f80 Params: >>> DefaultTime2Retain=0.
3/25 21:46:22.795 f80 Params: >>> MaxOutstandingR2T=1.
3/25 21:46:22.795 f80 Params: >>> DataPDUInOrder=Yes.
3/25 21:46:22.795 f80 Params: >>> DataSequenceInOrder=Yes.
3/25 21:46:22.795 f80 Params: >>> X-com.cisco.PingTimeout=NotUnderstood.
3/25 21:46:22.795 f80 Params: >>> X-com.cisco.sendAsyncText=NotUnderstood.
3/25 21:46:22.795 f80 Params: >>> X-com.cisco.protocol=NotUnderstood.
3/25 21:46:22.795 150 T[1]: session 0x8, connection 0x8 : end of stage 1, next stage 3.
3/25 21:46:22.795 150 C[8], IN_LOGIN: Event - LOGIN_ACCEPT.
3/25 21:46:22.795 150 C[8], LIN: T5.
3/25 21:46:24.262 524 debug: Minidump 'C:\Program Files\Rocket Division Software\StarWind\starwind.20080325.214622.mdmp' created successfully.

aaron (staff) · Wed Mar 26, 2008 8:38 pm

We've got the same bugreport over the e-mail and analyzing the logs. We'll let you know when we'll have a solution. ASAP of course

Thank you!