-
Notifications
You must be signed in to change notification settings - Fork 0
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
Remove access logs older than 3 months #45
Comments
…(causes bloated syslog)
…profile (causes bloated syslog)" This reverts commit 135c9a0.
…fEngine to ERROR
This forwarding has been temporarily disabled in avni cloud staging, prerelease and prod. application logs -> journal logs -> syslogs were getting bloated due to repeated warning logs from ehcache DefaultSizeOfEngine since release 10.0.x. Log level has been changed to error for this. Syslog itself is being rotated by logrotate but we were writing too fast for the rotation to help. Deletion of older tomcat access logs being tested with tomcat config |
…in test/application.properties
Staging access logs Before:
After:
|
Marking it as Tech type QA, to ensure we check the server state before the deploy and validate all the fixes after deployment. Test cases
|
@1t5j0y Should we enable "ForwardToSyslog" on deployment of 10.1 to prod server.? |
Yes. Updated avniproject/avni-product#1657 |
Issue:
Not clearing the old access logs is leading to GBs of uncleared old data - which can be cleared regularly to avoid out of disk space issue.
AC:
Clear access-logs older than 3 months from
/var/log/avni_server/log
folder.The text was updated successfully, but these errors were encountered: