Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#805310: libsasl2-modules: Annoying message "DIGEST-MD5 common mech free" with svn in systemd journal

662 views
Skip to first unread message

Vincent Lefevre

unread,
Nov 16, 2015, 4:40:03 PM11/16/15
to
Package: libsasl2-modules
Version: 2.1.26.dfsg1-14+b1
Severity: minor

Whenever I use svn, even something like "svn help", a meaningless
message appears in the systemd journal, e.g. journalctl gives:

[...]
Nov 16 21:55:27 zira svn[30840]: DIGEST-MD5 common mech free
Nov 16 21:57:12 zira svn[30987]: DIGEST-MD5 common mech free
Nov 16 21:57:14 zira svn[31025]: DIGEST-MD5 common mech free
Nov 16 21:57:20 zira svn[31051]: DIGEST-MD5 common mech free
Nov 16 21:57:20 zira svn[31026]: DIGEST-MD5 common mech free
Nov 16 21:57:25 zira svn[31052]: DIGEST-MD5 common mech free
Nov 16 21:57:26 zira svn[31086]: DIGEST-MD5 common mech free
Nov 16 21:57:27 zira svn[31087]: DIGEST-MD5 common mech free
Nov 16 21:57:28 zira svn[31111]: DIGEST-MD5 common mech free
Nov 16 21:57:33 zira svn[31112]: DIGEST-MD5 common mech free
Nov 16 21:57:34 zira svn[31139]: DIGEST-MD5 common mech free
Nov 16 21:57:36 zira svn[31158]: DIGEST-MD5 common mech free
Nov 16 21:57:37 zira svn[31168]: DIGEST-MD5 common mech free
Nov 16 21:58:11 zira svn[31286]: DIGEST-MD5 common mech free
Nov 16 21:58:12 zira svn[31287]: DIGEST-MD5 common mech free
[...]

That's annoying. According to dgrep, this message comes from
libsasl2-modules.

This problem already occurred back in 2011:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932

but probably for sysvinit machines. It was fixed in 2014 with:

* Add logcheck snippet to suppress "DIGEST-MD5 common mech free" messages
(Closes: #732771, #631932).

but this has no effect on my systemd machines. On sysvinit (and systemd)
machines, this message doesn't appear in "/var/log/syslog".

-- System Information:
Debian Release: stretch/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libsasl2-modules depends on:
ii libc6 2.19-22
ii libssl1.0.2 1.0.2d-3

libsasl2-modules recommends no packages.

Versions of packages libsasl2-modules suggests:
pn libsasl2-modules-gssapi-mit | libsasl2-modules-gssapi-heimdal <none>
pn libsasl2-modules-ldap <none>
pn libsasl2-modules-otp <none>
pn libsasl2-modules-sql <none>

-- no debconf information

Thomas D

unread,
Nov 9, 2018, 8:10:03 AM11/9/18
to
Dear Maintainer,

I can confirm that this is still a bug in Debian 9.5.
I get this message all the time on my subversion server.

Any advice on how to get rid of this message for now?
And what plans are there to fix this in future releases?

BR
Thomas

Vincent Lefevre

unread,
Jul 5, 2020, 6:40:04 PM7/5/20
to
On 2020-07-02 11:57:41 +0200, Paride Legovini wrote:
> I didn't try it, but replacing
>
> /etc/logcheck/ignore.d.server/libsasl2-modules
>
> with the version proposed by IOhannes m zmoelnig [1] may work around the
> issue. If the change is confirmed to be working it should be very easy
> for the package maintainers to include it in the next upload.
>
> Paride
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805310#10

This does not work for me, but I haven't rebooted the machine.
Restarting the rsyslog and saslauthd services has no effect.

--
Vincent Lefèvre <vin...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Vincent Lefevre

unread,
Apr 14, 2022, 5:20:03 AM4/14/22
to
Control: reopen -1
Control: found -1 2.1.28+dfsg-2

On 2022-04-14 10:13:10 +0200, Bastian Germann wrote:
> This was resolved by Frédéric Brière.

This is not fixed. Or the bug has reappeared:

Apr 14 11:06:57 zira svn[1862693]: DIGEST-MD5 common mech free
Apr 14 11:07:32 zira svn[1862770]: DIGEST-MD5 common mech free
Apr 14 11:07:39 zira svn[1862771]: DIGEST-MD5 common mech free
Apr 14 11:07:52 zira svn[1862797]: DIGEST-MD5 common mech free
Apr 14 11:08:03 zira svn[1862798]: DIGEST-MD5 common mech free
Apr 14 11:08:06 zira svn[1862839]: DIGEST-MD5 common mech free
Apr 14 11:08:07 zira svn[1862840]: DIGEST-MD5 common mech free
Apr 14 11:08:07 zira svn[1862869]: DIGEST-MD5 common mech free
Apr 14 11:08:11 zira svn[1862870]: DIGEST-MD5 common mech free
Apr 14 11:08:36 zira svn[1862934]: DIGEST-MD5 common mech free

Bastian Germann

unread,
Apr 14, 2022, 5:50:03 AM4/14/22
to
Am 14.04.22 um 11:12 schrieb Vincent Lefevre:
> This is not fixed. Or the bug has reappeared:

Frédéric's patch is essentially the same that IOhannes proposed.
I do not see how the logcheck regex rule does not match your posted log.
But I am not familiar with logcheck regex evaluation. It should be standard Perl regexes...
Or is there something wrong with introducing the group (...)?

Does anyone familiar with logcheck see the problem and can propose a working patch?
I am happy to take it.

Vincent Lefevre

unread,
Apr 14, 2022, 6:00:03 AM4/14/22
to
I think that logcheck is unrelated:

Package: logcheck
Version: 1.3.23
[...]
Description-en: mails anomalies in the system logfiles to the administrator
Logcheck helps spot problems and security violations in your logfiles
automatically and will send the results to you in e-mail.
.
Logcheck was part of the Abacus Project of security tools, but this
version has been rewritten.

This package isn't even installed on my machine (I don't need/want
such mail).

The problem here is that the message is in the systemd journal
(not that I've received a mail with such a line).
0 new messages