Page 1 of 1

Second node sync Error

Posted: Fri Jan 23, 2015 10:26 am
by byty114
Hi,
I have 2 nodes Starwind configuraion.
On the Seconday node i have some errors, can you help me with some infromations?

1/17 21:42:26.451 a6c HA: CDistributedSyncCriticalSection::PushCommandFromSharer: (CSid = 0xCCC1) sharerID = 0xD0, cmdID = 1, result = BUSY (section is busy now).
1/17 21:42:26.451 c0 HA: CDistributedSyncCriticalSection::EnterOnTheDistributeSharersSide: (CSid = 0xCCC1) ENTER command on dist sharer(Id = 0xD0) can't be complete. Sharer return BUSY.
1/17 21:43:01.336 a6c HA: CDistributedSyncCriticalSection::PushCommandFromSharer: (CSid = 0xCCC1) sharerID = 0xD0, cmdID = 1, result = BUSY (section is busy now).
1/17 21:43:01.336 c0 HA: CDistributedSyncCriticalSection::EnterOnTheDistributeSharersSide: (CSid = 0xCCC1) ENTER command on dist sharer(Id = 0xD0) can't be complete. Sharer return BUSY.
1/17 21:55:37.717 a6c HA: CDistributedSyncCriticalSection::PushCommandFromSharer: (CSid = 0xCCC1) sharerID = 0xD0, cmdID = 1, result = BUSY (section is busy now).
1/17 21:55:37.717 c0 HA: CDistributedSyncCriticalSection::EnterOnTheDistributeSharersSide: (CSid = 0xCCC1) ENTER command on dist sharer(Id = 0xD0) can't be complete. Sharer return BUSY.
1/17 21:57:49.167 a6c HA: CDistributedSyncCriticalSection::PushCommandFromSharer: (CSid = 0xCCC1) sharerID = 0xD0, cmdID = 1, result = BUSY (section is busy now).

Re: Second node sync Error

Posted: Fri Jan 23, 2015 1:57 pm
by byty114
Primary node has other type of errors:
1/20 18:34:07.300 1e64 HA: CNIXInitiatorISCSITransport::MountTarget: EXITing with failure, MountTargetDll failed with error code 1627!
1/20 18:34:12.090 1e88 Sw: *** ConnectPortal: An attempt to connect timed out without establishing a connection or connect was forcefully rejected.
1/20 18:34:12.090 1e88 HA: CNIXInitiatorISCSITransport::MountTarget: EXITing with failure, MountTargetDll failed with error code 1627!
1/20 18:34:13.328 1e64 Sw: *** ConnectPortal: An attempt to connect timed out without establishing a connection or connect was forcefully rejected.

Re: Second node sync Error

Posted: Mon Jan 26, 2015 3:22 pm
by Max (staff)
Hi,
To understand the issues better I need more information about the system:
1. Storage network diagram
2. StarWind version and build number
3. Underlying OS on StarWind servers
4. Symptoms of the issue, preceding events
5. License type used