MySQL启动报错 Starting MySQL.The server quit without updating PID file-问答-阿里云开发者社区-阿里云

开发者社区> tianyuchen> 正文

MySQL启动报错 Starting MySQL.The server quit without updating PID file

2016-11-16 10:27:14 2071 1

启动日志如下,帮忙找下问题所在
161116 09:30:31 mysqld_safe Starting mysqld daemon with databases from /data/mysql
2016-11-16 09:30:31 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.6.27-log) starting as process 12925 ...
2016-11-16 09:30:31 12925 [Note] Plugin 'FEDERATED' is disabled.
2016-11-16 09:30:31 12925 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-11-16 09:30:31 12925 [Note] InnoDB: The InnoDB memory heap is disabled
2016-11-16 09:30:31 12925 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-11-16 09:30:31 12925 [Note] InnoDB: Memory barrier is not used
2016-11-16 09:30:31 12925 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-11-16 09:30:31 12925 [Note] InnoDB: Using CPU crc32 instructions
2016-11-16 09:30:31 12925 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-11-16 09:30:31 12925 [Note] InnoDB: Completed initialization of buffer pool
2016-11-16 09:30:31 12925 [Note] InnoDB: Highest supported file format is Barracuda.
2016-11-16 09:30:31 12925 [Note] InnoDB: 128 rollback segment(s) are active.
2016-11-16 09:30:31 12925 [Note] InnoDB: Waiting for purge to start
2016-11-16 09:30:31 7ff87f3fa700 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
2016-11-16 09:30:31 7ff87f3fa700 InnoDB: Assertion failure in thread 140705263494912 in file fil0fil.cc line 875
InnoDB: Failing assertion: ret
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
01:30:31 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=16777216
read_buffer_size=2097152
max_used_connections=0
max_threads=1000
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 = 10269157 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/local/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0x90109c]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x357)[0x6727c7]
/lib64/libpthread.so.0(+0xf130)[0x7ff894de9130]
/lib64/libc.so.6(gsignal+0x37)[0x7ff893df45d7]
/lib64/libc.so.6(abort+0x148)[0x7ff893df5cc8]
/usr/local/mysql/bin/mysqld[0xa6ee11]
/usr/local/mysql/bin/mysqld[0xa6f03e]
/usr/local/mysql/bin/mysqld[0xa76873]
/usr/local/mysql/bin/mysqld[0xa419f9]
/usr/local/mysql/bin/mysqld[0xa2a591]
/usr/local/mysql/bin/mysqld[0xa106c5]
/usr/local/mysql/bin/mysqld[0x9babd5]
/usr/local/mysql/bin/mysqld[0x9b7927]
/usr/local/mysql/bin/mysqld[0x9b94f7]
/usr/local/mysql/bin/mysqld[0x989bd2]
/usr/local/mysql/bin/mysqld[0x9dd72e]
/usr/local/mysql/bin/mysqld[0x9d06c7]
/lib64/libpthread.so.0(+0x7df5)[0x7ff894de1df5]
/lib64/libc.so.6(clone+0x6d)[0x7ff893eb51ad]
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.
161116 09:30:31 mysqld_safe mysqld from pid file /data/mysql/mysql.pid ended

取消 提交回答
全部回答(1)
  • dongshan8
    2019-07-17 20:26:23

    题主您好,

    看提示信息,好象是权限问题,或部分文件损坏了。

    0 0
相关问答

17

回答

【大咖问答】对话PostgreSQL 中国社区发起人之一,阿里云数据库高级专家 德哥

阿里ACE 彭飞 2019-07-10 09:36:10 961272浏览量 回答数 17

145

回答

【新手入门】云服务器linux使用手册

fanyue88888 2012-11-26 17:14:18 157032浏览量 回答数 145

8

回答

OceanBase 使用动画(持续更新)

mq4096 2019-02-20 17:16:36 333771浏览量 回答数 8

3

回答

请问postgres实时同步数据到mysql数据库有什么好的方案吗?

toni3 2019-06-29 14:55:43 115758浏览量 回答数 3

2

回答

mySQL数据库报错You have an error in your SQL syntax

落地花开啦 2016-02-14 16:09:24 126009浏览量 回答数 2

38

回答

安全组详解,新手必看教程

我的中国 2017-11-30 15:23:46 256820浏览量 回答数 38

249

回答

阿里云LNAMP(Linux + Nginx + Apache + MySQL + PHP)环境一键安装脚本

云代维 2014-02-14 15:26:06 302548浏览量 回答数 249

97

回答

Redhat/CentOS一键安装web环境全攻略

xiaofanqie 2011-08-11 14:51:38 123170浏览量 回答数 97

2

回答

区域选择帮助

fanyue88888 2012-12-07 15:54:30 203971浏览量 回答数 2

10

回答

【精品问答合集】MongoDB热门问答

李博 bluemind 2019-05-29 16:50:19 120833浏览量 回答数 10
+关注
tianyuchen
我什么都不知道...
0
文章
1
问答
问答排行榜
最热
最新
推荐问答
相关电子书
更多
文娱运维技术
立即下载
《SaaS模式云原生数据仓库应用场景实践》
立即下载
《看见新力量:二》电子书
立即下载