>-- Configuration Files: >/etc/mysql/conf.d/mysqld_safe_syslog.cnf 347fa9f3d579ffc06c39bf7e69f4fc6e [Errno 2] No such file or directory: >u'/etc/mysql/conf.d/mysqld_safe_syslog.cnf 347fa9f3d579ffc06c39bf7e69f4fc 6e' >/etc/mysql/conf.d/tokudb.cnf 64fddee896bfb1c3e63c983a63e25190 [Errno 2] No such file or directory: u'/etc/mysql/conf.d/tokudb.cnf >64fddee896bfb1c3e63c983a63e25190'
I have commented-out all lines that MYSQL_BOOTSTRAP calls from postinst, since it stuckc at it. When I kill dpkg from another terminal it says that it was on 67 line of server-10.0.postinst . I have tried installing from testing, stable, upstream repo. Ended up with mysqldump; apt-get purge mysql-common; rm -rf /etc/mysql /var/lib/mysql; Than I reinstalled it and loaded dump. Пн, 22 черв. 2015 о 15:11 Otto Kekäläinen <o...@seravo.fi> пише: > 2015-06-22 14:52 GMT+03:00 Yurii Kolesnykov <yuriko...@gmail.com>: > > * What was the outcome of this action? > > Stuck at "Configuring mariadb-server-10.0" > > Thanks for reporting this! > > Do you have any additional information what dpkg is stuck at? What > version of MariaDB did you have previously? > > > I can see in your report: > >-- Configuration Files: > >/etc/mysql/conf.d/mysqld_safe_syslog.cnf 347fa9f3d579ffc06c39bf7e69f4fc6e > [Errno 2] No such file or directory: > >u'/etc/mysql/conf.d/mysqld_safe_syslog.cnf > 347fa9f3d579ffc06c39bf7e69f4fc6e' > >/etc/mysql/conf.d/tokudb.cnf 64fddee896bfb1c3e63c983a63e25190 [Errno 2] > No such file or directory: u'/etc/mysql/conf.d/tokudb.cnf > >64fddee896bfb1c3e63c983a63e25190' > > > ..but only these files are supposed to be in the mariadb-common package: > > drwxr-xr-x root/root ./etc/mysql/ > -rw-r--r-- root/root ./etc/mysql/mariadb.cnf > drwxr-xr-x root/root ./etc/mysql/mariadb.conf.d/ > -rw-r--r-- root/root ./etc/mysql/mariadb.conf.d/mysqld.cnf > -rw-r--r-- root/root ./etc/mysql/mariadb.conf.d/client.cnf > -rw-r--r-- root/root ./etc/mysql/mariadb.conf.d/mysqld_safe.cnf > > The files mysqld_safe_syslog.cnf and tokudb.cnf however used to be a > part of the package. Maybe I've failed to re-register them from the > package properly and users updating from version X (which?) to 10.0.20 > experience this issue. >
