KOTS Installation/ Troubleshooting: App server will not come up after DB was restarted.

Riya Ray
Riya Ray
  • Updated

Author: Riya Ray, Jason De Paola

Date: December 04, 2023

Audience: Everyone

Environmental details: Self-hosted Jama Connect KOTS 

Summary: 

If the database server is turned off or restarted for any reason (planned or unexpected), the App server may not come up. We must execute the KOTS shutdown and startup scripts in this case because the application may not have recovered from the database switch event. 

Solution:

  1. Make sure your DB Server is up and running.
  2. On the Jama Application Server, run the below commands:
sudo /opt/ekco/shutdown.sh
sudo /opt/ekco/startup.sh

Please note that it may take some time for all the pods to come up. To monitor the pods, you can use the following command:

watch kubectl get pods
(Ctl-c to exit the watch)

Cause:

Because of the improper shutdown of the database server, the application session may have also terminated abruptly. 

Prevention: 

Ensure the database server is running before starting/ deploying the Jama KOTS App Server.

 

Additional Information/Metadata:

  • Troubleshooting
  • Jama KOTS installation

Feedback: Please leave feedback in the comments below.

 

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.