I am also seeing this behavior with a MAAS environment. After working around Bug #1243861, the juju-db service fails to start with the same symptom as seen in /var/log/upstart/juju-db.log
error command line: unknown option sslOnNormalPorts
Since this bug is out for code review, should I report a new bug?
Here are the specifics about the versions in use:
dev@maas-master:/var/lib/maas/ephemeral/precise/ephemeral/amd64/20131010$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy dev@maas-master:/var/lib/maas/ephemeral/precise/ephemeral/amd64/20131010$ cat info release=precise label=release serial=20131010 arch=amd64 name=maas-precise-12.04-amd64-20131010 dev@maas-master:/var/lib/maas/ephemeral/precise/ephemeral/amd64/20131010$ juju version 1.16.0-saucy-amd64
I am also seeing this behavior with a MAAS environment. After working around Bug #1243861, the juju-db service fails to start with the same symptom as seen in /var/log/ upstart/ juju-db. log
error command line: unknown option sslOnNormalPorts
Since this bug is out for code review, should I report a new bug?
Here are the specifics about the versions in use:
dev@maas- master: /var/lib/ maas/ephemeral/ precise/ ephemeral/ amd64/20131010$ lsb_release -a master: /var/lib/ maas/ephemeral/ precise/ ephemeral/ amd64/20131010$ cat info precise- 12.04-amd64- 20131010 master: /var/lib/ maas/ephemeral/ precise/ ephemeral/ amd64/20131010$ juju version
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 13.10
Release: 13.10
Codename: saucy
dev@maas-
release=precise
label=release
serial=20131010
arch=amd64
name=maas-
dev@maas-
1.16.0-saucy-amd64