Bug #1828

Can't Access Commons

Added by Sarah Morgano about 1 year ago. Updated about 1 year ago.

Status:ResolvedStart date:04/15/2012
Priority:NormalDue date:
Assignee:André Pitanga% Done:

0%

Category:Server
Target version:Not tracked
Severity:

Description

Hi all,

Is anyone else experiencing problems loading the Commons? I keep timing out.

Thanks,
Sarah

History

#1 Updated by André Pitanga about 1 year ago

Working on it... issue is real.

#2 Updated by Sarah Morgano about 1 year ago

Thanks, André and all the best.

#3 Updated by André Pitanga about 1 year ago

I flipped to the secondary site while I investigate but ...it doesn't seem to be responding...

#4 Updated by André Pitanga about 1 year ago

Ok, I'm not sure why the secondary site isn't responding this time, when it always did during testing. I guess this is how these things go ; )

All joking aside, I'll investigate this. Meanwhile I rebooted the primary server and everything came back up clean, so we should be good to go after 5 minutes when the DNS record flips back.

#5 Updated by Matt Gold about 1 year ago

  • Category set to Server
  • Status changed from New to Assigned
  • Assignee set to André Pitanga
  • Target version set to Not tracked

Thanks for your work on this, André and thanks for catching this, Sarah. André, maybe we should set up a separate ticket to troubleshoot the secondary server? Glad we're finding this problem now . . . .

#6 Updated by André Pitanga about 1 year ago

  • Status changed from Assigned to Resolved

Matt Gold wrote:

Thanks for your work on this, André and thanks for catching this, Sarah.

You're welcome, Matt.

André, maybe we should set up a separate ticket to troubleshoot the secondary server? Glad we're finding this problem now . . . .

So, as soon as the service was restored and panic mode was off I went back over the steps I took and realized, to my simultaneous dismay and relief, that I had copy-and-pasted the wrong IP for the secondary site. Yes, the secondary site was responding as required the whole time.

I guess I'll just close this issue for now as resolved. I don't yet see the root cause for the crash but I'll follow thorugh on that as much as possible separately.

#7 Updated by Matt Gold about 1 year ago

Okay -- well, that's a relief, André. Thanks again for your quick action on this on a Sunday!!

Also available in: Atom PDF