ROBERTOSANTANA
asked on
MySQL Service takes a very long time to start up
Hello,
THIS IS VERY URGENT, THANKS IN ADVANCE.
I've exactly the same error that's described in this link:
http://bugs.mysql.com/bug.php?id=28805
I can't find a solution, in my case MySql server takes around 25 minutes to start,
Any help will be appreciated.
Best Regards
THIS IS VERY URGENT, THANKS IN ADVANCE.
I've exactly the same error that's described in this link:
http://bugs.mysql.com/bug.php?id=28805
I can't find a solution, in my case MySql server takes around 25 minutes to start,
Any help will be appreciated.
Best Regards
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
My MySql Server version is MySQL 5.1.32-community so this is not the 4x version bug.
I've tried to stop the service and start MySQL with mysqld command and the server starts inmmediately so, where's the problem?
The registered command in MySQL Windows Service is: "D:\MySQL Server 5.1\bin\mysqld" --defaults-file="D:\MySQL Server 5.1\my.ini" MySQL51
There's any problem within the command?
If I start MySQL manually with mysqld command the server is reading my.ini file?
Thanks
I've tried to stop the service and start MySQL with mysqld command and the server starts inmmediately so, where's the problem?
The registered command in MySQL Windows Service is: "D:\MySQL Server 5.1\bin\mysqld" --defaults-file="D:\MySQL Server 5.1\my.ini" MySQL51
There's any problem within the command?
If I start MySQL manually with mysqld command the server is reading my.ini file?
Thanks
ASKER
When I start with mysqld command I receive a warning:
D:\MySQL Server 5.1\bin>mysqld
100109 9:25:33 [Warning] Changed limits: max_open_files: 2048 max_connections:
800 table_cache: 619
Thanks
D:\MySQL Server 5.1\bin>mysqld
100109 9:25:33 [Warning] Changed limits: max_open_files: 2048 max_connections:
800 table_cache: 619
Thanks
ASKER
I've found the solution, I changed the account that starts the service to the Administrator and now starts inmediately. demanzter thanks for the clue.
ASKER
The proposed solution was a clue to the definitive solution. Thanks.
It seems that this is a bug in mqsql 4x.