Re: Plyons WSGI on Apache2.2
Previously Graham Dumpleton wrote: Read: http://code.google.com/p/modwsgi/wiki/ConfigurationIssues Not sure why you want run a single thread. From memory would only want to do that if trying to attach gdb to daemon process and debug at C code level. I tried to run with a single thread for a bit since egg:Paste#evalerror complained it doesnot work in a multi-thread environment, but it turns out it still complains even if you limit mod_wsgi to one thread. Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: Plyons WSGI on Apache2.2
On Jun 17, 6:55 pm, Wichert Akkerman [EMAIL PROTECTED] wrote: Previously Graham Dumpleton wrote: Read: http://code.google.com/p/modwsgi/wiki/ConfigurationIssues Not sure why you want run a single thread. From memory would only want to do that if trying to attach gdb to daemon process and debug at C code level. I tried to run with a single thread for a bit since egg:Paste#evalerror complained it doesnot work in a multi-thread environment, but it turns out it still complains even if you limit mod_wsgi to one thread. Is Paste#evalerror the same as EvalException or something different? Whatever it is, presuming it sees: wsgi.multithread: False in WSGI environment it should be satisfied that it is single threaded. If you can confirm what Python class #evalerror maps to, will have a quick look at what its requirements are. Graham --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: Plyons WSGI on Apache2.2
Previously Graham Dumpleton wrote: Is Paste#evalerror the same as EvalException or something different? It's an entry point which maps to paste.evalexception.middleware.make_eval_exception which indeed sets up EvalException. Looking at the code I must have misremembered: it does not support a multi-process environment, but does support multi-threading. Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: Plyons WSGI on Apache2.2
On Jun 17, 7:24 pm, Wichert Akkerman [EMAIL PROTECTED] wrote: Previously Graham Dumpleton wrote: Is Paste#evalerror the same as EvalException or something different? It's an entry point which maps to paste.evalexception.middleware.make_eval_exception which indeed sets up EvalException. Looking at the code I must have misremembered: it does not support a multi-process environment, but does support multi-threading. Which means that: WSGIDaemonProcess debug alone, ie., allowing default single process to be created, should be sufficient. Note, don't use: WSGIDaemonProcess processes=1 The use of 'processes' option with any number makes mod_wsgi think you have a multiprocess configuration and sets wsgi.multiprocess to be True as a default. Having thus subtle difference was probably not good in hindsight and should have allowed flagging of single process as being part of multi process configuration in a different way. FWIW, you would use 'processes=1' where want only one process on a specific Apache instance, but are loading balancing overall across multiple Apache installations. Need some way in that case to override wsgi.multiprocess so application knows that although only one process in this Apache instance, that may also be running elsewhere. Graham --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: Plyons WSGI on Apache2.2
Read: http://code.google.com/p/modwsgi/wiki/ConfigurationIssues Not sure why you want run a single thread. From memory would only want to do that if trying to attach gdb to daemon process and debug at C code level. Graham On Jun 16, 3:52 am, Chris [EMAIL PROTECTED] wrote: I've gotten Pylons to successfully run via WSGI on Apache2.2, but only after disabling debugging. Followinghttp://code.google.com/p/modwsgi/wiki/DebuggingTechniques, I've tried to runmod_wsgiin a single thread daemon by appending the lines: WSGIDaemonProcess debug threads=1 WSGIProcessGroup debug to my httpd.conf. However, this completely breaks WSGI, generating the error: [Sun Jun 15 13:44:09 2008] [error] [client 127.0.0.1] (13)Permission denied:mod_wsgi(pid=11972): Unable to connect to WSGI daemon process 'debug' on '/etc/httpd/logs/wsgi.9910.15.1.sock' after multiple attempts. Since there are other applications running through Apache, I can't change the StartServers/ServerLimit params. Is there any other way to enable debugging without lobotomizing Apache? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
