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" <[email protected]> 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.
