-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
MySQLTuner does not work #483
Comments
Try this.. maybe
I believe your GIGANTIC logfile is giving you issues. Probably your sql instance logs are set to some high verbosity logging which results in big log files. Also, it could be that there are never any log file rotation being done on the actual file - which means your logfiles contains everything from the initial start of the instance, whenever the machine was created. To rotate your logs automatically and thus keep them relevant and of a decent size on a daily or, even, weekly/monthly basis, check out logrotate Hope this helps. Also, check if there is a |
Hi, First as @mathieu-aubin says implementing a log rotation can be nice. Maybe a control other file size greater than 200 Mb can be nice with a message advising implementing a log rotation strategy can be good. BR, |
closed via: Last 30k line are read. |
Fell free to reopen if needed |
We do run MySQLTuner but this does not completed. Please can you let me know that how can fix this issue?
The text was updated successfully, but these errors were encountered: