1043333 - celery management commands are not using the right log file

Status: RESOLVED FIXED

(Tree Management :: Treeherder, defect, P2)

Description

[Ed Morley [:emorley]]

Migrated from:
https://github.com/mozilla/treeherder-service/issues/162

uberj commented on 4 Jun:

{
Many celery commands (being spawned by supervisord via the ./bin/* scripts) don't seem to be actually respecting their --log-file parameters.

To reproduce:

(venv)vagrant@precise32:~/treeherder-service$ pwd
/home/vagrant/treeherder-service
(venv)vagrant@precise32:~/treeherder-service$ rm -f treeherder.log
(venv)vagrant@precise32:~/treeherder-service$ ./bin/run_celerybeat 
^C
(venv)vagrant@precise32:~/treeherder-service$ ls treeherder.log 
treeherder.log

All the celery jobs seem to be creating this local treeherder.log file (they should be using whatevery $LOGFILE is in their ./bin/run_celery* script)

I think @maurodoglio suggested that https://github.com/mozilla/treeherder-service/blob/master/treeherder/settings/base.py#L159 might be part of the issue.
}