No debug-log with MAAS, 14.04 and juju-core 1.17.5

rsyslog config is in place:

$ModLoad imfile

$InputFilePersistStateInterval 50
$InputFilePollInterval 5
$InputFileName /var/log/juju/machine-0.log
$InputFileTag juju-machine-0:
$InputFileStateFile machine-0
$InputRunFileMonitor

$ModLoad imtcp
$DefaultNetstreamDriver gtls
$DefaultNetstreamDriverCAFile /var/log/juju/ca-cert.pem
$DefaultNetstreamDriverCertFile /var/log/juju/rsyslog-cert.pem
$DefaultNetstreamDriverKeyFile /var/log/juju/rsyslog-key.pem
$InputTCPServerStreamDriverAuthMode anon
$InputTCPServerStreamDriverMode 1 # run driver in TLS-only mode
$InputTCPServerRun 6514

# Messages received from remote rsyslog machines have messages prefixed with a space,
# so add one in for local messages too if needed.
$template JujuLogFormat,"%syslogtag:6:$%%msg:::sp-if-no-1st-sp%%msg:::drop-last-lf%\n"

$FileCreateMode 0644
:syslogtag, startswith, "juju-" /var/log/juju/all-machines.log;JujuLogFormat
& ~
$FileCreateMode 0640

James, if you still have the environment, can you please check if the bootstrap machine has got rsyslog-gnutls installed? And also list the output of ls -l /var/log/juju?

Was the node you bootstrapped also running 14.04? I've tried with the 1.17.5 client and a 14.04 MAAS provider, bootstrapping a precise node and it generated the all-machines.log for me.

The bootstrap node was running 14.04; I just tested this with the OpenStack provider as well, with a 14.04 bootstrap node, and I see exactly the same issue.

ubuntu@james-page-bastion:~/openstack-charm-testing⟫ apt-cache policy rsyslog-gnutls
rsyslog-gnutls:
  Installed: (none)
  Candidate: 7.4.4-1ubuntu2
  Version table:
     7.4.4-1ubuntu2 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages

ubuntu@juju-jamespage-machine-0:~$ ls -l /var/log/juju/
total 4492
-rw------- 1 syslog syslog 879 Mar 21 12:19 ca-cert.pem
-rw-r--r-- 1 root root 4583341 Mar 21 12:26 machine-0.log
-rw------- 1 syslog syslog 830 Mar 21 12:19 rsyslog-cert.pem
-rw------- 1 syslog syslog 891 Mar 21 12:19 rsyslog-key.pem

ubuntu@juju-jamespage-machine-0:~$ apt-cache policy rsyslog-gnutls
rsyslog-gnutls:
  Installed: 7.4.4-1ubuntu2
  Candidate: 7.4.4-1ubuntu2
  Version table:
 *** 7.4.4-1ubuntu2 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
        100 /var/lib/dpkg/status

I just noticed that /var/log/juju is created owned by root. The local provider chowns the directory to syslog:adm, but really this should be done for all providers. I've moved the chown from local provider into the common cloud-init code in https://codereview.appspot.com/79310043/, which may fix this bug.

I've reproduced this trivially on azure, and changing ownership makes no difference. I'll keep looking.

BTW if anyone else wants to reproduce, just set, in environments.yaml:
    image-stream: daily
    default-series: trusty

I hadn't removed the spool file. If I remove it (/var/spool/rsyslog/machine-0) and restart rsyslog, I can get it to reliably write the file when the directory is owned by syslog:adm, and not when owned by root:root.

Confirmed that all-machines.log is now created when bootstrapping off trunk.

This bug was fixed in the package juju-core - 1.17.7-0ubuntu1

---------------
juju-core (1.17.7-0ubuntu1) trusty; urgency=medium

  * New upstream point release, including fixes for:
    - no debug log with all providers on Ubuntu 14.04 (LP: #1294776).
  * d/control: Add cpu-checker dependency to juju-local (LP: #1297077).
 -- James Page <email address hidden> Fri, 28 Mar 2014 08:58:42 +0000