RESOLVED: Intermittent service degradation for content upload and publishing service

Both content upload and publishing service are back to normal. Issue is resolved. No more update.

21-May-2013 0:45 PDT by Jianlan Song

Intermittent service degradation for content upload and publishing service

The DPS operations team noticed intermittent service degradation for content upload and publishing. Investigation is under way.

Next Update: 1 hour

20-May-2013 23:45 PDT by Kevin Cabral

Intermittent performance degradation for Content Distribution

UPDATE: 5/20 10am:  The repair process is continuing, however system response times returned to normal earlier this morning.  We’re continuing to monitor the situation and will update this page if we detect any further performance degradations.  Next update:  Tuesday, 10am PDT.

The DPS Ops team has detected an issue that is resulting in degraded performance from one of the storage subsystems used by the Distribution service.  Repairs are under way, but the service may experience periodically degraded performance until the work is complete.

19-May-2013 22:12 PDT by dps-admin

Adobe Content Viewer v26 for Amazon

The Adobe Content Viewer v26 for Amazon is approved and available in the Amazon marketplace.

7-May-2013 10:35 PDT by Neil Enns

Adobe Content Viewer v26 for iOS

The Adobe Content Viewer v26 for iOS is approved and will be available for download in the Apple App Store shortly.

6-May-2013 8:50 PDT by Neil Enns

Adobe Content Viewer v26 for Android

The Adobe Content Viewer v26 for Android is approved and available in the Google Play marketplace.

3-May-2013 8:20 PDT by Neil Enns

Update available for v26 App Builder

Last night we pushed a server-side update for App Builder to address an issue building the Adobe Content Viewer with enterprise mobile provisioning files. There is no client update for this fix. To take advantage of the update simply re-build the Adobe Content Viewer using v26 of App Builder.

3-May-2013 7:47 PDT by Neil Enns

Stuck or invisible publishing requests

Update: 05-03-2013 @ 10:13 pm PDT

Deployment complete.  You should be able to see all jobs in your publishing requests queue.  We have added logging to help us further isolate the root cause of the stuck jobs in so that we can fix it.  This only seems to happen during deployments and no jobs got stuck during this one.

Update: 05-03-2013 @ 12:14 pm PDT

Deployment scheduled for 9-11 pm PDT tonight.  There is no planned downtime.

Update: 05-02-2013 @ 5:40 pm PDT

The DPS operations team cancelled all stuck jobs.  Users should be able to publish now.

ETA for the fix deployment is after noon on 05/03/2013.  Specific time TBD

 

We have observed that a small number of publishing jobs are stuck in the publishing queue.  A user may see that there are no progress updates and that they are unable to cancel the job.  Other users notice that they can’t see the job in the Publish Requests view.

The development is testing a fix that will make them visible in Publish requests again.  Additional investigation into the root cause and a way to avoid such problems in the future is on-going.

We are working with our support teams to “unstick” jobs using operational procedures this afternoon.

Next update: When we have a deployment schedule for the fix noted above.

2-May-2013 14:15 PDT by Michelle Dalton

RESOLVED: Failures updating folios where articles were deleted

Update: 05-03-2013 @ 10:16 pm PDT

Deployment complete.  This issue is fully resolved.

Update: 05-03-2013 @ 12:19 pm PDT

Deployment scheduled for 9-11 pm PDT tonight.  There is no planned downtime.

Update: 05-02-2013 @ 5:43 pm PDT

ETA for the fix deployment is after noon on 05/03/2013.  Specific time is still TBD.

 

During the R26 deployment we discover a newly introduced bug that prevents users from updating a published folio after deleting articles.  You may temporarily work around this problem by unpublishing the folio and republishing.

The development team has isolated the problem and is testing a fix now.  We are currently considering a no downtime deployment tomorrow to resolve this issue.

Next update: When we have a deployment time proposal.

2-May-2013 14:06 PDT by Michelle Dalton

← Older posts