debug-log broken for local provider again

[Tim Penhey]

On 16/10/14 04:30, Curtis Hovey-Canonical wrote:
> On Tue, Oct 14, 2014 at 10:23 PM, Tim Penhey <tim.penhey at canonical.com> wrote:
>> Hi folks,
>>
>> while testing today I noticed that debug-log is broken for the local
>> provider because the all-machines.log file isn't being written out.
>>
>> Not done any more follow up yet.
> 
> I don't understand this sentence.
> 
> We can see from a recent failure in CI that all-machines.log was
> written out and captured:
>     http://juju-ci.vapour.ws:8080/job/local-deploy-utopic-amd64/500/
> 
> I ran 1.21-alpha2-trusty-amd64 and debug-log and it worked for me.
> 
> Which version of juju did you test? Shouldn't there be a bug tracking
> this issue?

Just checked this with master:


$ juju debug-log
ERROR cannot open log file: open
/var/log/juju-tim-local/all-machines.log: no such file or directory


$ ll /var/log/juju-tim-local/
total 96
drwxr-xr-x  2 syslog adm     4096 Oct 30 11:59 ./
drwxrwxr-x 27 syslog syslog  4096 Oct 30 11:56 ../
-rw-r--r--  1 root   root     883 Oct 30 11:59 ca-cert.pem
-rw-------  1 syslog syslog   599 Oct 30 11:57 logrotate.conf
-rwx------  1 syslog syslog   103 Oct 30 11:57 logrotate.run*
-rw-------  1 syslog syslog 27282 Oct 30 11:57 machine-0.log
-rw-------  1 syslog syslog  4145 Oct 30 11:59 machine-1.log
-rw-------  1 syslog syslog  4144 Oct 30 11:59 machine-2.log
-rw-------  1 syslog syslog   981 Oct 30 11:57 rsyslog-cert.pem
-rw-------  1 syslog syslog   887 Oct 30 11:57 rsyslog-key.pem
-rw-------  1 syslog syslog  8194 Oct 30 11:59 unit-mediawiki-0.log
-rw-------  1 syslog syslog 10466 Oct 30 11:59 unit-mysql-0.log


No all-machines.log

Although I do have another local provider running as another user with a
different rsyslog conf (from an older version).  I have a feeling it may
be sucking up the events.  I'll get around to checking shortly.

Tim