maas-proxy fails to start on freshly installed MAAS

Bug #1382266 reported by Christian Reis on 2014-10-16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Andres Rodriguez
maas (Ubuntu)

Bug Description

I'm not even sure why it's being used, but maas-proxy doesn't run on my freshly installed MAAS;

Oct 17 00:57:33 ubuntu squid3: Cannot open '/var/log/maas/proxy/access.log' for writing.#012#011The parent directory must be writeable by the#012#011user 'proxy', which is the cache_effective_user#012#011set in squid.conf.

I had to chown -R proxy /var/log/maas/proxy and then start again.

The UI also gives me no indication the proxy server is not running, so if it's being supplied by default to the nodes (I didn't specify it) it should give feedback if it's failed to start.

Related branches

Christian Reis (kiko) wrote :

The fix might be as simple as ensuring the permissions are correct in the init script.

Changed in maas:
milestone: none → 1.7.0
importance: Undecided → Critical
assignee: nobody → Andres Rodriguez (andreserl)
Changed in maas:
status: New → Invalid
Changed in maas (Ubuntu):
status: New → Confirmed
Raphaël Badin (rvb) wrote :

Looks similar to bug 1377964, but for a different file.

Christian Reis (kiko) wrote :

I see the postinst does indeed include a chown as the fix for bug 1377964. So someone explain to me, how could the postinst not get run if the package is installed?

Andres Rodriguez (andreserl) wrote :

Hi Kiko,

If you can reproduce this, can you please attach:


Christian Reis (kiko) on 2014-10-27
Changed in maas (Ubuntu):
status: Confirmed → Incomplete
Changed in maas:
status: Invalid → Incomplete
Blake Rouse (blake-rouse) wrote :

I have this same issue.

Changed in maas:
status: Incomplete → Triaged
Changed in maas (Ubuntu):
status: Incomplete → Confirmed
Christian Reis (kiko) on 2014-10-28
Changed in maas:
status: Triaged → Fix Committed
Changed in maas (Ubuntu):
status: Confirmed → Fix Committed
Changed in maas:
status: Fix Committed → Invalid
Christian Reis (kiko) on 2014-10-30
Changed in maas:
status: Invalid → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 1.7.0+bzr3299-0ubuntu2

maas (1.7.0+bzr3299-0ubuntu2) vivid; urgency=medium

  * debian/maas-common.postinst: Ensure that the maas user gets its home
    directory created in /var/lib/maas. (LP: #1399016)
 -- Andres Rodriguez <email address hidden> Thu, 04 Dec 2014 12:24:18 -0500

Changed in maas (Ubuntu):
status: Fix Committed → Fix Released

Hello Christian, or anyone else affected,

Accepted maas into utopic-proposed. The package will build now and be available at in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at . Thank you in advance!

tags: added: verification-needed
Andres Rodriguez (andreserl) wrote :

This issue has been verified to work both on upgrade and fresh install, and has been QA'd. Marking verification-done.

tags: added: verification-done
removed: verification-needed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers