面板进入突然出问题

今天进入面板突然就出现如下截图，已建的网站除了静态的可以访问，其余的也访问不了，面板是LInux系统的

完蛋啊，网站都没搞备份

参考此帖解决
http://www.bt.cn/bbs/thread-527-1-1.html

遇到同样的问题，按照帖子的操作，仍然失败。
自从201612.29，服务器未做任何登录。今天一登录就出现这个。

d5d 发表于 2017-2-20 11:03
遇到同样的问题，按照帖子的操作，仍然失败。
自从201612.29，服务器未做任何登录。今天一登录就出现这个。 ...

错误日志发出来看看

hitrun 发表于 2017-2-20 12:03
错误日志发出来看看

[root@btcn ~]# cat /www/server/data/*.err
161222 06:11:35 mysqld_safe Starting mysqld daemon with databases from /www/server/data
161222  6:11:35 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
161222  6:11:35 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.53-log) starting as process 38791 ...
161222  6:11:35 [Note] Plugin 'FEDERATED' is disabled.
161222  6:11:35 InnoDB: The InnoDB memory heap is disabled
161222  6:11:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
161222  6:11:35 InnoDB: Compressed tables use zlib 1.2.3
161222  6:11:35 InnoDB: Using Linux native AIO
161222  6:11:35 InnoDB: Initializing buffer pool, size = 1.0G
161222  6:11:35 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file /www/server/data/ibdata1 did not exist:
InnoDB: a new database to be created!
161222  6:11:35  InnoDB: Setting file /www/server/data/ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
161222  6:11:35  InnoDB: Log file /www/server/data/ib_logfile0 did not exist: new to be created
InnoDB: Setting log file /www/server/data/ib_logfile0 size to 256 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100 200
161222  6:11:36  InnoDB: Log file /www/server/data/ib_logfile1 did not exist: new to be created
InnoDB: Setting log file /www/server/data/ib_logfile1 size to 256 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100 200
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
161222  6:11:38  InnoDB: Waiting for the background threads to start
161222  6:11:39 InnoDB: 5.5.53 started; log sequence number 0
161222  6:11:39 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
161222  6:11:39 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
161222  6:11:39 [Note] Server socket created on IP: '0.0.0.0'.
161222  6:11:39 [Note] Event Scheduler: Loaded 0 events
161222  6:11:39 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.53-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
161222  6:17:37 [Note] /www/server/mysql/bin/mysqld: Normal shutdown

161222  6:17:37 [Note] Event Scheduler: Purging the queue. 0 events
161222  6:17:37  InnoDB: Starting shutdown...
161222  6:17:37  InnoDB: Shutdown completed; log sequence number 1595675
161222  6:17:37 [Note] /www/server/mysql/bin/mysqld: Shutdown complete

161222 06:17:37 mysqld_safe mysqld from pid file /www/server/data/btcn.pid ended
161222 06:17:38 mysqld_safe Starting mysqld daemon with databases from /www/server/data
161222  6:17:38 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
161222  6:17:38 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.53-log) starting as process 49820 ...
161222  6:17:38 [Note] Plugin 'FEDERATED' is disabled.
161222  6:17:38 InnoDB: The InnoDB memory heap is disabled
161222  6:17:38 InnoDB: Mutexes and rw_locks use GCC atomic builtins
161222  6:17:38 InnoDB: Compressed tables use zlib 1.2.3
161222  6:17:38 InnoDB: Using Linux native AIO
161222  6:17:38 InnoDB: Initializing buffer pool, size = 1.0G
161222  6:17:38 InnoDB: Completed initialization of buffer pool
161222  6:17:38 InnoDB: highest supported file format is Barracuda.
161222  6:17:38  InnoDB: Waiting for the background threads to start
161222  6:17:39 InnoDB: 5.5.53 started; log sequence number 1595675
161222  6:17:39 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
161222  6:17:39 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
161222  6:17:39 [Note] Server socket created on IP: '0.0.0.0'.
161222  6:17:39 [Note] Event Scheduler: Loaded 0 events
161222  6:17:39 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.53-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
161229  8:02:17 [Note] /www/server/mysql/bin/mysqld: Normal shutdown

161229  8:02:17 [Note] Event Scheduler: Purging the queue. 0 events
161229  8:02:17  InnoDB: Starting shutdown...
161229  8:02:18  InnoDB: Shutdown completed; log sequence number 11296358
161229  8:02:18 [Note] /www/server/mysql/bin/mysqld: Shutdown complete

