Bug 7617

Summary:	sysklogd running with -r and -s options causes server to stop accepting connections after a couple hours
Product:	[Retired] Red Hat Linux	Reporter:	monica <danf>
Component:	sysklogd	Assignee:	Bill Nottingham <notting>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	6.1	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-01-31 20:29:08 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 monica 1999-12-06 04:50:32 UTC

Brand new RedHat 6.1 install with all security updates as of today
installed.

Hardware is Pentium III - 500, 256M RAM, 3Com FastEtherlink XL, SiS 6326
AGP video.

Machine stopped accepting new connections after a couple hours running.
Kernel error messages indicated that no file handles were available.
Last time, killing sysklogd fixed the problem without reboot.  Since the
first symptom was that the machine ceased accepting new connections, I
tried restarting sysklogd without -r and without -s.  It appears to be
stable in this configuration, but I need syslog to accept remote log
entries.

Comment 1 Bill Nottingham 1999-12-06 17:21:59 UTC

Is the machine publically available on the internet? If so,
you may want to firewall your syslog port so that only
the machines you want to connect can connect.

If the machine can only be reached by your log clients,
never mind.

Comment 2 Bill Nottingham 1999-12-06 17:42:59 UTC

I'm testing it here, and it does *not* seem to be
leaking file descriptors under normal operation.