Hi,
I just installed DA on a clean Debian 6 server. Initially things seemed to run well, aside from Exim needing a small tweak to start up.
I then installed Spamassasin using the methods described in the knowledge base. This included installing many cpan plugins. However since then it seems MySQL does not start any more:
Is there any way to debug this? Mind you, this is a clean install with only the roundcube database present.
I just installed DA on a clean Debian 6 server. Initially things seemed to run well, aside from Exim needing a small tweak to start up.
I then installed Spamassasin using the methods described in the knowledge base. This included installing many cpan plugins. However since then it seems MySQL does not start any more:
110613 06:28:17 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
110613 6:28:17 [ERROR] Can't find messagefile '/usr/share/mysql/english/errmsg.sys'
110613 6:28:17 [Note] Plugin 'FEDERATED' is disabled.
110613 6:28:17 InnoDB: The InnoDB memory heap is disabled
110613 6:28:17 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
110613 6:28:17 InnoDB: Compressed tables use zlib 1.2.3
110613 6:28:17 InnoDB: Using Linux native AIO
110613 6:28:17 InnoDB: Initializing buffer pool, size = 128.0M
110613 6:28:17 InnoDB: Completed initialization of buffer pool
110613 6:28:17 InnoDB: highest supported file format is Barracuda.
110613 6:28:17 InnoDB: Waiting for the background threads to start
110613 6:28:18 InnoDB: 1.1.5 started; log sequence number 1676608
110613 6:28:18 [ERROR] Aborting
110613 6:28:18 InnoDB: Starting shutdown...
110613 6:28:18 - 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=131072
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 = 346064 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 = (nil) thread_stack 0x30000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x33)[0x83e39f3]
/usr/local/mysql/bin/mysqld(handle_segfault+0x476)[0x811dca6]
[0xb7885400]
/usr/local/mysql/bin/mysqld[0x83c65a7]
/usr/local/mysql/bin/mysqld[0x83c6f4d]
/lib/i686/cmov/libpthread.so.0(pthread_once+0x90)[0xb786e570]
/usr/local/mysql/bin/mysqld[0x8451030]
/usr/local/mysql/bin/mysqld[0x856322c]
/usr/local/mysql/bin/mysqld[0x856382a]
/usr/local/mysql/bin/mysqld[0x854eca1]
/usr/local/mysql/bin/mysqld[0x84c460b]
/usr/local/mysql/bin/mysqld[0x847359f]
/usr/local/mysql/bin/mysqld[0x856cdbe]
/usr/local/mysql/bin/mysqld[0x856d808]
/usr/local/mysql/bin/mysqld[0x8562837]
/usr/local/mysql/bin/mysqld[0x8496268]
/usr/local/mysql/bin/mysqld[0x848913e]
/lib/i686/cmov/libpthread.so.0(+0x5955)[0xb7868955]
/lib/i686/cmov/libc.so.6(clone+0x5e)[0xb7780e7e]
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.
110613 06:28:18 mysqld_safe mysqld from pid file /usr/local/mysql/data/swt12.pid ended
Is there any way to debug this? Mind you, this is a clean install with only the roundcube database present.
Last edited: