I'm using 0.9.1, and the problem didn't seem to be logged very well. I don't have a CACHE_PREFIX in my settings.py, and when I restart the server I get this:
Sat, 28 Apr 2012 10:03:33 root INFO Satchmo Started Sat, 28 Apr 2012 10:03:33 keyedcache WARNING No CACHE_PREFIX found in settings, using SITE_ID. Please update your settings to add a CACHE_PREFIX Perhaps a start would be for Satchmo to throw an error, log similarly to the above, or refuse to start altogether if the cache is inaccessible. Thanks! On Saturday, April 28, 2012 11:25:49 AM UTC-4, Chris Moffitt wrote: > > Yes, I've heard of it. I'm open to ideas on how to handle it more > gracefully. It's part of trying not to permanently store credit card > numbers, so we encrypt them in the cache. Obviously, if the cache goes > down, things get wonky. > > I'm open to other ideas that would be more robust but would be secure. > > -Chris > > On Sat, Apr 28, 2012 at 10:21 AM, Mike Hostetler <> wrote: > >> I've seen the same thing and even wrote about it on the list (though I >> didn't know Memcache had problems at the time). For payments to not process >> because cache is down is very weird for me to get a handle on, too. >> >> On Apr 28, 2012 10:17 AM, "Kevin Harvey" <> wrote: >> > >> > Hello all, I just finished debugging an error that stopped >> Authorize.net transactions through my Satchmo store. At the confirmation >> screen, after trying to submit the payment, the page refreshed and I got a >> 'Credit card number is required' message. It turns out that memcached had >> stopped running on my server, and without a cache Satchmo won't talk to >> Authorize.net. >> > >> > That's a pretty serious dependency that I never thought to monitor >> before. Has anyone else ever seen that? I probably need to start monitoring >> that memcached process directly, but what else can I do to avoid this >> situation in the future? >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups "Satchmo users" group. >> > To view this discussion on the web visit >> https://groups.google.com/d/msg/satchmo-users/-/WakEZt5AVKAJ. >> > 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. >> >> -- >> 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. >> > > -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To view this discussion on the web visit https://groups.google.com/d/msg/satchmo-users/-/plbAlqUSdbQJ. 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.
