Report forwarded
to debian-bugs-dist@lists.debian.org, jsbien@mimuw.edu.pl, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>: Bug#922644; Package mariadb-server-10.3.
(Mon, 18 Feb 2019 19:54:03 GMT) (full text, mbox, link).
Acknowledgement sent
to jsbien@mimuw.edu.pl (Janusz S. Bień):
New Bug report received and forwarded. Copy sent to jsbien@mimuw.edu.pl, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>.
(Mon, 18 Feb 2019 19:54:04 GMT) (full text, mbox, link).
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: mariadb-server-10.3: Unable to reinstall
Date: Mon, 18 Feb 2019 20:41:11 +0100
Package: mariadb-server-10.3
Version: 1:10.3.12-2
Severity: important
Dear Maintainer,
When I try to reinstall the package, I get
--8<---------------cut here---------------start------------->8---
Setting up mariadb-server-10.3 (1:10.3.12-2) ...
dpkg: error processing package mariadb-server-10.3 (--configure):
installed mariadb-server-10.3 package post-installation script subprocess returned error exit status 7
--8<---------------cut here---------------end--------------->8---
I don't use the MySQL directly, I'm just a user of MythTV which depends
on MariaDB. The recent change of the Internet provider resulted in the
change of the IP of my home computer which hosts the server and MythTV
clients stopped working. Not long ago a superficially similar problem
was solved by reinstalling the package, so I wanted to try this again.
BTW, I'm unable to login directly to the database, but the reason may be
independent of the problem described above (last time I have done it was
several years ago when diagnosing a different problem with MythTV).
Best regards
Janusz
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
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.70
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-6
ii libdbi-perl 1.642-1+b1
ii libpam0g 1.1.8-4
ii libssl1.1 1.1.1a-1
ii libstdc++6 8.2.0-20
ii lsb-base 10.2018112800
ii lsof 4.91+dfsg-1
ii mariadb-client-10.3 1:10.3.12-2
ii mariadb-common 1:10.3.12-2
ii mariadb-server-core-10.3 1:10.3.12-2
ii passwd 1:4.5-1.1
ii perl 5.28.1-4
ii psmisc 23.2-1
ii rsync 3.1.3-5
ii socat 1.7.3.2-2
ii zlib1g 1: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 mailutils [mailx] 1:3.5-2
pn mariadb-test <none>
pn netcat-openbsd <none>
pn tinyca <none>
-- Configuration Files:
/etc/mysql/mariadb.conf.d/50-server.cnf changed:
[server]
[mysqld]
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
% bind-address = 192.168.1.11
bind-address = 192.168.0.10
key_buffer_size = 16M
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8
myisam_recover_options = BACKUP
query_cache_limit = 1M
query_cache_size = 16M
log_error = /var/log/mysql/error.log
expire_logs_days = 10
max_binlog_size = 100M
character-set-server = utf8mb4
collation-server = utf8mb4_general_ci
[embedded]
[mariadb]
[mariadb-10.1]
-- debconf information:
mariadb-server-10.3/nis_warning:
mariadb-server-10.3/old_data_directory_saved:
mariadb-server-10.3/postrm_remove_databases: false
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>: Bug#922644; Package mariadb-server-10.3.
(Fri, 22 Feb 2019 14:39:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Otto Kekäläinen <otto@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>.
(Fri, 22 Feb 2019 14:39:05 GMT) (full text, mbox, link).
To: Janusz S. Bień <jsbien@mimuw.edu.pl>,
922644@bugs.debian.org
Subject: Re: [debian-mysql] Bug#922644: mariadb-server-10.3: Unable to reinstall
Date: Fri, 22 Feb 2019 15:51:34 +0200
Control: tags -1 moreinfo
Hello!
ma 18. helmik. 2019 klo 21.54 Janusz S. Bień (jsbien@mimuw.edu.pl) kirjoitti:
> When I try to reinstall the package, I get
>
> --8<---------------cut here---------------start------------->8---
> Setting up mariadb-server-10.3 (1:10.3.12-2) ...
> dpkg: error processing package mariadb-server-10.3 (--configure):
> installed mariadb-server-10.3 package post-installation script subprocess returned error exit status 7
> --8<---------------cut here---------------end--------------->8---
Thanks for reporting! Unfortunately the information above does not
reveal anything. What about the syslog/journald? Anything related
logged in /var/log or /var/lib/mysql ?
Added tag(s) moreinfo.
Request was from Otto Kekäläinen <otto@debian.org>
to 922644-submit@bugs.debian.org.
(Fri, 22 Feb 2019 14:39:05 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>: Bug#922644; Package mariadb-server-10.3.
(Fri, 22 Feb 2019 15:03:04 GMT) (full text, mbox, link).
Acknowledgement sent
to jsbien@mimuw.edu.pl:
Extra info received and forwarded to list. Copy sent to Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>.
(Fri, 22 Feb 2019 15:03:04 GMT) (full text, mbox, link).
Subject: Re: [debian-mysql] Bug#922644: mariadb-server-10.3: Unable to reinstall
Date: Fri, 22 Feb 2019 15:53:09 +0100
On Fri, Feb 22 2019 at 15:51 +02, Otto Kekäläinen wrote:
> Control: tags -1 moreinfo
>
> Hello!
>
> ma 18. helmik. 2019 klo 21.54 Janusz S. Bień (jsbien@mimuw.edu.pl) kirjoitti:
>> When I try to reinstall the package, I get
>>
>> --8<---------------cut here---------------start------------->8---
>> Setting up mariadb-server-10.3 (1:10.3.12-2) ...
>> dpkg: error processing package mariadb-server-10.3 (--configure):
>> installed mariadb-server-10.3 package post-installation script subprocess returned error exit status 7
>> --8<---------------cut here---------------end--------------->8---
>
> Thanks for reporting! Unfortunately the information above does not
> reveal anything. What about the syslog/journald? Anything related
> logged in /var/log or /var/lib/mysql ?
Thank you very much for your interest in my problem.
I've just reproduced the problem again.
In syslog I found
--8<---------------cut here---------------start------------->8---
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: Installation of system tables failed! Examine the logs in
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: /var/lib/mysql for more information.
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: The problem could be conflicting information in an external
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: my.cnf files. You can ignore these by doing:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: You can also try to start the mysqld daemon with:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: shell> /usr/sbin/mysqld --skip-grant-tables --general-log &
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: and use the command line tool /usr/bin/mysql
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: to connect to the mysql database and look at the grant tables:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: shell> /usr/bin/mysql -u root mysql
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: mysql> show tables;
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: Try 'mysqld --help' if you have problems with paths. Using
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: --general-log gives you a log in /var/lib/mysql that may be helpful.
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: The latest information about mysql_install_db is available at
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: You can find the latest source at https://downloads.mariadb.org and
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: the maria-discuss email list at https://launchpad.net/~maria-discuss
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: Please check all of the above before submitting a bug report
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]: at http://mariadb.org/jira
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23398]:
Feb 22 15:26:15 VivoPC-D8 mariadb-server-10.3.postinst[23462]: 2019-02-22 15:26:15 0 [Note] /usr/sbin/mysqld (mysqld 10.3.12-MariaDB-2) starting as process 23461 ...
--8<---------------cut here---------------end--------------->8---
but this instruction is confusing:
1. I don't see anything readable in /var/lib/mysql, ib_logfile0 seems to
me to be binary.
2. I don't have .my.cnf file at all.
3. I don't have /usr/sbin/mysqld.
4. I don't have /usr/sbin/mysql.
Moreover I don't think the process 23461 actually started.
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>: Bug#922644; Package mariadb-server-10.3.
(Fri, 22 Feb 2019 15:51:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Otto Kekäläinen <otto@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>.
(Fri, 22 Feb 2019 15:51:02 GMT) (full text, mbox, link).
Subject: Re: [debian-mysql] Bug#922644: mariadb-server-10.3: Unable to reinstall
Date: Fri, 22 Feb 2019 17:09:42 +0200
The problem is:
" Installation of system tables failed!"
What if you uninstall/purge, clear /etc/mysql and /var/lib/mysql and try again?
What is the output of 'find /etc/mysql -ls' ?
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>: Bug#922644; Package mariadb-server-10.3.
(Fri, 22 Feb 2019 16:45:06 GMT) (full text, mbox, link).
Acknowledgement sent
to jsbien@mimuw.edu.pl:
Extra info received and forwarded to list. Copy sent to Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>.
(Fri, 22 Feb 2019 16:45:06 GMT) (full text, mbox, link).
Subject: Re: [debian-mysql] Bug#922644: mariadb-server-10.3: Unable to reinstall
Date: Fri, 22 Feb 2019 17:40:29 +0100
On Fri, Feb 22 2019 at 17:09 +02, Otto Kekäläinen wrote:
> The problem is:
> " Installation of system tables failed!"
>
> What if you uninstall/purge, clear /etc/mysql and /var/lib/mysql and try again?
I was already thinking about purging the package, but I would like to be sure
what is the risk. Is there a chance I will loose the database needed for
playing MythTV recording?
>
> What is the output of 'find /etc/mysql -ls' ?
--8<---------------cut here---------------start------------->8---
jsbien@VivoPC-D8:~$ find /etc/mysql -ls
1050754 4 drwxr-xr-x 5 root root 4096 Feb 18 20:19 /etc/mysql
1052842 4 -rw-r--r-- 1 root root 682 Nov 10 2015 /etc/mysql/mysql.cnf
1062107 4 -rwxr-xr-x 1 root root 1620 Jan 18 21:04 /etc/mysql/debian-start
1052990 4 -rw------- 1 root root 333 Dec 13 2015 /etc/mysql/debian.cnf
1050755 4 -rw-r--r-- 1 root root 839 Sep 3 2015 /etc/mysql/my.cnf.fallback
1050756 4 drwxr-xr-x 2 root root 4096 Jan 27 07:52 /etc/mysql/conf.d
1050757 4 -rw-r--r-- 1 root root 55 Sep 3 2015 /etc/mysql/conf.d/mysqldump.cnf
1050758 4 -rw-r--r-- 1 root root 8 Sep 3 2015 /etc/mysql/conf.d/mysql.cnf
1050785 0 lrwxrwxrwx 1 root root 24 Sep 21 2015 /etc/mysql/my.cnf -> /etc/alternatives/my.cnf
1056833 4 drwxr-xr-x 2 root root 4096 Feb 18 20:19 /etc/mysql/mariadb.conf.d
1054306 4 -rw-r--r-- 1 root root 3719 Nov 25 2017 /etc/mysql/mariadb.conf.d/50-server.cnf.old
1062109 4 -rw-r--r-- 1 root root 3719 Jan 8 23:10 /etc/mysql/mariadb.conf.d/50-server.cnf.dpkg-dist
1053697 4 -rw-r--r-- 1 root root 1032 Jan 24 2017 /etc/mysql/mariadb.conf.d/50-mysqld_safe.cnf
1054307 4 -rw-r--r-- 1 root root 3737 Nov 25 2017 /etc/mysql/mariadb.conf.d/50-server.cnf~
1052733 4 -rw-r--r-- 1 root root 336 Oct 2 2016 /etc/mysql/mariadb.conf.d/50-mysql-clients.cnf
1050452 4 -rw-r--r-- 1 root root 733 Jul 31 2018 /etc/mysql/mariadb.conf.d/50-client.cnf
1053698 4 -rw-r--r-- 1 root root 3768 Feb 4 18:31 /etc/mysql/mariadb.conf.d/50-server.cnf
1573035 4 drwxr-xr-x 2 root root 4096 Nov 25 2017 /etc/mysql/mysql.conf.d
1573046 4 -rw-r--r-- 1 root root 3027 Nov 10 2015 /etc/mysql/mysql.conf.d/mysqld.cnf
1573401 4 -rw-r--r-- 1 root root 3046 Nov 25 2017 /etc/mysql/mysql.conf.d/mysqld.cnf.old
1573397 4 -rw-r--r-- 1 root root 3027 Nov 25 2017 /etc/mysql/mysql.conf.d/mysqld.cnf.old~
1573044 4 -rw-r--r-- 1 root root 21 Nov 10 2015 /etc/mysql/mysql.conf.d/mysqld_safe_syslog.cnf
1049051 4 -rw-r--r-- 1 root root 869 Oct 2 2016 /etc/mysql/mariadb.cnf
--8<---------------cut here---------------end--------------->8---
I guess this is not relevant, but I made some experiments with
bind-address values; currently it is just 127.0.0.1.
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>: Bug#922644; Package mariadb-server-10.3.
(Fri, 22 Feb 2019 18:42:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Otto Kekäläinen <otto@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>.
(Fri, 22 Feb 2019 18:42:03 GMT) (full text, mbox, link).
Subject: Re: [debian-mysql] Bug#922644: mariadb-server-10.3: Unable to reinstall
Date: Fri, 22 Feb 2019 20:39:21 +0200
pe 22. helmik. 2019 klo 18.40 Janusz S. Bień (jsbien@mimuw.edu.pl) kirjoitti:
>
> On Fri, Feb 22 2019 at 17:09 +02, Otto Kekäläinen wrote:
> > The problem is:
> > " Installation of system tables failed!"
> >
> > What if you uninstall/purge, clear /etc/mysql and /var/lib/mysql and try again?
>
> I was already thinking about purging the package, but I would like to be sure
> what is the risk. Is there a chance I will loose the database needed for
> playing MythTV recording?
Yes, purging the package will delete /var/lib/mysql and all of your data.
Your configs look OK. Unfortunately I am not able to figure out what
might the problem with this data.
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>: Bug#922644; Package mariadb-server-10.3.
(Fri, 22 Feb 2019 19:09:03 GMT) (full text, mbox, link).
Acknowledgement sent
to jsbien@mimuw.edu.pl:
Extra info received and forwarded to list. Copy sent to Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>.
(Fri, 22 Feb 2019 19:09:03 GMT) (full text, mbox, link).
Subject: Re: [debian-mysql] Bug#922644: mariadb-server-10.3: Unable to reinstall
Date: Fri, 22 Feb 2019 20:07:54 +0100
On Fri, Feb 22 2019 at 20:39 +02, Otto Kekäläinen wrote:
> pe 22. helmik. 2019 klo 18.40 Janusz S. Bień (jsbien@mimuw.edu.pl) kirjoitti:
>>
>> On Fri, Feb 22 2019 at 17:09 +02, Otto Kekäläinen wrote:
>> > The problem is:
>> > " Installation of system tables failed!"
>> >
>> > What if you uninstall/purge, clear /etc/mysql and /var/lib/mysql and try again?
>>
>> I was already thinking about purging the package, but I would like to be sure
>> what is the risk. Is there a chance I will loose the database needed for
>> playing MythTV recording?
>
> Yes, purging the package will delete /var/lib/mysql and all of your data.
>
> Your configs look OK. Unfortunately I am not able to figure out what
> might the problem with this data.
Fortunately I can live without MythTV by using a MS Windows program for
TV. Nevertheless I would like to solve my problem in some reasonable
future. I will come bacǩ to it probably in April, after some planned
hardware change.
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>: Bug#922644; Package mariadb-server-10.3.
(Mon, 25 Feb 2019 06:21:03 GMT) (full text, mbox, link).
Acknowledgement sent
to jsbien@mimuw.edu.pl:
Extra info received and forwarded to list. Copy sent to Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>.
(Mon, 25 Feb 2019 06:21:03 GMT) (full text, mbox, link).
To: Debian Bug Tracking System <submit@bugs.debian.org>
Cc: 922644@bugs.debian.org
Subject: Re: Bug#922644: mariadb-server-10.3: Unable to reinstall
Date: Mon, 25 Feb 2019 07:20:18 +0100
On Mon, Feb 18 2019 at 20:41 +01, Janusz S. Bień wrote:
[...]
> -- Configuration Files:
> /etc/mysql/mariadb.conf.d/50-server.cnf changed:
> [server]
> [mysqld]
> user = mysql
> pid-file = /var/run/mysqld/mysqld.pid
> socket = /var/run/mysqld/mysqld.sock
> port = 3306
> basedir = /usr
> datadir = /var/lib/mysql
> tmpdir = /tmp
> lc-messages-dir = /usr/share/mysql
> skip-external-locking
> % bind-address = 192.168.1.11
^^^
The silly typo was the culprit.
The credit for spotting it goes to Stephen Worthington:
http://lists.mythtv.org/pipermail/mythtv-users/2019-February/399639.html
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>: Bug#922644; Package mariadb-server-10.3.
(Mon, 25 Feb 2019 06:21:16 GMT) (full text, mbox, link).
Acknowledgement sent
to jsbien@mimuw.edu.pl:
Extra info received and forwarded to list. Copy sent to Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>.
(Mon, 25 Feb 2019 06:21:16 GMT) (full text, mbox, link).
Reply sent
to Otto Kekäläinen <otto@debian.org>:
You have taken responsibility.
(Mon, 25 Feb 2019 09:21:05 GMT) (full text, mbox, link).
Notification sent
to jsbien@mimuw.edu.pl (Janusz S. Bień):
Bug acknowledged by developer.
(Mon, 25 Feb 2019 09:21:05 GMT) (full text, mbox, link).
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.