Bug 753851

Summary:	mysql-server will not start
Product:	[Fedora] Fedora	Reporter:	Donald Edward Winslow <dew>
Component:	mysql	Assignee:	Tom Lane <tgl>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	16	CC:	hhorak, tgl
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-17 15:39:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Donald Edward Winslow 2011-11-14 17:07:40 UTC

Description of problem:

I had mysql-server (mysqld) working in Fedora 16, but I installed some updates this morning and now it won't start (with the service or systemctl commands). None of the updates were mysql packages, but I don't know where to file this bug report--I don't understand what's wrong.

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

mysql-server-5.5.16-3.fc16.x86_64

How reproducible:

every time

Steps to Reproduce:
1. Run "service mysqld start" or "systemctl start mysqld.service".
2.
3.
  
Actual results:

Error message: "Job failed. See system logs and 'systemctl status' for details."
Systemctl status indicates that it did indeed fail. Logs show nothing informative to me. Navigating to a locally served php page with a web-browser yields a database connection error.

Expected results:

mysqld should start, with a happy green <OK>. Systemctl status should show that it's active. Locally served php scripts should present the text and images stored in the database.

Additional info:

Comment 1 Tom Lane 2011-11-15 13:51:26 UTC

There is not enough information in this bug report to say anything useful ... but do your symptoms match bug #754072 ?

Comment 2 Tom Lane 2011-11-17 15:39:25 UTC

For lack of information, I'm assuming that this is indeed the same as bug #754072.

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

Comment 3 Donald Edward Winslow 2011-11-17 22:04:11 UTC

Yes, it is a duplicate of 754072, and it's fixed for me by selinux-policy-3.10.0-56.fc16.

Donald