Hi, the first one ... N: Ignoring file '20auto-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
... is an unrelated issue. In fact not so much an issue than a FYI message telling you that since the update this file is no more active, but still around if you want/need to retain anything. The second one ... aeltaib@aeltaib-PC:~$ mysql -u root -p Enter password: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) ... first seems to be bug 1670629, but that is about timing on upgrade. But you report this connect after the upgrade. On the upgrade itself the server fails to start, and due to that the upgrade is being considered failed. >From the log: Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details. invoke-rc.d: initscript mysql, action "start" failed. ● mysql.service - MySQL Community Server Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Wed 2017-05-31 14:30:33 EET; 7ms ago Process: 8758 ExecStartPost=/usr/share/mysql/mysql-systemd-start post (code=exited, status=0/SUCCESS) Process: 8757 ExecStart=/usr/sbin/mysqld [0;1;31m(code=exited, status=1/FAILURE)[0m Process: 8750 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS) Main PID: 8757 (code=exited, status=1/FAILURE) May 31 14:30:33 aeltaib-PC systemd[1]: [0;1;31mFailed to start MySQL Community Server.[0m May 31 14:30:33 aeltaib-PC systemd[1]: [0;1;39mmysql.service: Unit entered failed state.[0m May 31 14:30:33 aeltaib-PC systemd[1]: [0;1;39mmysql.service: Failed with result 'e...'.[0m An extended look at a full systemctl status mysql might shed some extra light. But mostly the last mysql start I think was crashed by (from the log): 2017-05-31T12:30:35.024009Z 0 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use 2017-05-31T12:30:35.024015Z 0 [ERROR] Do you already have another mysqld server running on port: 3306 ? 2017-05-31T12:30:35.024029Z 0 [ERROR] Aborting So is there anything running? Questions: - What are the permissions of /var/run/mysqld/mysqld.sock? - Would it work if you run through sudo? - if /var/run/mysqld/mysqld.sock which process owns it (lsof) and is that process running? - output of "systemctl status mysql.service" - is there a mysql running already? - are the mysql configured ports un ise by something else? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694705 Title: package mysql-server-5.7 5.7.18-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1694705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
