启动MYSQL错误麻烦军哥帮忙新人一枚

cinbo 发表于 2016-8-21 12:22:12

我用的是LNMP1.2，MYSQL启动时候出现如下错误：# service mysql restart ERROR! MySQL server PID file could not be found!Starting MySQL... ERROR! The server quit without updating PID file (/usr/local/mysql/var/Cinbo.pid).
下面是这个Cinbo.err错误日志的一部分，昨天还好好的，不知道哪里的问题，突然今天这样了，VPS硬重启了启动MYSQL也是这样错误：

2016-08-20 02:34:25 1363 IP address '171.114.151.7' could not be resolved: Name or service not known
2016-08-20 03:12:33 1363 IP address '222.186.58.160' could not be resolved: Name or service not known
2016-08-20 05:42:21 1363 IP address '14.152.95.142' could not be resolved: Name or service not known
2016-08-20 08:46:16 1363 IP address '23.251.57.6' could not be resolved: Name or service not known
2016-08-20 20:57:02 1363 IP address '101.200.143.29' could not be resolved: Name or service not known
2016-08-21 01:28:37 1363 IP address '155.94.163.15' has been resolved to the host name '155.94.163.15.static.quadranet.com', which resembles IPv4-address itself.
2016-08-21 01:59:05 1363 Disk is full writing './mysql-bin.000017' (Errcode: 28 - No space left on device). Waiting for someone to free space...
2016-08-21 01:59:05 1363 Retry in 60 secs. Message reprinted in 600 secs
2016-08-21 02:09:05 1363 Disk is full writing './mysql-bin.000017' (Errcode: 28 - No space left on device). Waiting for someone to free space...
2016-08-21 02:09:05 1363 Retry in 60 secs. Message reprinted in 600 secs
2016-08-21 02:19:05 1363 Disk is full writing './mysql-bin.000017' (Errcode: 28 - No space left on device). Waiting for someone to free space...
2016-08-21 02:19:05 1363 Retry in 60 secs. Message reprinted in 600 secs
2016-08-21 02:29:05 1363 Disk is full writing './mysql-bin.000017' (Errcode: 28 - No space left on device). Waiting for someone to free space...
2016-08-21 02:29:05 1363 Retry in 60 secs. Message reprinted in 600 secs
2016-08-21 02:39:05 1363 Disk is full writing './mysql-bin.000017' (Errcode: 28 - No space left on device). Waiting for someone to free space...
2016-08-21 02:39:05 1363 Retry in 60 secs. Message reprinted in 600 secs
2016-08-21 02:49:05 1363160821 11:08:00 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
2016-08-21 11:08:02 0 TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-08-21 11:08:02 1380 Plugin 'FEDERATED' is disabled.
2016-08-21 11:08:02 b77206d0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2016-08-21 11:08:02 1380 InnoDB: Using atomics to ref count buffer pool pages
2016-08-21 11:08:02 1380 InnoDB: The InnoDB memory heap is disabled
2016-08-21 11:08:02 1380 InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-08-21 11:08:02 1380 InnoDB: Memory barrier is not used
2016-08-21 11:08:02 1380 InnoDB: Compressed tables use zlib 1.2.3
2016-08-21 11:08:02 1380 InnoDB: Not using CPU crc32 instructions
2016-08-21 11:08:02 1380 InnoDB: Initializing buffer pool, size = 16.0M
2016-08-21 11:08:02 1380 InnoDB: Completed initialization of buffer pool
2016-08-21 11:08:02 1380 InnoDB: Highest supported file format is Barracuda.
2016-08-21 11:08:02 1380 InnoDB: The log sequence numbers 1626130 and 1626130 in ibdata files do not match the log sequence number 1626140 in the ib_logfiles!
2016-08-21 11:08:02 1380 InnoDB: Database was not shutdown normally!
2016-08-21 11:08:02 1380 InnoDB: Starting crash recovery.
2016-08-21 11:08:02 1380 InnoDB: Reading tablespace information from the .ibd files...
2016-08-21 11:08:02 1380 InnoDB: Restoring possible half-written data pages
2016-08-21 11:08:02 1380 InnoDB: from the doublewrite buffer...
2016-08-21 11:08:02 1380 InnoDB: 128 rollback segment(s) are active.
2016-08-21 11:08:02 1380 InnoDB: Waiting for purge to start
2016-08-21 11:08:02 1380 InnoDB: 5.6.23 started; log sequence number 1626140
03:08:02 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 = 793794 Kbytes 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
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x33)
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x432)

