MySQL Forums
Forum List  »  InnoDB

unable connect mysql server RedHat
Posted by: chin tiau tan
Date: April 18, 2013 05:18AM

Hi MYSQL expert

i've installed mysql in linux redhat , i can start the mysql deamon

[root@localhost mysql]# service mysql status
MySQL running (7240) [ OK ]

, but i failed to connect mysql server

i run the command " mysqld -u root "

the error message as below :

2013-04-18 12:18:33 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-04-18 12:18:33 7817 [Note] Plugin 'FEDERATED' is disabled.
2013-04-18 12:18:33 7817 [Note] InnoDB: The InnoDB memory heap is disabled
2013-04-18 12:18:33 7817 [Note] InnoDB: Mutexes and rw_locks use InnoDB's own implementation
2013-04-18 12:18:33 7817 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-04-18 12:18:33 7817 [Note] InnoDB: CPU does not support crc32 instructions
2013-04-18 12:18:33 7817 [Note] InnoDB: Using Linux native AIO
2013-04-18 12:18:33 7817 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-04-18 12:18:33 7817 [Note] InnoDB: Completed initialization of buffer pool
2013-04-18 12:18:33 7817 [Note] InnoDB: Highest supported file format is Barracuda.
2013-04-18 12:18:33 7817 [Note] InnoDB: The log sequence numbers 1626007 and 1626007 in ibdata files do not match the log sequence number 1626027 in the ib_logfiles!
2013-04-18 12:18:33 7817 [Note] InnoDB: Database was not shutdown normally!
2013-04-18 12:18:33 7817 [Note] InnoDB: Starting crash recovery.
2013-04-18 12:18:33 7817 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-04-18 12:18:33 7817 [Note] InnoDB: Restoring possible half-written data pages
2013-04-18 12:18:33 7817 [Note] InnoDB: from the doublewrite buffer...
2013-04-18 12:18:33 7817 [ERROR] InnoDB: Unable to lock ./mysql/innodb_table_stats.ibd, error: 11
2013-04-18 12:18:33 7817 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2013-04-18 12:18:33 b7fb16d0 InnoDB: Assertion failure in thread 3086685904 in file line 870
InnoDB: Failing assertion: ret
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: about forcing recovery.
19:18:33 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67580 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000
The manual page at contains
information that should help you find out what is causing the crash.

please help

Options: ReplyQuote

Written By
unable connect mysql server RedHat
April 18, 2013 05:18AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.