When accessing the Track application URL, users may see the error message “Service is not available.” Restarting services alone may not resolve the issue.
The root cause is usually an ownership mismatch between the service startup user (nastel) and files/directories owned by root. Correcting permissions and restarting the services typically resolves the problem.
Observed Behavior
Browser displays “Service is not available.”
Tomcat logs (
catalina.out) show stack trace errors such as:java.lang.RuntimeException: Cannot get ProviderTypes at com.nastel.jkool.ui.context.listeners.JKQLContextListener.getProviderTypesList
Services appear to restart, but the Track UI remains unavailable.
Cause
This typically occurs when some Track, CEP, ActiveMQ, Tomcat, or related components fail to initialize correctly due to incorrect file or directory ownership. If certain files or directories are owned by root but the services are started under the nastel user, components cannot access the required resources, leading to failure.
Resolution
Stop all services (Tomcat, CEP, ActiveMQ, Kafka, Zookeeper, etc.).
Log in as
root.Correct the file ownership for the Nastel installation directory:
(Adjust the path if your installation directory differs.)chown -R nastel:nastel /opt/nastel
Restart all services under the
nasteluser.Verify that the Track login page loads successfully.
Additional Steps for Troubleshooting (if the issue persists)
Review the following logs for errors during startup:
catalina.out(Tomcat)cep.log(CEP)activemq.log(ActiveMQ)