[Bug 1360400] Re: Invalid maas.log permission caused django to crash

[Andres Rodriguez]

Julian,

I did have maas-django.log. The old owners of the maas.log there were
maas:maas but the new ones (after upgrade) syslog:syslog.

I Installed 1.6.0 and upgraded to 1.7.0~beta1. This was reproduced more
than twice so i think we can reproduce to figure out what;s wrong.


On Mon, Aug 25, 2014 at 8:35 PM, Julian Edwards <1360400 at bugs.launchpad.net>
wrote:

> The permissions for maas.log should *not* be maas:maas.  There is a line
> in the packaging that does:
>
>         chown syslog:syslog /var/log/maas/maas.log
>
> which is correct, because the only process that writes maas.log is
> syslog.
>
> Questions:
>  * what were the old owners of the maas.log?
>  * did you have a maas-django.log?
>
> I suspect something went wrong with the upgrade and you didn't accept
> the required changes to the django config file in trunk, which redirects
> its log to maas-django.log.
>
> ** Changed in: maas (Ubuntu)
>        Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1360400
>
> Title:
>   Invalid maas.log permission caused django to crash
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1360400/+subscriptions
>


-- 
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1360400

Title:
  Invalid maas.log permission caused django to crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1360400/+subscriptions