오브리닷넷(Obbli.net)

오픈수세 13.1 - MySQL 을 MariaDB 로 전환시 문제점 본문

IT/오픈수세 다듬기

오픈수세 13.1 - MySQL 을 MariaDB 로 전환시 문제점

아주가끔은 2014. 1. 28. 22:59
반응형

 MySQL 을 MariaDB 로 전환시 다음의 문제점이 발생

# /etc/init.d/mysql restart
redirecting to systemctl restart mysql
Job for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details.
# systemctl status mysql.service
mysql.service - LSB: Start the MySQL database server
Loaded: loaded (/etc/init.d/mysql)
Active: failed (Result: exit-code) since 화 2014-01-28 22:45:19 KST; 11s ago
Process: 14271 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)

1월 28 22:44:49 cwart systemd[1]: Starting LSB: Start the MySQL database server...
1월 28 22:44:49 cwart mysql[14271]: Will update MySQL now, if you encounter any problems, please read following file:
1월 28 22:44:49 cwart mysql[14271]: /usr/share/doc/packages/mariadb/README.SuSE
1월 28 22:44:49 cwart mysql[14271]: Running protected MySQL...
1월 28 22:45:19 cwart mysql[14271]: error: /var/tmp/mysql-protected.6lEWYf/mysql.sock file didn't appeared...
1월 28 22:45:19 cwart mysql[14271]: Try checking "/var/log/mysql/mysqld-upgrade-run.log"...
1월 28 22:45:19 cwart mysql[14271]: ..failed
1월 28 22:45:19 cwart systemd[1]: mysql.service: control process exited, code=exited status=1
1월 28 22:45:19 cwart systemd[1]: Failed to start LSB: Start the MySQL database server.
1월 28 22:45:19 cwart systemd[1]: Unit mysql.service entered failed state.

로그대로 /var/log/mysql/mysqld-upgrade-run.log 따라 살펴보고 구글링 해보니

140128 22:49:32 mysqld_safe mysqld from pid file /var/tmp/mysql-protected.7522XJ/mysqld.pid ended
140128 22:56:51 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140128 22:56:51 InnoDB: The InnoDB memory heap is disabled
140128 22:56:51 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140128 22:56:51 InnoDB: Compressed tables use zlib 1.2.8
140128 22:56:51 InnoDB: Using Linux native AIO
140128 22:56:51 InnoDB: Initializing buffer pool, size = 128.0M
140128 22:56:51 InnoDB: Completed initialization of buffer pool
140128 22:56:51 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
140128 22:56:51 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
140128 22:56:51 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140128 22:56:51 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.

innoDB 로그 파일에 문제가 있다는 리포트 발견

https://bugzilla.novell.com/show_bug.cgi?id=844113

해결볍 찾아 링크 찾아가보니 로그파일을 모두 삭제하라는 조언, 그리고 로그파일 확인

# ls /var/lib/mysql/i*
/var/lib/mysql/ib_logfile0 /var/lib/mysql/ib_logfile1 /var/lib/mysql/ibdata1

두개의 로그파일(ib_logfile0, ib_logfile1) 확인 하고 두개 다 삭제

그리고 서버 재시작. 성공

Tags: , , , ,

Powered by Qumana

반응형