Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1062054 - /var/log/mariadb/mariadb.log owned by root:root makes mariadb unstartable
Summary: /var/log/mariadb/mariadb.log owned by root:root makes mariadb unstartable
Status: CLOSED DUPLICATE of bug 1061045
Alias: None
Product: Fedora
Classification: Fedora
Component: mariadb
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Honza Horak
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-02-06 05:18 UTC by Steven Dake
Modified: 2016-04-26 23:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-02-06 13:21:05 UTC

Attachments (Terms of Use)

Description Steven Dake 2014-02-06 05:18:44 UTC
Description of problem:
The /var/log/mariadb/mariadb.log file is owned by root:root.  systemd can't start mariadb because it uses the mysql user and is unable to write to the log file.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start the cloud qcow2 image at with OpenStack (via libvirt may also work):
2. yum -y install mariadb mariadb-server httpd wordpress      
3. systemctl start mariadb.service

Actual results:
mariadb fails to start complaining about unable to open /var/log/mariadb/mariadb.log

Expected results:
mariadb starts

Additional info:
chown mysql.mysql /var/log/mariadb/mariadb.log resolves the problem because mysql is able to write to the file (since it is run as the mysql:mysql user).

I am surprised the log file is owned by the package - I would not expect this to be the case.

Comment 1 Honza Horak 2014-02-06 13:21:05 UTC
(In reply to Steven Dake from comment #0)
> I am surprised the log file is owned by the package - I would not expect
> this to be the case.

Owning the log file by a package is actually correct, but the owner really should be mysql:mysql. Anyway, this problem should be fixed by update for bug 1061045.

*** This bug has been marked as a duplicate of bug 1061045 ***

Note You need to log in before you can comment on or make changes to this bug.