Bug 7759

Summary:	syslog fails to log ipchains rules that have log option set
Product:	[Retired] Red Hat Linux	Reporter:	Matthew Galgoci <mgalgoci>
Component:	sysklogd	Assignee:	Bill Nottingham <notting>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	1999-12-15 22:09:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthew Galgoci 1999-12-12 03:41:17 UTC

This report was from a customer.

Basically, syslog fails to log packets that match logging rules under
certain circumstances. He has about 200 packet filtering rules, and has
to restart the logger in order for logging to work. I was not able to
duplicate the problem with a single rule.

He also pointed me to a patch against sysklogd that reportedly fixes the
problem:
ftp://ftp.ocs.com.au/pub/ksymoops/patch-sysklogd-1-3-32-ksymoops-1.gz

Comment 1 Bill Nottingham 1999-12-13 16:07:59 UTC

Um, the 'patch-sysklogd-1-3-31-ksymoops-1.gz' that's in
that directory shouldn't have *anything* to do with
whether or not ipchains-type packets are logged.

Comment 2 Bill Nottingham 1999-12-15 22:09:59 UTC

Actually, does he have klogd running?

One of the things that patch fixes is a possible
segfault in klogd - if klogd died, ipchains-type
packets wouldn't be logged.

In any case, the segfault fixed by that patch
is fixed in the latest sysklogd in Raw Hide.