Bug 113884 - Timeout error occurred trying to start MySQL Daemon.
Summary: Timeout error occurred trying to start MySQL Daemon.
Status: CLOSED DUPLICATE of bug 108779
Alias: None
Product: Fedora
Classification: Fedora
Component: mysql (Show other bugs)
(Show other bugs)
Version: 1
Hardware: athlon Linux
Target Milestone: ---
Assignee: Kim Ho
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2004-01-19 21:44 UTC by Jonathan Eskritt
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 19:00:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jonathan Eskritt 2004-01-19 21:44:23 UTC
Description of problem:
Mysql used to work for me through all redhat linux versions. When I
upgraded to fedora core it would no longer start up. I have tried
doing a fresh reinstall, but It still doesn't start.

When the init script is run (service msqld start) I get the error:

Timeout error occurred trying to start MySQL Daemon.
Starting MySQL:                                            [FAILED]

If I delete the /var/lib/mysql/mysql and /var/lib/mysql/test databases
(there is no socket), the startup script works until I set the root
user's password. After the  password is set, when I shut the database
down and start it up again I get the same error.

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

How reproducible:

Comment 1 Miloslav Trmac 2004-01-20 09:34:17 UTC
Duplicate of bug 108779.
Triage->Duplicate 108779.

Comment 2 Kim Ho 2004-01-20 13:47:50 UTC
Please perform an up2date.

The updated script uses anonymous users. If you want to remove
anonymous users or use your own setup for pinging the server, you'll
have to make changes to the script.

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

Comment 3 Red Hat Bugzilla 2006-02-21 19:00:50 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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