Christoph Zwerschke schrieb: > I am using supervisor 2.1 with the following config on a Linux server: > > user=<username> > command=env USER=<username> HOME=/home/<username> start-<appname>
The last line is the crucial point, I think. In more recent versions, supervisord doesn't seem to set these env vars automaticlly anymore. I remember that I had to add a similar line to my supervisord.conf when I deployed a new app recently, and it took me quite a while to figure out why it wouldn't work without it. So, a good tip for debugging is always to replace your actual app with a small shell script, that just writes some environment info to a file and then run supervisord and see what's written to this file. For example: #!/bin/bash CONFFILE=/path/to/conffile DEBUGLOGFILE=/path/to/debug.log # Write some debugging info to examine some permission issues EUID=$(id -u) EGID=$(id -g) RUID=$(id -r -u) RGID=$(id -r -g) USR=$(id -n -u) GRP=$(id -n -g) GRPS=$(id -n -G) ACCESS_CONF=$(test -r $CONFFILE && echo yes || echo no) echo "Date: $(date)" >>"$DEBUGLOGFILE" echo "Running as user: $USR ($EUID, real: $RUID)" >>"$DEBUGLOGFILE" echo "Running with group: $GRP ($EGID, real: $RGID)" >>"$DEBUGLOGFILE" echo "Groups: $GRPS" >>"$DEBUGLOGFILE" >>"$DEBUGLOGFILE" echo "Umask: $(umask)" >>"$DEBUGLOGFILE" echo "Can read configuration: $ACCESS_CONF" >>"$DEBUGLOGFILE" echo >>"$DEBUGLOGFILE" # end debugging logging Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
