Bug#926231: [debian-mysql] Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql
Please try again with latest version in Debian unstable: mariadb-10.3 1:10.3.13-2
Bug#926231: [debian-mysql] Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql
What does the MariaDB error log say when the ALTER TABLE in the postinst run? ti 2. huhtikuuta 2019 klo 17.30 Graham Cobb kirjoitti: > Package: mariadb-server-10.3 > Version: 1:10.3.13-2 > Followup-For: Bug #926231 > > The bug still exists in 1:10.3.13-2 > > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (900, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) (ignored: > LC_ALL set to en_IE.utf8), LANGUAGE=en_GB (charmap=UTF-8) (ignored: LC_ALL > set to en_IE.utf8) > Shell: /bin/sh linked to /bin/bash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages mariadb-server-10.3 depends on: > ii adduser 3.118 > ii debconf [debconf-2.0] 1.5.71 > ii galera-3 25.3.25-1 > ii gawk 1:4.2.1+dfsg-1 > ii iproute2 4.20.0-2 > ii libc6 2.28-8 > ii libdbi-perl 1.642-1+b1 > ii libgnutls30 3.6.6-2 > ii libpam0g 1.3.1-5 > ii libstdc++68.3.0-4 > ii lsb-base 10.2019031300 > ii lsof 4.91+dfsg-1 > ii mariadb-client-10.3 1:10.3.13-2 > ii mariadb-common1:10.3.13-2 > ii mariadb-server-core-10.3 1:10.3.13-2 > ii passwd1:4.5-1.1 > ii perl 5.28.1-5 > ii psmisc23.2-1 > ii rsync 3.1.3-6 > ii socat 1.7.3.2-2 > ii zlib1g1:1.2.11.dfsg-1 > > Versions of packages mariadb-server-10.3 recommends: > ii libhtml-template-perl 2.97-1 > > Versions of packages mariadb-server-10.3 suggests: > ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-1 > ii mailutils [mailx] 1:3.5-3 > ii mailx 1:20081101-2 > pn mariadb-test > ii netcat-openbsd 1.195-2 > ii tinyca 0.7.5-6 > > -- debconf information: > mariadb-server-10.3/nis_warning: > mariadb-server-10.3/old_data_directory_saved: > mariadb-server-10.3/postrm_remove_databases: false > > ___ > pkg-mysql-maint mailing list > pkg-mysql-ma...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-mysql-maint
Bug#926231: [debian-mysql] Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql
On Wed, Apr 3, 2019 at 11:12 PM Graham Cobb wrote: > I'm not sure what the "MariaDB error log" is but I have found the following > entries in syslog: It's /var/log/mysql/error.log
Bug#926231: [debian-mysql] Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql
Have you tried running mysql_upgrade or systemctl restart mariadb ? Both commands will run some mysql.user table modifications to compensate on how MySQL 5.7 is different from MySQL 5.6 and previous ones.
Bug#926231: [debian-mysql] Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql
Control: severity -1 normal I am sorry but I am not able to replicate this bug. So it cannot at least be common, thus downgrading severity. Please figure out a way for me to replicate it so I can debug what is happening. Also, check out if there is any output at /var/log/mysql/* Here are is an example of steps I used to debug Jessie mysql-5.5 -> Buster mariadb-10.3 upgrade with systemd active: laptop$ docker run -d --privileged --name upgrade-test -v /sys/fs/cgroup:/sys/fs/cgroup:ro jrei/systemd-debian laptop$ docker exec -it upgrade-test bash container$ sed -i "s/101/0/g" -i /usr/sbin/policy-rc.d # Enables maint script to do restarts rm /etc/apt/sources.list.d/backports.list apt update && apt install -y mysql-server systemctl status mysql -> OK nano /etc/apt/sources.list -> jessie -> buster apt update && apt install -y apt procps apt install mariadb-server -y # systemctl status mysql * mariadb.service - MariaDB 10.3.13 database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2019-04-16 08:26:15 UTC; 10s ago Docs: man:mysqld(8) https://mariadb.com/kb/en/library/systemd/ Process: 7138 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS) Process: 7145 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 7147 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exite d, status=0/SUCCESS) Process: 7226 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS) Process: 7229 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Main PID: 7195 (mysqld) Status: "Taking your SQL requests now..." Tasks: 31 (limit: 4915) Memory: 66.4M CGroup: /system.slice/docker.service/system.slice/mariadb.service `-7195 /usr/sbin/mysqld Apr 16 08:26:14 f3554bc9396a systemd[1]: Starting MariaDB 10.3.13 database server... Apr 16 08:26:15 f3554bc9396a mysqld[7195]: 2019-04-16 8:26:15 0 [Note] /usr/sbin/mysqld (mysqld 10.3.13-MariaDB-2) starting as process 7195 ... Apr 16 08:26:15 f3554bc9396a /etc/mysql/debian-start[7228]: Upgrading MySQL tables if necessary. Apr 16 08:26:15 f3554bc9396a /etc/mysql/debian-start[7246]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables Apr 16 08:26:15 f3554bc9396a systemd[1]: Started MariaDB 10.3.13 database server. So no problems here. We also have extensive testing in Salsa (e.g. https://salsa.debian.org/mariadb-team/mariadb-10.3/pipelines/43484) and it does not show any problems in upgrades.
Bug#926231: [debian-mysql] Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql
On Tue, 16 Apr 2019 11:33:23 +0300 Otto Kekäläinen wrote: Hello Otto, >I am sorry but I am not able to replicate this bug. So it cannot at >least be common, thus downgrading severity. > >Please figure out a way for me to replicate it so I can debug what is >happening. Also, check out if there is any output at /var/log/mysql/* I'm not the original bug submitter, but I hope I can offer some help, as I have successfully worked around the problem; Here, the mysql server was not running, and the mariadb-server-10.3 upgrade failed. I couldn't restart the server, but after some searching the internet I found that doing the following: root# rm /var/lib/mysql/ib* user$ /etc/init.d/mysql start got the server running. Then, I tried: #dpkg --configure mariadb-server-10.3 which, after a few minutes, succeeded. I have no idea how, when or why the problem (i.e. server stopped running) occurred, but I'm now back on track. I hope this of help to the original submitter, as well as yourself. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" I can't do a thing 'cause I can't relax Independence Day - Comsat Angels pgpsewCMvWK5C.pgp Description: OpenPGP digital signature
