Judgenode Down issue

Jaap Eldering jaap at jaapeldering.nl
Thu Aug 4 16:03:26 CEST 2016


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 at jaapeldering.nl>
> *Sent: *27 July 2016 06:18 PM
> *To: *Aneesh R <mailto:aneeshktr.amrita at gmail.com>;
> domjudge-devel at domjudge.org <mailto:domjudge-devel at domjudge.org>
> *Cc: *Anand Shenoi <mailto:shenoianand at 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 at domjudge.org
> https://www.domjudge.org/mailman/listinfo/domjudge-devel

-------------- next part --------------
[Jul 27 09:06:32] judgedaemon[1939]: warning: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judgings: couldn't connect to host
[Jul 27 09:23:39] judgedaemon[1939]: warning: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judgings: couldn't connect to host
[Jul 27 09:27:04] judgedaemon[1939]: error: Error while executing curl PUT to url http://10.0.0.151/domjudge/api/judgings/556: couldn't connect to host
[Jul 27 09:41:39] judgedaemon[4909]: warning: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judgings: couldn't connect to host
[Jul 27 09:42:47] judgedaemon[4909]: warning: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judgings: couldn't connect to host
[Jul 27 09:44:49] judgedaemon[6266]: error: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judgehosts: couldn't connect to host
[Jul 27 10:16:03] judgedaemon[6275]: warning: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judgings: couldn't connect to host
[Jul 27 10:37:12] judgedaemon[8756]: error: Error while executing curl PUT to url http://10.0.0.151/domjudge/api/judgings/565: couldn't connect to host
[Jul 27 10:38:26] judgedaemon[9072]: Found unfinished judging j565 in my name; given back
[Jul 27 11:09:24] judgedaemon[10881]: warning: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judgings: couldn't connect to host
[Jul 27 11:26:33] judgedaemon[10881]: warning: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judgings: couldn't connect to host
[Jul 27 11:29:31] judgedaemon[12513]: error: Error while executing curl PUT to url http://10.0.0.151/domjudge/api/judgings/579: couldn't connect to host
[Jul 27 11:30:09] judgedaemon[12568]: Found unfinished judging j579 in my name; given back
[Jul 27 11:43:38] judgedaemon[12568]: warning: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judgings: couldn't connect to host
[Jul 27 12:00:55] judgedaemon[12568]: warning: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judgings: couldn't connect to host
[Jul 27 12:18:05] judgedaemon[12568]: warning: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judgings: couldn't connect to host
[Jul 27 12:35:51] judgedaemon[12568]: warning: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judgings: couldn't connect to host
[Jul 27 12:53:00] judgedaemon[12568]: warning: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judgings: couldn't connect to host


More information about the DOMjudge-devel mailing list