Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

catalina and localhost_access_log files are still created into container #168

Open
AlvaroVega opened this issue Jan 27, 2021 · 4 comments
Open

Comments

@AlvaroVega
Copy link
Member

AlvaroVega commented Jan 27, 2021

/usr/local/tomcat/logs

catalina.2019-11-29.log localhost_access_log.2020-01-10.txt localhost_access_log.2020-04-17.txt localhost_access_log.2020-07-20.txt localhost_access_log.2020-10-22.txt
catalina.2020-03-16.log localhost_access_log.2020-01-11.txt localhost_access_log.2020-04-18.txt

....

localhost_access_log.2020-01-07.txt localhost_access_log.2020-04-14.txt localhost_access_log.2020-07-17.txt localhost_access_log.2020-10-19.txt manager.2021-01-26.log
localhost_access_log.2020-01-08.txt localhost_access_log.2020-04-15.txt localhost_access_log.2020-07-18.txt localhost_access_log.2020-10-20.txt
localhost_access_log.2020-01-09.txt localhost_access_log.2020-04-16.txt localhost_access_log.2020-07-19.txt localhost_access_log.2020-10-21.txt

ls | wc -l
468

@AlvaroVega
Copy link
Member Author

@cesarjorgemartinez
Copy link
Contributor

Hum, this fix is very restrictive, sometimes faults can be determined by reading those logs

@AlvaroVega
Copy link
Member Author

AlvaroVega commented Jan 27, 2021

Can we do :
Edit "$CATALINA_BASE"/bin/catalina.sh file
Find CATALINA_OUT="$CATALINA_BASE"/dev/stdout'
Replace with new path.
?

@cesarjorgemartinez
Copy link
Contributor

cesarjorgemartinez commented Jan 27, 2021

I need to test this. I'll tell you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants