An example of a failure to start a MySQL process under Ubuntu

Source: Internet
Author: User

Failure phenomena:

MySQL cannot start

1:DMESG |grep MySQL

[101353.820000] init:mysql Post-start process (9077) terminated with status 1
[101354.650000] init:mysql main process (9113) terminated with status 1
[101354.650000] Init:mysql respawning too fast, stopped

2:grep Mysql/var/log/syslog

213 APR 1 19:35:33 asiulo kernel: [101110.450000] init:mysql Post-start process (8815) terminated with status 1
214 APR 1 19:35:33 asiulo kernel: [101110.590000] init:mysql main process (8846) terminated with status 1
215 APR 1 19:35:33 asiulo kernel: [101110.590000] init:mysql respawning too fast, stopped

3:tail-100/var/log/mysql/error.log

1 130401 10:27:28 [Note] Plugin ' federated ' is disabled.
2 130401 10:27:28 innodb:the InnoDB memory heap is disabled
3 130401 10:27:28 innodb:mutexes and rw_locks use GCC atomic builtins
4 130401 10:27:28 innodb:compressed tables use zlib 1.2.7
5 130401 10:27:28 innodb:using Linux native AIO
6 130401 10:27:28 innodb:initializing buffer pool, size = 128.0M
7 130401 10:27:28 innodb:completed initialization of buffer pool
8 130401 10:27:28 innodb:highest supported file format is Barracuda.
9 Innodb:the log sequence number in Ibdata files does not match
Innodb:the log sequence number in the ib_logfiles!
130401 10:27:28 Innodb:database is not shut down normally!
Innodb:starting crash recovery.
innodb:reading tablespace information from the. ibd files ...
innodb:restoring possible Half-written data pages from the Doublewrite
Innodb:buffer ...
130401 10:27:28 innodb:assertion Failure in thread 3062129168 on file fsp0fsp.c line 2102
Innodb:failing Assertion:inode
Innodb:we intentionally generate a memory trap.
Innodb:submit a detailed bug report to http://bugs.mysql.com.
Innodb:if you get repeated assertion failures or crashes, even
Innodb:immediately after the mysqld startup, there may
Innodb:corruption in the InnoDB tablespace. Refer to
23innodb:http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
Innodb:about forcing recovery.
02:27:28 Utc-mysqld got signal 6;
Could is because a bug. It is also possible the this binary
One of the libraries it linked against IS corrupt, improperly built,
Or misconfigured. This error can also is caused by malfunctioning hardware.
We'll try our best to scrape up some info that'll hopefully help
Diagnose the problem, but since we have already crashed,
Something is definitely wrong and this may fail.
32
key_buffer_size=16777216
read_buffer_size=131072
Max_used_connections=0
Approx. max_threads=151
Panax Notoginseng thread_count=0
Connection_count=0
It's possible that mysqld could
Key_buffer_size + (read_buffer_size + sort_buffer_size) *max_threads = 346079 K bytes of memory
Hope that ' s OK; If not, decrease some variables in the equation.
42
Thread pointer:0x0
Attempting backtrace. You can use the following information-to-find out
A where mysqld died. If you see no messages after this, something went
Terribly wrong ...
Stack_bottom = 0 Thread_stack 0x30000
Manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Information that should help you find out what's causing the crash.

Verification is the result of a innodb failure. Depending on the method in the red link:

You can add the following line to the [mysqld] section of your option file before restarting the server:

[Mysqld]
Innodb_force_recovery = 4

Add this setting to/ETC/MYSQL/MY.CNF, and the start MySQL service will return to normal.

Comments:

4 (Srv_force_no_ibuf_merge)

Prevent Insert buffer merge operations. If they would cause a crash, do not do them. Do not calculate table statistics.

The process of pre-processing the reinstallation of MySQL is also documented:

Re-install MySQL

Delete MySQL:

Apt-get Autoremove--purge Mysql-server

Apt-get Remove Mysql-common

Clean up residual data:

Dpkg-l |grep ^rc|awk ' {print $} ' |sudo Xargs dpkg-p

And then execute the next Apt-get autoremove.

Install MySQL:
Apt-get Install mysql-server-5.5
Apt-get Install mysql-client-5.5//Normal, this step is already included in the previous step, no need to install.
Apt-get Install Php5-mysql

Installation Complete execution

#dpkg-reconfigure Reconfiguration
Dpkg-reconfigure mysql-server-5.5

#quick MySQL Package check
Dpkg-l *mysql*

Disable MySQL to do domain name resolution
[Mysqld]
Skip-name-resolve

Complete!

An example of a failure to start a MySQL process under Ubuntu

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.