Dear maintainer,
I must agree with Sebastian Kutsch.
irqbalance may not be the better way to treat interruption problem but it
is doing is job quite good on a (squeeze - 3.2.0-0.bpo.4-amd64).
Regards,
Faustin LAMMLER
http://www.falared.net
Hi Helumt,
thanks for the workaround!
Isn't the following line more appropriate (options before
arguments)?
find /var/cache/approx -mindepth 1 -empty -type d -delete
Regards,
Faustin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Hi Paul,
my guess is that the DB crashed so the 'tc.log' file was created and it
prevent the mariadb-server to start again.
Let me check with the dev team were to investigate on this possible
crash and I will come back to you.
In the mean time, if you want to continue your investigation, I
ld
try?
--
Faustin Lammler
MariaDB Foundation
I can confirm the problem and I am able to reproduce it.
Steps:
1/ on jessie, install mariadb-server and apparmor
2/ enable apparmor (on fresh jessie, it is not enabled by default for
mysqld):
https://wiki.debian.org/AppArmor/HowToUse?action=show=AppArmor%2FHowTo#Enable_AppArmor
3/ replace
Hi Harald,
thank you for your help!
Linking this bug to MariaDB bug report tool:
https://jira.mariadb.org/browse/MDEV-13672
Faustin
Hi Paul.
Could you provide me the content of syslog and mysql log when dpkg fails?
I see that Apparmor is enabled, could you also send me the result of:
$ sudo aa-status
Is there any apparmor mysqld profile (/etc/apparmor.d/usr.sbin.mysqld)?
Faustin
Paul,
can you try to rename the tc.log file?
Do you know which version of mariadb-server you are upgrading from?
Hi Otto,
I can not reproduce this.
Upgrade from:
- 10.1.23-9+deb9u1 to 10.1.24-6 > OK
- 10.1.23-9+deb9u1 to 10.1.34-1 > OK
This was added to my sources.list:
deb [check-valid-until=no]
http://snapshot.debian.org/archive/debian/20170624T094211Z/ buster main
non-free contrib
deb
Control: severity -1 normal
Hi,
linking this to MDEV-11170 as it contains information (and script), to
rollback on mysql:
https://jira.mariadb.org/browse/MDEV-11170
Faustin
Hi Albert,
can you confirm if this bug is now resolved (and close it)?
Regards,
Faustin
file on location specified in config
Reply-To: faus...@fala.red
Hi Stefan,
thank you for your help!
I have just installed mariadb-server on a fresh stable debian 9 (KVM
platform) and I can not reproduce this (I am able to change path of pid
file):
$ sudo apt install mariadb-server
$ sudo rep -r
Hi Thomas,
can you please investigate further on Ondřej's suggestion (apparmor).
Please check out this for information on how to verify it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900398#10
Is there any chance that you are using a "non official kernel"?
What is the systemd version
Hi Ozzloy,
from what I see, you are using the Linux 3.2.0-4-amd64 kernel that is
the oldoldstable kernel.
https://packages.debian.org/search?keywords=linux-image-3.2.0-4-amd64
Is there any reason why you are using this kernel version?
Can you try to reproduce the bug with a more recent kernel
Hi Stefanos,
thank you for your report.
I can confirm this on the latest stable Debian release
(10.1.26-0+deb9u1). Problem is also present on Debian testing release
(1:10.1.35-1).
I see two solutions:
- the one you suggested 'loose-default-character-set=utf8mb4';
- using
/logrotate.conf
It seems that mysqladmin is unable to connect to the database. May I ask
you to verify this point? Does the user 'debian-sys-maint' still exists?
Regards,
--
Faustin Lammler
Hi Ralf,
thank you for your report.
This seems to be a connexion problem and can be caused by the database
being under heavy load. Then the connexion times out and rotation of
logs can't be achieved. May that be possible?
Regards,
Faustin
Hi Nicolas,
Thank you for taking the time to report this bug.
Unfortunately, we cannot work on this bug because your description
didn't include enough information.
You may find it helpful to read "How to report a bug in Debian using
reportbug" https://www.debian.org/Bugs/Reporting
Thanks!
Package: mariadb-server-10.1
Version: 1:10.1.29-6+b1
Severity: normal
Hi Corey,
thank you for your report.
If this is acceptable for you, you can use the official mariadb package
from MariaDB repository that is build against OpenSSL:
https://downloads.mariadb.org/mariadb/repositories
Regards,
Faustin
Hi Francisco,
I found an issue very close to this in MariaDB's Jira:
https://jira.mariadb.org/browse/CONC-124
I can't tell you for now if this is the way it is supposed to work, must
check this point.
The second solution you proposed should be preferred as I saw some
problem with symlink and
Hi Alex,
thanks for your report.
This is confirmed and step to reproduce are:
$ sudo apt install mariadb-server-core-10.1
$ /usr/bin/mysql_install_db
FATAL ERROR: Could not find /usr/bin/my_print_defaults
...
> Please either move mysql_install_db into mariadb-server-10.1, or move
>
scope
Reply-To: faus...@fala.red
Hi,
can you please take a look at:
https://github.com/monitoring-plugins/monitoring-plugins/pull/1522
https://github.com/monitoring-plugins/monitoring-plugins/issues/1508#issuecomment-334528542
> Please do not use MYSQL_PORT. Instead use a 0 to have the library
Control: forwarded -1 https://github.com/keplerproject/luasql/issues/108
Hi,
in case you did not saw this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919395#36
> this looks like a bug. MYSQL_SERVER_VERSION is documented here:
>
Control: forwarded -1 https://redmine.kannel.org/issues/795
Hi,
This seems to be a bug (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919395#36):
> error: 'MYSQL_SERVER_VERSION' undeclared
>
> this looks like a bug. MYSQL_SERVER_VERSION is documented here:
>
Hi Adrian,
in case you did not saw this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919395#36
> error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect'
>
> This is not a bug. MYSQL.reconnect was not part of the API, even in 5.5
>
Otto,
here are the issues opened to notify upstream devs about Sergei's
analysis:
https://github.com/OpenSIPS/opensips/issues/1589
https://github.com/keplerproject/luasql/issues/108
https://github.com/jabberd2/jabberd2/issues/193
https://redmine.kannel.org/issues/795
In addition, as requested,
Control: forwarded -1 https://github.com/jabberd2/jabberd2/issues/193
Hi Lucas,
please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919395#36:
> error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect'
>
> This is not a bug. MYSQL.reconnect was not part of the API, even in
Faustin Lammler ,
17/01/2019 - 19:23:00 (-0300):
> Regarding 919375 and 919408, can you @Sergei confirm this
> https://github.com/monitoring-plugins/monitoring-plugins/pull/1522 and
> this https://github.com/monitoring-plugins/monitoring-plugins/pull/1522?
And this
https://github.com/m
ave tested 10.1 and 10.3 from mariadb repo, they are both
OK.
If you have time and want to contribute on a patch, feel free to read
this :-)
https://wiki.debian.org/Teams/MySQL/patches
Have a nice week-end,
--
Faustin Lammler
Hi Yannik,
thanks for your report!
I am able to reproduce this and the problem is only present in the
Debian package version of MariaDB.
This bug seems also described there:
https://jira.mariadb.org/browse/MDEV-8457
If this is an acceptable solution until the bug is resolved, you can use
the
Hi Marc,
thank you for your help!
May I ask you which version of mariadb you where upgrading from?
And also please respond to the following:
> I commented out the audit plugin relateted lines in the mariadb config
> file.
Can you give me the path of this config file?
Did you uncommented the
Olaf van der Spek ,
21/11/2018 - 15:03:07 (+0100):
> It's a non-existing path (hopefully), so apt won't read any files from
> /etc/apt/sources.d (the default for that setting).
OK but I still can not understand why they do that. And why apt then
removes these packages:
default-mysql-server
Jeremy Davis ,
21/11/2018 - 15:57:31 (+1100):
> I'll aim to provide as much relevant info as possible, if there is
> anything else you need please ask. Hopefully it's not too waffley and/or
> includes too much irrelevant info... (I'm often told that I need to turn
> verbosity down...)
Verbosity
Thanks Olaf!
Olaf van der Spek ,
21/11/2018 - 14:52:05 (+0100):
> /etc/apt/sources.list.d/
> File fragments for locations to fetch packages from. Configuration
> Item: Dir::Etc::SourceParts.
Yes, but what does 'nonexistent'?
> This, plus the restriction in the apt command to only use security sources,
> makes dist-upgrade remove any package with a failed dependency.
Thanks David for this (and Olaf for your initial guess), it is now clear to me
what happened.
Let me check with Otto why this new dependence was added.
Marc,
I am not able to reproduce this.
Here are my steps:
- installation of mariadb-server-10.1_10.1.26-0+deb9u1;
- load and activation of the audit plugin:
$ cat /etc/mysql/my.cnf | grep -v ^#
[mysqld]
plugin_load=server_audit=server_audit.so
Hi Jeremy, thank you for your report.
To work on this, I need to be able to reproduce it.
Are you able to provide a step-by-step procedure?
If not, dpgk -l could help to understand what apt dependencies may be
problematic. And what happened when you reinstalled mariadb. Which
command did you
Hi Marc and thanks Marco for your input!
I may have found something. I think the plugin is not activated because
of the spaces (or tab) you use in the config file.
I am able to reproduce the error if I use:
plugin_load = server_audit = server_audit.so
But if I use (without space):
Hi Otto!
This may be related to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879099.
And some useful information could be found there:
https://jira.mariadb.org/browse/MDEV-15835
For the moment I don't know if my suggestion on MDEV-15835 could apply
to this too.
Faustin
Mea culpa, this is not a solution:
> - using 'character-sets-dir=utf8mb4'.
> - the one you suggested 'loose-default-character-set=utf8mb4';
This is a solution, and you can also just comment it:
'# default-character-set=utf8mb4';'
Problem is that this impacts other mysql clients program.
So one
Hi Peter,
could you have a look at
https://github.com/MariaDB/mariadb-connector-c/pull/101 and check if it
looks good to you (it seems to be pretty similar patch).
Faustin
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-18721
Thanks Alan for the report and Peter for the patch!
I have just opened an issue on upstream bug tracking system
(https://jira.mariadb.org).
It is now linked to this bug report.
Regards,
Faustin
Hi Matthew!
Thank you for this workaround.
Feel free to add any comment to https://github.com/lxc/lxc/pull/2758 if
needed.
Olaf,
It seems that in this case, the error log should indeed be in the
datadir ($ldata -> /var/lib/mysql).
I have double checked and this behavior is the same since 10.1 (Debian
or upstream).
See:
https://salsa.debian.org/mariadb-team/mariadb-10.1/blob/master/scripts/mysql_install_db.sh#L489
Control: forwarded -1 https://github.com/lxc/lxc/pull/2758
Matthew,
I able to reproduce this and I have the exact same error (mariadb log +
apparmor on host).
Your workaround is working but it seems that removing only these 3 lines
is sufficient:
> ProtectSystem=full
> PrivateDevices=true
>
Hi Matthew,
Thanks for your report!
I have no platform setup to test this so I have to install one but I am
not a LXC expert. Do you think this could be tested into a libvirt VM?
If I understand correctly, you have a Debian testing host and you are
running an LXC container with 10.3 mariadb
Hi Olaf!
Since there has not been any change on the mysql_install_db.sh script
regarding this for long, I thought that such output message was normal
and that the error log would be as it says in /var/lib/mysql.
But on Debian it is not and you are right, error log goes to
Hi Olaf!
Thanks for your report.
Can I ask you what steps leads to this?
Regards,
Faustin
Hi again,
I have just checked and this seems to be the default directory
for the error log:
https://mariadb.com/kb/en/library/overview-of-mariadb-logs/
> The error log
>
> - Always enabled
> - Usually a file in the data directory, but some distributions may
> move this to other
Olaf,
yes this is true but your output comes from the mysql_install_db.sh
install script (not from mariadb server itself).
I can't see any change between 10.1 and 10.3 version (and 10.4 upstream
version) regarding this behavior, let me dig a bit more and check if
this is normal.
Faustin
Hi Conrad,
I have just successfully installed mariadb-server (10.1.38-0+deb9u1) on
a fresh Debian Stretch.
There must be something wrong with your setup because fresh installation
of mariadb-server from official Debian repository is widely tested and
we would have a lot more people complaining.
Hi Olaf,
do you think that
https://salsa.debian.org/mariadb-team/mariadb-10.3/merge_requests/12
resolves the bug or is there anything more you want me to test in order
to double check?
Thanks!
Faustin
signature.asc
Description: PGP signature
Hi Michael,
I can confirm this bug and I am not able to reproduce it with the
upstream 10.1 version (from the official MariaDB repo).
I will check what's the diff and if we can expect a fix in the next
release based on the upstream version or if we have to submit a specific
patch directly on
Olaf van der Spek ,
12/06/2019 - 15:50:05 (+0200):
> MR 12 is (kinda) unrelated to #917086.
Sorry I confused
https://salsa.debian.org/olafvdspek-guest/mariadb-10.3/commit/55d06886f5a81c10a00822078aac3ea0090c1b7f
with MR 12.
Faustin
signature.asc
Description: PGP signature
Otto Kekäläinen ,
12/06/2019 - 20:39:53 (+0300):
> > > MR 12 is (kinda) unrelated to #917086.
> > Sorry I confused
> > https://salsa.debian.org/olafvdspek-guest/mariadb-10.3/commit/55d06886f5a81c10a00822078aac3ea0090c1b7f
> > with MR 12.
>
> Note that this commit is not on the master branch and
Control: tags -1 + fixed pending
Hi,
the fix is already in the next version (debian/10.1.40-0+deb9u1).
Maybe Otto can confirm when this version will be uploaded?
Regards,
Faustin
signature.asc
Description: PGP signature
Hi,
this upload would also fix #928758, it's not a critical bug but it would
be nice to fix it.
Regards!
Faustin
signature.asc
Description: PGP signature
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-19490
Hi Roman,
Thank you for your report. This is a known bug and it's going to be
resolved in 10.3.16 version.
https://jira.mariadb.org/browse/MDEV-19490
Regards,
Faustin
signature.asc
Description: PGP signature
Hi Michael!
May I ask you to have a look at
https://salsa.debian.org/mariadb-team/mariadb-10.3/merge_requests/20 and
verify if this seems correct to you?
Regards,
Faustin
signature.asc
Description: PGP signature
Hi Gregory!
Thanks you for the confirmation and the "workaround".
The issue as just been resolved for Buster (see 939819).
I will check with Otto when the next upload is planned for Stretch.
Regards,
Faustin
signature.asc
Description: PGP signature
Control: -1 tags moreinfo
Control: -1 severity normal
Hi Tom!
Otto Kekäläinen ,
17/04/2019 – 10:52:42 (+0300):
> ke 17. huhtik. 2019 klo 9.21 Tom (tgrom.autom...@nuegia.net) kirjoitti:
> >
> > > > Can you please test again using latest MariaDB release 10.3.13-1
> > > > (which now switched to
Hi Olaf,
did you finally managed to setup the TLS between client and server?
Let me know if you want me to test something based on
https://mariadb.com/kb/en/library/securing-connections-for-client-and-server/
and
https://mariadb.com/kb/en/library/certificate-creation-with-openssl/.
Faustin
Olaf
Control: tags -1 moreinfo
Hi Michael!
Thank you for your report.
I am not able to reproduce the 404 you are talking about on a fresh
Stretch installation, are you sure that your apt cache is up to date or
that you are using default apt preferences?
This is what I have just tested successfully:
Hi Michael,
thank you for your suggestion!
This is already in the pipe, see:
https://github.com/MariaDB/server/pull/1172
https://jira.mariadb.org/browse/MDEV-15526
I have no idea when or if this could be incorporated in 10.3. Let me
come back to you once I have more information.
Regards,
Control: severity -1 important
Michael,
I have just realized that MDEV-15526 is closed because the problem is
resolved on 10.4 (by not deploying mysql sysv init script if systemd is
detected on post-installation), but problem still exist on 10.3.
So disabling mariadb service does not disable
Hi Michael!
Michael Biebl ,
20/09/2019 – 22:20:22 (+0200):
> Regarding my feedback, I guess the answer depends on what the goals of
> upstream are and Debian.
>
> Is the goal to keep the mysql aliasing or not?
>
> From what I gathered from the upstream bug report, upstream (at least
> one
Hi!
Thank you for your report.
Unfortunately I am not able to reproduce the problem using the same
repositories (ftp.de.debian.org).
I see that you are using "unstable" in your apt sources.list, did you
made any changes in your apt preferences that could lead to this
problem?
Regards,
Faustin
Hi Mark!
On a fresh Buster installation, you should not have the problem. There
must be something else in your setup that lead to this.
If you want to understand better how to install unstable packages on a
stable Debian, I suggest you to read some documentation about "apt
pinning".
For
Hi Richard!
Indeed, https://wiki.debian.org/ReleaseGoals/RunDirectory.
I'll consider the implication and if we should try to upstream it or do
it on Debian only.
Regards,
Faustin
signature.asc
Description: PGP signature
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-18841
I have just asked on the upstream jira.
signature.asc
Description: PGP signature
Control: reopen -1
signature.asc
Description: PGP signature
forwarded -1 https://jira.mariadb.org/browse/MDEV-21586
signature.asc
Description: PGP signature
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-21586
signature.asc
Description: PGP signature
Hi!
Indeed https://github.com/MariaDB/server/blob/10.4/debian/not-installed#L4
It seems that the move was done in 10.4 to not deploy it anymore due to
it's huge size.
Otto, do you know if this binary is provided by another deb or if there
is any way to get it through Debian repositories.
Control: forcemerge -1 971399
signature.asc
Description: PGP signature
Control: merge -1 971399
Hi Antonio!
Thanks for your report.
This is duplicate of #971399.
Faustin
signature.asc
Description: PGP signature
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-23567
Control: severity -1 wishlist
signature.asc
Description: PGP signature
PR submitted upstream:
https://github.com/MariaDB/server/pull/1105
signature.asc
Description: PGP signature
Control: forward -1 https://jira.mariadb.org/browse/MDEV-22552
signature.asc
Description: PGP signature
Control: severity -1 moreinfo
Hi!
Olaf van der Spek ,
17/06/2020 – 08:19:54 (+0200):
> > The file /etc/dnsroots.global is created when you install the djbdns
> > package itself.
>
> Is djbdns installed? Was it installed previously?
Another thought:
Some internet boxes do not let you use a
Control: tags -1 moreinfo
signature.asc
Description: PGP signature
Control: tags -1 moreinfo
signature.asc
Description: PGP signature
Control: forward -1 https://jira.mariadb.org/browse/MDEV-23050
Hi Russel!
This may be related to:
- https://jira.mariadb.org/browse/MDEV-23050
- https://jira.mariadb.org/browse/MDEV-23321
Faustin
signature.asc
Description: PGP signature
Control: severity -1 moreinfo
signature.asc
Description: PGP signature
Hi Otto!
Otto Kekäläinen ,
23/09/2020 – 15:52:34 (+0300):
> The error "Unknown option: default-character-set" is also fixed in
> MariaDB 10.5.5 as the /etc/mysql/mariadb.conf.d/50-client.cnf no
> longer defines anything about charsets or utf8mb4 (it relies on the
> server to enforce utf8mb4
Control: forward -1 https://jira.mariadb.org/browse/MDEV-12190
Hi Otto!
So shouldn't we tag wontfix?
signature.asc
Description: PGP signature
Hi,
the tip from Michael Pietsch seems to have been confirmed in the KB
documentation, see comments from Jean Weisbuch
https://mariadb.com/kb/en/certificate-creation-with-openssl/
So if it's a certificate format problem due to a bad generation
procedure, I guess we could close this.
I have
Conrtol: forwarded -1 https://jira.mariadb.org/browse/MDEV-18061
Hi Olaf!
I see that you opened a jira issue about this, remember to forward bug
reports to upstream issue so we can track them better.
What about Sergei last message, do you have any further comments?
Regards,
Faustin
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-22659
Hi Bob!
Thanks for your help.
The jira issue you are pointing on is correct (so I am forwarding this
bug report to it).
Feel free to do it next time, that helps us a lot in maintaining this
complex package.
Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-23697
Hi Lucio!
Thanks for your report.
Indeed:
| docker run --name test --privileged -d -v /sys/fs/cgroup:/sys/fs/cgroup:ro
fauust/docker-systemd:debian-sid
| docker exec -it test bash -c "apt update && apt -y install mariadb-server"
|
Control: forwarded -1 https://github.com/facebook/rocksdb/issues/7051
signature.asc
Description: PGP signature
ile:1534:
_module_/var/lib/dkms/wireguard/1.0.20200520/build] Error 2
| make[1]: *** [Makefile:146: sub-make] Error 2
| make: *** [Makefile:8: all] Error 2
| make: Leaving directory '/usr/src/linux-headers-4.19.0-6-amd64'
Let me know if I should open this bug report upstream.
Regards,
--
Faus
-upgrade;
6/ mariadb-server is installed and up and running (10.3.22).
--
Faustin Lammler
GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79
signature.asc
Description: PGP signature
Hi Jörg!
I am not sure that I understand what are the steps that I could follow
to verify this.
Are you trying to dist-upgrade from buster to sid?
In that case, I was not able to reproduce the error in a container with
the following steps:
| # podman run -it debian:10 bash
| # apt update
| # apt
Hi Richard!
This can not be considered as a bug and you are asking to make default
an increase of the max_open_files option because your setup needs it.
Why not consider instead overriding the systemd unit default option with
what you think is the best value for your setup?
Search for
Richard van den Berg ,
07/12/2020 – 19:20:12 (+0100):
> Ok, so the 16384 limit in /lib/systemd/system/mariadb.service is actually
> the default from upstream?
Yes, see:
https://github.com/MariaDB/server/blob/10.6/support-files/mariadb.service.in#L146
> That seems odd to me as it warns it needs
Control: severity -1 normal
Control: tags -1 + moreinfo
signature.asc
Description: PGP signature
Thanks Olaf, your help is very appreciated!
Can I kindly ask you to open an issue directly on jira.mariadb.org then
(and forward this BR when it's open).
I have already searched for such issue on jira but nothing cames out.
Regards,
Faustin
signature.asc
Description: PGP signature
1 - 100 of 182 matches
Mail list logo
