Tomcat access log import/analyze job does not load any logs if Alternate Logs Directory is set up.
search cancel

Tomcat access log import/analyze job does not load any logs if Alternate Logs Directory is set up.

book

Article ID: 235512

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

After we set up the Alternate Logs Directory in Log Configuration, when we run the "Tomcat access log import/analyze", it looks the job completed successfully, but nothing is loaded from app-access.log.

STEPS TO REPRODUCE: 
1. Open CSA (NSA) and set up Alternate Logs Directory and restart Clarity Service. 
2. Run the "Tomcat access log import/analyze" job.

Expected Results: 
The job imports logs from existing app-access.log. 

Actual Results:
The job Run Status shows "Completed", but the job log shows "Imported 0 log lines for service=app, host=(server name:port)" and nothing is imported. 

Environment

Release : 15.8.1

Component : Clarity Scheduler

Resolution

The problem has been investigated on DE64185 and confirmed that the problem was resolved in 15.9.3 (DE58162).

However, after you set up Alternate Logs Directory, you need to redeploy the services (i.e. service stop remove add deploy start app) to populate the access logs in alternate directory.

Also, for old access logs, please manually move them to the new logs folder. 

Additional Information

Check Log Files

Tomcat Access Log Import/Analyze Job

200615: DE58162 Setting up Alternate Log directory in CSA will not move all the logs there, missing system logs, access logs, admin.log etc.