Author Topic: Flexraid service doesn't start automatically on Win10  (Read 2797 times)

Offline Bugman

  • Newbie
  • *
  • Posts: 17
  • Karma: +0/-0
    • View Profile
Flexraid service doesn't start automatically on Win10
« on: May 26, 2016, 11:23:03 am »
Hi: I upgraded to Win10 yesterday from Win7. Prior to the upgrade I installed the latest release of Flexraid and everything ran well with the Service starting automatically with the storage pool.

After the upgrade to Win10 I have to start the Flexraid Service manually. Even though the Flexraid service is flagged to start automatically it does not. The settings for the pool have the service starting after 10000 ms. Never had this a problem in the past.

Any ideas?

Logs below:

This log refers to the restart of the PC. The service was running before the restart.

[2016-05-26 12:13:38,140] INFO : Service stopping...
[2016-05-26 12:13:38,334] INFO : Stopping views...
[2016-05-26 12:13:38,428] INFO : Unmounting View...
[2016-05-26 12:13:43,741] INFO : Unmounting View complete...
[2016-05-26 12:13:45,208] INFO : Stopping scheduler...
[2016-05-26 12:13:45,792] INFO : Stopping web server...
[2016-05-26 12:13:45,969] INFO : Stopping socket server...
[2016-05-26 12:13:46,078] INFO : Shutting down at: 5/26/16 12:13 PM
[2016-05-26 12:13:46,078] INFO : Closing all client connections...
[2016-05-26 12:13:46,078] INFO : Exiting all processes...
[2016-05-26 12:13:47,360] ERROR: Connection refused: connect
java.net.ConnectException: Connection refused: connect
   at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
   at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
   at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
   at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
   at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
   at java.net.PlainSocketImpl.connect(Unknown Source)
   at java.net.SocksSocketImpl.connect(Unknown Source)
   at java.net.Socket.connect(Unknown Source)
   at com.tchegbe.lib.b.a.b.a(Unknown Source)
   at com.tchegbe.lib.b.a.e.a(Unknown Source)
   at com.tchegbe.lib.b.a.g.a(Unknown Source)
   at com.tchegbe.lib.common.i.d.b(Unknown Source)
   at com.tchegbe.lib.common.i.a.run(Unknown Source)
[2016-05-26 12:13:48,141] ERROR: Connection refused: connect
java.net.ConnectException: Connection refused: connect
   at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
   at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
   at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
   at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
   at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
   at java.net.PlainSocketImpl.connect(Unknown Source)
   at java.net.SocksSocketImpl.connect(Unknown Source)
   at java.net.Socket.connect(Unknown Source)
   at com.tchegbe.lib.b.a.b.a(Unknown Source)
   at com.tchegbe.lib.b.a.e.a(Unknown Source)
   at com.tchegbe.lib.b.a.g.a(Unknown Source)
   at com.tchegbe.lib.common.i.d.a(Unknown Source)
   at com.tchegbe.lib.common.i.a.<unknown>(Unknown Source)
   at com.tchegbe.lib.common.i.a.<unknown>(Unknown Source)
   at com.tchegbe.lib.common.i.a.<unknown>(Unknown Source)
   at com.tchegbe.lib.io.a.h.run(Unknown Source)

This portion of the log is after I manually start the service.

[2016-05-26 12:36:36,392] INFO : Setting core service port to 9595
[2016-05-26 12:36:36,392] INFO : Setting Http port to 8080
[2016-05-26 12:36:36,392] INFO : Https port not set. Https requests will not be serviced...
[2016-05-26 12:36:36,406] INFO : Starting FlexRAID...
[2016-05-26 12:36:36,406] INFO : FlexRAID 2.1 [Snapshot 1.1 / Storage Pool 2.0] [2015.11.01]
[2016-05-26 12:36:36,431] INFO : Started: May 26, 2016 12:36:36 PM EDT
[2016-05-26 12:36:49,278] INFO : Initiating FlexRAID Storage Pool...
[2016-05-26 12:36:49,397] INFO : Host OS = Microsoft Windows [Version 10.0.10586]
[2016-05-26 12:36:49,397] INFO : Building View Registry...
[2016-05-26 12:36:49,428] INFO : Building Auto View Registry...
[2016-05-26 12:36:49,505] INFO : Loading View options...
[2016-05-26 12:36:50,173] INFO : Using Auto-View definition...
[2016-05-26 12:36:50,173] INFO : Building View Handler...
[2016-05-26 12:36:50,465] INFO : Mounting Storage Pool drive...
[2016-05-26 12:37:12,198] INFO : Reconnecting Video="Z:" /GRANT:Everyone,FULL


Offline DarkKnight

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +1/-0
    • View Profile
Re: Flexraid service doesn't start automatically on Win10
« Reply #1 on: August 19, 2016, 12:52:12 pm »
Creating a new Thread with a workaround and screenshots to help.

http://forum.flexraid.com/index.php?topic=48947
« Last Edit: August 19, 2016, 01:14:24 pm by DarkKnight »

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Flexraid service doesn't start automatically on Win10
« Reply #2 on: August 20, 2016, 01:42:02 am »
In the most likely case, you need to set the service to delay start: https://www.google.com/#q=delay+startup+programs+windows+10

Offline DarkKnight

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +1/-0
    • View Profile
Re: Flexraid service doesn't start automatically on Win10
« Reply #3 on: August 20, 2016, 02:31:51 pm »
In the most likely case, you need to set the service to delay start: https://www.google.com/#q=delay+startup+programs+windows+10

