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

[surfingalien]

i'm making this discussion come up as i have the same problem as
described on 3 diferent machine all running ubuntu 10.04 (2 laptops and
1 server). if this is not so important for the laptop, it counts for my
server as i usually read the syslog to see if evrything works fine...
without a log file, i'm coming blind...

I didn't change any permisions on any file on these machine. for example
I had this bug on my server last week, and reinstalled it 7 days ago.
reading the syslog a couple of days after it shows:

jean-louis at x-wing:~$ tail -100 /var/log/syslog 
Jan 21 06:40:30 x-wing rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="2173" x-info="http://www.rsyslog.com"] rsyslogd was HUPed, type 'lightweight'.
Jan 21 07:17:01 x-wing CRON[3990]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jan 21 08:17:01 x-wing CRON[4003]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jan 21 09:17:01 x-wing CRON[4017]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

when googling: rsyslogd was HUPed, type 'lightweight' there are
thousands of links coming up, then this is not an isolated problem.

what should be done to solve this issue ?

i am available for any information,  and can even provide an access to a
machine if i can help solving.

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

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