MySQL problem

Modje

Verified User
Joined
Nov 16, 2005
Messages
15
Hello,

I just saw that we can uwe the custombuild script to update mysql but there went something wrong...
I use DA on Debian 3.1

So, I updated MySQL to 5.0.45 but now mysql won't start...

When I do:
Code:
/usr/local/mysql-5.0.45-linux-i686/support-files/mysql.server start
I get this:
Code:
Starting MySQL/usr/local/mysql-5.0.45-linux-i686/support-files/mysql.server: line 159: kill: (15943) - Unknow process
 ERROR!
Everitime when I try /etc/init.d/mysqld start is tell's me that mysql has been started but is actually hasn't...

Can someone help me with this?
 

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
8,343
Location
LT, EU
Try this:
Code:
/etc/init.d/mysqld stop
killall -9 mysqld
/etc/init.d/mysqld start
 
Last edited:

Modje

Verified User
Joined
Nov 16, 2005
Messages
15
Didn't work...
Code:
/etc/init.d/mysqld stop
Stopping mysqld: [ FAILED ]

killall -9 mysql
mysql: no process stopped (translated from dutch)

/etc/init.d/mysqld start
Starting mysqld: [ OK ]
It says OK but it didn't start.
 

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
8,343
Location
LT, EU
Use "killall -9 mysqld". P.S. if you want - I can take a look at your server, just PM me with your server details.
 

bighouse

New member
Joined
Oct 13, 2007
Messages
1
How was this fixed

I just installed mysql 5.0.45 on a Fedora box, and it has this exact same issue.

How did you fix this. Please specify so we all can know.

Thanks,
BigHouse
 

MadHag

Verified User
Joined
Aug 26, 2008
Messages
79
Location
French Pyrenees
Yes, can we know, I have the same problem today.

Seems to be a path problem that's all but what and where I do not know just yet.

David
 

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
8,343
Location
LT, EU
I don't remember what was the fix. If you want - I can take a look at your server for free.
 

MadHag

Verified User
Joined
Aug 26, 2008
Messages
79
Location
French Pyrenees
Thanks you for that, it's ok now. Thanks.

Apparently it was a corrupted mysql install because the file was not on DA's servers?

David
 
Top