HTTPS
AMH 社区首页
AMH社区 - 开放自由有价值的社区
|
|
|---|---|
|
logan |
logan 发表于 2013-12-04 13:09:08
131204 9:16:04 [Warning] IP address '61.147.103.154' could not be resolved: Name or service not known
131204 9:16:04 [Warning] IP address '61.147.103.154' could not be resolved: Name or service not known 131204 12:24:31 [ERROR] /usr/local/mysql/bin/mysqld: Incorrect key file for table '/tmp/#sql_3e4c_0.MYI'; try to repair it 131204 12:24:31 [ERROR] Got an error from unknown thread, /home/amh_install/packages/untar/mysql-5.5.33/storage/myisam/mi_write.c:226 131204 12:24:50 [ERROR] /usr/local/mysql/bin/mysqld: Incorrect key file for table '/tmp/#sql_3e4c_0.MYI'; try to repair it 131204 12:24:50 [ERROR] Got an error from unknown thread, /home/amh_install/packages/untar/mysql-5.5.33/storage/myisam/mi_write.c:226 131204 12:24:52 [ERROR] /usr/local/mysql/bin/mysqld: Sort aborted: Error writing file '/tmp/MYLnVLpM' (Errcode: 28) 131204 12:24:52 [ERROR] /usr/local/mysql/bin/mysqld: Sort aborted: Error writing file '/tmp/MYaCxzMf' (Errcode: 28) 131204 12:24:52 [ERROR] /usr/local/mysql/bin/mysqld: Sort aborted: Error writing file '/tmp/MYYQBCtJ' (Errcode: 28) 131204 12:24:58 [ERROR] /usr/local/mysql/bin/mysqld: Sort aborted: Error writing file '/tmp/MYoTjoVx' (Errcode: 28) 131204 12:24:58 [ERROR] /usr/local/mysql/bin/mysqld: Sort aborted: Error writing file '/tmp/MYCS4ajH' (Errcode: 28) 131204 12:24:59 [Warning] Disk is full writing './mysql-bin.000006' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay f131204 12:32:01 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 131204 12:32:01 [Note] Plugin 'InnoDB' is disabled. 04:32:01 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=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 = 134081 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+0x2e)[0x76e43e] /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x386)[0x657906] /lib64/libpthread.so.0[0x2b7c2057fca0] 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. 131204 12:32:01 mysqld_safe mysqld from pid file /usr/local/mysql/data/MyCloudServer.pid ended 131204 12:33:15 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 131204 12:33:15 [Note] Plugin 'InnoDB' is disabled. 04:33: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=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 = 134081 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+0x2e)[0x76e43e] /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x386)[0x657906] /lib64/libpthread.so.0[0x2ad1ee499ca0] 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. 131204 12:33:15 mysqld_safe mysqld from pid file /usr/local/mysql/data/MyCloudServer.pid ended 131204 12:35:52 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 131204 12:35:52 [Note] Plugin 'InnoDB' is disabled. 131204 12:35:52 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 131204 12:35:52 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 131204 12:35:52 [Note] Server socket created on IP: '0.0.0.0'. 131204 12:35:52 [Note] Event Scheduler: Loaded 0 events 131204 12:35:52 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.5.33-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution ========================================================= 这几天来一直这样，刚刚还好好的一会面板 网站都打不开了 ，要重启服务器，在启动数据库 才可以 支持
2013-12-04 13:09:08 1
|
[求助帖]
数据库链接失败！管理帮忙分析下日志
