原先,使用@base與rpmforge的更新都一切正常…
然後,想說再加上epel和remi時發現,mysql可以update到5.5…所以就更新了…
然後,重新啟動mysqld,它就跟我說「無法啟動」…
到/var/log/mysqld.log查看,看到以下的東東
mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
[Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Using Linux native AIO
InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: Completed initialization of buffer pool
InnoDB: highest supported file format is Barracuda.
InnoDB: Waiting for the background threads to start
InnoDB: 5.5.35 started; log sequence number 1589359
[ERROR] /usr/libexec/mysqld: unknown option '--skip-locking'
[ERROR] Aborting
呃…[ERROR] /usr/libexec/mysqld: unknow option '--skip-locking'
怪了,為什麼會出現它自己都不知道的option,但重點是,在我使用這一段時間與yum @base、rpmforge時也一樣更新的mysql,重啟時也沒這個問題…太怪了。
所以,眼下直覺就是mysql 5.5(或中間的版本)一定有更新了一些variable…天殺的…
只好google…首先發現
Wamp MySQL will not start: unknown option '--skip-locking'才知道還真的是在5.5做的異動,所以去mysql官方找5.5版的Reference Manual,找到
MySQL 5.5 Reference Manual :: 1 General Information :: 1.4 What Is New in MySQL 5.5異動的東西不少…不過主要我還沒用到,就一個skip-locking而已
The --enable-locking and --skip-locking server options (use --external-locking and --skip-external-locking).
2 則留言:
你是胡文霖嗎?
我不是…
張貼留言