AMH 社区首页
AMH社区 - 开放自由有价值的社区
[求助帖] MYSQL无法启动 |
|
---|---|
kok |
kok 发表于 2013-11-12 18:00:05
[root@localhost ~]# amh mysql
============================================================= [LNMP/Nginx] Amysql Host - AMH 4.1 http://Amysql.com [AMH] MySQL Management please select: (1~6) 1) start 3) restart 5) force-reload 2) stop 4) reload 6) exit #? 3^H^H^H^H [AMH] MySQL Management please select: (1~6) 1) start 3) restart 5) force-reload 2) stop 4) reload 6) exit #? 3 MySQL server PID file could not be found! [FAILED] Starting MySQL.The server quit without updating PID file (/usr/local/mysql/data/localhost.localdomain.pid). [FAILED] 无缘无故就这样了。。。= = 啥都没动 突然发现404 然后重启AMH 卡在MYSQL 半天 然后就直接REBOOT 在来看MYSQL 挂了
点赞,加油! (1分)
2013-11-12 18:00:05 1
|
amysql |
看MySQL错误日志。
与搜索下论坛,MySQL启动相关问题的分析帖子。
回复
2013-11-12 21:16:54 2
AMH面板 - 好用高效低占用、安全可靠极稳定 |
kok |
本帖最后由 kok 于 2013-11-13 07:51 编辑
131113 07:34:39 mysqld_safe mysqld from pid file /usr/local/mysql/data/localhost.localdomain.pid ended 这个错误在日志看不懂百度了 都和我情况好像不一样。。 全部。 131010 11:59:54 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 131010 11:59:54 [Note] Plugin 'InnoDB' is disabled. 131010 11:59:54 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 131010 11:59:54 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 131010 11:59:54 [Note] Server socket created on IP: '0.0.0.0'. 131010 11:59:54 [Note] Event Scheduler: Loaded 0 events 131010 11:59:54 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.5.33-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 131010 12:06:09 [Note] /usr/local/mysql/bin/mysqld: Normal shutdown 131010 12:06:09 [Note] Event Scheduler: Purging the queue. 0 events 131010 12:06:09 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete 131010 12:06:09 mysqld_safe mysqld from pid file /usr/local/mysql/data/localhost.localdomain.pid ended 131010 12:06:11 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 131010 12:06:12 [Note] Plugin 'InnoDB' is disabled. 131010 12:06:12 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 131010 12:06:12 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 131010 12:06:12 [Note] Server socket created on IP: '0.0.0.0'. 131010 12:06:12 [Note] Event Scheduler: Loaded 0 events 131010 12:06:12 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.5.33-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 131111 13:51:21 [Warning] Disk is full writing './mysql-bin.000004' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space) 131111 13:51:21 [Warning] Retry in 60 secs. Message reprinted in 600 secs 131111 14:01:22 [Warning] Disk is full writing './mysql-bin.000004' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space) 131111 14:01:22 [Warning] Retry in 60 secs. Message reprinted in 600 secs 131111 14:11:22 [Warning] Disk is full writing './mysql-bin.000004' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space) 131111 14:11:22 [Warning] Retry in 60 secs. Message reprinted in 600 secs 131111 14:21:23 [Warning] Disk is full writing './mysql-bin.000004' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space) 131111 14:21:23 [Warning] Retry in 60 secs. Message reprinted in 600 secs 131111 14:31:23 [Warning] Disk is full writing './mysql-bin.000004' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space) 131111 14:31:23 [Warning] Retry in 60 secs. Message reprinted in 600 secs 131111 14:41:23 [Warning] Disk is full writing './mysql-bin.000004' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space) 131111 14:41:23 [Warning] Retry in 60 secs. Message reprinted in 600 secs 131111 14:51:23 [Warning] Disk is full writing './mysql-bin.000004' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space) 131111 14:51:23 [Warning] Retry in 60 secs. Message reprinted in 600 secs 131111 15:01:23 [Warning] Disk is full writing './mysql-bin.000004' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space) 131111 15:01:23 [Warning] Retry in 60 secs. Message reprinted in 600 secs 131111 15:11:23 [Warning] Disk is full writing './mysql-bin.000004' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space) 131111 15:11:23 [Warning] Retry in 60 secs. Message reprinted in 600 secs 131111 15:21:23 [Warning] Disk is full writing './mysql-bin.000004' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space) 131111 15:21:23 [Warning] Retry i131112 17:32:32 mysqld_safe A mysqld process already exists 131112 17:34:26 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 131112 17:34:27 [Note] Plugin 'InnoDB' is disabled. 09:34:27 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 = 133460 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 0x30000 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x33)[0x83a5233] /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x390)[0x828cae0] [0xdd0420] /usr/local/mysql/bin/mysqld(wait_for_free_space+0x61)[0x838d631] /usr/local/mysql/bin/mysqld(my_write+0xe0)[0x83a3e20] /usr/local/mysql/bin/mysqld(my_b_flush_io_cache+0x46c)[0x8390cac] /usr/local/mysql/bin/mysqld(_ZN13MYSQL_BIN_LOG21sync_purge_index_fileEv+0x20)[0x8311070] /usr/local/mysql/bin/mysqld(_ZN13MYSQL_BIN_LOG4openEPKc13enum_log_typeS1_10cache_typebmbb+0xda)[0x83186aa] /usr/local/mysql/bin/mysqld[0x811dc1e] /usr/local/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0x648)[0x811e6c8] /usr/local/mysql/bin/mysqld(main+0x22)[0x81161f2] /lib/libc.so.6(__libc_start_main+0xdc)[0x8dfebc] /usr/local/mysql/bin/mysqld[0x8116111] 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. 131112 17:34:27 mysqld_safe mysqld from pid file /usr/local/mysql/data/localhost.localdomain.pid ended 131112 17:43:40 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 省略。。。。。。 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)[0x83a5233] /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x390)[0x828cae0] [0xa85420] /usr/local/mysql/bin/mysqld(wait_for_free_space+0x61)[0x838d631] /usr/local/mysql/bin/mysqld(my_write+0xe0)[0x83a3e20] /usr/local/mysql/bin/mysqld(my_b_flush_io_cache+0x46c)[0x8390cac] /usr/local/mysql/bin/mysqld(_ZN13MYSQL_BIN_LOG21sync_purge_index_fileEv+0x20)[0x8311070] /usr/local/mysql/bin/mysqld(_ZN13MYSQL_BIN_LOG4openEPKc13enum_log_typeS1_10cache_typebmbb+0xda)[0x83186aa] /usr/local/mysql/bin/mysqld[0x811dc1e] /usr/local/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0x648)[0x811e6c8] /usr/local/mysql/bin/mysqld(main+0x22)[0x81161f2] /lib/libc.so.6(__libc_start_main+0xdc)[131113 07:40:29 mysqld_safe mysqld from pid file /usr/local/mysql/data/localhost.localdomain.pid ended
回复
2013-11-13 07:42:44 3
|
kok |
找到突然这样的原因了 自动备份 一下子备份了N多个把磁盘弄满了。。。
回复
2013-11-13 07:56:15 4
|
Yusky |
;P你备份设置错了。刚才看了下
回复
2013-11-13 11:19:14 5
|
amysql |
回复
2013-11-13 13:32:19 6
|
kok |
引用: 谢谢 开始没想到这方面,论坛搜索了半天 突然想是不是满了 一查果然。。。
回复
2013-11-14 09:16:43 7
|
achome |
很困惑啊,这个遇到问题了,还是没解决
回复
2020-04-07 16:19:21 8
|
achome |
有基础教程吗,需要多学习一些
回复
2020-04-07 16:22:07 9
|