On 22 May 2017 at 21:22, Duran, Randy G randy.g.duran@intel.com wrote:
I currently have an issue with starting lava-publisher. Whenever I run python manage.py lava-publisher I get output log:
That's the wrong command in the first place.
/etc/init.d/lava-publisher runs lava-server manage lava-publisher
so use: sudo service lava-publisher restart
That makes a massive difference. lava-publisher is not a trivial python script, it needs the django settings and the correct database.
Called locally with just manage.py, it will be using the development database which is empty (deliberately as that is how the unit tests run).
2017-05-22 20:10:28,061 INFO publisher Dropping priviledges
2017-05-22 20:10:28,061 ERROR publisher Unable to lookup the user or the group
2017-05-22 20:10:28,062 ERROR publisher Unable to drop priviledges
Only when testing the jinja2 templates are any calls made without using lava-server manage (or ./lava_server/manage.py for local unit tests using the empty development database).
I followed same steps to install from same repository on both machines. I somehow think this has to do with user or group not stored in database but I am not sure.
If started with python, it has no access to the production database.