Activities

July 2013
M T W T F S S
« Jun   Aug »
1234567
891011121314
15161718192021
22232425262728
293031  

MySQL : [ERROR] Error message file ‘/usr/share/mysql/english/errmsg.sys’ had only 706 error messages

Today I got an error on MySQL server when I was restart a MySQL daemon tonight. This is the first time I see such an error. The exact error was,

130724 10:39:38 [ERROR] Error message file ‘/usr/share/mysql/english/errmsg.sys’ had only 706 error messages,
but it should contain at least 728 error messages.

MySQL server log will look like this

130724 10:22:43 mysqld_safe mysqld from pid file /sqldata/mysql/db01.pid ended
130724 10:39:38 mysqld_safe Starting mysqld daemon with databases from /sqldata/mysql
130724 10:39:38 [ERROR] Error message file '/usr/share/mysql/english/errmsg.sys' had only 706 error messages,
but it should contain at least 728 error messages.
Check that the above file is the right version for this program!
130724 10:39:38 [Note] Plugin 'FEDERATED' is disabled.
130724 10:39:38 InnoDB: The InnoDB memory heap is disabled
130724 10:39:38 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130724 10:39:38 InnoDB: Compressed tables use zlib 1.2.3
130724 10:39:38 InnoDB: Using Linux native AIO
130724 10:39:38 InnoDB: Initializing buffer pool, size = 5.0G
InnoDB: HugeTLB: Warning: Failed to allocate 5494538240 bytes. errno 1
InnoDB HugeTLB: Warning: Using conventional memory pool
130724 10:39:38 InnoDB: Completed initialization of buffer pool
130724 10:39:38 InnoDB: highest supported file format is Barracuda.
130724 10:39:38  InnoDB: Waiting for the background threads to start
130724 10:39:39 InnoDB: 1.1.8 started; log sequence number 1289060205483
130724 10:39:39 [ERROR] Aborting
130724 10:39:39  InnoDB: Starting shutdown...
130724 10:39:41  InnoDB: Shutdown completed; log sequence number 1289060205483
130724 10:39:41 [Note]
130724 10:39:41 mysqld_safe mysqld from pid file /sqldata/mysql/fc-db01LA.pid ended

So I can not start the MySQL service again. I’d tried to copy the file “/usr/share/mysql/english/errmsg.sys” from other server to here but no luck. Most of the Google thread advise to re-install the MySQL version.

Solution : Re-install the MySQL Server

You may use #yum remove mysql command to uninstall the MySQL. If you installed MySQL manually, you may need to find the package name first and remove it manually.

[root@db01 ~]# rpm -qa | grep "MySQL"
MySQL-shared-5.5.25a-1.el6.x86_64
MySQL-server-5.5.25a-1.el6.x86_64
MySQL-devel-5.5.25a-1.el6.x86_64
perl-DBD-MySQL-4.013-3.el6.x86_64
MySQL-client-5.5.25a-1.el6.x86_64
[root@db01 ~]# rpm -e MySQL-server-5.5.25a-1.el6.x86_64 MySQL-devel-5.5.25a-1.el6.x86_64 MySQL-client-5.5.25a-1.el6.x86_64 MySQL-shared-5.5.25a-1.el6.x86_64

Finally I’ve removed the MySQL rpm install and installed it back. Pls keep in mind that you will not modify any changes in my.cnf especially the option force_recovery which may harm the data.

It will not anticipate any data loss during the time.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>