2010/10/18 kevin <[email protected]>: > On Sun, Oct 17, 2010 at 6:16 PM, Anand Chitipothu <[email protected]> > wrote: >> >> 2010/10/17 kevin <[email protected]>: >> > i have one nginx in front of two gunicorns that are running in two >> > different >> > machines. >> > now if there is an error in the app it gets printed in the same machine >> > as >> > gunicorn is running. >> > earlier i had all errors coming to nginx error log with fastcgi. >> > how to get the same behavior with gunicorn. >> > >> > this is how i run gunicorn >> > /usr/bin/python /usr/bin/gunicorn --bind 0.0.0.0:8550 --pid /tmp/app_pid >> > --workers 5 code:subdomain_app_wsgi >> >> The nginx server is acting as a proxy for your gunicorn server, >> forwarding the HTTP requests. So nginx won't be able to access the >> error logs of gunicorn. > > what is the recommended way for handling errors in such a case? is it > possible to email the errors ?
Redirect the log to a file. /usr/bin/python /usr/bin/gunicorn --bind 0.0.0.0:8550 --pid /tmp/app_pid --workers 5 code:subdomain_app_wsgi 2>&1 > /tmp/gunicorn.log Now you have 2 log files, one on each machine. Isn't that good enough? -- You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en.
