CES Service in stopped state
I've noticed that sometimes after my CES server is restarted the CES service fails to start automatically but all other services (RabbitMQ and Search API) startup fine.
I see these entries in the even log but I do not see any anything in the CES logs that indicate why it failed to start.
The Coveo Enterprise Search 7 x64 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
A timeout was reached (30000 milliseconds) while waiting for the Coveo Enterprise Search 7 x64 service to connect.
Any hints on how to debug this?
This message seems to be logged by the Windows Services manager who starts the services at boot time. It seems that the CES service takes more than 30 seconds to start on your machine. Common reasons the CES service can be slow to start:
- Hardware requirements not met. You need at least good CPUs and a decent amount of RAM and hard drive space to run CES (see Coveo Platform Hardware and Software Requirements).
- CES configuration is very large and takes time to load. Look at the size of your
C:\CES7\Config\config.txtfile. Also look for a CES system log about ConfigObjectCache size just after CES is started (see The ConfigObjectCache is swapping to disk. Performance might be adversely affected). You might need to increase the size of this cache for CES to start, stop and perform faster.