EmergencyEMERGENCY? Get 24/7 Help Now!

Win a free ticket to RailsConf!


Posted on:

|

By:


PREVIOUS POST
NEXT POST
Share Button

I have one free ticket to give away to RailsConf next week in Baltimore! Post a comment to win, and if you aren’t the winner, I’ll give you a discount code for Percona Live as a consolation prize.

Here’s the catch: you have to find at least one thing wrong with the following typical logrotate configuration for MySQL. This should be easy even if you’re not a MySQL expert :-)

Share Button
PREVIOUS POST
NEXT POST


Baron Schwartz

Baron is the lead author of High Performance MySQL. He is a former Percona employee.



Categories:
MySQL


Comments
  • Baron Schwartz Post author

    Everything. Finding things wrong with it is like shooting fish in a barrel. I’ll blog about it someday.

    Reply

  • W. Andrew Loe III

    Baron,

    What are the correct answers to the questions? What is busted with syslog logging?

    Reply

  • Hmm. If I remember logrotate correctly, the compress gets executed before the flush-logs; so you run the risk of adding lines to an already-compressed logfile – and maybe lines added *during* compression will be lost depending on the compression utility’s behaviour.

    Reply

  • Ronald Bradford

    Not withstanding you should never roll your log file. See my views at http://ronaldbradford.com/blog/the-correct-approach-to-rolling-mysql-logs-2010-02-22/.

    aron perhaps you should expand on your post to the readers about issues with how to roll the slow query log, and about changes in log file writing in MySQL 5.5 that affects historical processes.

    Reply

  • Chunhui Huang

    When you run “flush logs”, the mysqld.log will be rename to mysqld.log-old

    Reply

  • John Paul Ashenfelter

    Sweet/thanks! Should I find you guys down here tomorrow or Tu?

    Reply

  • Baron Schwartz Post author

    Vitaly, I either confused you, or you are extremely clever and funny :)

    I’ll write a blog post sometime about what’s wrong with the default logrotate scripts for MySQL. The free ticket goes to John!

    Reply

  • Vitaly Tskhovrebov

    * It’s a bit harder to ‘rotate’ mysql databases then a text files;
    * InnoDB row will not exceed 8000 bytes under some conditions;
    * MySQL is an additional point of failure;

    Is it enough? :-)

    Reply

  • Baron Schwartz Post author

    For bonus points (but no bonus tickets), tell me what’s busted about logging to syslog with MySQL, too!

    Reply

  • John Paul Ashenfelter

    You don’t want the “create 600 mysql mysql” line — it’s commented out in the default config.

    But the real problem is you’re logging to a file and not syslog :)

    Reply

Leave a Reply

Percona’s widely read Percona Data Performance blog highlights our expertise in enterprise-class software, support, consulting and managed services solutions for both MySQL® and MongoDB® across traditional and cloud-based platforms. The decades of experience represented by our consultants is found daily in numerous and relevant blog posts.

Besides specific database help, the blog also provides notices on upcoming events and webinars.

Want to get weekly updates listing the latest blog posts? Subscribe to our blog now! Submit your email address below.

No, thank you. Please do not ask me again.