161229 08:02:18 mysqld_safe mysqld from pid file /www/server/data/btcn.pid ended
161229 08:02:19 mysqld_safe Starting mysqld daemon with databases from /www/server/data
161229  8:02:19 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
161229  8:02:19 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.53-log) starting as process 53677 ...
161229  8:02:19 [Note] Plugin 'FEDERATED' is disabled.
161229  8:02:19 InnoDB: The InnoDB memory heap is disabled
161229  8:02:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins
161229  8:02:19 InnoDB: Compressed tables use zlib 1.2.3
161229  8:02:19 InnoDB: Using Linux native AIO
161229  8:02:19 InnoDB: Initializing buffer pool, size = 1.0G
161229  8:02:20 InnoDB: Completed initialization of buffer pool
161229  8:02:20 InnoDB: highest supported file format is Barracuda.
161229  8:02:20  InnoDB: Waiting for the background threads to start
161229  8:02:21 InnoDB: 5.5.53 started; log sequence number 11296358
161229  8:02:21 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
161229  8:02:21 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
161229  8:02:21 [Note] Server socket created on IP: '0.0.0.0'.
161229  8:02:21 [Note] Event Scheduler: Loaded 0 events
161229  8:02:21 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.53-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
161229  8:03:05 [Note] /www/server/mysql/bin/mysqld: Normal shutdown

161229  8:03:05 [Note] Event Scheduler: Purging the queue. 0 events
161229  8:03:05  InnoDB: Starting shutdown...
161229  8:03:06  InnoDB: Shutdown completed; log sequence number 11298220
161229  8:03:06 [Note] /www/server/mysql/bin/mysqld: Shutdown complete

