RavenDB fail to start on Windows Server after a reboot

[Pierre]

Hi all,

On our two Windows server, RavenDB fail to start after a server reboot, despite the fact the service is marked as Automatic start.

We tried Delayed start, without success.

Anyone having the issue and the solution?

Thanks a lot

[Igal Merhavia]

Hi,

Can you try to start it from the command line and send us the error message?

In addition, please send us the log files.

Best regards,

Igal

--
You received this message because you are subscribed to the Google Groups "RavenDB - an awesome database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ravendb/0e47e207-4cfa-4522-973d-5105271cde53n%40googlegroups.com.

[Oren Eini (Ayende Rahien)]

Do you have anything in the Event Log?

Anything in the logs directory? 

On Mon, Mar 21, 2022 at 10:24 AM Pierre <pme...@gmail.com> wrote:

--

You received this message because you are subscribed to the Google Groups "RavenDB - an awesome database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ravendb/0e47e207-4cfa-4522-973d-5105271cde53n%40googlegroups.com.

--

Oren Eini CEO   /   Hibernating Rhinos LTD Mobile:  972-52-548-6969 Sales:  sa...@ravendb.net Skype:  ayenderahien Support:  sup...@ravendb.net

[Oren Eini (Ayende Rahien)]

If you restart manually, does it work?

[Pierre Mengal]

Nothing in log files, until we start it manually.

After a manual or an automatic restart:

You received this message because you are subscribed to a topic in the Google Groups "RavenDB - an awesome database" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ravendb/lX-010CSp-o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ravendb+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ravendb/CAF0G-ZipWa8tinGQH8xi_dHtjNeHavG_nrZi8sJ0K1ygcJsqag%40mail.gmail.com.

[Oren Eini (Ayende Rahien)]

Do you have any entries in the event log?

To view this discussion on the web visit https://groups.google.com/d/msgid/ravendb/CACV7Fti4-GgzXrQLcka379Lvxsou00sc4U2BN6O6yGwpUnEhUg%40mail.gmail.com.

[Pierre Mengal]

Nothing new after the restart. Only when I start the service manually afterwards.

Nothing in the event viewer either.

To view this discussion on the web visit https://groups.google.com/d/msgid/ravendb/CAF0G-Zg%2BNhUWXWPDkfP2cdKwYC7ZjhJH%2BUjYXvT3wQ_sW_LPBw%40mail.gmail.com.

[Oren Eini (Ayende Rahien)]

That is really strange. Do you have RavenDB setup on a network drive, which may take time to spin up?

There should be some additional information, maybe see here:

https://stackoverflow.com/questions/1067531/are-there-any-log-file-about-windows-services-status

To view this discussion on the web visit https://groups.google.com/d/msgid/ravendb/CACV7FtiK1y6KyhmkVrKbbH7DFoC96dDMYtWMbC%3D0dh0Kw92_eg%40mail.gmail.com.

[Pierre Mengal]

Here you go:

A timeout was reached (30000 milliseconds) while waiting for the RavenDB service to connect.

then

The RavenDB service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

The problem is very similar to this one (we do have problems sometimes with Octopus Deploy):

https://help.octopus.com/t/octopusdeploy-service-fails-to-start-after-reboot/357

To view this discussion on the web visit https://groups.google.com/d/msgid/ravendb/CAF0G-ZhO5yx0_xU%3Dnt_gZBg-q8mFkuUgRX_AYXU1MQTj6qhqXw%40mail.gmail.com.

[Oren Eini (Ayende Rahien)]

That makes little sense, to be honest. There shouldn't be anything that would cause it to hang. And we aren't using the global .NET Framework.

Try increasing the startup time of the service? 

And check the logs/ directory, there might be some indication there.

I wonder if there is something that may be blocking it. Maybe run with info log level?

To view this discussion on the web visit https://groups.google.com/d/msgid/ravendb/CACV7FthLdOuXxFZ1cMjgbMVJjoPn1DzA3grozMRh1cH8Rue24g%40mail.gmail.com.

[Pierre Mengal]

It didn't help. We ended up creating a scheduled task triggered at startup that will call net start RavenDB every 2 minutes 5 times.

Not optimal. The production version of RavenDB will be installed on a linux box anyway... so I think the problem will be solved for us at the same time.

To view this discussion on the web visit https://groups.google.com/d/msgid/ravendb/CAF0G-Zj%3DDL0JkAHycSEOov48xhgQJPryJdsV-fJSPZYwouoLig%40mail.gmail.com.

[Oren Eini (Ayende Rahien)]

If you can set the startup exec to a script that would re-direct the stdout to a file, we may be able to tell more. If you are running on Linux in production, that isn't a real issue in the long term, yes

To view this discussion on the web visit https://groups.google.com/d/msgid/ravendb/CACV7FtiCfJ1dAbB97%2BaAryiXso7PEdEUS7utxe9hNr166388Qg%40mail.gmail.com.