StarWind iSCSI SAN
StarWind Native SAN for Hyper-V
 

Node after reboot inaccessable

Pure software-based VM-centric and flash-friendly VM storage (iSCSI, SMB3, NFS, iSER and NVMe over Fabrics) including free version. Same software embedded on StarWind ready nodes.

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

Node after reboot inaccessable

Postby Peter-s7 » Mon Mar 04, 2019 12:17 pm

Hi guys,

i did a fresh install with Version 8.5 on two Windows Server 2019 machines. After setup both nodes and creating 2 HAImages, i did a failovertest. I did a restart of the second node. After the reboot was completed, the HAImages shown as synchronized, but i am no longer able to configure the second Node.

As well using the management console to connect as trying to add a HAImage with the second node as a replication partner, the error message is the same.

Connection failed
Starwind Service not found on Host "hostname" : 3261

Any ideas?

Cheers,
Peter
Peter-s7
 
Posts: 3
Joined: Mon Mar 04, 2019 12:10 pm

Re: Node after reboot inaccessable

Postby Peter-s7 » Mon Mar 04, 2019 2:49 pm

Additional Info:

Node_1 netstat-na

TCP 172.16.44.24:139 0.0.0.0:0 LISTENING
TCP 172.16.44.24:3260 0.0.0.0:0 LISTENING
TCP 172.16.44.24:3261 0.0.0.0:0 LISTENING
TCP 172.16.44.24:3261 172.16.44.24:60230 ESTABLISHED

Node_2 netstat-na

TCP 172.16.44.25:139 0.0.0.0:0 LISTENING
TCP 172.16.44.25:3260 0.0.0.0:0 LISTENING

Something seems to be wrong with the service itself. A reboot and also running the SMI-S Agent again does not help.

Cheers,
Peter
Peter-s7
 
Posts: 3
Joined: Mon Mar 04, 2019 12:10 pm

Re: Node after reboot inaccessable

Postby Peter-s7 » Tue Mar 05, 2019 10:32 am

Solution:

- Disconnect 2nd Node as a replication partner for all HA Volumes
- Re-Install Starwind on Node_2
- Delete all legacy valumes, first from Management Console, Second from Disks
- Re-Add the 2nd Node as a Replication Partner for the HA-Volumes

Now it's working, even after a reboot. Don't know where the error was.

But it's solved.

Cheers,
Peter-s7
 
Posts: 3
Joined: Mon Mar 04, 2019 12:10 pm

Re: Node after reboot inaccessable

Postby Oleg(staff) » Wed Mar 06, 2019 12:45 pm

Hi Peter,
That is not expected behaviour.
Could you please collect the logs using this tool?
Please share the logs with us.
Oleg(staff)
Staff
 
Posts: 567
Joined: Fri Nov 24, 2017 7:52 am


Return to StarWind Virtual SAN / StarWind Virtual SAN Free / StarWind HyperConverged Appliance / StarWind Storage Appliance

Who is online

Users browsing this forum: No registered users and 5 guests