Internal Server Error when going to


Status Graveyard
Server Operations
10 years ago
3 years ago


(Reporter: mcsmurf, Assigned: aravind)






10 years ago
To reproduce:
1. Go to

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.


10 years ago
Summary: Internal Server Error when goint to → Internal Server Error when going to
Assignee: nobody → server-ops
Component: Hg: Customizations → Server Operations
QA Contact: hg.customizations → mrz
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
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.

Comment 3

10 years ago
looking into this.
Assignee: server-ops → aravind

Comment 4

10 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.
Last Resolved: 10 years ago
Resolution: --- → FIXED
Product: → Graveyard
You need to log in before you can comment on or make changes to this bug.