VPS侦探论坛

 找回密码
 注册
查看: 7503|回复: 6

[Oracle] 【新手小白求救】mysql 启动MySQL server PID file could not be found!

[复制链接]
发表于 2016-3-18 21:10:22 | 显示全部楼层 |阅读模式

centos 64位key_buffer_size=1677160318 20:32:35 mysqld_safe mysqld from pid file /usr/local/mysql/var/VM_10_67_centos.pid ended160318 20:47:14 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var160318 20:47:14 InnoDB: The InnoDB memory heap is disabled160318 20:47:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins160318 20:47:14 InnoDB: Compressed tables use zlib 1.2.7160318 20:47:14 InnoDB: Initializing buffer pool, size = 16.0M160318 20:47:14 InnoDB: Completed initialization of buffer pool160318 20:47:14 InnoDB: highest supported file format is Barracuda.InnoDB: Log scan progressed past the checkpoint lsn 208366134160318 20:47:14  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 doublewriteInnoDB: buffer...InnoDB: Doing recovery: scanned up to log sequence number 208366144InnoDB: Last MySQL binlog file position 0 2699, file name ./mysql-bin.000008160318 20:47:14  InnoDB: Waiting for the background threads to start160318 20:47:15 InnoDB: 5.5.42 started; log sequence number 20836614412:47:15 UTC - mysqld got signal 11 ;This could be because you hit a bug. It is also possible that this binaryor 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 helpdiagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.key_buffer_size=16777216read_buffer_size=262144max_used_connections=0max_threads=1000thread_count=0connection_count=0It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 795907 K  bytes of memoryHope that's ok; if not, decrease some variables in the equation.Thread pointer: 0x0Attempting backtrace. You can use the following information to find outwhere mysqld died. If you see no messages after this, something wentterribly wrong...stack_bottom = 0 thread_stack 0x40000/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x20)[0x75e1a0]/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x359)[0x656b59]/usr/lib64/libpthread.so.0(+0xf130)[0x7fe49e4b0130]The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html containsinformation that should help you find out what is causing the crash.160318 20:47:15 mysqld_safe mysqld from pid file /usr/local/mysql/var/VM_10_67_centos.pid ended

本帖子中包含更多资源

您需要 登录 才可以下载或查看,没有账号?注册

x
美国VPS推荐: 遨游主机LinodeLOCVPS主机云搬瓦工80VPSVultr美国VPS主机中国VPS推荐: 阿里云腾讯云。LNMP付费服务(代装/问题排查)QQ 503228080
 楼主| 发表于 2016-3-18 21:13:12 | 显示全部楼层


日志文件
说明
军哥怎么办呐????????????????????????????????????



key_buffer_size=16777216
read_buffer_size=262144
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 = 795907 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+0x20)[0x75e1a0]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x359)[0x656b59]
/usr/lib64/libpthread.so.0(+0xf130)[0x7f09e0e94130]
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.
160318 20:31:55 mysqld_safe mysqld from pid file /usr/local/mysql/var/VM_10_67_centos.pid ended
160318 20:32:33 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
160318 20:32:33 InnoDB: The InnoDB memory heap is disabled
160318 20:32:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160318 20:32:33 InnoDB: Compressed tables use zlib 1.2.7
160318 20:32:34 InnoDB: Initializing buffer pool, size = 16.0M
160318 20:32:34 InnoDB: Completed initialization of buffer pool
160318 20:32:34 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 208366134
160318 20:32:34  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: Doing recovery: scanned up to log sequence number 208366144
InnoDB: Last MySQL binlog file position 0 2699, file name ./mysql-bin.000008
160318 20:32:34  InnoDB: Waiting for the background threads to start
160318 20:32:35 InnoDB: 5.5.42 started; log sequence number 208366144
12:32:35 UTC - mysqld got signal 11 ;
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=1677160318 20:32:35 mysqld_safe mysqld from pid file /usr/local/mysql/var/VM_10_67_centos.pid ended
160318 20:47:14 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
160318 20:47:14 InnoDB: The InnoDB memory heap is disabled
160318 20:47:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160318 20:47:14 InnoDB: Compressed tables use zlib 1.2.7
160318 20:47:14 InnoDB: Initializing buffer pool, size = 16.0M
160318 20:47:14 InnoDB: Completed initialization of buffer pool
160318 20:47:14 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 208366134
160318 20:47:14  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: Doing recovery: scanned up to log sequence number 208366144
InnoDB: Last MySQL binlog file position 0 2699, file name ./mysql-bin.000008
160318 20:47:14  InnoDB: Waiting for the background threads to start
160318 20:47:15 InnoDB: 5.5.42 started; log sequence number 208366144
12:47:15 UTC - mysqld got signal 11 ;
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=262144
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 = 795907 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+0x20)[0x75e1a0]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x359)[0x656b59]
/usr/lib64/libpthread.so.0(+0xf130)[0x7fe49e4b0130]
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.
160318 20:47:15 mysqld_safe mysqld from pid file /usr/local/mysql/var/VM_10_67_centos.pid ended
Linux下Nginx+MySQL+PHP自动安装工具:https://lnmp.org
发表于 2016-3-18 21:25:27 | 显示全部楼层

首先检查硬盘或分区占用情况,再看https://bbs.vpser.net/thread-13040-1-1.html
美国VPS推荐: 遨游主机LinodeLOCVPS主机云搬瓦工80VPSVultr美国VPS主机中国VPS推荐: 阿里云腾讯云。LNMP付费服务(代装/问题排查)QQ 503228080
 楼主| 发表于 2016-3-18 21:49:25 | 显示全部楼层

http://bbs.vpser.net/thread-13040-1-1.html




军哥还是不行啊,怎么办好急啊,拜托军哥了。
Linux下Nginx+MySQL+PHP自动安装工具:https://lnmp.org
 楼主| 发表于 2016-3-18 22:32:25 | 显示全部楼层

回复 3# 的帖子


军哥还是不行啊,怎么办好急啊,拜托军哥了。

军哥运维代购:http://shop63846532.taobao.com/

发表于 2016-3-19 09:52:29 | 显示全部楼层

目前别没其他什么好办法
发表于 2016-6-15 10:38:39 | 显示全部楼层

和你一个问题,解决没有呀
美国VPS推荐: 遨游主机LinodeLOCVPS主机云搬瓦工80VPSVultr美国VPS主机中国VPS推荐: 阿里云腾讯云。LNMP付费服务(代装/问题排查)QQ 503228080
您需要登录后才可以回帖 登录 | 注册

本版积分规则

小黑屋|手机版|Archiver|VPS侦探 ( 鲁ICP备16040043号-1 )

GMT+8, 2024-12-5 22:10 , Processed in 0.032285 second(s), 17 queries .

Powered by Discuz! X3.4

© 2001-2023 Discuz! Team.

快速回复 返回顶部 返回列表