Logs seem incomplete

[Gavin Panella]

While trying to diagnose problems in the Garage MAAS I kept getting 500 Internal Server Errors from MAAS and/or Apache, but nothing about the error was coming out in /var/log/maas/* or /var/log/apache/*.

[Julian Edwards (julian-edwards)]

Something has gone wrong with logs - using logger.info() is not producing anything anywhere.

[Raphaël Badin (rvb)]

The fact that a 500 Internal Server error does not generate a log is puzzling and a critical bug (although I suspect it's related to this particular setup because I've never seen this).

Now, the default log level is ERROR (as defined by contrib/maas_local_settings.py:LOGGING.handlers.log.level). So, by default, logger.info() doesn't produce anything.

[Julian Edwards (julian-edwards)]

On 08/10/13 17:01, Raphaël Badin wrote:
> The fact that a 500 Internal Server error does not generate a log is
> puzzling and a critical bug (although I suspect it's related to this
> particular setup because I've never seen this).
>
> Now, the default log level is ERROR (as defined by
> contrib/maas_local_settings.py:LOGGING.handlers.log.level). So, by
> default, logger.info() doesn't produce anything.
>

That seems a bit crack to me. We should be showing INFO.

[Julian Edwards (julian-edwards)]

More info - I changed the default log level in maas_local_settings to DEBUG, and it didn't make any DEBUG logs appear :(

[Raphaël Badin (rvb)]

I just got a 500 error and saw traceback, as expected, in/var/log/maas/maas.log.

I'm closing this until we can find the root cause, as it seems to be site-specific. Any new on that front Gavin?

[Raphaël Badin (rvb)]

@Julian: what you saw is bug 1241054.

[Gavin Panella (allenap)]

Yeah, I suspect this was environment specific. I'll leave this as Incomplete and let it expire; maybe someone else will observe the issue and want to comment.

[Launchpad Janitor (janitor)]

[Expired for MAAS because there has been no activity for 60 days.]