maas-proxy fails to start on freshly installed MAAS
Bug #1382266 reported by
Christian Reis
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Andres Rodriguez | ||
maas (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
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/
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
lp:~maas-maintainers/maas/fix_lp1382266
- Christian Reis (community): Needs Information
- Blake Rouse (community): Approve
- Diff: 0 lines
Changed in maas: | |
status: | New → Invalid |
Changed in maas (Ubuntu): | |
status: | New → Confirmed |
Changed in maas (Ubuntu): | |
status: | Confirmed → Incomplete |
Changed in maas: | |
status: | Invalid → Incomplete |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas (Ubuntu): | |
status: | Confirmed → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Invalid |
Changed in maas: | |
status: | Invalid → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The fix might be as simple as ensuring the permissions are correct in the init script.