Bug 682583

Summary: Mysql server can't start
Product: [Fedora] Fedora Reporter: megder <megdera>
Component: mysqlAssignee: Tom Lane <tgl>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: 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-03-06 22:24:39 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 megder 2011-03-06 22:05:01 UTC
Description of problem:

After first installation and reboot the Mysql server can't start.

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


How reproducible:


Steps to Reproduce:
1.install mysql-server.x86_64 5.5.9-2.fc15 
2. restart fedora 15
3. service mysqld start
  
Actual results:
Mysql server can't start.

Expected results:
Mysql server running

Additional info:
dump of the file log (/var/log/mysqld.log)
<dump>
110306 23:02:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
110306 23:02:57 [Note] Plugin 'FEDERATED' is disabled.
110306 23:02:57 InnoDB: The InnoDB memory heap is disabled
110306 23:02:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110306 23:02:57 InnoDB: Compressed tables use zlib 1.2.5
110306 23:02:57 InnoDB: Using Linux native AIO
110306 23:02:57 InnoDB: Initializing buffer pool, size = 128.0M
110306 23:02:57 InnoDB: Completed initialization of buffer pool
110306 23:02:57 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
110306 23:02:57  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
110306 23:02:57  InnoDB: Waiting for the background threads to start
110306 23:02:58 InnoDB: 1.1.5 started; log sequence number 1595675
110306 23:02:58 [ERROR] /usr/libexec/mysqld: Can't create/write to file '/var/run/mysqld/mysqld.pid' (Errcode: 2)
110306 23:02:58 [ERROR] Can't start server: can't create PID file: No such file or directory
110306 23:02:58 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
</dump>

Comment 1 megder 2011-03-06 22:24:39 UTC

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