Hello Graham, NB: That's a work project and I'm on weekend now, so I'll only be able to try something practical on Monday morning CET.
On Friday, December 5, 2014 8:53:13 PM UTC+1, Graham Dumpleton wrote: Are you sure your application is actually running in daemon mode and not > embedded mode? > Pretty sure, that's something I've verified a long time ago. But of course a valid point, I'm going to recheck just to be 100% sure. > Are you using IP addresses in the VirtualHost directive line? > > There is a suspected issue with logging where logging doesn't come out in > some cases where an IP address was used in VirtualHost directive. > This might be (though I think it's a wildcard), I'll have to check when I'm at work again. > Also make sure you are looking in main Apache error log and not just the > virtual host error log. > This strikes me as the most obvious explanation -- I indeed haven't looked at the main error log, thinking that mod_wsgi is local to a virtual host so to speak (which is obviously wrong for third party modules like mod_wsgi). Again, I'll have to check, but I'm currently 80% certain, that this will explain the missing logs issue. It doesn't, however, explain why there are still encoding errors. > Finally, when you say you are about to upgrade, in testing you are > actually using 4.2.5 to validate behaviour? > I'm afraid I do not get exactly what you are asking (knowing your blog posts and documentation you seem to have something in mind so I want to give as precise an answer as it gets). I'll try to describe the setup: like I mentioned earlier, we are currently using mod_wsgi 3.3 on SuSE Linux Enterprise 11 and I wanted to upgrade to at least 3.4 to get the locale feature. However, since 4.2.5 packages of mod_wsgi for SLE11 are readily available from http://build.opensuse.org and I haven't found any obvious blockers and incompatibilites in the release notes, I've decided to try that first. I certainly could try 3.5 (3.4 + security fix, right?) first to be as close to production version as possible, but that would require building a proper package by myself, which I didn't see the reason to. The testing goes like this: we put up a properly installed test server instance with mod_wsgi 3.3 and a patched apache2's init.d script, verify that said encoding problem is nowhere to be seen, upgrade mod_wsgi to 4.2.5 and remove the init.d workaround, then verify that encoding problems are there again. The last step has been to add lang and locale options to WSGIDaemonProcess and check again -- problems should be gone then. This is where it failed, I'm still getting those encoding errors. I hope this answers your question at least a bit. Thank you for your help so far. Nikolai. > > Graham > > On 05/12/2014, at 11:06 PM, Nikolai Prokoschenko <[email protected] > <javascript:>> wrote: > > Hello, > > I'm running our Django application on mod_wsgi on a SLES11 SP3 > installation. SLES' apache2 doesn't have an envvars file and also resets > all environment variables before start so I used to patch its init.d script > to include LANG and LC_ALL in the main process. > > So far I'm using mod_wsgi 3.3 but I'm about to upgrade to 4.2.5, so I > figured I could throw that patch away and use lang= and locale= parameters > to WSGIDaemonProcess. I've added "lang=de_DE.UTF-8 locale=de_DE.UTF-8" to > the WSGIDaemonProcess line, however, it doesn't seem to work at all. > > What I know: > > 1. Options get accepted by mod_wsgi (no error on startup) > 2. Debug logging works (I'm getting mod_wsgi messages with debug level in > the apache error log if LogLevel is set to "debug") > 3. I do NOT get any logs about activated locale and lang settings (which > should be there in debug log level according to > https://github.com/GrahamDumpleton/mod_wsgi/blob/4.2.5/src/server/mod_wsgi.c#L8860 > ) > 4. Locale settings do NOT work (application crashes where files with UTF-8 > encoded filenames are accessed) > > I tried reading the mod_wsgi code, which doesn't seem to be broken, but I > still don't see how 1, 2 and 3 are possible simultaneously. Is there > something I might be missing? > > I'm thankful for any ideas. > > Nikolai. > > > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected] <javascript:> > . > Visit this group at http://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
