Bug 137438 - MySQL server timeout error on startup
Summary: MySQL server timeout error on startup
Keywords:
Status: CLOSED DUPLICATE of bug 142328
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: mysql
Version: 3.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tom Lane
QA Contact: David Lawrence
URL:
Whiteboard:
: 137573 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-28 14:43 UTC by none
Modified: 2013-07-03 03:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:06:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description none 2004-10-28 14:43:56 UTC
Description of problem:
I installed the latest 'mysql-server' package, now when I try to start
the database server, I got the following error message:

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

The MySQL server starts up and works fine anyway.

Version-Release number of selected component (if applicable):
mysql-server-3.23.58-2.3

How reproducible:
Always

Steps to Reproduce:
1. up2date mysql-server
2. service mysqld stop
3. service mysqld start

Expected Results:  Since the MySQL server starts up and works fine,
there should be no error message on screen.

Comment 1 Tom Lane 2004-10-28 14:57:39 UTC
Have you perhaps disabled anonymous users in MySQL?  If so, this is
expected behavior --- see the /etc/rc.d/init.d/mysqld script.  You can
tweak the script to use a valid username if you like.  I don't really
know of any better way to make the script test for server ready :-(

Comment 2 Tom Lane 2004-10-29 16:19:42 UTC
*** Bug 137573 has been marked as a duplicate of this bug. ***

Comment 3 Jim Faulkner 2004-11-01 16:25:15 UTC
Modifying the /etc/rc.d/init.d/mysqld does not seem to be an
acceptable solution.  Doing that requires that either
a) I have a user who is allowed access without a password
or
b) I type the clear-text password for the user directly into the rc
script.

I'd prefer to do neither.  The old startup script seemed to work fine...


Comment 4 Tom Lane 2004-11-01 16:52:02 UTC
The best solution I can think of is to create a user who has no
permissions to actually do anything; then whether you give it a
password or not hardly matters ...

It may be that MySQL 4.x has a better way to probe for
is-the-server-up-yet than this, but I don't know of one in 3.x.

Comment 5 Tom Lane 2004-12-09 02:02:29 UTC
I'm planning to adopt the solution shown in bug #142328.

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

Comment 6 Red Hat Bugzilla 2006-02-21 19:06:40 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.