Друзья, помогите разобраться в чем дело: Имеем: сервер CentOS (release 5.9 (Final)) на нем крутятся openvz контейнеры. В одном из них при старте не запускается мускуль. В контенере работает убунта:
root@zabbix:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.1 LTS
Release: 12.04
Codename: precise
Мускуль вылетает со следующей ошибкой:
Jan 31 20:47:32 zabbix mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Jan 31 20:47:32 zabbix mysqld: 130131 20:47:32 [Note] Plugin 'FEDERATED' is disabled.
Jan 31 20:47:32 zabbix mysqld: 130131 20:47:32 InnoDB: The InnoDB memory heap is disabled
Jan 31 20:47:32 zabbix mysqld: 130131 20:47:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jan 31 20:47:32 zabbix mysqld: 130131 20:47:32 InnoDB: Compressed tables use zlib 1.2.3.4
Jan 31 20:47:32 zabbix mysqld: 16:47:32 UTC - mysqld got signal 11 ;
Jan 31 20:47:32 zabbix mysqld: This could be because you hit a bug. It is also possible that this binary
Jan 31 20:47:32 zabbix mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Jan 31 20:47:32 zabbix mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Jan 31 20:47:32 zabbix mysqld: We will try our best to scrape up some info that will hopefully help
Jan 31 20:47:32 zabbix mysqld: diagnose the problem, but since we have already crashed,
Jan 31 20:47:32 zabbix mysqld: something is definitely wrong and this may fail.
Jan 31 20:47:32 zabbix mysqld:
Jan 31 20:47:32 zabbix mysqld: key_buffer_size=16777216
Jan 31 20:47:32 zabbix mysqld: read_buffer_size=131072
Jan 31 20:47:32 zabbix mysqld: max_used_connections=0
Jan 31 20:47:32 zabbix mysqld: max_threads=151
Jan 31 20:47:32 zabbix mysqld: thread_count=0
Jan 31 20:47:32 zabbix mysqld: connection_count=0
Jan 31 20:47:32 zabbix mysqld: It is possible that mysqld could use up to
Jan 31 20:47:32 zabbix mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346681 K bytes of memory
Jan 31 20:47:32 zabbix mysqld: Hope that's ok; if not, decrease some variables in the equation.
Jan 31 20:47:32 zabbix mysqld:
Jan 31 20:47:32 zabbix mysqld: Thread pointer: 0x0
Jan 31 20:47:32 zabbix mysqld: Attempting backtrace. You can use the following information to find out
Jan 31 20:47:32 zabbix mysqld: where mysqld died. If you see no messages after this, something went
Jan 31 20:47:32 zabbix mysqld: terribly wrong...
Jan 31 20:47:32 zabbix mysqld: stack_bottom = 0 thread_stack 0x30000
Jan 31 20:47:32 zabbix mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7f22d6cca039]
Jan 31 20:47:32 zabbix mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x483)[0x7f22d6b909c3]
Jan 31 20:47:32 zabbix mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f22d58e1cb0]
Jan 31 20:47:32 zabbix mysqld: /usr/sbin/mysqld(+0x687e58)[0x7f22d6e00e58]
Jan 31 20:47:32 zabbix mysqld: /usr/sbin/mysqld(+0x5da8e6)[0x7f22d6d538e6]
Jan 31 20:47:32 zabbix mysqld: /usr/sbin/mysqld(+0x5db54c)[0x7f22d6d5454c]
Jan 31 20:47:32 zabbix mysqld: /usr/sbin/mysqld(+0x5df9a5)[0x7f22d6d589a5]
Jan 31 20:47:32 zabbix mysqld: /usr/sbin/mysqld(+0x5aadb9)[0x7f22d6d23db9]
Jan 31 20:47:32 zabbix mysqld: /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7f22d6b93091]
Jan 31 20:47:32 zabbix mysqld: /usr/sbin/mysqld(+0x3081d1)[0x7f22d6a811d1]
Jan 31 20:47:32 zabbix mysqld: /usr/sbin/mysqld(_Z11plugin_initPiPPci+0xa94)[0x7f22d6a847f4]
Jan 31 20:47:32 zabbix mysqld: /usr/sbin/mysqld(+0x281b76)[0x7f22d69fab76]
Jan 31 20:47:32 zabbix mysqld: /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x59b)[0x7f22d69fe26b]
Jan 31 20:47:32 zabbix mysqld: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f22d4f3876d]
Jan 31 20:47:32 zabbix mysqld: /usr/sbin/mysqld(+0x27b9b5)[0x7f22d69f49b5]
Jan 31 20:47:32 zabbix mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Jan 31 20:47:32 zabbix mysqld: information that should help you find out what is causing the crash.
Jan 31 20:47:32 zabbix mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
При том что странно, если на центосе выполнить.
vzctl set 202 --ram 1G --save
То руками мускуль запускается отлично.
Вот конфиг контейнера:
KMEMSIZE="14372700:14790164"
LOCKEDPAGES="2048:2048"
PRIVVMPAGES="65536:69632"
SHMPAGES="21504:21504"
NUMPROC="1000"
PHYSPAGES="0:262144"
VMGUARPAGES="33792:unlimited"
OOMGUARPAGES="26112:unlimited"
NUMTCPSOCK="360:360"
NUMFLOCK="188:206"
NUMPTY="16:16"
NUMSIGINFO="256:256"
TCPSNDBUF="1720320:2703360"
TCPRCVBUF="1720320:2703360"
OTHERSOCKBUF="1126080:2097152"
DGRAMRCVBUF="262144:262144"
NUMOTHERSOCK="360:360"
DCACHESIZE="3409920:3624960"
NUMFILE="9312:9312"
AVNUMPROC="180:180"
NUMIPTENT="128:128"
# Disk quota parameters (in form of softlimit:hardlimit)
DISKSPACE="10485760:10485760"
DISKINODES="200000:220000"
QUOTATIME="0"
# CPU fair scheduler parameter
CPUUNITS="2000"
VE_ROOT="/vz/root/$VEID"
VE_PRIVATE="/vz/private/$VEID"
OSTEMPLATE="ubuntu-12.04-x86_64"
ORIGIN_SAMPLE="basic"
IP_ADDRESS="13x.11x.20x.202/26 10.0.0.202/26"
NAMESERVER="8.8.8.8"
HOSTNAME="zabbix"
ONBOOT="yes"
SWAPPAGES="1000"
CPUS="4"
NETIF=""
Вариант для распечатки