161229 08:03:06 mysqld_safe mysqld from pid file /www/server/data/btcn.pid ended
161229 08:05:29 mysqld_safe Starting mysqld daemon with databases from /www/server/data
161229  8:05:30 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
161229  8:05:30 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.53-log) starting as process 2203 ...
161229  8:05:30 [Note] Plugin 'FEDERATED' is disabled.
161229  8:05:30 InnoDB: The InnoDB memory heap is disabled
161229  8:05:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins
161229  8:05:30 InnoDB: Compressed tables use zlib 1.2.3
161229  8:05:30 InnoDB: Using Linux native AIO
161229  8:05:30 InnoDB: Initializing buffer pool, size = 1.0G
161229  8:05:30 InnoDB: Completed initialization of buffer pool
161229  8:05:30 InnoDB: highest supported file format is Barracuda.
161229  8:05:30  InnoDB: Waiting for the background threads to start
161229  8:05:31 InnoDB: 5.5.53 started; log sequence number 11298220
161229  8:05:31 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
161229  8:05:31 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
161229  8:05:31 [Note] Server socket created on IP: '0.0.0.0'.
161229  8:05:31 [Note] Event Scheduler: Loaded 0 events
161229  8:05:31 [Note] /www/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.53-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
170119 20:41:13 [Warning] Disk is full writing './mysql-bin.000006' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
170119 20:41:13 [Warning] Retry in 60 secs. Message reprinted in 600 secs
170119 20:51:13 [Warning] Disk is full writing './mysql-bin.000006' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
170119 20:51:13 [Warning] Retry in 60 secs. Message reprinted in 600 secs
170119 21:01:13 [Warning] Disk is full writing './mysql-bin.000006' (Errcode: 28). Waiting for someone to free space... (Exp170220 03:36:45 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170220  3:36:45 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
170220  3:36:45 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.53-log) starting as process 3538 ...
170220  3:36:45 [Note] Plugin 'FEDERATED' is disabled.
170220  3:36:45 InnoDB: The InnoDB memory heap is disabled
170220  3:36:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170220  3:36:45 InnoDB: Compressed tables use zlib 1.2.3
170220  3:36:45 InnoDB: Using Linux native AIO
170220  3:36:45 InnoDB: Initializing buffer pool, size = 1.0G
170220  3:36:45 InnoDB: Completed initialization of buffer pool
170220  3:36:45  InnoDB: Log file /www/server/data/ib_logfile0 did not exist: new to be created
InnoDB: Setting log file /www/server/data/ib_logfile0 size to 256 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB:170220  3:36:45  InnoDB: Error: Write to file /www/server/data/ib_logfile0 failed at offset 0 0.
InnoDB: 1048576 bytes should have been written, only -1 were written.
InnoDB: Operating system error number 28.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 28 means 'No space left on device'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/ ... em-error-codes.html
InnoDB: Error in creating /www/server/data/ib_logfile0: probably out of disk space
170220  3:36:45 [ERROR] Plugin 'InnoDB' init function returned error.
170220  3:36:45 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
02:36:45 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=268435456
read_buffer_size=4194304
max_used_connections=0
max_threads=500
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 = 4363909 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
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x76231e]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x65659a]
/lib64/libpthread.so.0[0x3ab8e0f7e0]
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.
170220 03:36:45 mysqld_safe mysqld from pid file /www/server/data/btcn.pid ended
170220 03:40:30 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170220  3:40:30 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
170220  3:40:30 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.53-log) starting as process 4061 ...
170220  3:40:30 [Note] Plugin 'FEDERATED' is disabled.
170220  3:40:30 InnoDB: The InnoDB memory heap is disabled
170220  3:40:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170220  3:40:30 InnoDB: Compressed tables use zlib 1.2.3
170220  3:40:30 InnoDB: Using Linux native AIO
170220  3:40:30 InnoDB: Initializing buffer pool, size = 1.0G
170220  3:40:30 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file /www/server/data/ib_logfile0 is of different size 0 0 bytes
InnoDB: than specified in the .cnf file 0 268435456 bytes!
170220  3:40:30 [ERROR] Plugin 'InnoDB' init function returned error.
170220  3:40:30 [ERROR]170220 03:40:30 mysqld_safe mysqld from pid file /www/server/data/btcn.pid ended
170220 03:44:34 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170220  3:44:34 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
170220  3:44:34 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.53-log) starting as process 2230 ...
170220 03:47:08 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170220  3:47:09 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
170220  3:47:09 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.53-log) starting as process 2223 ...
170220  3:47:09 [Note] Plugin 'FEDERATED' is disabled.
170220  3:47:09 InnoDB: The InnoDB memory heap is disabled
170220  3:47:09 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170220  3:47:09 InnoDB: Compressed tables use zlib 1.2.3
170220  3:47:09 InnoDB: Using Linux native AIO
170220  3:47:09 InnoDB: Initializing buffer pool, size = 1.0G
170220  3:47:09 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file /www/server/data/ib_logfile0 is of different size 0 0 bytes
InnoDB: than specified in the .cnf file 0 268435456 bytes!
170220  3:47:09 [ERROR] Plugin 'InnoDB' init function returned error.
170220  3:47:09 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
02:47:09 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=268435456
read_buffer_size=4194304
max_used_connections=0
max_threads=500
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 = 4363909 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
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x76231e]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x65659a]
/lib64/libpthread.so.0[0x3ab8e0f7e0]
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.
170220 03:47:09 mysqld_safe mysqld from pid file /www/server/data/btcn.pid ended
170220 04:00:56 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170220  4:00:56 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
170220  4:00:56 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.53-log) starting as process 3205 ...
170220  4:00:56 [Note] Plugin 'FEDERATED' is disabled.
170220  4:00:56 InnoDB: The InnoDB memory heap is disabled
170220  4:00:56 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170220  4:00:56 InnoDB: Compressed tables use zlib 1.2.3
170220  4:00:56 InnoDB: Using Linux native AIO
170220  4:00:56 InnoDB: Initializing buffer pool, size = 1.0G
170220  4:00:56 InnoDB: Completed initialization of buffer pool
170220  4:00:56  InnoDB: Log file /www/server/data/ib_logfile0 did not exist: new to be created
InnoDB: Setting log file /www/server/data/ib_logfile0 size to 256 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB:170220  4:00:56  InnoDB: Error: Write to file /www/server/data/ib_logfile0 failed at offset 0 0.
InnoDB: 1048576 bytes should have been written, only -1 were written.
InnoDB: Operating system error number 28.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk 170220 04:00:56 mysqld_safe mysqld from pid file /www/server/data/btcn.pid ended
[root@btcn ~]#

d5d 发表于 2017-2-20 13:36
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where  ...

进入ssh输入df 看磁盘是否占用满了没空间了

hitrun 发表于 2017-2-20 14:09
进入ssh输入df 看磁盘是否占用满了没空间了

[root@ ~]# df
Filesystem      1K-blocks       Used Available Use% Mounted on
/dev/sda2      1921461120 1920824332         0 100% /
tmpfs             8143936          0   8143936   0% /dev/shm
/dev/sda1          194241      38325    145676  21% /boot

[root@ ~]# df -i
Filesystem        Inodes  IUsed     IFree IUse% Mounted on
/dev/sda2      122019840 110143 121909697    1% /
tmpfs            2035984      1   2035983    1% /dev/shm
/dev/sda1          51200     39     51161    1% /boot

hitrun 发表于 2017-2-19 22:28
参考此帖解决
http://www.bt.cn/bbs/thread-527-1-1.html

参照帖子已解决，谢谢

hitrun 发表于 2017-2-19 22:28
参考此帖解决
http://www.bt.cn/bbs/thread-527-1-1.html

参照帖子已解决，谢谢

[root@~]# service mysqld start
Starting MySQL. ERROR! The server quit without updating PID file (/www/server/data/btcn.pid).

You must reply to abuses on 48 hours max. After this delay, your server will be shutdown


可能被XX了。