Vesta Control Panel - Forum

Posted: **Fri Jul 12, 2013 12:22 pm**

Hello!

I am unable to install Vesta on Centos6-64bit (the O/S is not mentioned in the installation instructions, so I guessed it after errors on Ubuntu).

The installation always fails on starting mysqld with this:

Code: Select all

...
...
You can test the MySQL daemon with mysql-test-run.pl
cd /usr/mysql-test ; perl mysql-test-run.pl

Please report any problems with the /usr/bin/mysqlbug script!

                                                           [  OK  ]
MySQL Daemon failed to start.
Starting mysqld:                                           [FAILED]
Error: mysqld start failed

mysqld log shows the following clues:

Code: Select all

[root@test ~]# cat /var/log/mysqld.log 
130712 07:51:32 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130712  7:51:32 [Note] Plugin 'FEDERATED' is disabled.
130712  7:51:32 InnoDB: The InnoDB memory heap is disabled
130712  7:51:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130712  7:51:32 InnoDB: Compressed tables use zlib 1.2.3
130712  7:51:32 InnoDB: Using Linux native AIO
130712  7:51:32  InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
InnoDB: Warning: io_setup() attempt 1 failed.
InnoDB: Warning: io_setup() attempt 2 failed.
InnoDB: Warning: io_setup() attempt 3 failed.
InnoDB: Warning: io_setup() attempt 4 failed.
InnoDB: Warning: io_setup() attempt 5 failed.
130712  7:51:34  InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
130712  7:51:34 InnoDB: Fatal error: cannot initialize AIO sub-system
130712  7:51:34 [ERROR] Plugin 'InnoDB' init function returned error.
130712  7:51:34 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130712  7:51:34 [ERROR] Unknown/unsupported storage engine: InnoDB
130712  7:51:34 [ERROR] Aborting

130712  7:51:34 [Note] /usr/libexec/mysqld: Shutdown complete

130712 07:51:34 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
130712 08:15:37 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130712  8:15:37 [Note] Plugin 'FEDERATED' is disabled.
130712  8:15:37 InnoDB: The InnoDB memory heap is disabled
130712  8:15:37 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130712  8:15:37 InnoDB: Compressed tables use zlib 1.2.3
130712  8:15:37 InnoDB: Using Linux native AIO
130712  8:15:37  InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
InnoDB: Warning: io_setup() attempt 1 failed.
InnoDB: Warning: io_setup() attempt 2 failed.
InnoDB: Warning: io_setup() attempt 3 failed.
InnoDB: Warning: io_setup() attempt 4 failed.
InnoDB: Warning: io_setup() attempt 5 failed.
130712  8:15:39  InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
130712  8:15:39 InnoDB: Fatal error: cannot initialize AIO sub-system
130712  8:15:39 [ERROR] Plugin 'InnoDB' init function returned error.
130712  8:15:39 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130712  8:15:39 [ERROR] Unknown/unsupported storage engine: InnoDB
130712  8:15:39 [ERROR] Aborting

130712  8:15:39 [Note] /usr/libexec/mysqld: Shutdown complete

Posted: **Sat Jul 13, 2013 8:10 am**

It seems that vps does not have sufficient resources to launch mysql server. I have seen similar behaviour on instances running by openvz/virtuozzo. If it is your case too, check the /proc/user_beancounters for failcnt values. It can give you a hint.

Posted: **Sun May 11, 2014 3:57 pm**

I ran into the same problem on a debian wheezy:

Output from: /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
3918: kmemsize 59966994 62406656 3221225472 3221225472 0
lockedpages 0 8 786432 786432 0
privvmpages 63515 99642 9223372036854775807 9223372036854775807 0
shmpages 7135 7135 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numproc 47 90 9223372036854775807 9223372036854775807 0
physpages 361957 370944 0 1572864 0
vmguarpages 0 0 9223372036854775807 9223372036854775807 0
oomguarpages 6577 6597 9223372036854775807 9223372036854775807 0
numtcpsock 13 31 9223372036854775807 9223372036854775807 0
numflock 19 25 9223372036854775807 9223372036854775807 0
numpty 2 8 9223372036854775807 9223372036854775807 0
numsiginfo 0 36 9223372036854775807 9223372036854775807 0
tcpsndbuf 440624 754544 9223372036854775807 9223372036854775807 0
tcprcvbuf 212992 13925392 9223372036854775807 9223372036854775807 0
othersockbuf 60112 180304 9223372036854775807 9223372036854775807 0
dgramrcvbuf 0 25760 9223372036854775807 9223372036854775807 0
numothersock 76 82 9223372036854775807 9223372036854775807 0
dcachesize 47839109 48296107 1610612736 1610612736 0
numfile 695 945 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numiptent 24 24 9223372036854775807 9223372036854775807 0

Any suggestion?

Posted: **Sun May 11, 2014 4:04 pm**

Adding:
innodb_use_native_aio=0 to my.cnf fixes the problem.

Posted: **Sat May 17, 2014 7:42 pm**

Another fix which worked for me in the past is to use MariaDB. It has an awesome storage engine and always works (even on very low end VPS systems).

Give it a go. It just works (did for me anyway): http://mariadb.org. They even have a repository tool available to get the necessary repository keys and mirrors: https://downloads.mariadb.org/mariadb/repositories. It is also easy to switch from MySQL to MariaDB as they use the same code base and share the same functionalities (MariaDB does have a few more features, but is always backwards compatible with MySQL). Migrating to MariaDB is also very easy (I personally only have experience on Debian systems), you don't need to import all databases again. It's more or less like flipping a switch and it's done :)

c0urier wrote:Adding:
innodb_use_native_aio=0 to my.cnf fixes the problem.

More information about this command is here: http://dev.mysql.com/doc/refman/5.6/en/ ... native_aio

Vesta Control Panel - Forum

Unable to install - always fails at mysqld

Unable to install - always fails at mysqld

Re: Unable to install - always fails at mysqld

Re: Unable to install - always fails at mysqld

Re: Unable to install - always fails at mysqld

Re: Unable to install - always fails at mysqld