Hi On F24, I can't start mariadb-server 'systemctl start mariadb Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.' I don't understand what happens Thanks for any idea
/var/log/mariadb.log 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: The InnoDB memory heap is disabled 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Memory barrier is not used 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Compressed tables use zlib 1.2.8 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Using Linux native AIO 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Using SSE crc32 instructions 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Completed initialization of buffer pool 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Highest supported file format is Barracuda. InnoDB: No valid checkpoint found. InnoDB: If you are attempting downgrade from MySQL 5.7.9 or later, InnoDB: please refer to http://dev.mysql.com/doc/refman/5.6/en/upgrading-downgrading.html InnoDB: If this error appears when you are creating an InnoDB database, InnoDB: the problem may be that during an earlier attempt you managed InnoDB: to create the InnoDB data files, but log file creation failed. InnoDB: If that is the case, please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html 2016-07-12 17:44:57 140485538900160 [ERROR] Plugin 'InnoDB' init function returned error. 2016-07-12 17:44:57 140485538900160 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2016-07-12 17:44:57 140485538900160 [Note] Plugin 'FEEDBACK' is disabled. 2016-07-12 17:44:57 140485538900160 [Warning] GSSAPI plugin : default principal 'mariadb/localhost.localdomain@' not found in keytab 2016-07-12 17:44:57 140485538900160 [ERROR] mysqld: Server GSSAPI error (major 851968, minor 2529639093) : gss_acquire_cred failed -Unspecified GSS failure. Minor code may provide more information. Keytab FILE:/etc/krb5.keytab is nonexistent or empty. 2016-07-12 17:44:57 140485538900160 [ERROR] Plugin 'gssapi' init function returned error. 2016-07-12 17:44:57 140485538900160 [ERROR] Unknown/unsupported storage engine: InnoDB 2016-07-12 17:44:57 140485538900160 [ERROR] Aborting
On 12 July 2016 at 18:00, maderios maderios@gmail.com wrote:
Hi On F24, I can't start mariadb-server 'systemctl start mariadb Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.' I don't understand what happens Thanks for any idea
/var/log/mariadb.log 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: The InnoDB memory heap is disabled 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Memory barrier is not used 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Compressed tables use zlib 1.2.8 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Using Linux native AIO 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Using SSE crc32 instructions 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Completed initialization of buffer pool 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Highest supported file format is Barracuda. InnoDB: No valid checkpoint found. InnoDB: If you are attempting downgrade from MySQL 5.7.9 or later, InnoDB: please refer to http://dev.mysql.com/doc/refman/5.6/en/upgrading-downgrading.html InnoDB: If this error appears when you are creating an InnoDB database, InnoDB: the problem may be that during an earlier attempt you managed InnoDB: to create the InnoDB data files, but log file creation failed. InnoDB: If that is the case, please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html 2016-07-12 17:44:57 140485538900160 [ERROR] Plugin 'InnoDB' init function returned error. 2016-07-12 17:44:57 140485538900160 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2016-07-12 17:44:57 140485538900160 [Note] Plugin 'FEEDBACK' is disabled. 2016-07-12 17:44:57 140485538900160 [Warning] GSSAPI plugin : default principal 'mariadb/localhost.localdomain@' not found in keytab 2016-07-12 17:44:57 140485538900160 [ERROR] mysqld: Server GSSAPI error (major 851968, minor 2529639093) : gss_acquire_cred failed -Unspecified GSS failure. Minor code may provide more information. Keytab FILE:/etc/krb5.keytab is nonexistent or empty. 2016-07-12 17:44:57 140485538900160 [ERROR] Plugin 'gssapi' init function returned error. 2016-07-12 17:44:57 140485538900160 [ERROR] Unknown/unsupported storage engine: InnoDB 2016-07-12 17:44:57 140485538900160 [ERROR] Aborting -- Maderios --
I had a similar and strange issue a few hours ago; I did the following and I was able to start the service sudo setenforce 0 sudo systemctl start mariadb sudo setenforce 1 sudo systemctl restart mariadb
On 07/12/2016 06:05 PM, Earl A Ramirez wrote:
I had a similar and strange issue a few hours ago; I did the following and I was able to start the service sudo setenforce 0 sudo systemctl start mariadb sudo setenforce 1 sudo systemctl restart mariadb
It doesn't work for me. I don't think it's a selinux problem.
On 07/12/2016 06:00 PM, maderios wrote:
Hi On F24, I can't start mariadb-server 'systemctl start mariadb Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.'
Hi I discovered that, strangely, dnf doesn't delete mysql installation in /var/lib/mysql when I uninstall old Mysql. Mariadb tried to use /var/lib/mysql/*, that's why it did not work After removing this directory, I can start mariadb. Greetings
On 07/14/2016 10:20 AM, maderios wrote:
On 07/12/2016 06:00 PM, maderios wrote:
Hi On F24, I can't start mariadb-server 'systemctl start mariadb Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.'
Hi I discovered that, strangely, dnf doesn't delete mysql installation in /var/lib/mysql when I uninstall old Mysql. Mariadb tried to use /var/lib/mysql/*, that's why it did not work After removing this directory, I can start mariadb.
Most uninstalls don't delete _data_ files created by the application-- just in case the uninstall was an "oops!" and you still want the data. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - If you put the federal government in charge of the Sahara Desert, - - in five years there'd be a shortage of sand. - - -- Milton Friedman - ----------------------------------------------------------------------
On 07/14/2016 11:42 AM, Rick Stevens wrote:
On 07/14/2016 10:20 AM, maderios wrote:
On 07/12/2016 06:00 PM, maderios wrote:
Hi On F24, I can't start mariadb-server 'systemctl start mariadb Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.'
Hi I discovered that, strangely, dnf doesn't delete mysql installation in /var/lib/mysql when I uninstall old Mysql. Mariadb tried to use /var/lib/mysql/*, that's why it did not work After removing this directory, I can start mariadb.
Most uninstalls don't delete _data_ files created by the application-- just in case the uninstall was an "oops!" and you still want the data.
It is strange that 2 different db management SW, are coded to use same data dir. Should not each db management package make use of a data dir that bears it's installation name, such as /var/lib/mariadb.d for mariadb ? This would have spared the OP the unpleasant experience.
On 07/14/2016 10:51 AM, jd1008 wrote:
On 07/14/2016 11:42 AM, Rick Stevens wrote:
On 07/14/2016 10:20 AM, maderios wrote:
On 07/12/2016 06:00 PM, maderios wrote:
Hi On F24, I can't start mariadb-server 'systemctl start mariadb Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.'
Hi I discovered that, strangely, dnf doesn't delete mysql installation in /var/lib/mysql when I uninstall old Mysql. Mariadb tried to use /var/lib/mysql/*, that's why it did not work After removing this directory, I can start mariadb.
Most uninstalls don't delete _data_ files created by the application-- just in case the uninstall was an "oops!" and you still want the data.
It is strange that 2 different db management SW, are coded to use same data dir. Should not each db management package make use of a data dir that bears it's installation name, such as /var/lib/mariadb.d for mariadb ? This would have spared the OP the unpleasant experience.
As I understand it, MariaDB is supposed to be the replacement for MySQL as far as Fedora is concerned. I can see two possibilities: a) there's a permission issue in that /var/lib/mysql is owned by the old mysql user and mariadb uses a different user; or b) the MySQL databases aren't compatible with the MariaDB version installed. Without the logs, it's pretty hard to tell. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - Millihelen (n): The amount of beauty required to launch one ship. - ----------------------------------------------------------------------
On 07/14/2016 08:13 PM, Rick Stevens wrote:
As I understand it, MariaDB is supposed to be the replacement for MySQL as far as Fedora is concerned. I can see two possibilities: a) there's a permission issue in that /var/lib/mysql is owned by the old mysql user and mariadb uses a different user; or b) the MySQL databases aren't compatible with the MariaDB version installed. Without the logs, it's pretty hard to tell.
*OLD* /var/log/mariadb.log
2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: The InnoDB memory heap is disabled 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Memory barrier is not used 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Compressed tables use zlib 1.2.8 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Using Linux native AIO 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Using SSE crc32 instructions 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Completed initialization of buffer pool 2016-07-12 17:44:57 140485538900160 [Note] InnoDB: Highest supported file format is Barracuda. InnoDB: No valid checkpoint found. InnoDB: If you are attempting downgrade from MySQL 5.7.9 or later, InnoDB: please refer to http://dev.mysql.com/doc/refman/5.6/en/upgrading-downgrading.html InnoDB: If this error appears when you are creating an InnoDB database, InnoDB: the problem may be that during an earlier attempt you managed InnoDB: to create the InnoDB data files, but log file creation failed. InnoDB: If that is the case, please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html 2016-07-12 17:44:57 140485538900160 [ERROR] Plugin 'InnoDB' init function returned error. 2016-07-12 17:44:57 140485538900160 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2016-07-12 17:44:57 140485538900160 [Note] Plugin 'FEEDBACK' is disabled. 2016-07-12 17:44:57 140485538900160 [Warning] GSSAPI plugin : default principal 'mariadb/localhost.localdomain@' not found in keytab 2016-07-12 17:44:57 140485538900160 [ERROR] mysqld: Server GSSAPI error (major 851968, minor 2529639093) : gss_acquire_cred failed -Unspecified GSS failure. Minor code may provide more information. Keytab FILE:/etc/krb5.keytab is nonexistent or empty. 2016-07-12 17:44:57 140485538900160 [ERROR] Plugin 'gssapi' init function returned error. 2016-07-12 17:44:57 140485538900160 [ERROR] Unknown/unsupported storage engine: InnoDB 2016-07-12 17:44:57 140485538900160 [ERROR] Aborting
On 07/14/2016 12:13 PM, Rick Stevens wrote:
On 07/14/2016 10:51 AM, jd1008 wrote:
On 07/14/2016 11:42 AM, Rick Stevens wrote:
On 07/14/2016 10:20 AM, maderios wrote:
On 07/12/2016 06:00 PM, maderios wrote:
Hi On F24, I can't start mariadb-server 'systemctl start mariadb Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.'
Hi I discovered that, strangely, dnf doesn't delete mysql installation in /var/lib/mysql when I uninstall old Mysql. Mariadb tried to use /var/lib/mysql/*, that's why it did not work After removing this directory, I can start mariadb.
Most uninstalls don't delete _data_ files created by the application-- just in case the uninstall was an "oops!" and you still want the data.
It is strange that 2 different db management SW, are coded to use same data dir. Should not each db management package make use of a data dir that bears it's installation name, such as /var/lib/mariadb.d for mariadb ? This would have spared the OP the unpleasant experience.
As I understand it, MariaDB is supposed to be the replacement for MySQL as far as Fedora is concerned. I can see two possibilities: a) there's a permission issue in that /var/lib/mysql is owned by the old mysql user and mariadb uses a different user; or b) the MySQL databases aren't compatible with the MariaDB version installed. Without the logs, it's pretty hard to tell.
But the installation process should create a unique user also, specific to the name of the db package. Keeping things separate is, as I see it, the way to go to prevent clashing pathnames.
On 07/14/2016 11:22 AM, jd1008 wrote:
But the installation process should create a unique user also, specific to the name of the db package. Keeping things separate is, as I see it, the way to go to prevent clashing pathnames.
mariadb at this point is supposed to be pretty much a drop-in replacement for mysql. By keeping the same username and directories, it makes it much easier for users to continue using existing documentation. I don't know if mariadb is supposed to be able to use existing mysql databases, but I would expect so.
-
Earl Ramirez -
JD -
maderios -
Rick Stevens -
Samuel Sieb