ok, I'll rephrase, a bit harshly... why are you insisting on passing something completely undocumented to wsgiscriptalias ? If there's a good reason, you should be able to sort it out, or at least explain clearly the reason behind it. Sadly, "it works for the first request" isn't really "it works". Web2py is dropping apache "primary" support because of tons of those nonsensical setups weirdness. You insisting on a totally different config from the mainstream isn't helping. Without a solid reason, you'll probably end revisiting your config by yourself, just because you're the only one willing to do so. Those errors are easy to research on google and are not tied to web2py setups: it seems a general issue with apache. If you don't want "to run uwsgi and be happy" as suggested, at least give the people trying to help the benefit of the doubt, then maybe, but just maybe, bash them around insisting on a better config EXPLAINING why it's better (and working): they'll happily take your input and spread your wisdom thoughout all the plagued community restricted to run apache. For the time being, please consider the above suggestion PLUS restricting every single entry-point to your web2py sites with a solid copy of the same configuration AND a WSGIDaemonProcess with a different name for every entry. That seems to seal the deal for any apache+wsgi installation.
-- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
