The OpenNET Project / Index page

[ новости /+++ | форум | теги | ]

форумы  помощь  поиск  регистрация  майллист  вход/выход  слежка  RSS
"перезапуски mysqld: По щучьему веленью, по своему хотению"
Вариант для распечатки  
Пред. тема | След. тема 
Форумы OpenNET: Виртуальная конференция (Public)
Изначальное сообщение [Проследить за развитием треда]

"перезапуски mysqld: По щучьему веленью, по своему хотению"  
Сообщение от Arifolth email(ok) on 17-Сен-07, 13:44 
Приветствую всех
проблема такая - mysqld крутящийся на линуховой машине периодически нерегулярно перезапускается.
сам по себе. перед этим наблюдается жуткая тормозня - иногда машинка свопится. но не всегда - иногда просто тормозит. проц не загружен. гиг рама. пол гига своп. собран из сырцов, 5.0.27
что с ним можно сделать? мистика какая-то...
в логах только
...
070917 8:25:37 [ERROR] /usr/local/libexec/mysqld: Sort aborted
Number of processes running now: 0
070917 09:26:06 mysqld restarted
070917 9:26:09 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070917 9:26:11 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 26 243881726.
InnoDB: Doing recovery: scanned up to log sequence number 26 243881726
InnoDB: Last MySQL binlog file position 0 3566027, file name ./mysql-bin.000062
070917 9:26:11 InnoDB: Started; log sequence number 26 243881726
070917 9:26:11 [Note] Recovering after a crash using mysql-bin
070917 9:26:11 [Note] Starting crash recovery...
070917 9:26:11 [Note] Crash recovery finished.
070917 9:26:11 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.0.27-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
070917 9:28:42 [ERROR] /usr/local/libexec/mysqld: Sort aborted
...

my.cnf испоользуется из дистрибутива, huge, слегка правленный

# Example MySQL config file for very large systems.
#
# This is for a large system with memory of 1G-2G where the system runs mainly
# MySQL.
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/var) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

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

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port = 3306
socket = /var/lib/mysql/mysql.sock
skip-locking
key_buffer = 384M
max_allowed_packet = 1M
table_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size = 32M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 45

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking

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

# 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

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin

# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 384M
#bdb_max_lock = 100000

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /var/lib/mysql/
#innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend
#innodb_log_group_home_dir = /var/lib/mysql/
#innodb_log_arch_dir = /var/lib/mysql/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 364M
innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 175M
innodb_table_locks = 0
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 0
innodb_lock_wait_timeout = 50
innodb_locks_unsafe_for_binlog = 1

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash

[isamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

заранее благодарен за ответы
_________________
WBR, Arifolth

Высказать мнение | Ответить | Правка | Наверх | Cообщить модератору

 Оглавление

Сообщения по теме [Сортировка по времени, UBB]


1. "перезапуски mysqld: По щучьему веленью, по своему хотению"  
Сообщение от Koba LTD on 17-Сен-07, 16:27 
>[оверквотинг удален]
>sort_buffer_size = 256M
>read_buffer = 2M
>write_buffer = 2M
>
>[mysqlhotcopy]
>interactive-timeout
>
>заранее благодарен за ответы
>_________________
>WBR, Arifolth

что крутиться мускуле какая средня загрузка, объем баз, среднее кол-во записей - и другое по возможности в студию

Высказать мнение | Ответить | Правка | Наверх | Cообщить модератору

2. "перезапуски mysqld: По щучьему веленью, по своему хотению"  
Сообщение от Arifolth email(ok) on 21-Сен-07, 17:32 
>[оверквотинг удален]
>>
>>[mysqlhotcopy]
>>interactive-timeout
>>
>>заранее благодарен за ответы
>>_________________
>>WBR, Arifolth
>
>что крутиться мускуле какая средня загрузка, объем баз, среднее кол-во записей -
>и другое по возможности в студию

вообщем тёмные силы электричества - проапгрейдися на 5.0.45 и всё описанные проблемы исчезли... и никакого шаманства!

Высказать мнение | Ответить | Правка | Наверх | Cообщить модератору

Архив | Удалить

Индекс форумов | Темы | Пред. тема | След. тема
Оцените тред (1=ужас, 5=супер)? [ 1 | 2 | 3 | 4 | 5 ] [Рекомендовать для помещения в FAQ]




Партнёры:
PostgresPro
Inferno Solutions
Hosting by Hoster.ru
Хостинг:

Закладки на сайте
Проследить за страницей
Created 1996-2024 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру