On-line engine blitz tourney July
Moderators: hgm, Rebel, chrisw
-
- Posts: 349
- Joined: Sat Aug 06, 2016 8:31 pm
- Location: United States
Re: On-line engine blitz tourney July
It appeared to me that KingSlayer lost on time vs RookieMonster in the first round, but instead of a result, I got a message about an invalid command once its time had expired. I then logged out and can no longer get back in; it seems to think I'm entering non alpha characters for a user name. If no one else is having issues, please withdraw RM.
Erin Dame
Author of RookieMonster
Author of RookieMonster
-
- Posts: 43
- Joined: Tue Mar 25, 2014 10:34 pm
Re: On-line engine blitz tourney July
Same problem for me! Can't login any more!
-
- Posts: 2488
- Joined: Tue Aug 30, 2016 8:19 pm
- Full name: Rasmus Althoff
Re: On-line engine blitz tourney July
Same here during the game against Eichhoernchen. Fics last message was some binary garbage followed by "nil: Command not found". Login doesn't work anymore.
Rasmus Althoff
https://www.ct800.net
https://www.ct800.net
-
- Posts: 481
- Joined: Tue Jul 03, 2018 10:19 am
- Full name: Folkert van Heusden
Re: On-line engine blitz tourney July
Me too!
Embla was playing (on rpi3 & i7) and both got thrown out and now no longer can I connect.
-
- Posts: 51
- Joined: Sun Jul 10, 2016 9:12 pm
- Location: Lund, Sweden
- Full name: Martin Danielsson
Re: On-line engine blitz tourney July
I managed to login again now.
-
- Posts: 96
- Joined: Fri Jul 06, 2018 1:09 am
- Location: Chicago, IL
- Full name: Josh Odom
Re: On-line engine blitz tourney July
Looks like the random character issue is happening again
-
- Posts: 2488
- Joined: Tue Aug 30, 2016 8:19 pm
- Full name: Rasmus Althoff
Re: On-line engine blitz tourney July
yupp, here also. can't login.
Rasmus Althoff
https://www.ct800.net
https://www.ct800.net
-
- Posts: 115
- Joined: Mon Sep 17, 2012 8:59 pm
Re: On-line engine blitz tourney July
Stuck again
-
- Posts: 349
- Joined: Sat Aug 06, 2016 8:31 pm
- Location: United States
Re: On-line engine blitz tourney July
Yes, it happened again. Sad part is these two pretty wins were lost to the ether as neither were saved in the WinBoard PGN.
Erin Dame
Author of RookieMonster
Author of RookieMonster
-
- Posts: 27817
- Joined: Fri Mar 10, 2006 10:06 am
- Location: Amsterdam
- Full name: H G Muller
Re: On-line engine blitz tourney July
Sorry guys,
I see no alterative but to cancel the tourney for tonight. I took the server off line.
It is clear to me what the problem is: most of you connect through timeseal, which encrypts everything you sent to the ICS. The ICS sends the encrypted input to a separate process, running the timeseal decoder, which then gives it the decrypted input back. It is this process that crashes and dies, so that the ICS only sees the encrypted input. Which it of course rejects as invalid.
The timeseal decoder is closed source.
This has happened once before, and the cause was the too long kibitz lines from one of the participating engines. I could fix that by having the ICS clip the lines it sends to the decoder to a safe length. So I am surprised the problem can occur again. But the ICS saves a command log, so I shoul be able to figure out which was the last input line before the commands got gibberish. This is the line that must have crashed the decoder. Hopefully seeing that line can give me an idea what it contains that is problematic, so I can defuse such lines before they go to the decoder. This will take some time.
I see no alterative but to cancel the tourney for tonight. I took the server off line.
It is clear to me what the problem is: most of you connect through timeseal, which encrypts everything you sent to the ICS. The ICS sends the encrypted input to a separate process, running the timeseal decoder, which then gives it the decrypted input back. It is this process that crashes and dies, so that the ICS only sees the encrypted input. Which it of course rejects as invalid.
The timeseal decoder is closed source.
This has happened once before, and the cause was the too long kibitz lines from one of the participating engines. I could fix that by having the ICS clip the lines it sends to the decoder to a safe length. So I am surprised the problem can occur again. But the ICS saves a command log, so I shoul be able to figure out which was the last input line before the commands got gibberish. This is the line that must have crashed the decoder. Hopefully seeing that line can give me an idea what it contains that is problematic, so I can defuse such lines before they go to the decoder. This will take some time.