Bug 141434
Summary: | cannot start mysqld | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Florin Andrei <florin> |
Component: | selinux-policy-targeted | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | jpenix |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:07:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Florin Andrei
2004-12-01 02:23:32 UTC
First off /var/log/mysqld.log is labeled incorrectly. It should be mysqld_log_t. You can execute restorecon /var/log/mysqld.log to fix this. I don't know how it got mislabeled. The initialization of the mysql database has been reported and is being worked on. Hopefully a new version of mysqld will be available shortly. For the time being you can execute setenforce 0 mysql_install_db setenforce 1 and everything should work. Thanks Daniel, your suggestions worked. Just running restorecon /var/log/mysqld.log was not enough, i had to also go through the initialization procedure you described (setenforce...). Now mysql seems to be working fine. *** This bug has been marked as a duplicate of 141062 *** I am running mysql-server-4.1.7-0FC3 rpms from mysql.com, along with mysql-shared-compat-3.23.58-1 rpm created against instructions that can be found at fedoranews.org. I encountered this problem when after yum upgrading various rpms, I do not know when it broke or how. Doing the initialisation procedurs described in comment #1 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=141434#c1 fixed this problem. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |