Bug 22300 - bind & syslogd deadlock under high load
Summary: bind & syslogd deadlock under high load
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sysklogd
Version: 6.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-14 15:26 UTC by Kirill Pushkin
Modified: 2014-03-17 02:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-12-15 16:02:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Kirill Pushkin 2000-12-14 15:26:30 UTC
Speciality: syslogd is configured to receive external messages from
Cisco router.

Sometimes (may take a week) under high load named hangs until its restart.
strace -p <named_pid> says:
send(3,"<syslog message>

After disabling of receiving of external messages by syslogd all work
just fine.

Possible problem: syslog resolves IP to name for external message, but
named is busy by sending message to syslog in that time.

Comment 1 Kirill Pushkin 2000-12-14 15:28:22 UTC
btw, rpm -q bind sysklogd :

bind-8.2.2_P7-0.6.2
sysklogd-1.3.31-17


Comment 2 Bill Nottingham 2000-12-30 07:01:11 UTC
This will be fixed in sysklogd-1.4-4, which will be in the next
rawhide release; you will be able to start syslogd with the '-x'
option that disables reverse lookups of incoming messages.


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