package mariadb-server-10.0 10.0.25-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[omamana]

i have 0 idea how this bug exists . i remember i first saw it after downloading some stuff to pass a 403 forbidden error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mariadb-server-10.0 10.0.25-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Jun 10 07:30:41 2016
DuplicateSignature:
 package:mariadb-server-10.0:10.0.25-0ubuntu0.16.04.1
 Installing new version of config file /etc/logrotate.d/mysql-server ...
 dpkg: error processing package mariadb-server-10.0 (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-05-10 (30 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Logs.var.log.daemon.log:

Logs.var.log.mysql.error.log:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=f62252da-3da3-45a3-8b0d-dea76a8176fb ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: mariadb-10.0
Title: package mariadb-server-10.0 10.0.25-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.mysql.debian-start: [deleted]

[Seth Arnold (seth-arnold)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Faustin (fauust)]

Hi,
relevant lines are :
juin 10 07:30:41 hostname mysqld_safe[5538]: [108B blob data]
juin 10 07:30:41 hostname mysqld_safe[5538]: Fatal error in defaults handling. Program aborted
juin 10 07:30:41 hostname mysqld_safe[5538]: [98B blob data]
juin 10 07:30:41 hostname mysqld_safe[5538]: Fatal error in defaults handling. Program aborted
juin 10 07:30:41 hostname mysqld_safe[5538]:
juin 10 07:30:41 hostname mysqld_safe[5538]: Installation of system tables failed! Examine the logs in
juin 10 07:30:41 hostname mysqld_safe[5538]: /var/lib/mysql for more information.
juin 10 07:30:41 hostname mysqld_safe[5538]:
juin 10 07:30:41 hostname mysqld_safe[5538]: The problem could be conflicting information in an external
juin 10 07:30:41 hostname mysqld_safe[5538]: my.cnf files. You can ignore these by doing:
juin 10 07:30:41 hostname mysqld_safe[5538]:
juin 10 07:30:41 hostname mysqld_safe[5538]: shell> /usr/bin/scripts/mysql_install_db --defaults-file=~/.my.cnf
juin 10 07:30:41 hostname mysqld_safe[5538]:
juin 10 07:30:41 hostname mysqld_safe[5538]: You can also try to start the mysqld daemon with:
juin 10 07:30:41 hostname mysqld_safe[5538]:
juin 10 07:30:41 hostname mysqld_safe[5538]: shell> /usr/sbin/mysqld --skip-grant --general-log &
juin 10 07:30:41 hostname mysqld_safe[5538]:
juin 10 07:30:41 hostname mysqld_safe[5538]: and use the command line tool /usr/bin/mysql
juin 10 07:30:41 hostname mysqld_safe[5538]: to connect to the mysql database and look at the grant tables:
juin 10 07:30:41 hostname mysqld_safe[5538]:
juin 10 07:30:41 hostname mysqld_safe[5538]: shell> /usr/bin/mysql -u root mysql
juin 10 07:30:41 hostname mysqld_safe[5538]: mysql> show tables;
juin 10 07:30:41 hostname mysqld_safe[5538]:
juin 10 07:30:41 hostname mysqld_safe[5538]: Try 'mysqld --help' if you have problems with paths. Using
juin 10 07:30:41 hostname mysqld_safe[5538]: --general-log gives you a log in /var/lib/mysql that may be helpful.
juin 10 07:30:41 hostname mysqld_safe[5538]:
juin 10 07:30:41 hostname mysqld_safe[5538]: The latest information about mysql_install_db is available at
juin 10 07:30:41 hostname mysqld_safe[5538]: https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
juin 10 07:30:41 hostname mysqld_safe[5538]: MariaDB is hosted on launchpad; You can find the latest source and
juin 10 07:30:41 hostname mysqld_safe[5538]: email lists at http://launchpad.net/maria
juin 10 07:30:41 hostname mysqld_safe[5538]:
juin 10 07:30:41 hostname mysqld_safe[5538]: Please check all of the above before submitting a bug report
juin 10 07:30:41 hostname mysqld_safe[5538]: at http://mariadb.org/jira

Could you try any of these?

[Launchpad Janitor (janitor)]

[Expired for mariadb-10.0 (Ubuntu) because there has been no activity for 60 days.]