Your message dated Sun, 31 Jul 2016 09:24:20 +1000 with message-id <[email protected]> and subject line celeryd: Initscript doesn't start daemon has caused the Debian Bug report #824786, regarding celeryd: Initscript doesn't start daemon to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 824786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824786 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: celeryd Severity: important Dear Maintainer, Default celeryd package ships with the (upstream) SysV initscript and creates a system user named celery. By default this user has /bin/false as a shell. So if you set correct variables in /etc/default/celery and start the daemon, celery never starts. This is the relevant function from the initscript: _chuid () { su "$CELERYD_USER" -c "$CELERYD_MULTI $*" } Simply changing this to: su "$CELERYD_USER" --shell=/bin/sh -c "$CELERYD_MULTI $*" works. I don't know if this is the best way to fix this, though. I'm marking this important because the package celeryd only provides the initscript. Running the worker proccess by hand of course works.
--- End Message ---
--- Begin Message ---Version: 3.1.23-4 This was fixed in May, but the bug was not closed correctly. celery (3.1.23-4) unstable; urgency=medium * Update standards version to 3.9.8 * Fix su invocation. Close: #824786. -- Brian May <[email protected]> Wed, 25 May 2016 18:09:45 +1000 Regards -- Brian May <[email protected]>
--- End Message ---
