Bug 754672

Summary: mysqld.service does not start
Product: [Fedora] Fedora Reporter: Juan <jfarre>
Component: mysqlAssignee: Tom Lane <tgl>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: 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:34:13 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:
Attachments:
Description Flags
The relevant extract from /var/log/messages none

Description Juan 2011-11-17 09:59:23 UTC 
Created attachment 534169 [details]
The relevant extract from /var/log/messages

Description of problem:
In Fedoraq 15, mysqld used to appear in system-config-services.
Since I installed Fedora 16, it does not appear there.
When I try to start mysql using systemctl, it fails.

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

How reproducible:
Just try to start mysql server with systemctl

Steps to Reproduce:
1. sudo tail -f /var/log/messages
2. sudo systemctl start mysqld.service
  
Actual results:
The service fails to start.
Output of the command is:
Job failed. See system logs and 'systemctl status' for details.

Expected results:
mysql server starts normally

Additional info:

sudo systemctl status mysqld.service
mysqld.service - MySQL database server
	  Loaded: loaded (/lib/systemd/system/mysqld.service; disabled)
	  Active: failed since Thu, 17 Nov 2011 10:52:33 +0100; 1min 22s ago
	 Process: 3520 ExecStart=/usr/bin/mysqld_safe --nowatch --basedir=/usr (code=exited, status=127)
	 Process: 3504 ExecStartPre=/usr/libexec/mysqld-prepare-db-dir (code=exited, status=0/SUCCESS)
	  CGroup: name=systemd:/system/mysqld.service
Comment 1 Tom Lane 2011-11-17 15:34:13 UTC 

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