Ubuntu
logwatch package

logwatch stunnel script doesn't match any stunnel4 log entries

Bug #313275 reported by Zach on 2009-01-02

8

Affects		Status	Importance	Assigned to	Milestone
	logwatch (Ubuntu)	Expired	Low	Unassigned

Bug Description

Binary package hint: logwatch

The regular expressions in the stunnel script that is deployed with logwatch are unable to match any stunnel4 log entries.

I have attached a patch that tweaks several of the regular expressions in the script and adds or enhances the script's identification ability, including:
Certificate Verification
Input Connections
Outbound Connections
stunnel version information

Package information:

Package: logwatch
Priority: optional
Section: admin
Installed-Size: 2168
Maintainer: Ubuntu Core Developers <email address hidden>
Architecture: all
Version: 7.3.6-1ubuntu1

Package: stunnel4
Priority: optional
Section: net
Installed-Size: 484
Maintainer: Ubuntu MOTU Developers <email address hidden>
Architecture: i386
Version: 3:4.21-1

Revision history for this message

Zach (uid000) wrote on 2009-01-02:

#1

patch to fix logwatch stunnel script's regexes Edit (2.8 KiB, text/plain)

Revision history for this message

Zach (uid000) wrote on 2009-01-05:

#2

Replace the previous patch. Change "Incomming" to "Inbound" Edit (2.8 KiB, text/plain)

Adding new patch to replace mispelled "Incomming" with "Inbound" for reporting inbound connection count. This patch is against the original script and therefore replaces the previous patch.

Revision history for this message

Willi Mann (foss-ml) wrote on 2009-09-12:

#3

Speaking as the Debian Maintainer of logwatch: Rather than removing the ^ from the existing regexes, we should find out why they don't work. Can you post some loglines please? at least two for each expression would be good. Anonymisations are OK, but don't add characters that do not occur in your logs.

Revision history for this message

Chuck Short (zulcss) wrote on 2009-10-08:

#4

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

Changed in logwatch (Ubuntu):
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

Chuck Short (zulcss) wrote on 2010-04-21:

#5

Thanks for the patch ill have a look at this again for maverick.

Changed in logwatch (Ubuntu):
status:	Incomplete → Triaged

Revision history for this message

Dave Walker (davewalker) wrote on 2010-07-15:

#6

@Chuck, Have you had a chance to look at this patch? Thanks.

Revision history for this message

Dave Walker (davewalker) wrote on 2011-06-13:

#7

Setting back to incomplete as i believe this is still blocked on the log extracts as outlined in comment #3.

Thanks.

Changed in logwatch (Ubuntu):
status:	Triaged → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-08-13:

#8

[Expired for logwatch (Ubuntu) because there has been no activity for 60 days.]

Changed in logwatch (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Patches

Add patch

Remote bug watches

Bug watches keep track of this bug in other bug trackers.