Also found all-machines.log issue with 1.21

[Menno Smits]

The fix for this is merging into master and 1.21 now.

The problem was that for local provider based environments, unit and
machine agents weren't including the required namespace in their log
message tags. rsyslogd on the server was expecting to see the namespace so
it filtered out the unexpected messages. I think this regression was
probably introduced when we started using a Go syslog client on non-state
server machines instead of rsyslogd (so that we can have non-Linux
machines).



On 27 November 2014 at 14:23, Menno Smits <menno.smits at canonical.com> wrote:

>
>
> On 27 November 2014 at 10:52, Tim Penhey <tim.penhey at canonical.com> wrote:
>
>> https://bugs.launchpad.net/juju-core/+bug/1396796
>>
>> Would love other people to check.
>>
>> I don't know if it happens on other providers, just using local right now.
>>
>> I would appreciate it if someone could confirm working or not working on
>> EC2.
>>
>
> I've checked on EC2 and the problem doesn't appear to happen there, both
> when upgrading or starting with fresh install. Seems like this is a local
> only issue.
>
> I've been digging in to this problem with the local provider but don't
> have an answer yet, just theories.
>
> - Menno
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20141127/2476915b/attachment-0001.html>