Closed Bug 937488 Opened 12 years ago Closed 12 years ago

I receive a 503 Service Unavailable error message after submitting a bug to bugzilla

Categories

(Bugzilla :: Creating/Changing Bugs, defect)

4.0.2
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: ajeesh.r, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/30.0.1599.114 Chrome/30.0.1599.114 Safari/537.36 Steps to reproduce: Client tried to raise one issue in bugzilla and I tried to save changes after solving an issue in bugzilla. Actual results: Received a 503 Service Unavailable error message after submitting an issue to bugzilla. After looking into the list of issues, came to see that the bug is submitted successfully. Expected results: The 503 error message is not expecting while raising an issue or after save changes.
Severity: normal → major
Priority: -- → P1
this isn't a bug in bugzilla, "503 service unavailable" your varnish cache wasn't able to contact your bugzilla server.
Group: bugzilla-security
Severity: major → normal
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Priority: P1 → --
Resolution: --- → INVALID
Thanks for your quick response. But how this can be resolved/checked from our end ?
(In reply to ajeesh r from comment #2) > Thanks for your quick response. But how this can be resolved/checked from > our end ? you need to use one of our support mechanisms for support (this bugzilla instance is only for reporting bugs). see http://www.bugzilla.org/support/ while i can't give you any more support here, you should start by looking at the error log files for both your back-end web server and varnish to determine why it wasn't available at that time.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: