Question
Openlitespeed Log Rolling Size
- Posted on November 19, 2019
- Linux BasicsDigitalOcean 1-Click Apps MarketplaceServer OptimizationUbuntu 16.04
Asked by qy2009
Hi,
Almost every 2 days my logs are max out my disk space, over 50G, the logs are under /usr/local/lsws/logs
How can I limit the log size inside Openlitespeed?
I tried the console, the the log limit/rotation options are only for error.log. Not logs in that path.
Thanks!
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.
This promotional offer applies to new account only.
Hi,
Just want to share the findings and solution here.
Error message found: Too many error message(Accept failed:Too many open files!) can be fixed by increasing the Server Configuration -> Tuning -> Max Connections & Max SSL Connections to higher number, e.g. 10000…
Default error log rotate is 30 days. So in general you won’t get disk full issue due to too many error logs.
The rolling function: When the log size over 10M, it will create a new log file and keep logging it. The 10M log will be archived and will be deleted after default 30 days.
To prevent log fill up the disk, you can try method:
keepDays 1to/usr/local/lsws/conf/httpd_config.conferrorlog logs/error.log section. In this way, the error log will only store for one dayerror.log.*. In this way, all archived log will be removed.I will discuss with our developer see if we can provide some option on GUI(web admin) or something else to avoid the issue in the future.
Best, Eric
I ran into the same issue and changed the error log level to “error”. It was very verbose.
thanks so much for your help @eleu