On 04-08-16 01:10, Br. Anand Shenoi wrote:
> Hi Jaap!
>
> Please find the Judgehost log for the contest we had held on 27th.

I assume the contest ran approximately between 9am - 1pm? Before and
after those times I see many errors that the judgedaemon cannot connect
to the host (i.e. the domserver), but also during the contest there are
a couple of times this is reported, see attached lines filtered from the
judgedaemon log.

It looks like that the connection was not always up and the judgedaemon
couldn't reach the server. Alternatively, it could be that the server
was under high load (but then I'd expect to see timeouts as well) or
that it had a too low maximum connection count configured.

Did you see the same problem with other judgehosts?

Jaap



> *From: *Jaap Eldering <mailto:jaap@jaapeldering.nl>
> *Sent: *27 July 2016 06:18 PM
> *To: *Aneesh R <mailto:aneeshktr.amrita@gmail.com>;
> domjudge-devel@domjudge.org <mailto:domjudge-devel@domjudge.org>
> *Cc: *Anand Shenoi <mailto:shenoianand@gmail.com>
> *Subject: *Re: Judgenode Down issue
>
>
>
> Hi Aneesh,
>
> On 27-07-16 08:01, Aneesh R wrote:
>> Dear Team
>>
>> We have hosted Domjudge 5.0.1 in our university, on 27-07-16 we have
>> conducted practice test for our students , we are facing some issue in
>> judgenode  each 10-15 minutes it will goes down , i here attached the
>> screen shots of apache error log file,anyone can help me to resolve the
>> judgehost node down issue . We have separate technical wing is here ,i
>> just enquire with them they told it occur due to the problem set time
>> limit . For example one problem time limit have 1 minut after that the
>> judgenode will goes down
>>
>> I think appache error log is not much for identify this problem, if
>> anything more please specify i will update here
>
> Could you attach the judge log file from one of the judgehosts that has
> experienced this problem at least a few times?
>
> Also, was the DOMjudge website in any way slow to respond when this
> occurred? Since my first guess would be a timeout issue when the
> judgedaemons are trying to contact the server via the REST API.
>
> Jaap
>
> _______________________________________________
> DOMjudge-devel mailing list
> DOMjudge-devel@domjudge.org
> https://www.domjudge.org/mailman/listinfo/domjudge-devel