Don't forget to restart lava-server-gunicorn service after any change to settings.conf.


Rgds

Le jeu. 4 avr. 2019 à 11:09, Steve McIntyre <steve.mcintyre@linaro.org> a écrit :
Hi Frank,

On Thu, Apr 04, 2019 at 08:30:18AM +0000, Frank, Matthias wrote:
>
>I upgrade my lava-server package (from backports) to 2019-03 on debian stretch.
>After this is get an django error:

>
>ERROR 2019-04-04 08:24:16,694 exception Invalid HTTP_HOST header: '
><my-host-name>'. You may need to add '<my-host-name>' to ALLOWED_HOSTS.
>
>The browser reports a Bad Request (400)
>
>So I added <my-host-name> and “*” to ALLOWED_HOSTS in /usr/lib/python3/
>dist-packages/lava_scheduler_app/settings.py and /usr/lib/python3/dist-packages
>/django/conf/global_settings.py but the error is still present. Are these the
>wrong file or what could be the problem?

This change in Django has bitten lots of people, yes. :-(

The correct place is in /etc/lava-server/settings.conf . If things
still don't work, check that your settings.conf is valid using

  $ sudo lava-server manage check --deploy

It's all too easy to make changes that might break that file and cause
it to be ignored.

--
Steve McIntyre                                steve.mcintyre@linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs


_______________________________________________
Lava-users mailing list
Lava-users@lists.lavasoftware.org
https://lists.lavasoftware.org/mailman/listinfo/lava-users


--
Rémi Duraffort
LAVA Team, Linaro