1 (edited by DarkSpace 2011-04-17 13:33:34)

Topic: MySQL issue after upgarde to 5.5.11

Hello,

I just recently upgraded my CentOS machine from 5.5 to 5.6 and I'm still using remi repo from the link below. Is it the right one?

- http://rpms.famillecollet.com/enterpris … ease-5.rpm

Today I updated MySQL and PHP on the same machine and suddenly MySQL didn't want to start. I have noticed that this was because specific settings in 'my.cnf' file. It works with default 'my.cnf' file but not with my old one (please see below)

Is there any reason why my configuration file it's not working with new MySQL version or should I use different remi repository from now?

Default 'my.cnf' file:

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

# To enable the InnoDB Plugin, uncomment the 2 next lines
#ignore-builtin-innodb
#plugin-load=innodb=ha_innodb_plugin.so

# To enable InnoDB-related INFORMATION_SCHEMA tables
# Join the following options to above directive
  ;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

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

My customized 'my.cnf' file:

[mysqld]
#datadir=/var/lib/mysql
#socket=/var/lib/mysql/mysql.sock
#user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

# To enable the InnoDB Plugin, uncomment the 2 next lines
#ignore-builtin-innodb
#plugin-load=innodb=ha_innodb_plugin.so

# To enable InnoDB-related INFORMATION_SCHEMA tables
# Join the following options to above directive
  ;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

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
skip-locking
skip-innodb
query_cache_limit=8M
query_cache_size=256M
query_cache_type=1
max_connections=500
max_user_connections=10
interactive_timeout=20
wait_timeout=20
connect_timeout=6
thread_cache_size=128
key_buffer=16M
join_buffer=1M
max_allowed_packet=16M
table_cache=1024
record_buffer=1M
sort_buffer_size=2M
read_buffer_size=2M
max_connect_errors=10
# Try number of CPU's*2 for thread_concurrency
thread_concurrency=4
myisam_sort_buffer_size=64M
#log-bin
server-id=1

[mysql.server]
user=mysql
basedir=/var/lib

[safe_mysqld]
#err-log=/var/log/mysqld.log
#pid-file=/var/lib/mysql/mysql.pid
open_files_limit=8192

[mysqldump]
quick
max_allowed_packet=16M

[mysql]
no-auto-rehash
#safe-updates

[isamchk]
key_buffer=32M
sort_buffer=32M
read_buffer=16M
write_buffer=16M

[myisamchk]
key_buffer=32M
sort_buffer=32M
read_buffer=16M
write_buffer=16M

#Accept connections from the local host only
bind-address=127.0.0.1

Re: MySQL issue after upgarde to 5.5.11

Explanation should be in the mysqld.log

110417 15:58:25 [ERROR] /usr/libexec/mysqld: unknown option '--skip-locking'
110417 15:58:25 [ERROR] Aborting

So, just remove this directive. (seems to be replace by skip-external-locking for a very long time)

Laptop:  Fedora 38 + rpmfusion + remi (SCL only)
x86_64 builder: Fedora 39 + rpmfusion + remi-test
aarch64 builder: RHEL 9 with EPEL
Hosting Server: CentOS 8 Stream with EPEL, rpmfusion, remi

Re: MySQL issue after upgarde to 5.5.11

Thanks for prompt reply.

There was two more directives which prevent MySQL to start:
- skip-locking
- skip-innodb
- record_buffer=1M

Do you think I should keep the default MySQL settings or if I change them is it going to improve performance. Do you know where I can find some correct settings for MySQL 5.5.11 to tune it up.

Re: MySQL issue after upgarde to 5.5.11

You should try mysqltunner.pl, which give you some valuable tips.

wget mysqltuner.pl
perl mysqltuner.pl

Default configuration is a minimal one. Optimization should be applied for better performance.

P.S. you can also read the sample configuration provided in /usr/share/doc/mysql-server-*/my-*.cnf

Laptop:  Fedora 38 + rpmfusion + remi (SCL only)
x86_64 builder: Fedora 39 + rpmfusion + remi-test
aarch64 builder: RHEL 9 with EPEL
Hosting Server: CentOS 8 Stream with EPEL, rpmfusion, remi

Re: MySQL issue after upgarde to 5.5.11

How can i learn MYSQL i am new to this field but i am willing to learn