root@AY140317001652599dc4Z:~# amh mysql start
=============================================================
[Linux] AMH 5.0
http://amh.sh

[mysql start]
=============================================================
=============================================================
[Linux] AMH 5.0
http://amh.sh

[mysql-5.5.37 start]
=============================================================
mysql-5.5.37
[OK] mysql-5.5.37 is already installed.
Starting MySQL
.The server quit without updating PID file (/home/usrdata/mysql-5.5.37/mysql.pid). ... failed!
140929 14:43:32 mysqld_safe Starting mysqld daemon with databases from /home/usrdata/mysql-5.5.37
140929 14:43:32 [Note] Plugin 'InnoDB' is disabled.
140929 14:43:32 [Note] Event Scheduler: Loaded 0 events
140929 14:43:32 [Note] /usr/local/mysql-5.5.37/bin/mysqld: ready for connections.
Version: '5.5.37-log' socket: '/tmp/mysql-5.5.37.sock' port: 0 Source distribution
140929 15:04:21 [Note] /usr/local/mysql-5.5.37/bin/mysqld: Normal shutdown

140929 15:04:21 [Note] Event Scheduler: Purging the queue. 0 events
140929 15:04:23 [Warning] /usr/local/mysql-5.5.37/bin/mysqld: Forcing close of thread 204 user: 'root'

140929 15:04:23 [Note] /usr/local/mysql-5.5.37/bin/mysqld: Shutdown complete

140929 15:04:23 mysqld_safe mysqld from pid file /home/usrdata/mysql-5.5.37/mysql.pid ended
140929 15:04:24 mysqld_safe Starting mysqld daemon with databases from /home/usrdata/mysql-5.5.37
140929 15:04:24 [Note] Plugin 'InnoDB' is disabled.
140929 15:04:24 [Note] Event Scheduler: Loaded 0 events
140929 15:04:24 [Note] /usr/local/mysql-5.5.37/bin/mysqld: ready for connections.
Version: '5.5.37-log' socket: '/tmp/mysql-5.5.37.sock' port: 0 Source distribution
140929 23:26:05 [Note] /usr/local/mysql-5.5.37/bin/mysqld: Normal shutdown

140929 23:26:05 [Note] Event Scheduler: Purging the queue. 0 events
140929 23:26:07 [Warning] /usr/local/mysql-5.5.37/bin/mysqld: Forcing close of thread 1985 user: 'root'

140929 23:26:07 [Note] /usr/local/mysql-5.5.37/bin/mysqld: Shutdown complete

140929 23:26:07 mysqld_safe mysqld from pid file /home/usrdata/mysql-5.5.37/mysql.pid ended
140929 23:26:09 mysqld_safe Starting mysqld daemon with databases from /home/usrdata/mysql-5.5.37
140929 23:26:09 [Note] Plugin 'InnoDB' is disabled.
140929 23:26:09 [Note] Event Scheduler: Loaded 0 events
140929 23:26:09 [Note] /usr/local/mysql-5.5.37/bin/mysqld: ready for connections.
Version: '5.5.37-log' socket: '/tmp/mysql-5.5.37.sock' port: 0 Source distribution
141120 16:53:24 mysqld_safe A mysqld process already exists
141120 16:53:25 [Note] /usr/local/mysql-5.5.37/bin/mysqld: Normal shutdown

141120 16:53:25 [Note] Event Scheduler: Purging the queue. 0 events
141120 16:53:26 [Note] /usr/local/mysql-5.5.37/bin/mysqld: Shutdown complete

141120 16:53:26 mysqld_safe mysqld from pid file /home/usrdata/mysql-5.5.37/mysql.pid ended
141120 16:54:51 mysqld_safe Starting mysqld daemon with databases from /home/usrdata/mysql-5.5.37
141120 16:54:52 [Note] Plugin 'InnoDB' is disabled.
141120 16:54:52 [Note] Event Scheduler: Loaded 0 events
141120 16:54:52 [Note] /usr/local/mysql-5.5.37/bin/mysqld: ready for connections.
Version: '5.5.37-log' socket: '/tmp/mysql-5.5.37.sock' port: 0 Source distribution
141124 22:32:43 [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)
141124 22:32:43 [Warning] Retry in 60 secs. Message reprinted in 600 secs
141124 22:42:43 [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)
141124 22:42:43 [Warning] Retry in 60 secs. Message reprinted in 600 secs
141124 22:52:43 [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)
141124 22:52:43 [Warning] Retry in 60 secs. Message reprinted in 600 secs
141124 23:02:43 [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)
141124 23:02:43 [Warning] Retry in 60 secs. Message reprinted in 600 secs
141124 23:12:43 [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)
141124 23:12:43 [Warning] Retry in 60 secs. Message reprinted in 600 secs
141124 23:22:43 [Warning] Disk i141125 00:05:31 mysqld_safe A mysqld process already exists
141125 0:05:32 [Note] /usr/local/mysql-5.5.37/bin/mysqld: Normal shutdown

