creating a local environment stops the syslog (1.19.3)

[David Britton]

authlog also, anything controlled by rsyslogd. There appears to be a redirect error or similar in the rsyslog.d file that the local provider prints out. Once you destroy the environment, logs all come back to normal.

This is a pretty critical bug.

To repro,

    echo 'foo' | logger -p local0.notice
    <notice the entry in /var/log/syslog>

    juju bootstrap local
    echo 'foo' | logger -p local0.notice
    <notice nothing in syslog>

    juju destroy-environment local
    echo 'foo' | logger -p local0.notice
    <notice the entry in /var/log/syslog again>

local is defined simply as:

  local:
    type: local
    default-series: precise

Note, also just removing the /etc/rsyslog.d/*juju* file that is in place brings back syslog functionality.

[Andrew Wilkins (axwalk)]

The rsyslog config format is mystifying to me. I can get it to work again by changing $DefaultRuleset from "local" to "remote". I don't understand why this works, though. Will need to see if Michael or Wayne know what the deal is.