https://hacks.mozilla.org/ is down/returning a blank page

VERIFIED FIXED

Status

Infrastructure & Operations
WebOps: Community Platform
--
critical
VERIFIED FIXED
4 years ago
4 years ago

People

(Reporter: stephend, Assigned: jd)

Tracking

Details

(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/1095] , URL)

(Reporter)

Description

4 years ago
https://hacks.mozilla.org/ is down

It returns a 200 OK, but is just a white page; maybe due to https://rpm.newrelic.com/accounts/263620/applications/2207221/traced_errors/2085851766 ?

Updated

4 years ago
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/1095]
(Assignee)

Updated

4 years ago
Assignee: server-ops-webops → jcrowe
(Assignee)

Comment 1

4 years ago
It is back up for now, I have removed the memcache settings for now, I will investigate why this caused the issue.
(Assignee)

Comment 2

4 years ago
This is an issue that is not easy to fix. There is a problem when running multidomain Wordpress and another wordpress at the same time plus using the memcache plugin. The keys are unique between instances on a multidomain but somehow they are shared between that and the other install (this one is a single domain, but that is not relevant). I dug through the memcache caches for quite a while attempting to track down any keys that were not unique. It winds up that they are all unique (being prefixed correctly), so it must be a bug in the memcache plugin on key retrieval. There is already an outstanding bug on file with the plugin maintainer, but being as it has seen little traction recently I will not hold my breath.

None of this is all that relevant in reality. We are planing on migrating this blog to the new multidomain platform in short order. That platform has memcache, it was setting up that platform that eventually led to this issue. Anyhow, since this blog will be migrating soon (I will be filing a bug for that) I do not feel it necessary to spend a bunch of time working this issue. As such I am going to resolve this bug as is. The downside is that the blog may be a bit slower with memcache disabled. If this becomes an issue, let me know and I will prioritize migrating this blog above some others that are currently ahead of it on the list.

Regards
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Reporter)

Comment 3

4 years ago
(In reply to Jason Crowe [:jd] from comment #2)
> This is an issue that is not easy to fix. There is a problem when running
> multidomain Wordpress and another wordpress at the same time plus using the
> memcache plugin. The keys are unique between instances on a multidomain but
> somehow they are shared between that and the other install (this one is a
> single domain, but that is not relevant). I dug through the memcache caches
> for quite a while attempting to track down any keys that were not unique. It
> winds up that they are all unique (being prefixed correctly), so it must be
> a bug in the memcache plugin on key retrieval. There is already an
> outstanding bug on file with the plugin maintainer, but being as it has seen
> little traction recently I will not hold my breath.
> 
> None of this is all that relevant in reality. We are planing on migrating
> this blog to the new multidomain platform in short order. That platform has
> memcache, it was setting up that platform that eventually led to this issue.
> Anyhow, since this blog will be migrating soon (I will be filing a bug for
> that) I do not feel it necessary to spend a bunch of time working this
> issue. As such I am going to resolve this bug as is. The downside is that
> the blog may be a bit slower with memcache disabled. If this becomes an
> issue, let me know and I will prioritize migrating this blog above some
> others that are currently ahead of it on the list.
> 
> Regards

Thanks, Jason; do you have the bug # handy for "migrating this blog to the new multidomain platform in short order"?
(Assignee)

Comment 4

4 years ago
You bet, bug 1059013

I just filed it. I am working on another right now which has given me a bit of trouble due to some customizations. That one should be completed tomorrow.
(Reporter)

Comment 5

4 years ago
(In reply to Jason Crowe [:jd] from comment #4)
> You bet, bug 1059013
> 
> I just filed it. I am working on another right now which has given me a bit
> of trouble due to some customizations. That one should be completed tomorrow.

Thanks; verified fixed -- with the acknowledgement that bug 1059013 will redress comment 3.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.