mysql-5.1.42-1
+
Par Remi le vendredi 1 janvier 2010, 08:29 - Archives - Lien permanent
RPM of the MySQL Community Server 5.1.42 are available in remi repository for EL 4 & 5 and for Fedora. See Changelog.
This build use a spec file close to the one from Rawhide. The Federated "storage engines" is activated by default by the launch script.
For the new InnoDB plugin, the configuration file(/etc/my.cnf) contains the directives need to enable it.
Notice : the new configuration file provided disable the old_passwords. The old clients (mysql 3.x et 4.0) couldn't connect anymore, but newest mysqlnd could. It is also necessary to change all passwords to take benefit of the new hash method.
WARNING: before upgrading, a full backup of your databases seems mandatory (a logical dump using mysqldump for example).
Simplest way to install is to use yum !
yum --enablerepo remi update mysql-server
For whose who prefer the download and manual installation, see the repository
Like after each upgrade, running the mysql_upgrade command is required. It checks all tables in all databases for incompatibilities with the current version of MySQL Server. If a table is found to have a possible incompatibility, it is checked. If any problems are found, the table is repaired. In all case, reading the documentation is recommended:
If you often need to read the manual, create a launcher with the command
chmsee /usr/share/doc/mysql-5.1.38/manual.chm
No update for the mysql-manual package, but version 5.1.38 still available.
Commentaires
Hello Remi,
The RHEL4 version seems to have some problems with innodb-plugin. I tried enabling innodb-plugin on a CentOS 4.8 box (with the latest updates) and it dies at startup with:
100116 10:39:51 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
100116 10:39:51 [Note] Plugin 'ndbcluster' is disabled.
100116 10:39:51 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=134217728
read_buffer_size=16777216
max_used_connections=0
max_threads=400
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 657900 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
/usr/libexec/mysqld(my_print_stacktrace+0x33) [0x85859c9]
/usr/libexec/mysqld(handle_segfault+0x3da) [0x8214f8e]
/lib/tls/libpthread.so.0 [0xd2ea98]
/usr/lib/mysql/plugin/ha_innodb_plugin.so [0x80ea2f]
/usr/libexec/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x168) [0x8308b9a]
/usr/libexec/mysqld [0x83933e2]
/usr/libexec/mysqld(plugin_init(int*, char**, int)+0x5ed) [0x83970f5]
/usr/libexec/mysqld [0x821751b]
/usr/libexec/mysqld(main+0x63a) [0x821b53c]
/lib/tls/libc.so.6(__libc_start_main+0xd3) [0xbc9df3]
/usr/libexec/mysqld [0x8155eb1]
The manual page at http://dev.mysql.com/doc/mysql/en/c... contains
information that should help you find out what is causing the crash.
100116 10:39:51 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
The server is one of the nodes of a two-master replication setup and it starts up fine without innodb-plugin. The plugin was started using:
ignore-builtin-innodb
plugin-load=innodb=ha_innodb_plugin.so;innodb_trx=ha_innodb_plugin.so;innodb_locks=ha_innodb_plugin.so;innodb_cmp=ha_innodb_plugin.so;innodb_cmp_reset=ha_innodb_plugin.so;innodb_cmpmem=ha_innodb_plugin.so;innodb_cmpmem_reset=ha_innodb_plugin.so
innodb_file_per_table=1
innodb_file_format=barracuda
Any ideas or suggestions would be greatly appreciated. Thanks Remi.
Please use the Forums (better place for question / support)
I need to do some test to see if I can reproduce / explain this issue.
Have you try with a new DB or with an existing one ? (I think changing to baracuda file format need some work)
+
Thanks for the reply Remi, I've posted the issue there with a few more details.
Archived entry, see mysql-5.1.43-1