Description
This article provides guidance for safely shutting down and restarting a Katalyst D2D system. If servers are not restarted in the correct order, the Katalyst application will not automatically start, and users trying to access it will receive an HTTP status 404 - Not Found error.
Solution
Follow the recommended graceful shutdown procedure (see below) and avoid forced server power-offs, as they may compromise database integrity and impact service dependencies.
If Katalyst displays an HTTP 404 - Not Found error, review the system logs to determine whether the servers were recently restarted. Verify the startup sequence from the logs to ensure that all servers and services were brought online in the correct order.
Troubleshooting: If no other errors or issues are identified, access the Tomcat Manager Application, authenticate with the appropriate credentials, and manually start the Katalyst application.
Shutdown order (reverse of startup):
- Stop Katalyst D2D Web Server.
- Stop ProcessorJS Server.
- Stop ACD/Automation Server.
- Stop ACD/Spectrus DB Server.
- Stop Database Server.
- Stop ACD/Arcus Server.
Startup order (i.e. after weekend):
- Start ACD/Arcus Server.
- Start Database Server.
- Start ACD/Spectrus DB Server.
- Start ACD/Automation Server.
- Start ProcessorJS Server.
- Start Katalyst D2D Web Server.
Rationale:
Protect database integrity by stopping databases gracefully to avoid uncommitted transaction loss and data/index corruption.
Respect service dependencies to prevent connection failures, startup errors, and silent data issues.
Comments
0 comments
Article is closed for comments.