On Wed, 2008-23-04 at 15:37 -0700, mbertoldi wrote: > Just another check, is the ipn method using **kwargs?
Yes, and thanks for the help. I've narrowed it down now to something to do with the user running the process. To my chagrin, my supervisord is all mucked up and is not switching users as I thought I had instructed it to do. So in production mode the site is being run as root because supervisord runs as root ( it's supposed to, but it's not switching users before issuing the command. ) Starting the site backgrounded in production mode from the site account user works. Starting it with supervisord or manually from sudo makes the problem happen. But to me, this is really weird. Root should have access to everything, correct? And everything else on the site ( prior to ipn addition ) has been running fine, started as root ( egads! ) by my misconfigured supervisord. So does anyone know something that would prevent a tg app started as root from receiving an incoming post request? Is there any reason mod_proxy would do something strange in this circumstance? I guess I'd better learn supervisord better today... Thanks iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
