> If the logging system you are using is trying to output to sys.stdout ... No, I am not logging to stderr or stdout
> If not using sys.stdout but a file of your own as output for logging, > also be aware that you can't use relative path names for files as when > using Apache there isn't really a guarantee about what the working > directory of your application will be. I am also using absolute paths. I was initially logging using the Syslog Handler, however when I switched over to mod_wsgi this did not work. How I performed this, was using the standard pylons config, which uses the python config for logging. I created a syslog handler with its respective formatter and made it the default output for the root logger.When this didn't work in mod_wsgi I thought it mght be specific to syslog to I attempted t use a FileHandler. Which ended up having the same effect, where it works in standalone mode and not under mod_wsgi. After trying these two versions and failed I wanted to see if I can acheive any logging using the documented wsgi.errors handlers, however not able to see any logging through my calls to log anywhere. All I see is the startup, any exceptions and shutdown in the apache error.log. I have not turned out stdout in mod_wsgi and is not willing to do so. I did some invistigating and realized, it is not loading my config specified in the .ini file. It works fine in standalone mode, but it seems to ignore the logging part under mod_wsgi. Any ideas how the logging can be enabled in pylons under mod_wsgi. Thanks, Hatem --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
