Bug 126153

Summary:	dev-db/mysql-5.0.19 init script should be able to remove /var/run/mysqld/mysqld.sock if present
Product:	Gentoo Linux	Reporter:	Ivan Yosifov <iyosifov>
Component:	[OLD] Server	Assignee:	Gentoo Linux MySQL bugs team <mysql-bugs>
Status:	RESOLVED WONTFIX
Severity:	trivial
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Ivan Yosifov 2006-03-14 06:18:07 UTC

home ~ # /etc/init.d/mysql start
 *  ...
 * "/var/run/mysqld/mysqld.sock" is still present.
 * Please check that it's not owned by other servers and then remove it.                                              [ !! ]
home ~ #   

Sometimes when the PC is not shutdown properly ( crash, needing a hard reboot, power blackout... ) the socket file will remain behind. This should not prevent mysql from being started on next boot, but with the current init script it does. IMO the init script should either remove the socket by default or this should be made configurable. 

Having to manually remove the socket every once in a while is tedious.

Comment 1 Francesco R. (RETIRED) gentoo-dev

2006-03-14 06:33:16 UTC

(In reply to comment #0)
> home ~ # /etc/init.d/mysql start
>  *  ...
>  * "/var/run/mysqld/mysqld.sock" is still present.
>  * Please check that it's not owned by other servers and then remove it.       
>                                       [ !! ]
> home ~ #   
> 
> Sometimes when the PC is not shutdown properly ( crash, needing a hard reboot,
> power blackout... ) the socket file will remain behind. This should not 
prevent


When a database is shutted down badly, check and/or repair the tables is good advice.

> mysql from being started on next boot, but with the current init script it
> does. IMO the init script should either remove the socket by default or this
> should be made configurable. 
> 
> Having to manually remove the socket every once in a while is tedious.
> 

try NOCHECK=1 in /etc/conf.d/mysql , never tryed it on this circumstances but it should work.

Comment 2 Ivan Yosifov 2006-03-14 06:40:11 UTC

(In reply to comment #1)
> try NOCHECK=1 in /etc/conf.d/mysql , never tryed it on this circumstances but
> it should work.

Seems to work. Thanks.

Comment 3 Francesco R. (RETIRED) gentoo-dev

2006-03-18 03:23:21 UTC

conf.d/mysql cleaned