Facebook
Twitter
Servus
Basic Pleskian
Hi,
in a few words: Today I made the upgrade of MariaB from 10.3.19 (from 10.3.18). Two hours later I also made the libmariadb3 upgrade.
During the upgrade the question came, if I want to replace the /etc/mysql/my.cnf.
I hit D for showing the differences. After examination, I wanted to hit: Keep the currently-installed version.
But however I hit the wrong letter "N" for no.
It installed the new one, which I later replaced by the old one. It seems everything okay with the upgrade.
Problem: My examination took half an hour. I got the message W: Operation was interrupted before it could finish
When I call the status of Mariadb (active running) it throws the following output (FATAL ERROR in the end!):
But by grep mariadb /var/log/dpkg.log | grep upgrade I get (seems okay):
How can I check if the upgrade is really successful or wrong?
in a few words: Today I made the upgrade of MariaB from 10.3.19 (from 10.3.18). Two hours later I also made the libmariadb3 upgrade.
During the upgrade the question came, if I want to replace the /etc/mysql/my.cnf.
I hit D for showing the differences. After examination, I wanted to hit: Keep the currently-installed version.
But however I hit the wrong letter "N" for no.
It installed the new one, which I later replaced by the old one. It seems everything okay with the upgrade.
Problem: My examination took half an hour. I got the message W: Operation was interrupted before it could finish
Code:
root@server:~# aptitude upgrade
The following packages will be upgraded:
galera-3 grafana libmariadb3 mysql-common
4 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 68.2 MB of archives. After unpacking 139 kB will be used.
Do you want to continue? [Y/n/?] Y
Get: 1 https://packages.grafana.com/oss/deb stable/main amd64 grafana amd64 6.4.4 [59.9 MB]
Get: 2 http://mirror.truenetwork.ru/mariadb/repo/10.3/ubuntu bionic/main amd64 galera-3 amd64 25.3.28-bionic [8,167 kB]
Get: 3 http://mirror.truenetwork.ru/mariadb/repo/10.3/ubuntu bionic/main amd64 libmariadb3 amd64 1:10.3.19+maria~bionic [147 kB]
Get: 4 http://mirror.truenetwork.ru/mariadb/repo/10.3/ubuntu bionic/main amd64 mysql-common all 1:10.3.19+maria~bionic [5,528 B]
Fetched 68.2 MB in 2s (28.3 MB/s)
N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
(Reading database ... 218833 files and directories currently installed.)
Preparing to unpack .../galera-3_25.3.28-bionic_amd64.deb ...
Unpacking galera-3 (25.3.28-bionic) over (25.3.27-bionic) ...
Preparing to unpack .../libmariadb3_1%3a10.3.19+maria~bionic_amd64.deb ...
Unpacking libmariadb3:amd64 (1:10.3.19+maria~bionic) over (1:10.3.18+maria~bionic) ...
Preparing to unpack .../mysql-common_1%3a10.3.19+maria~bionic_all.deb ...
Unpacking mysql-common (1:10.3.19+maria~bionic) over (1:10.3.18+maria~bionic) ...
Preparing to unpack .../grafana_6.4.4_amd64.deb ...
Unpacking grafana (6.4.4) over (6.4.3) ...
Setting up libmariadb3:amd64 (1:10.3.19+maria~bionic) ...
Setting up mysql-common (1:10.3.19+maria~bionic) ...
Configuration file '/etc/mysql/my.cnf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** my.cnf (Y/I/N/O/D/Z) [default=N] ? D
Configuration file '/etc/mysql/my.cnf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** my.cnf (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/mysql/my.cnf ...
Setting up galera-3 (25.3.28-bionic) ...
Setting up grafana (6.4.4) ...
Restarting grafana-server service... OK
Processing triggers for mariadb-server-10.3 (1:10.3.19+maria~bionic) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for systemd (237-3ubuntu10.31) ...
Processing triggers for ureadahead (0.100.0-21) ...
W: Operation was interrupted before it could finish
Current status: 0 (-4) upgradable.When I call the status of Mariadb (active running) it throws the following output (FATAL ERROR in the end!):
Code:
root@server:~# service mariadb status
● mariadb.service - MariaDB 10.3.19 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf, override.conf
Active: active (running) since Wed 2019-11-06 22:45:04 CET; 27min ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Main PID: 8063 (mysqld)
Status: "Taking your SQL requests now..."
Tasks: 39 (limit: 4915)
CGroup: /system.slice/mariadb.service
└─8063 /usr/sbin/mysqld
Nov 06 22:45:04 server.example.com /etc/mysql/debian-start[8111]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Nov 06 22:45:04 server.example.com /etc/mysql/debian-start[8111]: Looking for 'mysql' as: /usr/bin/mysql
Nov 06 22:45:04 server.example.com /etc/mysql/debian-start[8111]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Nov 06 22:45:04 server.example.com /etc/mysql/debian-start[8111]: Phase 1/7: Checking and upgrading mysql database
Nov 06 22:45:04 server.example.com /etc/mysql/debian-start[8111]: Running 'mysqlcheck' with connection arguments: --socket='/var/run/mysqld/mysqld.sock' --socket='/var/run/
Nov 06 22:45:04 server.example.com /etc/mysql/debian-start[8111]: # Connecting to localhost...
Nov 06 22:45:04 server.example.com /etc/mysql/debian-start[8111]: Processing databases
Nov 06 22:45:04 server.example.com /etc/mysql/debian-start[8111]: mysql
Nov 06 22:45:04 server.example.com /etc/mysql/debian-start[8111]: /usr/bin/mysqlcheck: Got error: 1142: SELECT command denied to user 'root'@'localhost' for table 'column_s
Nov 06 22:45:04 server.example.com /etc/mysql/debian-start[8111]: FATAL ERROR: Upgrade failedBut by grep mariadb /var/log/dpkg.log | grep upgrade I get (seems okay):
Code:
root@server:~# grep mariadb /var/log/dpkg.log | grep upgrade
2019-11-06 16:11:48 upgrade mariadb-common:all 1:10.3.18+maria~bionic 1:10.3.19+maria~bionic
2019-11-06 16:11:48 upgrade mariadb-server:all 1:10.3.18+maria~bionic 1:10.3.19+maria~bionic
2019-11-06 16:11:49 upgrade mariadb-client-core-10.3:amd64 1:10.3.18+maria~bionic 1:10.3.19+maria~bionic
2019-11-06 16:11:49 upgrade mariadb-server-10.3:amd64 1:10.3.18+maria~bionic 1:10.3.19+maria~bionic
2019-11-06 16:11:52 upgrade mariadb-client-10.3:amd64 1:10.3.18+maria~bionic 1:10.3.19+maria~bionic
2019-11-06 16:11:53 upgrade mariadb-server-core-10.3:amd64 1:10.3.18+maria~bionic 1:10.3.19+maria~bionic
2019-11-06 16:18:49 upgrade libmariadb3:amd64 1:10.3.18+maria~bionic 1:10.3.19+maria~bionicHow can I check if the upgrade is really successful or wrong?
Last edited:
