Bug 7617 - sysklogd running with -r and -s options causes server to stop accepting connections after a couple hours
sysklogd running with -r and -s options causes server to stop accepting conne...
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: sysklogd (Show other bugs)
6.1
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Bill Nottingham
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-12-05 23:50 EST by monica
Modified: 2014-03-16 22:11 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-01-31 15:29:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description monica 1999-12-05 23:50:32 EST
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 12:21:59 EST
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 12:42:59 EST
I'm testing it here, and it does *not* seem to be
leaking file descriptors under normal operation.

Note You need to log in before you can comment on or make changes to this bug.