Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 22300

Summary:	bind & syslogd deadlock under high load
Product:	[Retired] Red Hat Linux	Reporter:	Kirill Pushkin <kp>
Component:	sysklogd	Assignee:	Bill Nottingham <notting>
Status:	CLOSED RAWHIDE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	dr, 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-12-15 16:02:31 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 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.