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

[Nikolaus Rath]

On 09/07/2011 02:16 PM, Barry Warsaw 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? 

# ls -l /var/log/syslog
-rw-rw-r-- 1 root adm 0 2011-09-07 10:11 /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 don't think so:

[0] spitzer:~# logger a new, improved testing message
[0] spitzer:~# tail /var/log/syslog
[0] spitzer:~#

> 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've attached my logrotate.conf in case it matters.

> 
> I still can't reproduce your problem. :(

Well, let me know if there's anything I can do to help...

[0] spitzer:~# dpkg-query -l rsyslog
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                 Version              Description
+++-====================-====================-========================================================
ii  rsyslog              4.2.0-2ubuntu8.1     enhanced multi-threaded
syslogd

Best,


   -Nikolaus

-- 
 »Time flies like an arrow, fruit flies like a Banana.«

  PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C


** Attachment added: "logrotate.conf"
   https://bugs.launchpad.net/bugs/407862/+attachment/2369675/+files/logrotate.conf

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