Service Unavailable

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
the_extremist
Posts: 14
Joined: Thu Jan 06, 2022 11:51 am

Mon May 23, 2022 1:53 pm

Hello, I have a problem. I Have two nodes with StarWind vSan Free. The same nodes are connected to by ms iscsi to each other and by local. I have about 15 HA Images and every thing works fine to this day.
We had a problem with power, ups died after two hours and now I have a problem with connected by iscsi to the nodes.

This is the screen from NODE-01, all connections are inactive
Image

On the NODE-02 I see connected by NODE-01 ??? Whats wrong with it ?

Image

I Cannot connected from NODE-01 to StarWind NODE-01. I get an error "Service Unavailable".
Below logs

Image

--------------------
UPDATE

I create a new HA Image and it's works fine. Synchro after reboot two nodes start normally but only on the new HA image.
How to start it manually or something ?

Image
yaroslav (staff)
Staff
Posts: 2361
Joined: Mon Nov 18, 2019 11:11 am

Mon May 23, 2022 4:04 pm

Greetings,

The HA devices must be not synchronized on one side. Check the management console, please. Do you see NOT SYNCHRONIZED on one node or both? If you see not synchronized on both nodes, please see https://knowledgebase.starwindsoftware. ... -blackout/.
On the NODE-02 I see connected by NODE-01 ??? Whats wrong with it ?
The identifiers you are referring to are StarWind identifiers. They mean that HA devices have connections over Synchronization and iSCSI links. Not synchronized devices cannot be accessed by MS iSCSI Initiator and do not have the MS iSCSI IQN on the list (i.e., iqn.1991-05.com.microsoft...).
I create a new HA Image and it's works fine. Synchro after reboot two nodes start normally but only on the new HA image.
How to start it manually or something ?
You need to start synchronization using the SyncHaDevice script.
NOTE: it marks the side where run as synchronized. Use it carefully according to this article https://knowledgebase.starwindsoftware. ... -blackout/.
Mutual not synchronized status may be related to write-back cache. See how to disable it here https://knowledgebase.starwindsoftware. ... -l1-cache/.

Also, please make sure to use the latest available StarWind VSAN Build.
the_extremist
Posts: 14
Joined: Thu Jan 06, 2022 11:51 am

Mon May 23, 2022 4:38 pm

Hello, thanks for your reply.

I see NOT SYNCHRONIZED on both side, but I use free edition. Is there any power shell script to do the same as gui ?
yaroslav (staff)
Staff
Posts: 2361
Joined: Mon Nov 18, 2019 11:11 am

Mon May 23, 2022 6:28 pm

Hi,

Yes, plese see my previous post.
You need to start synchronization using the SyncHaDevice script.
NOTE: it marks the side where run as synchronized. Use it carefully according to this article https://knowledgebase.starwindsoftware. ... -blackout/
Mutual not synchronized status may be related to write-back cache. See how to disable it here https://knowledgebase.starwindsoftware. ... rinciples/

Also, please make sure to use the latest available StarWind VSAN Build.
the_extremist
Posts: 14
Joined: Thu Jan 06, 2022 11:51 am

Thu Jul 28, 2022 2:53 pm

Hello, this is the result of SyncHaDevice script.

Image

This happend on both nodes.

Code: Select all

param($addr="127.0.0.1", $port=3261, $user="root", $password="starwind", $deviceName="HAImage1")

Import-Module StarWindX

try
{
	Enable-SWXLog

	$server = New-SWServer $addr $port $user $password

	$server.Connect()

	$device = Get-Device $server -name $deviceName
	if( !$device )
	{
		Write-Host "Device not found" -foreground red
		return
	}

	if($device.SyncStatus -ne [SwHaSyncStatus]::SW_HA_SYNC_STATUS_SYNC)
	{
		Write-Host "Synchronize device $($device.name)" -foreground yellow
		$device.Synchronize([SwHaSyncType]::SW_HA_SYNC_FULL, "")
		#$device.MarkAsSynchronized()
	}
	else
	{
		Write-Host "Device $($device.name) is synchronized" -foreground yellow
	}
}
catch
{
	Write-Host $_ -foreground red
}
finally
{
	$server.Disconnect()
}
pause
This is the status on both nodes

Image
the_extremist
Posts: 14
Joined: Thu Jan 06, 2022 11:51 am

Fri Jul 29, 2022 6:16 am

Anyone ?
yaroslav (staff)
Staff
Posts: 2361
Joined: Mon Nov 18, 2019 11:11 am

Fri Jul 29, 2022 6:47 am

Is other node showing as synchronized?
the_extremist
Posts: 14
Joined: Thu Jan 06, 2022 11:51 am

Fri Jul 29, 2022 9:52 am

Noo, there is the same status as you see on both nodes.
SyncHaDevice script not working, error as you see
yaroslav (staff)
Staff
Posts: 2361
Joined: Mon Nov 18, 2019 11:11 am

Fri Jul 29, 2022 10:13 am

Please try stopping the service and run the script on the node you believe to carry the up-to-date data.
the_extremist
Posts: 14
Joined: Thu Jan 06, 2022 11:51 am

Fri Jul 29, 2022 10:23 am

Services stopped on node-01. On the node-2 I try to run script, but it didn't work.

Image
yaroslav (staff)
Staff
Posts: 2361
Joined: Mon Nov 18, 2019 11:11 am

Fri Jul 29, 2022 12:39 pm

Run the script locally, please.
the_extremist
Posts: 14
Joined: Thu Jan 06, 2022 11:51 am

Fri Jul 29, 2022 1:53 pm

Done, now I have something like this :

Image

What is the next step ?
yaroslav (staff)
Staff
Posts: 2361
Joined: Mon Nov 18, 2019 11:11 am

Fri Jul 29, 2022 2:55 pm

You can see the process of remediating the power outage in this KB https://knowledgebase.starwindsoftware. ... -blackout/.
You were running the script for HAImage1, not HAImage3. From what I see, the target of HAImage3 is missing the corresponding device on SRV-NODE-01. Please check if the device is present on the underlying storage. I'd like to mention that the default script does not remove the disk or replication partner. This is why I'd like to have the logs for both nodes collected with Log Collector https://knowledgebase.starwindsoftware. ... collector/

You ran the script for one device out of three. You need to run it for other devices.
NOTE: it marks the side where run as synchronized. Use it carefully according to this article https://knowledgebase.starwindsoftware. ... -blackout/
Mutual not synchronized status may be related to write-back cache (see operating principles https://knowledgebase.starwindsoftware. ... rinciples/).
EDIT: See how to disable write back cache here https://knowledgebase.starwindsoftware. ... -l1-cache/
Post Reply