Failed to initialize plugins while starting mysqld

Hi, Michael!

On Sep 03, Michael Rack wrote:
>
> New question #123919 on Maria:
> https://answers.launchpad.net/maria/+question/123919
>
> Dear List,
>
> i've upgraded from MariaDB 5.1.47 to MariaDB 5.1.49. I compile from source and used the same configure-line as before:
>
> ./configure --prefix=/opt/maria-db-5.1.49 --sysconfdir=/etc/mysql --mandir=/usr/share/man --enable-shared --enable-static --with-charset=latin1 --with-extra-charsets=all --with-pthread --with-unix-socket-path=/tmp/mysql.sock --with-tcp-port=3306 --with-mysqld-user=mysql --with-zlib-dir=/usr --with-ssl=/usr --with-libevent=/usr --with-plugins=all --with-maria-tmp-tables
>
> After starting mysqld, i have the following error:
>
> > 100815 20:27:14 [ERROR] Failed to initialize plugins.
> > 100815 20:27:14 [ERROR] Aborting
> >
> > 100815 20:27:14 [Note] /opt/maria-db-5.1.49/libexec/mysqld: Shutdown complete
>
> The most important change since 5.1.47 was the move from InnoDB to XtraDB, as i know. I don't use InnoDB or XtraDB, but i like to have the ability to use it, if i need it.
>
> What is the Problem behind "Failed to initialize pluglins" ?

The problem is not "behind" - it's "above".
Seriously, I mean that the error log above the line "Failed to
initialize pluglins" should contain the reason of the failure.

I don't mean the line directly previous to "Failed to initialize
pluglins", but some line above typically will have the reason.

Regards,
Sergei

Hi Sergei,

the log-file-entrys i've posted is not cutted. There only these few lines. I don't know how to increase the verbosity to see what is really happend.

Hm.

MySQL can fail like that if it won't be able to allocate memory for
plugin data structures - but that's just few hundreds bytes, I don't
understand how it can fail.

Try to start mysqld with --skip-grant-tables or with --help --verbose
and see if either of that say "Failed to initialize plugins".

Regards,
Sergei

Same story with me (--with-plugins=all), but when I compiled with --with-plugins=max-no-ndb everything was back to normal.

I can confirm the observation of Nikolay: I just compiled with --with-plugins=max-no-ndb and it worked.

Possibly one is already aware of the problem:

http://kb.askmonty.org/v/ndb-disabled-in-mariadb

Ok, I've looked into it. It has nothing to do with NDB. The problem is the Federated engine plugin.

MariaDB comes with two pluguns - Federated and FederatedX - that both call themselves "federated" (from the server point of view). Which is fine, as long as you don't try to load them both at the same time.

FederatedX is compiled into the server in the "max" or "max-no-ndb" configurations. Federated is not compiled into the server in any named configurations. But "all" configuration tries to compiles literally *all* plugins into the server. Which fails on startup when the server tries to activate the second "federated" plugin.

Workaround: don't use "all", use "max".