/usr/local/mysql/bin/mysqld(wait_for_free_space+0x7a)
/usr/local/mysql/bin/mysqld(my_write+0x14d)
/usr/local/mysql/bin/mysqld(my_b_flush_io_cache+0x39d)
/usr/local/mysql/bin/mysqld(_ZN13MYSQL_BIN_LOG21sync_purge_index_fileEv+0x20)
/usr/local/mysql/bin/mysqld(_ZN13MYSQL_BIN_LOG11open_binlogEPKcS1_10cache_typembbbP28Format_description_log_event+0x128)
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0x3df)
/usr/local/mysql/bin/mysqld(main+0x1b)
/lib/i686/nosegneg/libc.so.6(__libc_start_main+0xe6)
/usr/local/mysql/bin/mysqld
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.
160821 11:08:02 mysqld_safe mysqld from pid file /usr/local/mysql/var/Cinbo.pid ended
160821 11:10:14 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
2016-08-21 11:10:15 0 TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-08-21 11:10:15 1948 Plugin 'FEDERATED' is disabled.
2016-08-21 11:10:15 b77d26d0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2016-08-21 11:10:15 1948 InnoDB: Using atomics to ref count buffer pool pages
2016-08-21 11:10:15 1948 InnoDB: The InnoDB memory heap is disabled
2016-08-21 11:10:15 1948 InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-08-21 11:10:15 1948 InnoDB: Memory barrier is not used
2016-08-21 11:10:15 1948 InnoDB: Compressed tables use zlib 1.2.3
2016-08-21 11:10:15 1948 InnoDB: Not using CPU crc32 instructions
2016-08-21 11:10:15 1948 InnoDB: Initializing buffer pool, size = 16.0M
2016-08-21 11:10:15 1948 InnoDB: Completed initialization of buffer pool
2016-08-21 11:10:15 1948 InnoDB: Highest supported file format is Barracuda.
2016-08-21 11:10:15 1948 InnoDB: The log sequence numbers 1626130 and 1626130 in ibdata files do not match the log sequence number 1626140 in the ib_logfiles!
2016-08-21 11:10:15 1948 InnoDB: Database was not shutdown normally!
2016-08-21 11:10:15 1948 InnoDB: Starting crash recovery.
2016-08-21 11:10:15 1948 InnoDB: Reading tablespace information from the .ibd files...
2016-08-21 11:10:15 1948 InnoDB: Restoring possible half-written data pages
2016-08-21 11:10:15 1948 InnoDB: from the doublewrite buffer...
2016-08-21 11:10:15 1948 InnoDB: 128 rollback segment(s) are active.
2016-08-21 11:10:15 1948 InnoDB: Waiting for purge to start
2016-08-21 11:10:15 1948 InnoDB: 5.6.23 started; log sequence number 1626140
03:10: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.

[ 本帖最后由 cinbo 于 2016-8-21 12:26 编辑 ]

cinbo 发表于 2016-8-21 12:26:37

难道是攻击吗？发帖时候多次提示带有攻击的请求

licess 发表于 2016-8-21 19:03:31

(Errcode: 28 - No space left on device). Waiting for someone to free space...
硬盘空间或当前分区已满

论坛发帖时有waf会拦截恶意的代码

cinbo 发表于 2016-8-21 21:39:14

空间不会满啊还多着呢，现在MYSQL 启动错误：
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
这个目录怎么就没有任何文件呢？一直就没登录过VPS 最近，突然今天网站打不开一直，这个错误莫名其妙呢，怎么解决那？磁盘空间指的是硬盘还是哪里的

[ 本帖最后由 cinbo 于 2016-8-21 21:49 编辑 ]

cinbo 发表于 2016-8-22 10:38:16

回复 3# 的帖子

已经解决了，是空间占用满的问题多谢，要研究下优化了

页: [1]

VPS侦探论坛's Archiver