Unsolved
This post is more than 5 years old
1 Rookie
•
8 Posts
0
938
November 7th, 2014 11:00
How to diagnose why Watch4Net’/APG's Tomcat service is stopping
Hello, we are running Watch4Net version v6.2u4. Recently the "Default Tomcat" service has been stopping on its own. This is an important service to keep up and running. Would anyone know which logs to view in order to identify the reasons for this service to stop? Or how to identify why this service is stopping?
Thanks so much!
Stu
No Events found!
ConorLawlor
2 Intern
•
233 Posts
0
November 10th, 2014 01:00
Hi Stu,
In the UI the Tomcat logs can be viewed from Administration >> Centralized Management >> <
StuHut
1 Rookie
•
8 Posts
0
November 10th, 2014 07:00
Hello Conor, thanks for the reply... I checked all the logs your specified above and did not find any warning or sever entries during our tomcat unavailable timeframes from November 5, 2014 2pm to November 6, 2014 7am (see log file names below)... If you happen to know of any other logs I could check please let me know.
Logs I checked for November 5, 2014 at 2pm:
audit.2014-11-05.log
catalina.2014-11-05.log
localhost.2014-11-05.log
service.log
stdout_20141031.log
access_log.2014-11-05
localhost.2014-11-04.log
Thanks again!
Stu