Comment 5 for bug 1658067

Thanks for the help,

Actually I have to do /etc/init.d/mysql restart each time I'm using
mysql for the websites i'm developing locally (127.0.0.1) so it can
work. When I'm using symfony, I have to use these 2 lines to clear the
cache :

     php /var/www/Symfony/bin/console cache:clear
     chmod 777 -R /var/www/Symfony/var/cache/dev

which isn't quite nice. So maybe there's a problem with some files that
cannot be accessed. Just trying to help too. A password is needed for
pma, because I also had to use that :

     use mysql;
     CREATE USER 'user1'@'localhost' IDENTIFIED BY 'pass';
     GRANT ALL PRIVILEGES ON *.* TO 'user1'@'localhost' IDENTIFIED BY
'pass';

in order to recover the password I had lost. I haven't used symfony for
a long time but I think I have to log in with user1 to make it work.

Le 23/01/2017 à 13:19, ChristianEhrhardt a écrit :
> Hi,
> from the log
> mysql_upgrade: Got error: 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) while connecting to the MySQL server
> Upgrade process encountered error and will not continue.
> mysql_upgrade failed with exit status 11
>
> That means the server did not start, and due to that later processes of
> the upgrade would fail - therefore it breaks here.
>
> The error log itself doesn't hold too much on that - it seems to start shutting down right after being up:
> 2017-01-20T11:50:55.797820Z 0 [Note] mysqld: ready for connections.
> Version: '5.7.17-0ubuntu0.16.04.1' socket: '/tmp/tmp.4JyEzHaYGM/mysqld.sock' port: 3306 (Ubuntu)
> 2017-01-20T11:50:55.798261Z 0 [Note] Giving 0 client threads a chance to die gracefully
> 2017-01-20T11:50:55.798287Z 0 [Note] Shutting down slave threads
>
> Your config at https://launchpadlibrarian.net/303220958/MySQLConf.etc.mysql.mysql.conf.d.mysqld.cnf.txt uses the default socket path, so other than the unexpected immediate shutdown I don't see an issue.
> I'd expect more a "error: Reason" anywhere, but this way I'm kind of lost.
>
> The reason the messge shows up over and over again is that it retries
> every time.
>
> I wonder if anything comes to your mind that this could be any sort of a
> special case to your custom setup of mysql?
>
>
> ** Changed in: mysql-5.7 (Ubuntu)
> Status: Confirmed => Incomplete
>