Closed Bug 646237 Opened 15 years ago Closed 15 years ago

People receiving Service Unavailable note when trying to use sign-up form

Categories

(Participation Infrastructure :: Phonebook, defect)

x86
macOS
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 646325

People

(Reporter: davidwboswell, Assigned: wbowden)

References

()

Details

Since the page at mozilla.org/phonebook went live I've had two people tell me they've received the following note when trying to sign-up through the Responsys form: "Service Unavailable The service is temporarily unavailable. Please try again later." One person who reported this said it worked for them on the second try. Is this related to Responsys or is this something with how the form is set up on this landing page?
(In reply to comment #0) I submitted 5 email address and all were okay. Are you seeing sporadic 500 errors across the site? What other pages do form processing? Does the amount of data in Responsys seem reasonable compared to the number of POST requests to the phonebook page or are we losing data? If anyone can reproduce, steps would be helpful.
We're getting it sporadically throughout the site - including on our main newsletter opt-in http://www.mozilla.com/newsletter/. I just did a test there and had the same experience that David describes above. However, I've tried it several time since and it seems to be working. Opening a new bug for mozilla.com to investigate what's happening.
Severity: normal → critical
Depends on: 646325
This looks like the same issue on both sign-up forms so I'll mark this one as a dupe. Feel free to un-dupe it if it would be better to have these as separate bugs.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Although this might be better for the mozilla.com component (the signup form is there), verifying duplicate.
Status: RESOLVED → VERIFIED
Component: mozillians.org → Phonebook
Product: Websites → Community Tools
QA Contact: mozillians-org → phonebook
Version: unspecified → other
You need to log in before you can comment on or make changes to this bug.