Network latency and temporary CPU or memory spikes may extend startup times and disrupt startup of the subsequent dependent services.
Details
Services use Automatic (Delayed Start), with a 120-second delay, and generally start in this order:
- SSO,
- Control Panel,
- Gateway,
- Auth Service,
- Imaging Console,
- Dashboards, and
- Analysis Node.
To avoid delays and subsequent disruption of dependent services and ensure that the services are started automatically, please configure the Service Startup Checker to trigger the service startup batch file provided with the installation. For more details please refer Microsoft Windows Services startup checker
Service Startup Checker is a batch script (which can be run either manually or automatically via a Scheduled Task) that will check whether the services are up and running, and if not, start them for you.
if any service takes longer to start and causes dependent services to fail, the Service Startup Checker automatically trigger the service startup batch file provided with the installation.
Each service’s logs can be checked to compare start and ready timestamp. For eg startup time of the Analysis Node, can be found from the service start and service-ready entries in the analysis-node.log. The Service Startup Checker can be used to trigger the installed service startup batch file if delays cause failures.
Resources
CAST Imaging v3 Product Documentation
CAST Imaging Troubleshooting Guides
Additional Resources
CAST Highlight Product Documentation
CAST Highlight Troubleshooting Guides
Ticket Number
60158
Comments