[Bug 407862] Re: Messages not being sent to system logs

[Rainer Gerhards]

>From my PoV, this is a problem that stems back to either the config
provided and/or other packages.

Ubuntu makes rsyslog drop privileges. That's fine, though has some
documented quirks until v6. Most importantly for this bug, files are
opened before dropping privs. Nevertheless, files are created with
proper owners *iff* the owner is properly configured. Then, privs are
dropped. If the file owner is wrong, rsyslog can close files on HUP, but
obviously not reopen it.

The described problem happens under the following circumstances:

(a) rsyslog.conf does not corretly contain file owner directives, so
files are in the initial phase created with wrong user

(b) a third party package (usually logrotate) re-creates the files with
an invalid owner or permissions

For both problems bug reports exists here. In rsyslog v6, I have finally
refactored the code so that files are opened after priv drop. With the
current state of affairs, this means that rsyslog v6 on Ubuntu will
probably never start. So I really think it would be time to clean-up
package dependencies or run rsyslog as root if the source of changing
file permissions can not be found.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/407862

Title:
  Messages not being sent to system logs

Status in Rsyslog:
  Fix Released
Status in “rsyslog” package in Ubuntu:
  Confirmed

Bug description:
  First reported on Ubuntu 9.10 Alpha3
  It affects Ubuntu 10.04 Lucid Lynx Final Release, too.

  rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="2296"
  x-info="http://www.rsyslog.com"] rsyslogd was HUPed, type
  'lightweight'.

  After the above message in syslog no more messages are sent to any
  system logs. Plugging and unplugging an usb device produce no
  messages, although the device is mounted an works fine. Also, nothing
  is produced by the logger command.

  The problem occurs in a desktop and in a VirtualBox virtual machine.
  It occurred soon after karmic alpha 3 installation and persisted after
  installing all available updates in both environments.

  I'm attaching a typical syslog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/rsyslog/+bug/407862/+subscriptions