Software-based VM-centric and flash-friendly VM storage + free version
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
-
bkdilse
- Posts: 62
- Joined: Mon Sep 10, 2018 6:14 am
Fri Nov 29, 2019 3:00 pm
Hi,
Upgraded my 2 node free Storage nodes to latest version, and now they loose Sync.
Yesterday they became unsynch'd
Today same thing.
I can see this in the log:
Srv: *** iScsiServer::listenConnections: *LICENSE* Rejected iSCSI connection to x.x.x.x:3260 from x.x.x.x:52853.Maximum of 0 allowed clients already connected to the server!
EDIT: Just checked previous logs (prior to yesterday), and there are no License errors.
What's going on, should I regress to previous version?
Any fix for this?
This is pretty bad !
-
bkdilse
- Posts: 62
- Joined: Mon Sep 10, 2018 6:14 am
-
bkdilse
- Posts: 62
- Joined: Mon Sep 10, 2018 6:14 am
Tue Dec 03, 2019 12:44 pm
Boris (staff) wrote:Looks like an issue with licensing. What build gives you this issue?
The one in the subject
Version V8, build 13279 (24 October 2019)
-
Boris (staff)
- Staff
- Posts: 805
- Joined: Fri Jul 28, 2017 8:18 am
Tue Dec 03, 2019 1:03 pm
Sorry, totally missed it...
Could you collect logs from your hosts using StarWind Log Collector and share them with me? Do not forget to send your license file used there, too.
-
bkdilse
- Posts: 62
- Joined: Mon Sep 10, 2018 6:14 am
Tue Dec 03, 2019 1:08 pm
Boris (staff) wrote:Sorry, totally missed it...
Could you collect logs from your hosts using StarWind Log Collector and share them with me? Do not forget to send your license file used there, too.
I've actually regressed back to 2 versions being. And flush the log directory after confirming it all work (mistake, as I had loads of space).
-
Boris (staff)
- Staff
- Posts: 805
- Joined: Fri Jul 28, 2017 8:18 am
Tue Dec 03, 2019 1:34 pm
Well... At least I believe it works for you now, right?
If you ever try upgrading to the next builds and get the same reproduced just keep this thread in mind. We will definitely want to check the logs on our side. This particular build was supposed to resolve the issue, yet you are the second person reporting it did not.
-
bkdilse
- Posts: 62
- Joined: Mon Sep 10, 2018 6:14 am
Tue Dec 03, 2019 1:40 pm
Boris (staff) wrote:Well... At least I believe it works for you now, right?
If you ever try upgrading to the next builds and get the same reproduced just keep this thread in mind. We will definitely want to check the logs on our side. This particular build was supposed to resolve the issue, yet you are the second person reporting it did not.
Sure will do.
-
jimtheITguy
- Posts: 1
- Joined: Sat Dec 21, 2019 10:50 am
Sat Dec 21, 2019 10:53 am
Just to report I have experienced the same issue on a 2 node VSAN Free, might be worth sticking a link up to a previous version just incase as had to go hunting for a version to roll back to
