ryslogd logging breaks with local provider (after logrotate?)

Bug #1332545 reported by Christian Reis
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Won't Fix
Medium
Unassigned

Bug Description

I'm using the local provider, and something has installed /etc/rsyslog.d/25-juju-juju-local.conf.

I've found that this is breaking logging on my machine, likely related to logrotate. Symptoms:

  - /var/log/syslog contains entries for the exact period between Jun 20 08:01:32 and 08:01:37
  - "start rsyslog" and "restart rsyslog" does not cause "rsyslogd:... start" entries to be written to /var/log/syslog
  - ps auxw confirms that ryslogd is running
  - /var/log/syslog does not show new entries
  - running rsyslogd -d dumps debug messages but after issuing the line "initialization completed, transitioning to regular run mode", I get dumped back into the prompt and nothing appears in the logs.

The simple way I have found to fix this has been to just remove 25-juju-juju-local.conf from /etc/rsyslog.d/.

I'm using:

kiko@chorus:/etc/rsyslog.d$ dpkg -l | grep juju
ii juju 1.19.3-0ubuntu1~12.04.1~juju1 next generation service orchestration system
ii juju-core 1.19.3-0ubuntu1~12.04.1~juju1 Juju is devops distilled - client
ii juju-local 1.19.3-0ubuntu1~12.04.1~juju1 dependency package for the Juju local provider

Curtis Hovey (sinzui)
tags: added: logging
Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
Curtis Hovey (sinzui)
tags: added: rsyslog
Changed in juju-core:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.