On Wed, 2004-12-29 at 09:30 +0100, Gorm J. Siiger wrote:
syslog-ng probably blocks on something, maybe on a DNS query. can you strace syslog-ng while it is blocked like this?
I found the problem, the reverse dns zone for one particular host was classless delegated, and that name-server was configured wrong.
Pretty interesting that syslog-ng fails that bad when dns doesn't work.
Once the problem was fixed everything went back to normal.
you can always disable resolving names from DNS, but what else could you do? if I'd do non-blocking DNS queries and would continue processing on other messages while waiting for a given message to resolve, then message ordering will be bad. An other solution might be to add non-DNS name lookups, e.g. resolve names from a private mechanism to make it possible to use names in messages and use IP addresses if it fails, but never block. What do you think about this solution? -- Bazsi