Respectfully, that's not a fix, it's a workaround with a long (i.e >2 min) delay.


Excerpted from Stack overflow:

In short, services set to Automatic will start during the boot process, while services set to start as Delayed will start shortly after boot. "Shortly after boot" is actually 2 minutes after the last "automatic" service has started, by default.

The workaround I posted currently has a permissions issue that I'm working to resolve, but when it works, it starts it up within seconds of booting like normal.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Flexraid service doesn't start automatically on Win10
« Reply #4 on: August 20, 2016, 05:09:58 pm »
Respectfully, that's not a fix, it's a workaround with a long (i.e >2 min) delay.
...
Who told you it was a fix?
You are being given a workaround for your system specific issues - just in case that wasn't clear.  ;)

The delayed start is needed on your system because services required aren't ready by the time the FlexRAID service is started by the OS.
This is system specific and only affect select users given their particular system configuration.

FlexRAID has no control over when the OS chooses to start its services. Setting up explicit dependencies isn't done because we are talking about core services, which should normally be up.
Users that need the delay start have more fundamental issues that the key services (networking in this case) aren't starting fast enough before other programs are started.

Your workaround is a good effort (and appreciated), but it is not something we recommend.
If you don't like the delayed start approach because you have other services depending on the pool or something, then try to figure out why the networking services aren't starting fast enough on your system.
If no clear resolution is found, then try setting up dependencies as follow in a DOS prompt:
Code: [Select]
sc config FlexRAID depend= Netman

Offline DarkKnight

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +1/-0
    • View Profile
Re: Flexraid service doesn't start automatically on Win10
« Reply #5 on: August 24, 2016, 07:51:03 pm »
Who told you it was a fix?
You are being given a workaround for your system specific issues - just in case that wasn't clear.  ;)

The delayed start is needed on your system because services required aren't ready by the time the FlexRAID service is started by the OS.
This is system specific and only affect select users given their particular system configuration.

FlexRAID has no control over when the OS chooses to start its services. Setting up explicit dependencies isn't done because we are talking about core services, which should normally be up.
Users that need the delay start have more fundamental issues that the key services (networking in this case) aren't starting fast enough before other programs are started.

Your workaround is a good effort (and appreciated), but it is not something we recommend.
If you don't like the delayed start approach because you have other services depending on the pool or something, then try to figure out why the networking services aren't starting fast enough on your system.
If no clear resolution is found, then try setting up dependencies as follow in a DOS prompt:
Code: [Select]
sc config FlexRAID depend= Netman

Making F/R dependent on a service it's actually dependent on sounds like a reasonable solution.

From what people are saying, it seems this issue affects all Windows 10 + Flexraid users. If that's the case, then the problem isn't with my configuration. My network services are up in literal seconds once the desktop is up. I don't suspect MSFT is going to change anything to accommodate this issue, that leaves you to integrate a fix.

Why does Flexraid even need the netman service to be up to start the pool? The service reads like it's just there to monitor network configurations.

Quote
Network Connections (Netman) Service Defaults in Windows 10

Manages objects in the Network and Dial-Up Connections folder, in which you can view both local area network and remote connections.

FWIW, I only posted a workaround because there was no other viable means to autostarting the array after a reboot posted to the forums. It's kludgy, and way more complicated than it should be, but it shouldn't be necessary at all if F/R were behaving as expected.
« Last Edit: August 24, 2016, 07:54:45 pm by DarkKnight »

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Flexraid service doesn't start automatically on Win10
« Reply #6 on: August 25, 2016, 09:45:43 am »
Making F/R dependent on a service it's actually dependent on sounds like a reasonable solution.
...
Not when we are talking of core services that have higher priority. Service dependency should only be set for services at the same run level.
Network services should always start before application service. This is a fundamental design of the OS. If it does not on your system, then there are external issues causing this. This is not a bug and a workaround is most appropriate.

Quote
From what people are saying, it seems this issue affects all Windows 10 + Flexraid users. If that's the case, then the problem isn't with my configuration. My network services are up in literal seconds once the desktop is up. I don't suspect MSFT is going to change anything to accommodate this issue, that leaves you to integrate a fix.
...
None of my Windows 10 systems are affected. You are one of the select few affected. It is an issue with your system. Could be network driver related or could be other services on that system related.

Quote
Why does Flexraid even need the netman service to be up to start the pool? The service reads like it's just there to monitor network configurations.

FWIW, I only posted a workaround because there was no other viable means to autostarting the array after a reboot posted to the forums. It's kludgy, and way more complicated than it should be, but it shouldn't be necessary at all if F/R were behaving as expected.
The RAID-F service is really a two part service combined into one. The first service is TCP based and listens on port 9595. The second is HTTP based and listens on port 8080.

The service running on 8080 is the one telling the service on 9595 to start the pool. It comes from the fact that it is a client/server design, but both pieces got combined after the fact to keep the installation simple.
« Last Edit: August 25, 2016, 09:50:31 am by Brahim »

Offline thecig

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Flexraid service doesn't start automatically on Win10
« Reply #7 on: March 08, 2017, 06:20:40 am »
Hi. Sorry for bumping an old thread but I can't seem to get my storage pool to auto mount on Windows 10.
I've set both the "NZFS Web Client Service" and "NZFS Broker Service" to Automatic (Delayed start) but even after 4 minutes nothing happens.
I have to manually go into the WEBgui and start the storage pool.

I also tried to add a dependency via CMD "sc config FlexRAID depend= Netman" but got the following error:
[SC] OpenService FAILED 1060:

The specified service does not exist as an installed service.

Any help would be appreciated.