Richard Harding wrote: > I'm still working on test deploying a tg app using supervisor 2. I've > gone through the docs and the great blog post here: > http://paddyland.serveblog.net/article/13 > > *snip* > Ok, here's what happened. My prod.cfg is setup to create a log file with a path of server.log. When I tested the start command su'd in as the www-data user I was in my project's directory (/home/rharding/src/tg=avw) where it had permissions to create the server.log file.
When I run it from supervisor the current working directory is set to / where www-data does not have write permissions (which is why running the application as the root user did work). By hard coding in the path for the log file as /home/rharding/src/tg-avw/server.log it now runs properly in supervisord. My big question is how in the world could we have gotten the error that turbogears was reporting back to supervisor for display. The big trouble with this problem was that I couldn't get at the error message and just got these signal dying messages. The next step is to see if I can tell each application in supervisord to open/start in a specific working directory so that I don't have to hard code paths in prod.cfg. Rick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
