Monday, November 23, 2015

[Fedora Infrastructure] #4987: Magazine - 503 Varnish errors when using admin portal

#4987: Magazine - 503 Varnish errors when using admin portal
--------------------------+------------------------
Reporter: jflory7 | Owner: webmaster
Type: bug | Status: new
Priority: major | Milestone: asap
Component: Web Content | Version: Production
Severity: Trivial | Keywords: Magazine
Blocked By: | Blocking:
Sensitive: 0 |
--------------------------+------------------------
= Bug Description =
When inside of the WordPress admin panel for the Fedora Magazine, I often
get 503 errors and have trouble staying persistently connected / logged
in. This is especially true when clearing out the comment queue, but I've
run into the issue now where I cannot edit articles without timing in a
few seconds after opening the article.

This doesn't seem to affect the front end, but the backend is difficult
for me to use right now. I am unsure of whether this is widespread or
localized to me.

= Bug Analysis =
I am unsure to the cause, but I have two cases where I received 503 errors
from the Varnish cache server.

'''Cleaning out comments''':

- 503 Backend fetch failed
- Guru Mediation, XID: 27722808

'''Drafting an article''':

- 503 Backend fetch failed
- Guru Mediation, XID: 27367471

Reloading the page usually gets it to load back after two or three
attempts, but when clearing comments, the next time I try to clear more, I
receive this error, and when writing an article, I'll be notified within a
few seconds that my connection was lost and my changes are being saved to
my browser. Refreshing throws the error.

= Fix Recommendation =
Unsure of possible fix.

--
Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/4987>
Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure>
Fedora Infrastructure Project for Bugs, feature requests and access to our source code.
--
websites mailing list
websites@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

No comments:

Post a Comment