Geek Answers Handbook

RabbitMQ dependent Topshelf service does not start with reboot

I have windows services that use EasyNetQ and RabbitMQ. A service is usually started from the service control manager. However, I sometimes saw that when rebooting, the service does not start with an error in the service event log:

A timeout was reached (30000 milliseconds) The <serviceName> service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

I tried auto-delay service, and that didn't help.

In addition, I was thinking about setting up the recovery mechanism so that if it does not start, it restarts from the first and second and subsequent failures. Not sure if this will work.

So my questions are: how can I determine what a dependency is, which is why my service does not start sometimes?

+7
c # rabbitmq windows-services easynetq
source share

No one has answered this question yet.

See related questions:

647
ActiveMQ or RabbitMQ or ZeroMQ or
34
"Timeout has been reached while waiting to connect to the service" after reboot
14
Configure recovery options in Windows Services
10
Explained Windows Recovery Services settings
5
Automatic services do not start
one
Install a Windows service and start another service
0
Using console.readline ()
0
Windows service does not start
0
Failed to start Winsows Service
-one
Sometimes services do not start on Windows server 2016 after a computer reboot. Event IDs: 7000, 7009

More articles:


All Articles