Chrooted named stops logging when is restarted

Solution Verified - Updated -

Issue

  • When rsyslogd restarts (e.g. as the result of a logrotate) the chroot named daemon no longer logs anything to /var/log/messages.

Steps to reproduce:

  1. chrooted named daemon running
  2. service rsyslog restart
  3. Perform any action with BIND which would normally log an event e.g. rndc reload. No log entries are written to /var/log/messages by named.

Environment

  • Red Hat Enterprise Linux 5/6
  • bind-chroot
  • rsyslog

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In