Error: mysql config parsing failed

[aleda]

Hello. I rule my config.cnf (MySQL) in order to increase the possible number of entries/substitutions in the second. Bitrix has shown that I have a very low speed recording and replacement, only 35 operations, when reading 7500 times in the same second.

I found the option "innodb_flush_log_at_trx_commit = 1", you want to change to "0" in order to increase the number of operations of the write/replace. It was not in config, but I ordered "innodb_flush_log_at_trx_commit = 0" and actually write operations increased to 2000 - 2800, and replacement of up to 7000 - 8000 operations per second.

I was glad to have saved the configuration and continued to work on the site, closed configuration. However, the following site when it was necessary to create the database I got the error: "Error: mysql config parsing failed"

I'm trying to optimize the server, I have a core 2 x 2.4 GHz, 2Gb RAM, CentOS 6, some of the packages I had to install it manually, because they don't come from Vesta.

- -

Привет. Я правил конфиг my.cnf (MySQL) чтобы увеличить возможное количество записей/замен в секунду. Битрикс показывал что у меня очень низкая скорость записи и замене, всего 35 операций, при чтении 7500 раз за ту же секунду.

Я нашел опцию "innodb_flush_log_at_trx_commit = 1", которую требуется сменить на "0", дабы увеличить количество операций write/replace. Ее не было в конфиге, но я прописал "innodb_flush_log_at_trx_commit = 0" и на самом деле, операции записи выросли до 2000 - 2800, а замены до 7000 - 8000 операций в секунду.

Я обрадовался, сохранил конфигурацию и продолжил работу над сайтом, закрыв настройки. Однако на следующем сайте, когда нужно было создать базу данных я получил ошибку: "Error: mysql config parsing failed"

Я пытаюсь оптимизировать работу сервера, у меня 2 core x 2.4GHz, 2Gb RAM, CentOS 6, часть пакетов пришлось установить вручную, поскольку они не приходят с Vesta.

[skurudo]

You need to understand, what you do, and know about risks. innodb_flush_log_at_trx_commit it's tricky option:
http://dev.mysql.com/doc/refman/5.1/en/ ... trx_commit

You changed something in /usr/local/vesta//conf/mysql.conf ?

PS: Here is russian forum, if you like.

---

Нужно понимать, что вы сейчас делаете и прикинуть риски от этой опции, она слегка небезопасна может быть:
http://ruhighload.com/post/%D0%9A%D0%B0 ... trx_commit

Меняли что-то здесь /usr/local/vesta//conf/mysql.conf ?

PS: Есичо есть русскоязычный форум.

[aleda]

1. You changed something in /usr/local/vesta//conf/mysql.conf ?
2. PS: Here is russian forum, if you like.

1. No
2. Ok, thanks

[skurudo]

Mysql restart normal and not "gone away" or something like this?
What's database name you use: something simple or wirh special entities (_ or space)?

Can you show us mysql error log and /usr/local/vesta/log/* ?
May be there is any clue.

[aleda]

What's database name you use: something simple or wirh special entities (_ or space)?

Can you show us mysql error log and /usr/local/vesta/log/* ?
May be there is any clue.

Restart, or Stop+Start - normal
Any names/passwords for new - error

mysql-error.logShow

150311 23:32:26 [Note] Event Scheduler: Purging the queue. 0 events
150311 23:32:26 InnoDB: Starting shutdown...
150311 23:32:27 InnoDB: Shutdown completed; log sequence number 53981005
150311 23:32:27 [Note] /usr/libexec/mysqld: Shutdown complete

150311 23:32:27 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150311 23:32:27 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150311 23:32:27 [Note] Plugin 'FEDERATED' is disabled.
150311 23:32:27 InnoDB: The InnoDB memory heap is disabled
150311 23:32:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150311 23:32:27 InnoDB: Compressed tables use zlib 1.2.3
150311 23:32:27 InnoDB: Using Linux native AIO
150311 23:32:27 InnoDB: Initializing buffer pool, size = 128.0M
150311 23:32:27 InnoDB: Completed initialization of buffer pool
150311 23:32:27 InnoDB: highest supported file format is Barracuda.
150311 23:32:27 InnoDB: Waiting for the background threads to start
150311 23:32:28 InnoDB: 5.5.42 started; log sequence number 53981005
150311 23:32:28 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
150311 23:32:28 [Note] - '0.0.0.0' resolves to '0.0.0.0';
150311 23:32:28 [Note] Server socket created on IP: '0.0.0.0'.
150311 23:32:28 [Note] Event Scheduler: Loaded 0 events
150311 23:32:28 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.42-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi

Hmmm, this IP '0.0.0.0' - is anormal?