We're using Apache 2.2.13 prefork MPM with mod_wsgi 3.0RC4 in daemon mode.
We thought file cache was the issue as well, so switched to memcached via python-memcached with default settings, however this did not resolve the issue. It's coming up on startup or on navigating to admin. Are there any other suggestions? I'd hate to move the server over to using Lighttpd or Nginx only to face the same problem there, but if that's the only suggestion, then i guess i'll investigate as this problem is a showstopper. or is there a plan to make this section of the code more resilient to cache problems? Regards, Rui On Sep 16, 5:43 pm, Bruce Kroeze <[email protected]> wrote: > On Wed, Sep 16, 2009 at 6:50 AM, ruidc <[email protected]> wrote: > > > We're also getting this same problem intermittently, with both > > filecache and memcache. We're using postgres as the database. > > > Corey, did you ever get to the bottom of this? > > Chris, can you offer any other suggestions? > > For some reason, when "things are messed up" in your store, the first > symptom seems to be the dreaded "SettingNotSet" disorder. > > In my experience with production sites, the answer is most likely one of > these: > - You are using mod_python. Stop. Stop now. mod_python stinks. Use > mod_wsgi with Apache or preferably move to using Lighttpd or Nginx. I > have personally *never* seen a solid, stable, mod_python production > instance in the last two years. > > - Your cache is flaky. If you are using filecache, there could be > permissions issues. > > -- > Bruce Kroezehttp://www.ecomsmith.com > It's time to hammer your site into shape. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
