Details
-
Type:
Bug
-
Status: Closed
-
Resolution: Incomplete
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
root@serv1: wget http://downloads.mariadb.org/f/mariadb-galera-5.5.25/kvm-bintar-hardy-amd64/mariadb-galera-5.5.25-linux-x86_64.tar.gz/from/http:/mirror3.layerjet.com/mariadb
root@serv1: groupadd mysql
root@serv1: useradd -g mysql mysql
root@serv1: cd /usr/local
root@serv1: tar -zxvpf ~/mariadb
root@serv1: ln -s mariadb-galera-5.5.25-linux-x86_64 mysql
root@serv1: cd /etc/mysql
root@serv1: nano my.cnf and comment bind_adress
root@serv1: cd /usr/local/mysql
root@serv1: /usr/local/mysql# ./scripts/mysql_install_db --user=mysql --no-defaults
Installing MariaDB/MySQL system tables in './data' ...
120925 17:57:21 [ERROR] 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.
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
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.
Server version: 5.5.25-MariaDB
key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 335105 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x0
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 = 0x0 thread_stack 0x48000
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Launchpad bug id: 1056282