On 19 March 2010 21:30, Graham Dumpleton <[email protected]> wrote: > On 19 March 2010 18:01, michael geary <[email protected]> wrote: >> hallelujah! Progress. I was hoping you'd respond to me, Graham. Please see >> my responses below: >> >>> Take out: >>> >>> import socket >>> >>> Do you still get an error? >> >> no. that gives me Hello World! >> >>> >>> What version of mod_wsgi are you using? >> >> 3.1 >> >>> >>> Is this with embedded mode or daemon mode? >> >> embedded, i believe. >> >>> >>> Is this within a VirtualHost? If yes, are you checking main Apache >>> error log as well as that of VirtualHost? >> >> this was the useful bit. For some reason, on this server, my tracebacks are >> in the main log. WHEW! > > They shouldn't be though. > > If using embedded mode and you were to print messages direct to > sys.stderr they would go to main error log instead of VirtualHost, but > the tracebacks logged by mod_wsgi itself along with that lead in error > message should go to the VirtualHost error log. > > FWIW, if you print to sys.stderr under daemon mode and that daemon > process is defined within context of a VirtualHost where that > VirtualHost has CustomLog, then in that case output will go to > VirtualHost. So, daemon mode sys.stderr can be a bit different to > embedded mode. Anyway, this isn't relevant as traceback that mod_wsgi > produces for failed import doesn't go via sys.stderr and so it should > end up same place as lead in message. > >>> Post the configuration you are using in Apache to configure mod_wsgi >>> to run script. >> >> i'm not going to do this because i think you've hit on the issue and it's >> not this... >> >>> >>> Are you loading mod_python in the same Apache instance? >> >> no. >> >> anyway, now that i can actually debug, i see that my sys.path isn't correct. >> Thank you, thank you. I'm going to plow ahead and i'll chirp again if i get >> stuck. > > What were you doing to your sys.path to cause import of the socket > module to fail? > > You aren't trying to point at a Python installation different to what > mod_wsgi was compiled against are you, you shouldn't do that by > fiddling with sys.path. > > I still want to see your configuration. I also want to see what > CustomLog is set to in main Apache error log and what it is set to in > VirtualHost, plus any other configuration related to debugging.
Whoops, mean ErrorLog directives, not CustomLog. Graham > I have seen a couple of comments on Django irc logs about seeing the > 'exception occurred processing' but no traceback before, but because > the people have never actually come here and asked about it, I have > absolutely no information about it. Thus would appreciate it that you > don't just wander off. Give me the configuration and I will then give > you some tests scripts to run and have you describe the result. This > will help me work out what causes this issue. > > Graham > -- You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en.
