On 22/09/16 13:59, to...@tuxteam.de wrote:
> On Thu, Sep 22, 2016 at 01:07:49PM +0200, Tony van der Hoff wrote:
>> On 22/09/16 12:56, to...@tuxteam.de wrote:
>>> On Thu, Sep 22, 2016 at 12:43:18PM +0200, Tony van der Hoff wrote:
>>>> Hi,
>>>> Running Jessie here. Performed apt-get upgrade yesterday, which included
>>>> a new version of mysql.
>>>> I now cannot connect to mysql:
>>>> ERROR 2002 (HY000): Can't connect to local MySQL server through socket
>>>> '/var/run/mysqld/mysqld.sock' (2)
>>>> Any suggestions on how to fix, please?
>>> Is the mysql daemon running? Try "service mysqld status" or however
>>> that's named in the brave new systemd world (I'm still in the messy
>>> old sysv world, mind you ;-)
>> Thanks tomas;
> You might check whether there's a process called (more or less) mysql
> around:
>   ps wwwaux | grep mysql
Ther was...

> you might have a look into wherever mysql places its log files (unless
> they've been kidnapped by systemd, in which case I'd have to defer to
> smarter people; but I don't believe that). Look somewhere in /var/log/mysql.
No all the log files were there, but empty...

> Then you might try to invoke (gasp!) "/etc/init.d/mysql start" (as root)
> yourself and see whether it spews any error messages giving any clues.

> Then you could issue an "netstat -antp" as root, to see whether the
> mysql daemon is listening on some other (non-default) port.

It turns out that the recent upgrade took mysql from 5.5 to 5.6. It
uninstalled mysql-server-5.5, but failed to install mysql-server-5.6,
due to an unmet dependency on mysql-server-core-5.6.

I manually installed mysql-server-core-5.6, after which mysql-server-5.6
installed fine.

Mysql now starts correctly.

Thanks for your help,


>> Ariège, France     |
> Wonderful region, btw. I've got warm and sweet memories from summer
> 2015...

Very warm and sunny right now. The trees are just starting to change colour.

Tony van der Hoff  | mailto:t...@vanderhoff.org
Ariège, France     |

Reply via email to