[MDEV-9053] mariadb 10.0.* /etc/init.d/mysql start Failed ? Created: 2015-11-01  Updated: 2015-11-07  Resolved: 2015-11-07

Status: Closed
Project: MariaDB Server
Component/s: Scripts & Clients
Affects Version/s: 10.0.20
Fix Version/s: 10.0.20

Type: Bug Priority: Major
Reporter: sysdljr Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

CentOS 5.6, MariaDB Server 10.0.20


 Description   

when use mysql start scrit , after 15 minutes , show start failed:

# /etc/init.d/mysql start
 
Starting MySQL....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................[FAILED]

But, mysql error log show , mysqld already normal start . 

151101 18:00:40 [Note] /usr/sbin/mysqld: ready for connections.
 
Version: '10.0.20-MariaDB'  socket: '/home/maria20/data/mysql.sock'  port: 3306  MariaDB Server
 
2015-11-01 18:00:40 4e209940 InnoDB: Buffer pool(s) load completed at 151101 18:00:40

mysql client access normal too, if use mysqld_safe --defaults-file=/etc/my.cnf.d/server.cnf , mysqld service normal start . not error



 Comments   
Comment by Elena Stepanova [ 2015-11-01 ]

sysdljr,

If it happens all the time, the most common reason is that your mysqladmin settings, either the socket or the TCP host/port if you are using TCP protocol for mysqld, don't match those of mysqld.
If it was a one-time thing, then you probably hit some kind of a race-condition, when the server was started twice, or when a socket was removed by an accident.

If you are sure neither of those was the case, please provide your config files (all of them), and the complete error log.

Thanks.

Comment by sysdljr [ 2015-11-07 ]

reason: mysqladmin setting problem. It is OK now.
Thank you very much

Generated at Thu Feb 08 07:31:47 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.