Closed
Bug 643935
Opened 14 years ago
Closed 14 years ago
Mercurial repository's page is truncated
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: stephend, Assigned: nmeyerhans)
References
()
Details
Attachments
(1 file)
|
673.07 KB,
image/png
|
Details |
Screenshot
For whatever reason, http://hg.mozilla.org/ is truncated (no closing <html> tag, etc.).
|
||
Updated•14 years ago
|
Assignee: server-ops → nmeyerhans
|
Assignee | |
Comment 1•14 years ago
|
||
hgweb was crashing. A repository had been moved without hgweb's config being updated. It apparently doesn't like serving nonexistent repositories.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
|
Reporter | |
Comment 2•14 years ago
|
||
Verified FIXED; thanks -- were/are there checks for this? I guess it was returning a 200 OK response, so Nagios might not be sufficient, and it's kind of a special case...
Status: RESOLVED → VERIFIED
|
|
Assignee | |
Comment 3•14 years ago
|
||
The hgweb.cgi program throws a runtime exception if it encounters a repository in its configuration file that doesn't exist in the filesystem. Unfortunately, by the time it throws the exception, it has already output content up to the repository, which is why the HTTP code was 200.
It would be possible to write a nagios check to make sure that all the repos listed in the hgweb conf actually exist. IMO the better thing to do would be to fix hgweb such that this isn't a fatal error.
|
||
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•