Bug#1042399: mariadb-server 10.11.3-1 - innodb file ibdata1 continually growing, undo logs not being purged

binaries themselves are expected). > > > [1] https://mariadb.com/kb/en/mariadb-10-11-4-release-notes/ > [2] https://tracker.debian.org/news/1433062/accepted-mariadb-110114-1-source-into-unstable/ > > -- Andreas Laut System-Administrator -- Spark 5 GmbH Rheinstr. 97 64295 Darmstadt Germa

Bug#1042399: I confirm there is a problem

e the right way to report this to the issue? Should I just > post it to the mailing list or directly to some responsible person? > > > Sorry for asking you > > > best, Carsten. > -- Andreas Laut System-Administrator -- Spark 5 GmbH Rheinstr. 97 64295 Darmstadt Germa

Bug#1027337: second that bug

What we tested yesterday: dump the pdns database, drop it and push all data again into mariadb-server. To be sure that the data doesn't get messed up) After that we restarted pdns prozess. |mysqldump pdns > /tmp/pdns.sql; mysql -e "DROP DATABASE pdns"; mysql -e "CREATE DATABASE pdns";cat /tm

Bug#1027337: second that bug

Hi all, we'd like to say: We have hit the same bug in the same way and we have no idea what happens here. We are also running this mariadb server as powerdns backend (means small dataset) and since the upgrade to 10.5.18 the ressources usage increase constantly. Not only RSS of mariadbd. It'

Bug#1008667: lxcfs does restart on package update

Package: lxcfs Version: 3.0.3-2+deb10u1 Severity: important Dear Maintainer, the package was updated around 26.03./27.03. for Debian 10/buster and so lxcfs restarted. All lxc got their virtual proc filesystems lost and restart for the lxc is needed. But as we have them productive not all can be

Bug#983771: procps: /bin/ps -A -o lxc,.. f with lxc as column on debian testing shows no lxc name, only '-'

Package: procps Version: 2:3.3.17-4 Severity: normal Dear Maintainer, at Debian 10 I used to run this command: ps -A -o lxc,pid,time,args f --sort=lxc which are working very well to see what processes running in which lxc. At Debian Testing and also Sid the command above reports only '-' - for l

Bug#923534: zabbix-proxy-mysql: [zabbix-proxy-mysql] zabbix-proxy.conf with bad default option

Package: zabbix-proxy-mysql Version: 1:4.0.4 Severity: normal The zabbix-proxy.conf sets "Hostname" to "Zabbix Proxy" We don't wanna name all of our proxies "Zabbix Proxy" so we set "HostnameItem=system.run[/bin/hostname -f]" But if we set this in the "/etc/zabbix/zabbix_proxy.conf.d" dir, we get