Hi Olaf,
I can't confirm this on my systems, and I suspect that your mail command
is something that doesn't understand "-E 'set escape'". Could you check
what your mail command points to?
Here it is bsd-mailx:
# ls -l /usr/bin/mail lrwxrwxrwx 1 root root 22 Aug 4 2012
/usr/bin/mail ->
Control: found -1 0.11.2-2
Not sure what you mean with this bug.
Could you please share more details?
Sergio probably meant these messages you get when you activate a
banaction involving mails:
Date: Wed, 13 Oct 2021 19:30:01 +0200
From: Fail2Ban
To: root@localhost
Subject: [Fail2Ban]
Control: found -1 0.11.2-2
Control: tags -1 confirmed
I can confirm this on my bullseye test system:
- powertop: Multiple fail2ban threads with up to 12 events/s
- top: 0.3-1.0% CPU usage
Control: found -1 0.11.2-2
Control: found -1 0.10.2-2.1
I'm not sure yet if it's a bug, but current fail2ban versions still use
this in jail.conf:
destemail = root@localhost
Control: severity -1 normal
badips.com is no longer active, so this can probably be closed.
Removal in upstream master:
https://github.com/fail2ban/fail2ban/commit/6f4b6ec8ccdb68c75aec8225d8fa2b03ed19f320
Control: severity -1 normal
Control: fixed -1 0.11.2-2
This is working in at least bullseye/stable, using this configuration in
jail.local:
[recidive]
enabled = true
backend = pyinotify
#bantime = 1d
(That you need to configure "backend = pyinotify" is another issue, I'll
open another bug
Control: found -1 0.11.2-2
Control: found -1 0.10.2-2.1
Control: retitle -1 logrotate should be silent if package is in removed
state
Control: tags -1 + confirmed
That the file is left behind by a remove is not a bug in itself, because
only a purge would delete it. But the logrotate
Control: fixed -1 0.11.2-2
Control: fixed -1 0.10.2-2.1
Fixed in buster + bullseye.
Control: fixed -1 0.11.2-2
This bug is fixed, at least in bullseye/stable.
Control: fixed -1 0.10.2-2.1
Control: fixed -1 0.11.2-2
This was fixed upstream some ages ago (2014) in commit
9269664350656bbdbab0131754322a2a7b4a9739.
badips.com is no longer active, so this can probably be closed.
Removal in upstream master:
https://github.com/fail2ban/fail2ban/commit/6f4b6ec8ccdb68c75aec8225d8fa2b03ed19f320
Control: fixed -1 0.11.2-2
bullseye/stable's dovecot.conf now contains a regex matching
submission-login and even managesieve-login messages!
Control: fixed -1 0.11.2-2
The previous mail didn't process correctly (empty line between the two Control
pseudo-header?).
Control: fixed -1 0.10.2-2.1
Control: fixed -1 0.11.2-2
This is fixed in buster/oldstable and bullseye/stable.
Control: fixed -1 0.11.2-2
This is already possible as follows Add action.d/iptables-multiport24.conf:
# Fail2Ban configuration file
#
# Author: Cyril Jaquier
# Modified by Yaroslav Halchenko for multiport banning
# Modified by Mike Gerber to ban a whole /24 net
#
[INCLUDES]
before
Control: fixed -1 0.11.2-2
This is fixed in bullseye/stable. The jail also needs to be configured
to use a file-based backend, on a systemd/journald machine, but that's
for another bug.
Working configuration for jail.local:
[apache-fakegooglebot]
enabled = true
backend = pyinotify
Control: severity -1 wishlist
There is still no such rule in 0.11.2-2 and we should check what
bullseye/stable's libpam-google-authenticator is logging these days.
fixed 858587 0.11.2-2
thanks
This is fixed in (at least) bullseye/stable.
fixed 906087 0.11.2-2
thanks
This is fixed at least in bullseye, maybe in buster.
notfound 812690 0.11.2-2
fixed 812690 0.11.2-2
thanks
The rules are working in postfix.conf now, and postfix-sasl.conf is gone.
found 991367 0.11.2-2
thanks
This is also the case for bullseye/stable.
Control: fixed -1 0.11.2-2
This is fixed in 0.11.2-2.
found 988323 0.11.2-2
thanks
That's the default in upstream, too. See
https://github.com/roundcube/roundcubemail/blob/master/config/defaults.inc.php:
$config['log_file_ext'] = '.log';
In Debian, this changed either in buster or bullseye.
(One need to set backend = pyinotify or similar
notfound 841744 0.11.2-2
fixed 841744 0.11.2-2
thanks
This is fixed in 0.11.2-2 (bullseye aka stable) - the man page is now in
section 5.
notfound 902413 0.11.2-2
fixed 902413 0.11.2-2
thanks
This is fixed in 0.11.2-2 (bullseye aka stable).
notfound 910362 0.11.2-2
fixed 910362 0.11.2-2
thanks
This is fixed in 0.11.2-2 (bullseye).
notfound 946826 0.11.2-2
fixed 946826 0.11.2-2
thanks
This is fixed in 0.11.2-2 (bullseye).
found 960009 0.11.2-2
This bug is also affecting bullseye. The default postfix instance logs
to _SYSTEMD_UNIT=postfix@-.service, see also
/usr/share/doc/postfix/README.Debian.gz. Changing the journalmatch
accordingly fixes the problem.
Workaround in terms of ansible:
- name: "fix up
I also experienced this issue.
Hi,
* Sylvestre Ledru schrieb:
> And maybe not adding more info to this bug (as it is marked as closed)
The bug is closed because it was considered fixed. As it does not seem to be
fixed for installations with existing hundreds-of-MB fail2ban.sqlite3, it should
be reopened, IMHO.
Mike
Hi,
I have a number of Debian hosts that have these ever-growing fail2ban databases.
I tried to solve the problem by updating to 0.11.1-2 (the bullseye version).
Observations:
* Disk space usage DOUBLES by a backup copy of the database on upgrade:
total 574M
-rw--- 1 root root 300M Sep
I was also affected, broken update to 3.0.8-6+deb10u1. The patch mentioned fixed
the issue.
Changing the PYTHONPATH in debian/rules to
PYTHONPATH="$(CURDIR)/.pybuild/pythonX.Y_$(PYVERSION)/build/"
fixes this part of the build for me. (It then fails for testJournalFilesArg
when running as a user with -rfakeroot, but that is a different bug.)
I am also affected by this bug (0.9.6-2). fail2ban fails to ban, replacing every
"imap3" with "imap" in jail.conf fixes this for me.
Same bug as #867374
Package: wnpp
I'm orphaning "poc-streamer", an MP3/Ogg multicast/HTTP streamer and MP3
cutting tool, due to lack of time.
Cheers,
Mike
Dear maintainer(s),
I didn't realise that bugs in jessie-backports don't go into the bugtracker. So,
please close the bug as appropriate.
Thanks for your work,
Mike
Package: certbot
Version: 0.8.0-1~bpo8+1
Severity: important
Dear Maintainer,
After an update to certbot 0.8.0-1~bpo8+1 the certbot tool stopped working with
the following error:
# certbot
Traceback (most recent call last):
File "/usr/bin/certbot", line 5, in
from pkg_resources
Hi Michael,
* Michael Tokarev schrieb:
[ http://bugs.debian.org/685353 ]
05.09.2012 17:48, Mike Gerber wrote:
Unfortunately I can't currently as this is going into daily use now with the
working configuration and I don't really have a different machine at hand to
reproduce
The patch supplied by Nye Liu fixes this issue for me, too.
# dpkg -l | grep postgrey
ii postgrey 1.34-1.1 all greylisting implementation for Postfix
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi Ivo,
* Ivo De Decker schrieb:
As documented in /usr/share/doc/latencytop/README.Debian, latencytop needs a
kernel with the CONFIG_LATENCYTOP option to run. Enabling this option on
all (non-debug) kernels is not a good idea:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600935
Oh. Seems
Control: retitle -1 latencytop does not properly display error message when
CONFIG_LATENCYTOP kernel option is not set
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi Vassily, Hi Michael,
* malc schrieb:
Audio compiled without optimzations which should give meaningful
backtrace and contents of local variables.
Here it is, (both host and guest had 48kHz capture sample rate). kvm.real
is the qemu-kvm binary, version 1.1.1, -O0.
0x7f18106dfb6e in
Hi,
* malc schrieb:
On Wed, 5 Sep 2012, Mike Gerber wrote:
Here it is, (both host and guest had 48kHz capture sample rate). kvm.real
is the qemu-kvm binary, version 1.1.1, -O0.
To clarify things, i was under impression that you said that hang can not
be observed with 1:1 frequency
retitle 685353 kvm process hangs with 100% CPU usage when using sound
emulation
severity 685353 normal
thanks
Hi Michael,
* Michael Tokarev schrieb:
On 30.08.2012 22:03, malc wrote:
On Thu, 30 Aug 2012, Mike Gerber wrote:
[]
Vassily: Anything else you need when the hang happens again
retitle 685353 kvm process hangs with 100% CPU usage when using sound emulation
thanks
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi,
* malc schrieb:
Question - what's the frequency that the emulated card is operated in
(and what is the actual frequency host card provides)?
The guest now survived 72 hours using 44.1khz capture rate on host guest,
with the hda-intel emulation.
Also runs stable for 72 hours using the
Hi,
* malc schrieb:
Question - what's the frequency that the emulated card is operated in
(and what is the actual frequency host card provides)?
The guest now survived 72 hours using 44.1khz capture rate on host guest,
with the hda-intel emulation.
# cat
Hi Michael, Vassili,
* Michael Tokarev schrieb:
Can you also check whenever hda emulated device also shows this issue?
I'm now using
sound model='ich6'
alias name='sound0'/
address type='pci' domain='0x' bus='0x00' slot='0x06'
function='0x0'/
/sound
which
Hi, again,
(gdb) step
73 in /tmp/buildd/qemu-kvm-1.1.1+dfsg/audio/rate_template.h
(gdb)
75 in /tmp/buildd/qemu-kvm-1.1.1+dfsg/audio/rate_template.h
Btw, I started another gdb session today, before switching to ich6. qemu-kvm is
apparently looping here in rate_template.h
[Removing kvm@ from Cc, adding bugs.debian.org.)
* malc schrieb:
[..snip..]
It's also (appears) to be in the chunk of code written by Fabrice not me.
Last comment at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685353
doesn't include a backtrace.
To be honest I didn't do a backtrace
* malc schrieb:
What does p *rate yield? (i.e. other fields of rate are of
interest too)
I'll check that too, back on es1370, will take a few days of waiting.
Mike
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
found 685353 1.1.1+dfsg-1
thanks
Hi Michael,
The hanging kvm process uses 100% CPU, there's no serial console anymore,
no
access to VNC anymore. No output on netconsole either. Unfortunately, I
cannot
even get a useful gdb backtrace:
Finally, I figured out how to get a useful
Package: qemu-kvm
Version: 1.1.0+dfsg-3
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
I currently run 3 VMs using libvirt/qemu-kvm. Two of them are mostly idle and
stable, but the third one locks up within 1 or 2 days. This third VM
uses an emulated ES1370 sound
* Mike Gerber schrieb:
* Michael Tokarev schrieb:
On 20.08.2012 10:01, Mike Gerber wrote:
I currently run 3 VMs using libvirt/qemu-kvm. Two of them are mostly idle
and
stable, but the third one locks up within 1 or 2 days. This third VM
uses an emulated ES1370 sound card (host has
Hi Michael,
* Michael Tokarev schrieb:
On 20.08.2012 10:01, Mike Gerber wrote:
I currently run 3 VMs using libvirt/qemu-kvm. Two of them are mostly idle
and
stable, but the third one locks up within 1 or 2 days. This third VM
uses an emulated ES1370 sound card (host has an ASUS Xonar DX
Hi Michael,
The hanging kvm process uses 100% CPU, there's no serial console anymore,
no
access to VNC anymore. No output on netconsole either. Unfortunately, I
cannot
even get a useful gdb backtrace:
Finally, I figured out how to get a useful backtrace. Running gdb and then
using
Package: etckeeper
Version: 0.48
Severity: wishlist
etckeeper does not take the -m option for the commit command as svn/git/cvs
usually
does. This leads to a lot of commit messages that say -m on my systems, as
people (including myself) are used to type commit -m 'my message' instead of
commit
Package: imvirt
Version: 0.9.0-4
Severity: important
imvirt fails to detect the KVM hypervisor on my squeeze machines (using
the sid package, too). It seems it can't decide if it's QEMU or KVM. As
KVM is essentially QEMU on the rocks, it's not a surprise.
# imvirt
Unknown
# imvirt -d
The attached message triggers the bug for me.
Cheers,
Mike
Received: from localhost [127.0.0.1]
by localhost with IMAP (fetchmail-6.2.5)
for [EMAIL PROTECTED] (single-drop); Tue, 31 Oct 2006 09:00:35 +0100
(CET)
Received: from mail.app.leitwerk.net ([192.168.2.8]) by
tags 396443 patch
thanks
This is against:
ii offlineimap4.0.14 IMAP/Maildir synchronization and reader supp
The patch seems to work for me, might need some Python wizard and better
testing, though.
--- IMAP.py.orig2007-01-31 06:51:04.0 +0100
+++ IMAP.py
Hi
* Package name: kdebluetooth
Version : 1.0beta1
The KDE Bluetooth Framework provides several easy to use
tools to be used with Bluetooth devices.
I'd like to beta-test the package!
Cheers,
Mike
signature.asc
Description: Digital signature
Hi Priotr,
Von: Piotr Roszatycki [EMAIL PROTECTED]
Hi. Do you plan to release this toolset? I've found the mp3cue application
extremally useful.
The package will be uploaded shortly. Meanwhile, you can get the
package here:
http://bl0rg.net/~neingeist/poc-debian/
Bye,
Mike
--
To
Hi Piotr,
http://bl0rg.net/~neingeist/poc-debian/
Oh no. You're package doesn't support id3tag :(
It's in now!
Bye,
Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
64 matches
Mail list logo
