On-line engine blitz tourney November

[Maarten Claessens]

WaDuuttie was playing with winboard log on. The last lines before the crash:

Code: Select all

2035524 >first : usermove 2035525 >first : g6h6
nps: w=-1, b=-1
Display title 'WaDuuttie (17) vs. Rodin (1) {5 1}, gameInfo.variant = 0'
2035607 <first &#58; move c7h7
>ICS&#58; c7h7\012
>ICS&#58; kibitz !!! +99.98/62 &#40;0.00 sec, 3660 nodes, 3660 knps&#41; PV=c7h7\012
nodes = 3660, 3660
2035710 <first &#58; 1-0 &#123;White mates&#125;
GameEnds&#40;25, White mates, 5&#41;
ics input 167, castling = 45 45 45 45 45 45
Exiting&#58; Connection closed by ICS
silence
GameEnds&#40;28, xboard exit, 2&#41;
Interrupting first
2035710 >first &#58; force
2035711 >first &#58; quit

[Kempelen]

WaDuuttie was playing with winboard log on. The last lines before the crash:

Code: Select all

2035524 >first : usermove 2035525 >first : g6h6
nps: w=-1, b=-1
Display title 'WaDuuttie (17) vs. Rodin (1) {5 1}, gameInfo.variant = 0'
2035607 <first &#58; move c7h7
>ICS&#58; c7h7\012
>ICS&#58; kibitz !!! +99.98/62 &#40;0.00 sec, 3660 nodes, 3660 knps&#41; PV=c7h7\012
nodes = 3660, 3660
2035710 <first &#58; 1-0 &#123;White mates&#125;
GameEnds&#40;25, White mates, 5&#41;
ics input 167, castling = 45 45 45 45 45 45
Exiting&#58; Connection closed by ICS
silence
GameEnds&#40;28, xboard exit, 2&#41;
Interrupting first
2035710 >first &#58; force
2035711 >first &#58; quit

It is curious that the server just crash just at the mate and game ends. I was waching the game. Maybe a problem of disc space?

[ZirconiumX]

WaDuuttie was playing with winboard log on. The last lines before the crash:

Code: Select all

2035524 >first : usermove 2035525 >first : g6h6
nps: w=-1, b=-1
Display title 'WaDuuttie (17) vs. Rodin (1) {5 1}, gameInfo.variant = 0'
2035607 <first &#58; move c7h7
>ICS&#58; c7h7\012
>ICS&#58; kibitz !!! +99.98/62 &#40;0.00 sec, 3660 nodes, 3660 knps&#41; PV=c7h7\012
nodes = 3660, 3660
2035710 <first &#58; 1-0 &#123;White mates&#125;
GameEnds&#40;25, White mates, 5&#41;
ics input 167, castling = 45 45 45 45 45 45
Exiting&#58; Connection closed by ICS
silence
GameEnds&#40;28, xboard exit, 2&#41;
Interrupting first
2035710 >first &#58; force
2035711 >first &#58; quit

I suspect this is about as useful information as me having challenged rpiMinkoChess to a rated 2+12 match when it crashed.

[jdart]

I get in the winboard log:

Fatal Error: Could not connect to host winboard.nl, port 5000:
No connection could be made because the target machine actively refused it.

--Jon

[nionita]

I get in the winboard log:

Fatal Error: Could not connect to host winboard.nl, port 5000:
No connection could be made because the target machine actively refused it.

--Jon

Probably because the ICS server is not listening

[hgm]

gdb would be an idea, but it appears not to be installed. Apt-get install doesn't seem to be able to connect to anything.

[JVMerlino]

I get in the winboard log:

Fatal Error: Could not connect to host winboard.nl, port 5000:
No connection could be made because the target machine actively refused it.

--Jon

Probably because the ICS server is not listening

I am also unable to connect. Winboard gives the message "Connection closed by ICS."

[Henk]

Can't connect too. Has this something to do with firewall on server or so.

[Joost Buijs]

Well, so it is hopeless. The rebooting of the VPS did not cure it. I have no other ideas. I tried fsck, and it warned me that this would pretty much destroy the file system if I do it on a mounted device. But this is the system device, so I cannot possibly unmount it.

I see the problem, it is not going to be easy to solve this. Maybe you can run the tourney next week after you have found the problem.

I have the feeling that it has something to do with writing to disk, like already said maybe a file that is getting to large.

[brtzsnr]

Hi, HGM!

Thank you for your effort in organizing this monthly tournament.

Hiccups happen, servers crash, and it seems unlikely that the error will be fixed within the next 30min. Should the tournament be postponed for next week, so that you are not under pressure to fix the issue and hopfully make sure the server is up for long enough?

Regards,