Closed
Bug 453610
Opened 16 years ago
Closed 16 years ago
Internal Server Error when going to http://hg.mozilla.org/
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mcsmurf, Assigned: aravind)
References
()
Details
To reproduce: 1. Go to http://hg.mozilla.org/ Observe that the first three repositories are listed (actionmonkey, actionmonkey-tamarin and ast). The other repositories are not listed and above those three entries an "Internal Server Error - The server encountered an internal error or misconfiguration and was unable to complete your request. [...]" is displayed.
Reporter | ||
Updated•16 years ago
|
Summary: Internal Server Error when goint to http://hg.mozilla.org/ → Internal Server Error when going to http://hg.mozilla.org/
Updated•16 years ago
|
Assignee: nobody → server-ops
Component: Hg: Customizations → Server Operations
QA Contact: hg.customizations → mrz
Comment 1•16 years ago
|
||
Possibly also worth noting is that I'm getting the following when trying to push to comm-central: remote: Not trusting file /repo/hg/mozilla/comm-central/.hg/hgrc from untrusted user root, group hg_mozilla mozilla-central seems ok
Comment 2•16 years ago
|
||
The Internal Server Error and the error in comment #1 could well be related. comm-central might come next after ast, and there is a known problem in the current hg setup that makes for problems when this kind of thing happens. Also, not trusting the hgrc is a problem because it means hooks won't be executed, meaning no pushlog or single-head checks. So, probably just fixing the perms on .hg/hgrc for comm-central will fix this. Longer-term, making mod_wsgi a little more flexible about this thing (using PermitStderr directive or some such) might be helpful.
Assignee | ||
Comment 4•16 years ago
|
||
Fixed the owners on the hgrc files, both errors should be gone now. I am going to look for a better fix for this sometime today - either directory permissions or a cron job that scans and fixes the owners.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•9 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
•