Failed to start the "mysqld" service. Cannot start/stop/rest

[tjmaster]

Hello,
my mysql server can't start again i don'tknow why.
in my mysqld.log file i can see the flowwowing line ,but i don't know how to fix it
please i need your help.

150504 04:44:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150504 4:44:52 [Warning] option 'innodb-additional-mem-pool-size': signed value 512000 adjusted to 524288
150504 4:44:52 InnoDB: Initializing buffer pool, size = 2.0M
150504 4:44:52 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
150504 4:44:52 InnoDB: Database was 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...
InnoDB: Page directory corruption: infimum not pointed to
150504 4:44:53 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex ;InnoDB: End of page dump
150504 4:44:53 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
InnoDB: Page directory corruption: supremum not pointed to
150504 4:44:53 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex ;InnoDB: End of page dump
150504 4:44:53 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
150504 4:44:53InnoDB: Error: trying to access a stray pointer 0x80007fc1244a7ff8
InnoDB: buf pool start is at 0x7fc124498000, end at 0x7fc124698000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/ ... overy.html
InnoDB: how to force recovery.
150504 4:44:53 InnoDB: Assertion failure in thread 140467589236704 in file ../../storage/innobase/include/buf0buf.ic line 264
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 be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/ ... overy.html
InnoDB: about forcing recovery.
09:44:53 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.

key_buffer_size=8384512
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338336 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 0x40000
/usr/libexec/mysqld(my_print_stacktrace+0x29) [0x850989]
/usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a3ef3]
/lib64/libpthread.so.0(+0xf710) [0x7fc128807710]
/lib64/libc.so.6(gsignal+0x35) [0x7fc126e22925]
/lib64/libc.so.6(abort+0x175) [0x7fc126e24105]
/usr/libexec/mysqld(page_cur_search_with_match+0x77b) [0x79830b]
/usr/libexec/mysqld(btr_cur_search_to_nth_level+0x6ea) [0x73bb4a]
/usr/libexec/mysqld(btr_pcur_open_on_user_rec+0x64) [0x7ea8e4]
/usr/libexec/mysqld() [0x75a21f]
/usr/libexec/mysqld(dict_load_sys_table+0x59) [0x760089]
/usr/libexec/mysqld(dict_boot+0x91c) [0x7ebd1c]
/usr/libexec/mysqld(innobase_start_or_create_for_mysql+0x11f6) [0x7c8216]
/usr/libexec/mysqld() [0x72f5fb]
/usr/libexec/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x31) [0x697941]
/usr/libexec/mysqld() [0x71758b]
/usr/libexec/mysqld(plugin_init(int*, char**, int)+0x6e4) [0x719884]
/usr/libexec/mysqld() [0x5bf202]
/usr/libexec/mysqld(main+0x1b3) [0x5c1af3]
/lib64/libc.so.6(__libc_start_main+0xfd) [0x7fc126e0ed1d]
/usr/libexec/mysqld() [0x5098f9]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
150504 04:44:53 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

[TrevorH]

You appear to have a corrupted file on your installation. What is the output from rpm -qa \*mysql\* and from rpm -Va \*mysql\* ?

[tjmaster]

Hi Trevorth!

here are ouputs :
1- rpm -qa \*mysql\*
php-mysql-5.3.3-40.el6_6.x86_64
mysql-5.1.73-3.el6_5.x86_64
mysql-server-5.1.73-3.el6_5.x86_64
mysql-libs-5.1.73-3.el6_5.x86_64
mysql-connector-odbc-5.1.5r1144-7.el6.x86_64

2-rpm -Va \*mysql\*
S.5....T. c /etc/my.cnf

[tjmaster]

Hi Everyone,

i dind't yet get solution for my problem.
my mysql server is not starting.

please is there any help.

[TrevorH]

The output from the commands you ran show that the mysql binaries are OK so it looks like the files that make up the data portion of your database are corrupted. The log output that you initially posted has several links to http://dev.mysql.com/doc/refman/5.1/en/ ... overy.html so I would read that link and see what it suggests in order to attempt to recover. If worst comes to worst I think you need to think about restoring the data from a backup.

[aks]

You've got corruption (possibly due to partial writes) in the InnoDB. You could try and force a recovery, but it is rare that it works as expected.
You should restore from backup.
Also you InnoDB buffer pool is 2MB - is that by intention?

[tjmaster]

No, Aks.
I'm the one who set InnoBDB Buffer pool to 2MB.
I was trying to reinstall mysql server , before getting this issue.