[Expired for mysql-5.7 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mysql-5.7 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to file a bug report.
I created a Bionic container to test the upgrade of mysql version
5.7.21-1ubuntu1 to 5.7.34-0ubuntu0.18.04.1 and it worked as expected:
root@mysql-test:~# apt list --upgradable
Listing... Done
mysql-server-5.7/bionic-updates,bionic-security
Hi, still affecting MySQL 5.7.34...
So, it looks like you need to check var/lib/dpkg/info/mysql-
server-5.7.postinst every time MySQL has been updated, in case this file
has been replaced by a new one, with the line 370 uncommented...
This is still an issue, although this bug has been closed
I could not delete the tmp files in /var/lib/mysql-files
However, I commented line # 370 in "/var/lib/dpkg/info/mysql-
server-5.7.postinst" and thereafter the installation went through.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It looks like it has something to do with having no password for the
root user like on my dev box.
I have the same
[ERROR] 1396 Operation ALTER USER failed for 'root'@'localhost'
in my error log and after every try a stale *.tmp file in /var/lib
/mysql-files.
The "ALTER user" command
[Expired for mysql-5.7 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mysql-5.7 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm afraid this is leaving the realm of a bug report and entering one of
support.
The upgrade path in the code can be seen in /var/lib/dpkg/info/mysql-
server-5.7.postinst:
start_server "$mysql_statedir" "$tmpdir" "skip_grant" || result=$?
# If the server fails to start, then skip the
I'm afraid this is leaving the realm of a bug report and entering one of
support.
The upgrade path in the code can be seen in /var/lib/dpkg/info/mysql-
server-5.7.postinst:
start_server "$mysql_statedir" "$tmpdir" "skip_grant" || result=$?
# If the server fails to start, then skip the
Thanks Andreas - true but I think this was a symptom rather than a
cause. That lock issue was happening after I ran
sudo dpkg --configure -a
This kept hanging with the message
"This installation of MySQL is already upgraded to 5.7.25, use --force if you
still need to run mysql_upgrade"
I
I'm seeing errors like these in your logs:
2019-02-22T22:01:48.488648Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2019-02-22T22:01:48.488703Z 0 [Note] InnoDB: Check that you do not already have
another mysqld process using the same InnoDB data or log files.
Maybe you have a stale mysql
I'm seeing errors like these in your logs:
2019-02-22T22:01:48.488648Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2019-02-22T22:01:48.488703Z 0 [Note] InnoDB: Check that you do not already have
another mysqld process using the same InnoDB data or log files.
Maybe you have a stale mysql
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mysql-5.7 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817374
Title:
Stuck on this - tried a bunch of things up to purging mysql-server and
mysql-server-5.7 packages. Reinstalling proceeded fine until the same
blocking message:
Checking if update is needed.
This installation of MySQL is already upgraded to 5.7.25, use --force if you
still need to run
13 matches
Mail list logo
