| 1 |
On 2012-01-15 2:11 PM, Mick <michaelkintzios@×××××.com> wrote: |
| 2 |
> On Sunday 15 Jan 2012 18:35:01 Stéphane Guedon wrote: |
| 3 |
>> On Sunday 15 January 2012 18:26:09 Tanstaafl wrote: |
| 4 |
>>> After the update, I attempted to restart mysql but got: |
| 5 |
>>> |
| 6 |
>>> myhost : Sun Jan 15, 12:23:47 : ~ |
| 7 |
>>> |
| 8 |
>>> # /etc/init.d/mysql restart |
| 9 |
>>> * Starting mysql ... |
| 10 |
>>> * start-stop-daemon: /usr/sbin/mysqld is already running [ !! ] |
| 11 |
>>> * ERROR: mysql failed to start |
| 12 |
>>> |
| 13 |
>>> myhost : Sun Jan 15, 12:23:55 : ~ |
| 14 |
>>> |
| 15 |
>>> and in the log: |
| 16 |
>>> |
| 17 |
>>> Jan 15 12:23:55 myhost /etc/init.d/mysql[16429]: start-stop-daemon: |
| 18 |
>>> /usr/sbin/mysqld is already running |
| 19 |
>>> Jan 15 12:23:55 myhost /etc/init.d/mysql[16396]: ERROR: mysql failed to |
| 20 |
>>> start |
| 21 |
|
| 22 |
>> I have this since years ! |
| 23 |
>> Can't manage to get this error out ! |
| 24 |
>> I will look at the tread carefully ! |
| 25 |
|
| 26 |
> You could try: |
| 27 |
> |
| 28 |
> ps axf | grep mysql |
| 29 |
> |
| 30 |
> and then kill<PID> of mysql before you try to restart it. |
| 31 |
|
| 32 |
I can try that this weekend (this is a production server), but that |
| 33 |
would not be a *fix*, only an ugly workaround. |
| 34 |
|
| 35 |
No one else is having this problem or has an idea of how to fix it properly? |
Archives