Vicibox 6 MariaDB Crash

[hzavala]

My Maria db is crashing and we couldn't find any reason, we change memory size limit and other options but the error is ocurring. We are thinking to change to mariadb 5.5.45 from MariaDB website.

Any clue will be apprecieted.

Thanks.

- ViciBox Redux v.6.0.3-141118
mariadb-client-5.5.44-7.2.x86_64
mariadb-errormessages-5.5.44-7.2.x86_64
mariadb-5.5.44-7.2.x86_64

Dedicated Server is a HP 2 x E5-2650 v3 with 96 GB Ram 4 Disk 15 krpm 1+0

Code: Select all

[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,
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.44-MariaDB-log
key_buffer_size=1047527424
read_buffer_size=4194304
max_used_connections=825
max_threads=1202
thread_count=165
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 10891199 K  bytes
 of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x7fb3b657e460
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 = 0x7fb29f64ced8 thread_stack 0x48000

This is my.cnf config

Code: Select all

# Basic ViciBox my.cnf for a quad-core 8-GB RAM or so
# Use the dedicate my-big.cnf for 16+GB RAM and 8+ Cores
#

# The following options will be passed to all MySQL clients
[client]
#password       = your_password
port            = 3306
socket          = /var/run/mysql/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port            = 3306
socket          = /var/run/mysql/mysql.sock
datadir = /var/lib/mysql
skip-external-locking
#key_buffer_size = 2048M
key_buffer_size = 999M
max_allowed_packet = 2M
table_open_cache = 8192
sort_buffer_size = 4M
net_buffer_length = 8K
read_buffer_size = 4M
read_rnd_buffer_size = 16M
myisam_sort_buffer_size = 128M
thread_cache_size = 350
#query_cache_size = 96M
#query_cache_size = 48M
query_cache_size = 0
query_cache_type = 0
thread_concurrency=16
skip-name-resolve
connect_timeout=60
long_query_time=3
log_slow_queries
max_connections=1200
open_files_limit=24576
max_heap_table_size=512M
expire_logs_days=3
default-storage-engine=MyISAM
table_definition_cache=8192
table_cache=8192
concurrent_insert=2
myisam_recover
myisam_repair_threads=1
tmpdir          = /tmp/


# This will disable networking
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin

# binary logging format - mixed recommended
binlog_format=mixed

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id       = 1



# The safe_mysqld script
[safe_mysqld]
log-error       = /var/log/mysql/mysqld.log
socket          = /var/run/mysql/mysql.sock

[mysqldump]
socket          = /var/run/mysql/mysql.sock
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[myisamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

[mysqld_multi]
mysqld     = /usr/bin/mysqld_safe
mysqladmin = /usr/bin/mysqladmin
log        = /var/log/mysqld_multi.log
# user       = multi_admin
# password   = secret

# If you want to use mysqld_multi uncomment 1 or more mysqld sections
# below or add your own ones.

# WARNING
# --------
# If you uncomment mysqld1 than make absolutely sure, that database mysql,
# configured above, is not started.  This may result in corrupted data!
# [mysqld1]
# port       = 3306
# datadir    = /var/lib/mysql
# pid-file   = /var/lib/mysql/mysqld.pid
# socket     = /var/lib/mysql/mysql.sock
# user       = mysql

# [mysqld2]
# port       = 3307
# datadir    = /var/lib/mysql-databases/mysqld2
# pid-file   = /var/lib/mysql-databases/mysqld2/mysql.pid
# socket     = /var/lib/mysql-databases/mysqld2/mysql.sock
# user       = mysql

# [mysqld3]
# port       = 3308
# datadir    = /var/lib/mysql-databases/mysqld3
# pid-file   = /var/lib/mysql-databases/mysqld3/mysql.pid
# socket     = /var/lib/mysql-databases/mysqld3/mysql.sock
# user       = mysql

# [mysqld6]
# port       = 3309
# datadir    = /var/lib/mysql-databases/mysqld6
# pid-file   = /var/lib/mysql-databases/mysqld6/mysql.pid
# socket     = /var/lib/mysql-databases/mysqld6/mysql.sock
# user       = mysql


[ccabrera]

I recommend you downgrade to Vicibox 4.0, and then use MariaDB 5.1/5.2. I have a client who ran into exactly the same issues. After downgrading, it worked like a charm.

[omarrodriguezt]

From the vicibox manual

The 'mysql-tuning' command
The 'mysql-tuning' script will look at your currently running MySQL configuration and give you
generalized recommendations on tuning your my.cnf settings as well as show where any potential
problems are. This is especially useful for when things seem to be slowing down but nothings looks
obviously wrong. This is useful for when you hit your MySQL configured max connection limit. It will
also show you if you have ever allocated more memory then you have RAM which means you
swapped out to disk. All very useful things, but it is not 100% accurate in it's recommendations. It is
merely a tool used to guide you in the diagnosis of a problem. It should not be used for fine tuning but
for diagnostic and broad tuning.

[Vince-0]

Check your RAM.
I had Vici ISO 6 MariaDB crashes similar to your error log. I removed a 16GB RAM about a month ago and it hasn't crashed since.

Vin