URGENT DOMjudge PROBLEM in Southern California
tobias.werth at fau.de
Mon Nov 13 04:31:02 CET 2017
Happy to help.
Please collect logs (example judgedaemon log, syslog, apache logs,
mysql logs) and send them to team at domjudge.org for further analysis.
We'll see how we can improve the config check and error checks in
judgedaemon to reduce the likelihood of both failures.
On Sun, Nov 12, 2017 at 7:00 PM, Marc Furon <marcf at dslextreme.com> wrote:
> Tobias Werth wrote:
>> I don't have phone reception but I've sent you an invite to chat
>> via hangouts. Perhaps you can give more details on the compile
>> error or give me admin access to your domjudge installation?
> Tobi, THANK YOU so much for jumping in to help, and thanks to Keith as well.
> Fixing the permissions on the judging directory
> (/opt/domjudge/judgehost/judgings) got us back to where we were before, and
> we made some quick adjustments to the Apache configuration that seemed to
> help. I can't say for certain if that fixed everything because at that
> point the contest was close to over (we extended it by one hour) and some
> teams may have taken off already if they were not in the running. However,
> we were ultimately able to judge everything and complete the contest (albeit
> with contestants programming with no feedback for two hours).
> We in Southern California (that means me) would like to take you up on your
> offer for assistance with root cause analysis. I have the contest server
> sitting next to me here at home and can provide anything you might want that
> would help with troubleshooting. Please let me know what the best way will
> be to proceed.
> I owe the DOMjudge team big-time.
More information about the DOMjudge-devel