[bksvol-discuss] Re: Uopdate on last week's Bookshare site problems
- From: Scott Rains <scottr@xxxxxxxxxxxx>
- To: "bksvol-discuss@xxxxxxxxxxxxx" <bksvol-discuss@xxxxxxxxxxxxx>
- Date: Tue, 21 Jun 2011 13:36:20 -0700
Hi Jen,
The best first step is often to ask on this list if others are having the same
problem. If it seems like a pattern send me an email with something in the
subject line alerting me to "Problems Uploading" or similar. I can monitor and
catch increasing higher levels of engineer''s attention.
Our experience is that most often there are short disruption based on spurts of
heavy usage. In those cases engineering can do nothing and just trying later
works.
Scott
________________________________________
From: bksvol-discuss-bounce@xxxxxxxxxxxxx [bksvol-discuss-bounce@xxxxxxxxxxxxx]
On Behalf Of Jennifer Aberdeen [freespirit328@xxxxxxxxx]
Sent: Monday, June 20, 2011 4:04 PM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Re: Uopdate on last week's Bookshare site problems
Hi, does this have anything to do with my not being able to upload a scan?
I tried twice to upload a scan I just finished. It's in rich text format, but
it won't upload.
Should I report it?
Thanks,
Jen
___________________________________________________________________________________________________
Shop my store for the latest and greatest in beauty and wellness products!
www.youravon.com/jaberdeen<http://www.youravon.com/jaberdeen>
Jennifer Aberdeen, AVON Independent Sales Representative
freespirit328@xxxxxxxxx<mailto:freespirit328@xxxxxxxxx>
401-644-5607
----- Original Message -----
From: Scott Rains<mailto:scottr@xxxxxxxxxxxx>
To: bksvol-discuss@xxxxxxxxxxxxx<mailto:bksvol-discuss@xxxxxxxxxxxxx>
Sent: Monday, June 20, 2011 6:00 PM
Subject: [bksvol-discuss] Uopdate on last week's Bookshare site problems
Volunteers,
This explanation just in from Engineering
Scott
Last week, we struggled to diagnose a problem whereby Bookshare would become
unstable and then crash a few hours later.
It turns out that a bug was recently introduced in the code that integrates
Bookshare and the content management system (CMS). The issue was not found
during our standard testing phase because we do not stress test (e.g., simulate
heavy traffic) the parts of the system that integrate with the CMS.
Typically, we'd push out a quick fix but this problem is a bit more complex.
Upon diagnosis, our best option was to shutdown the CMS tool and let Bookshare
simply rely on it's internal cache. Early next week, we will push out the 3.4.2
release, including a fix to this problem. At that time the CMS tool will come
back online.
Note: The homepage is missing the most recently published content (e.g., about
Read2Go) and we will try to have that updated by tomorrow or Wed.
The engineering team will make sure that Operations and Marketing are kept
informed as we move to resolve this issue.
Other related posts:
