This bug was fixed in the package logwatch -
7.4.3+git20161207-2ubuntu1.2
---
logwatch (7.4.3+git20161207-2ubuntu1.2) bionic; urgency=medium
[ Bryce Harrington ]
* d/p/0020-dhcpd-Ignore-lease-age-under-threshold-messages.patch:
dhcpd: Ignore lease age under threshold messages
This bug was fixed in the package logwatch - 7.4.2-1ubuntu1.1
---
logwatch (7.4.2-1ubuntu1.1) xenial; urgency=medium
[ Bryce Harrington ]
* d/p/0020-dhcpd-Ignore-lease-age-under-threshold-messages.patch:
dhcpd: Ignore lease age under threshold messages
(LP: #1578001)
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644057
Title:
Excessive Disco
Per discussion on IRC, going to go with the SRU as-is since it's an
incremental improvement that doesn't make things worse. A subsequent
SRU could improve further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
When sshd disconnects it leaves a pair of messages:
Received disconnect from NN.NN.NN.NN port 42004:11: disconnected by user : 1
time(s)
Disconnected from NN.NN.NN.NN port 42072 : 1 time(s)
The second message, "Disconnected from" is what this bug report deals
with. The first message, "Rec
Hello Ben, or anyone else affected,
Accepted logwatch into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/logwatch/7.4.2-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Ben, or anyone else affected,
Accepted logwatch into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/logwatch/7.4.3+git20161207-2ubuntu1.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Changed in: logwatch (Ubuntu Xenial)
Status: Confirmed => Triaged
** Changed in: logwatch (Ubuntu Bionic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390214
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390213
--
You received this bug notification because you are a member o
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: logwatch (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644057
Tit
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: logwatch (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644057
Tit
** Changed in: logwatch (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644057
Title:
Excessive Disconnect unmatched entries from sshd
To manage notificat
This was fixed in cosmic in 7.4.3+git20161207-2ubuntu2. The bug didn't
auto-close because the bug number wasn't correctly mentioned in the
changelog of the package (it missed a "#").
I added tasks for xenial and bionic.
** Also affects: logwatch (Ubuntu Bionic)
Importance: Undecided
Sta
** Merge proposal linked:
https://code.launchpad.net/~kstenerud/ubuntu/+source/logwatch/+git/logwatch/+merge/354148
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644057
Title:
Excessive Disconn
** Description changed:
+ [Impact]
+
+ User ssh disconnect messages in syslog aren't handled by logwatch, and
+ thus end up in the "Unmatched Entries" section, one per event. This
+ clutters up the logwatch reports unnecessarily.
+
+ [Test Case]
+
+ # lxc launch ubuntu-daily:cosmic tester
+ # l
** Changed in: logwatch (Ubuntu)
Assignee: Nish Aravamudan (nacc) => (unassigned)
** Changed in: logwatch (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
Confirmed still happening in bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644057
Title:
Excessive Disconnect unmatched entries from sshd
To manage notifications about this bug go to:
http
** Changed in: logwatch (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644057
Title:
Excessive Disconnect unmatched entries from sshd
To manage notifications
** Bug watch added: Debian Bug tracker #855539
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855539
** Also affects: logwatch (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855539
Importance: Unknown
Status: Unknown
--
You received this bug notification becaus
Sorry for the delay on my end.
Here is one upstream commit that is relevant:
https://sourceforge.net/p/logwatch/git/ci/0490a1c4ccf1b811bce0cd68dfce8a9e346d7648/
This will correct for: "Received disconnect from..." with a port on the
end.
Another upstream commit:
https://sourceforge.net/p/logwatc
Is this likely to be fixed with a patch?
At the moment my LogWatch reports contain about 700-1000 lines per day
in the SSHD "Unmatched Entries" section, which makes it difficult to
read/check.
I'd rater not edit the LogWatch config files myself if it's going to be
patched.
--
You received this
I have a variety of lines that do not fit into Logwatch' regex for sshd.
They are mainly caused by the lack of a port in the formatting. There
are three typical lines that are affected:
Received disconnect from [***] port [***]:11: [preauth] : 1 time(s)
Disconnected from [***] port [***] [preauth
I think this is resolved upstream, and needs some verification of which
patches would need backporting. sshd changed the log formatting to
include the port, which broke logwatch's regex.
** Changed in: logwatch (Ubuntu)
Status: New => Triaged
** Tags added: server-next
** Changed in: logw
23 matches
Mail list logo
