rsyslog no longer creating new log files immediately after SIGHUP

Solution Verified - Updated -

Issue

  • After updating to rsyslog version 5, new log files are not created immediately after sending rsyslogd a HUP signal (for example, after the log files are moved by logrotate or a custom rotate script).
    • Previous versions of rsyslog created empty files immediately after receipt of SIGHUP.
    • Note: The expected behaviour is observed when doing a full restart: empty files are created.

Environment

  • Red Hat Enterprise Linux 6
    • rsyslog >= rsyslog-5.8.10-2.el6
  • Red Hat Enterprise Linux 5
    • rsyslog >= rsyslog5-5.8.12-4.el5

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

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content