Bug 39643
Summary: | sysklogd-1.3.31-12 hangs, uses no CPU time | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michael McConnell <linux> |
Component: | sysklogd | Assignee: | Jason Vas Dias <jvdias> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | sysklogd-1.4.1-22 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-08-25 23:14:58 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
Michael McConnell
2001-05-08 13:34:21 UTC
Are you using remote logging with a nameserver on the same machine? It's receiving logs from a remote machine, but the machine does not run a nameserver. Remote nameservers are reachable from it, but none of the machines have hostnames which resolve from the IP addresses. (We tend not to bother with local DNS in this lab) Just clearing out old bugs here. This one would definitely appear to be fixed with syslogd-1.4.1-22. |