← Back to team overview

maria-discuss team mailing list archive

Re: Change from MySQL to MariaDB - Problem with EVENTS-Table in information_schema


Am 20.12.2013 um 20:28 schrieb Reindl Harald:
> i thought more about
> * stop server
> * backup datadir
> * delete the db-folder from filesystem

There is no folder for information_schema.

"They are actually views, not base tables, so there are no files
associated with them... Also, there is no database directory with that
>From http://dev.mysql.com/doc/refman/5.5/en/information-schema.html

> before trying this try i "repair table" on any table in this meta-db!
This still doesn't work because I still have no rights:
Access denied for user 'root'@'localhost' to database 'information_schema'

> the following command may do the same easier
> mysqlcheck -h localhost --check-upgrade --all-databases --auto-repair
> --user=root -p

No change.

> what maybe interesting to post
> * stop mysqld
> * make the mysqld-log empty
> * start mysqld
> * post the complete output of the mysqld-log

I didn't find the mysqld-log, the files

and mysql.err are empty.
So I set (uncommented) in my.cnf

general_log_file        = /var/log/mysql/mysql.log
general_log             = 1

and now I get here, when I start mysql:

/usr/sbin/mysqld, Version: 5.5.34-MariaDB-1~precise-log (mariadb.org
binary distribution). started with:
Tcp port: 3306  Unix socket: /var/run/mysqld/mysqld.sock
Time                 Id Command    Argument

Not very interesting.
But I found in the syslog since yesterday noon every 2 minutes (!!!)
these entries:

Dec 19 12:02:12 myserver kernel: [1315576.363594] init: mysql main
process (9025) terminated with status 1
Dec 19 12:02:12 myserver kernel: [1315576.363659] init: mysql main
process ended, respawning
Dec 19 12:02:12 myserver /etc/mysql/debian-start[10200]: Upgrading MySQL
tables if necessary.
Dec 19 12:02:12 myserver /etc/mysql/debian-start[10203]:
/usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 19 12:02:12 myserver /etc/mysql/debian-start[10203]: Looking for
'mysql' as: /usr/bin/mysql
Dec 19 12:02:12 myserver /etc/mysql/debian-start[10203]: Looking for
'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 19 12:02:12 myserver /etc/mysql/debian-start[10203]: This
installation of MySQL is already upgraded to 5.5.34-MariaDB, use --force
if you still need to run mysql_upgrade
Dec 19 12:02:12 myserver /etc/mysql/debian-start[10214]: Checking for
insecure root accounts.
Dec 19 12:02:12 myserver /etc/mysql/debian-start[10219]: Triggering
myisam-recover for all MyISAM tables

(I replaced my server's name with myserver)

Do I understand this right, that every 2 minutes mysql server is
crashing (terminated with status 1)???
I don't find a hint in the syslog what could crash mysql.

And to restart mysql (service mysql restart) it takes about a minute!
This seems unnormal too.
I think I have a problem.

This is my my.cnf:

port        = 3306
socket        = /var/run/mysqld/mysqld.sock
socket        = /var/run/mysqld/mysqld.sock
nice        = 0
user        = mysql
pid-file    = /var/run/mysqld/mysqld.pid
socket        = /var/run/mysqld/mysqld.sock
port        = 3306
basedir        = /usr
datadir        = /var/lib/mysql
tmpdir        = /tmp
lc-messages-dir    = /usr/share/mysql
bind-address        =
key_buffer        = 16M
max_allowed_packet    = 16M
thread_stack        = 192K
thread_cache_size       = 8
myisam-recover         = BACKUP
query_cache_limit    = 1M
query_cache_size        = 16M
expire_logs_days    = 10
max_binlog_size         = 100M
max_allowed_packet    = 16M
key_buffer        = 16M
!includedir /etc/mysql/conf.d/

Follow ups