141125 0:05:32 [Note] Event Scheduler: Purging the queue. 0 events
141125 0:05:34 [Warning] /usr/local/mysql-5.5.37/bin/mysqld: Forcing close of thread 198822 user: 'root'

141125 0:05:34 [Warning] /usr/local/mysql-5.5.37/bin/mysqld: Forcing close of thread 198783 user: 'root'

141125 0:05:34 [Warning] /usr/local/mysql-5.5.37/bin/mysqld: Forcing close of thread 198780 user: 'txhd_bbs'

141125 0:05:34 [Warning] /usr/local/mysql-5.5.37/bin/mysqld: Forcing close of thread 198777 user: 'wx_we7_84215'

141125 00:07:00 mysqld_safe Starting mysqld daemon with databases from /home/usrdata/mysql-5.5.37
141125 0:07:01 [Note] Plugin 'InnoDB' is disabled.
16:07: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 = 134092 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-5.5.37/bin/mysqld(my_print_stacktrace+0x2e)[0x77376e]
/usr/local/mysql-5.5.37/bin/mysqld(handle_fatal_signal+0x41a)[0x65d77a]
/lib/libpthread.so.0(+0xeff0)[0x7f9c78badff0]
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.
141125 00:07:01 mysqld_safe mysqld from pid file /home/usrdata/mysql-5.5.37/mysql.pid ended
141125 00:11:42 mysqld_safe Starting mysqld daemon with databases from /home/usrdata/mysql-5.5.37
141125 0:11:42 [Note] Plugin 'InnoDB' is disabled.
16:11:42 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 = 134092 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-5.5.37/bin/mysqld(my_print_stacktrace+0x2e)[0x77376e]
/usr/local/mysql-5.5.37/bin/mysqld(handle_fatal_signal+0x41a)[0x65d77a]
/lib/libpthread.so.0(+0xeff0)[0x7fa5d0340ff0]
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.
141125 00:11:42 mysqld_safe mysqld from pid file /home/usrdata/mysql-5.5.37/mysql.pid ended
141125 00:12:59 mysqld_safe Starting mysqld daemon with databases from /home/usrdata/mysql-5.5.37
141125 0:12:59 [Note] Plugin 'InnoDB' is disabled.
16:12:59 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, impr141125 00:12:59 mysqld_safe mysqld from pid file /home/usrdata/mysql-5.5.37/mysql.pid ended
141125 00:17:06 mysqld_safe Starting mysqld daemon with databases from /home/usrdata/mysql-5.5.37
141125 0:17:06 [Note] Plugin 'InnoDB' is disabled.
16:17:06 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 = 134092 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-5.5.37/bin/mysqld(my_print_stacktrace+0x2e)[0x77376e]
/usr/local/mysql-5.5.37/bin/mysqld(handle_fatal_signal+0x41a)[0x65d77a]
/lib/libpthread.so.0(+0xeff0)[0x7f1893eb3ff0]
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.
141125 00:17:06 mysqld_safe mysqld from pid file /home/usrdata/mysql-5.5.37/mysql.pid ended
141125 00:17:51 mysqld_safe Starting mysqld daemon with databases from /home/usrdata/mysql-5.5.37
141125 0:17:51 [Note] Plugin 'InnoDB' is disabled.
16:17:51 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 = 134092 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-5.5.37/bin/mysqld(my_print_stacktrace+0x2e)[0x77376e]
/usr/local/mysql-5.5.37/bin/mysqld(handle_fatal_signal+0x41a)[0x65d77a]
/lib/libpthread.so.0(+0xeff0)[0x7fa08c4ecff0]
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.
141125 00:17:51 mysqld_safe mysqld from pid file /home/usrdata/mysql-5.5.37/mysql.pid ended
141125 00:20:49 mysqld_safe Starting mysqld daemon with databases from /home/usrdata/mysql-5.5.37
141125 0:20:49 [Note] Plugin 'InnoDB' is disabled.
16:20:49 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 = 134092 K bytes of memory
Hope that's ok; if not, dec141125 00:20:49 mysqld_safe mysqld from pid file /home/usrdata/mysql-5.5.37/mysql.pid ended
141125 00:21:39 mysqld_safe Starting mysqld daemon with databases from /home/usrdata/mysql-5.5.37
141125 0:21:39 [Note] Plugin 'InnoDB' is disabled.
16:21:39 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 = 134092 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-5.5.37/bin/mysqld(my_print_stacktrace+0x2e)[0x77376e]
/usr/local/mysql-5.5.37/bin/mysqld(handle_fatal_signal+0x41a)[0x65d77a]
/lib/libpthread.so.0(+0xeff0)[0x7f2a52641ff0]
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.
141125 00:21:39 mysqld_safe mysqld from pid file /home/usrdata/mysql-5.5.37/mysql.pid ended
[Error] mysql-5.5.37 start failed.
root@AY140317001652599dc4Z:~#