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

[Barry Warsaw]

Thanks for the details Nikolaus; I want to get just a bit more
information.

On Sep 07, 2011, at 02:15 PM, Nikolaus Rath wrote:

>[0] spitzer:~# logger testing
>[0] spitzer:~# tail -2 /var/log/syslog
> 10:08:48 beta AptDaemon: INFO: Shutdown was requested
>Sep  7 10:09:42 spitzer root: testing
>[0] spitzer:~# logrotate --force --verbose /etc/logrotate.conf
[output deleted]
>[0] spitzer:~# logger testing
>[0] spitzer:~# tail /var/log/syslog
>[0] spitzer:~# tail -2 /var/log/syslog.1 
>Sep  7 10:08:48 beta AptDaemon: INFO: Shutdown was requested
>Sep  7 10:09:42 spitzer root: testing
>
>
>==> no more messages in syslog.

At this point, what is the ownership and permissions on /var/log/syslog?

After the logrotate command, I can still send messages to syslog with

$ logger -i testing

Note that the -i is necessary to make each subsequent syslog entry different,
because /etc/rsyslogd.conf has

$RepeatedMsgReduction on

by default.  Thus if you're testing with just `logger testing` these messages
will get suppressed.  I just want to be sure that this isn't tricking you into
thinking that syslog is broken.

I also testing this with a very minimal logrotate.conf file:

-----snip snip-----
weekly
rotate 4
create

/var/log/syslog
{
    postrotate
        reload rsyslog >/dev/null 2>&1 || true
    endscript
    sharedscripts
}
-----snip snip-----

I still can't reproduce your problem. :(

-- 
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