Hello, I'm having a slight problem with a small pylons based WSGI app I'm trying to get working on my server. It was working fine, with mod_wsgi (on Apache2, Debian Lenny) under embedded mode, and I didn't mind restarting as I would only load it onto my live server when I needed to do live testing. However, since lunchtime today when trying my latest revision checkout, it was caching the version from the previous day, even after a quick `/etc/init.d/apache2 restart` (which is definitely doing a full reload of apache, but to be sure have also tried a `force- reload`). I've since tried running it in daemon mode, following the exact steps from the mod_wsgi installation notes, and with Apache2's LogLevel set to "info" I can definitely see it is spawning separate processes for each request handle, but still working with old source. I can tell it's old source because entire controller action, along with mako templates, and even some static content, are missing. I have touched my wsgi app, tried changing it's location in fact, looked into file permissions, and user/group permissions, and I'm beginning to run low on options.
I'm hoping someone can give me some suggestions as to what might be causing this. Cheers, Wes. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
