EmergencyEMERGENCY? Get 24/7 Help Now!

More on MySQL Error Messages

 | April 6, 2011 |  Posted In: Insight for DBAs, MySQL


I wrote about MySQL Error Messages before and as you might guess I’m not very happy with quality for error messages it produces. Now I’m revisiting this subject with couple of more annoying examples I ran into during last couple of days.

First question you should ask is what is error 17 ? Do to this you can run external utility perror:

It would be already a lot handy if one would walk through all error messages where error code is used and add the text description right into the code. ERROR 1010 (HY000): Error dropping database (can’t rmdir ‘./test/’, errno: 17 “File exists”) would already be a lot more helpful.

If you’re wondering why this could happen, the answer is you may get some extra files, which do not belong to MySQL in database directory. MySQL will only remove files it knows about such as “.frm” or “.MYI” when it is dropping the database, if you get something else, such as .sql file containing the dump of this database you will not be able to drop it until you remove this file manually.

Another enjoyable error message: “Can’t find messagefile ‘/usr/share/mysql/english/errmsg.sys”

Everything is good and clear right ? Nope !

The file does exist so “can’t find messagefile” error message is misleading to say the least. The error can’t open file would be much more appropriate here and error code (better with description) would be great.

What is the problem in this case ? It is SELinux denying permission to this file as can be seen from “dmesg”

The bad error reporting has an interesting property – you do not care as you do not see those error frequently, but when you do, especially if you’re under the time pressure, bad error reporting really hurts.
I wish Oracle would invest some time fixing those errors. No complicated code required and I bet this could be a great project for some Intern to complete over summer. Why do I point finger to Oracle you would ask, why do not we just fix it in Percona Server ? We could but because there are a lot of simple changes needed, plus many of message files would need to be corrected to include the place
to provide error description in addition to error code, this would make our merge process a lot more complicated, so it is a lot better if it is fixed in upstream.

Peter Zaitsev

Peter managed the High Performance Group within MySQL until 2006, when he founded Percona. Peter has a Master's Degree in Computer Science and is an expert in database kernels, computer hardware, and application scaling.


  • Hi,
    I have problem in Mysql replication on Slave Server.
    Probelm:: Last_SQL_Error: Could not execute Update_rows event on table cbs.airtel_high_priority_sms_que; Can’t find record in ‘airtel_high_priority_sms_que’, Error_code: 1032;
    handler error HA_ERR_KEY_NOT_FOUND; the event’s master log replication.010901, end_log_pos 80129959

    respective log in Master show ::
    # at 80127091
    # at 80127185
    # at 80128145
    # at 80129105
    # at 80129959
    #110429 13:22:24 server id 1 end_log_pos 80127185 Table_map: cbs.airtel_high_priority_sms_que mapped to number 471362
    #110429 13:22:24 server id 1 end_log_pos 80128145 Update_rows: table id 471362
    #110429 13:22:24 server id 1 end_log_pos 80129105 Update_rows: table id 471362
    #110429 13:22:24 server id 1 end_log_pos 80129959 Update_rows: table id 471362
    #110429 13:22:24 server id 1 end_log_pos 80130711 Update_rows: table id 471362 flags: STMT_END_F

    BINLOG ‘

    This problem show only with updates query.

  • I agree, error reporting in MySQL sucks. You should never have to run an external command to figure out what the system is talking about.

  • Agreed!

    Even though I now know exactly what error 17 (among others) means on our system, it took a little investigation the first time around…

  • Agreed!

    Even though I now know exactly what error 17 (among others) means on our system, it took a little investigation the first time around…

  • I’m getting this error and I’m having trouble resolving it – any help would be appreciated.

    A database ‘test’ exists and is empty. When I execute the command:


    I get the error in question in this article:

    ERROR 1010 (HY000): Error dropping database (can’t rmdir ‘./test/’, errno: 17)

    There is no directory ‘./test’. When I create an empty ‘/.test’ directory the command still fails.

    Any thoughts on where MySQL is trying to go to delete this ‘./test’ directory?


  • Well, I figured it out.

    I went to the MySQL basedir and in the data directory there was a ‘test’ directory with a hidden file ‘.empty’ of size 0.

    Removing that file allowed the DROP DATABASE test; command to execute successfully.


Leave a Reply