s.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason
179 views
Skip to first unread message
a.mach...@web.de
Jun 23, 2021, 3:28:56 AM6/23/21
to oTree help & discussion
Hello,
on Monday i will run my first Experiment using otree Version 5.2.4. and a Heroku-Server.
On devserver the Experiment works without mistakes.
However on Heroku somethimes a part of the participants get the following Error Message:
websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason
If participants refresh the page, this message disappears and participants can continue the experiment. This message rarely occurs, mostly the experiment works without errors.
The error occurs at the following point of the experiment. All 15 participants of a session arrive at a waiting page. There, groups are formed specifically. The error probably occurs during the formation of the groups.
I only use one dyno. Log is in the attachment.
How can I ensure that this error no longer occurs?
Thank you very much!
Best, André
On devserver the Experiment works without mistakes.
However on Heroku somethimes a part of the participants get the following Error Message:
websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason
If participants refresh the page, this message disappears and participants can continue the experiment. This message rarely occurs, mostly the experiment works without errors.
The error occurs at the following point of the experiment. All 15 participants of a session arrive at a waiting page. There, groups are formed specifically. The error probably occurs during the formation of the groups.
I only use one dyno. Log is in the attachment.
How can I ensure that this error no longer occurs?
Thank you very much!
Best, André
Chris @ oTree
Jun 23, 2021, 6:37:00 AM6/23/21
to oTree help & discussion
hi, thanks for the report and the logs. i have seen this error before in my logs, but i have never seen it actually produce an error for the user. I will definitely investigate it, although it may take me some time because i have not found a way to reproduce this issue personally.
Chris @ oTree
Jun 23, 2021, 6:37:42 AM6/23/21
to oTree help & discussion
is it possible this error happened while you were doing some configuration on the server? like changing a setting or deploying a new version of the code?
Chris @ oTree
Jun 23, 2021, 6:42:28 AM6/23/21
to oTree help & discussion
Also, are you sure this is the error that was causing the users to have a problem? were you running in debug mode or production mode? if production mode, then tracebacks are not included in the "application error 500" page, so maybe it was something else. Can you check earlier in your logs if some other error happened around that time?
a.mach...@web.de
Jun 23, 2021, 8:58:21 AM6/23/21
to oTree help & discussion
Hi, thank you for the fast response!
I was not doing some configuration on the server.
I got the logs from papertrail. In the logs I could see that exactly this error was repeated for several participants.
I'm pretty sure this error was to blame for the interruption. As I said, the participants only had to refresh the page and could continue playing.
I have also tried countless times since then to recreate the error and it has only reappeared once.
a.mach...@web.de
Jun 23, 2021, 9:01:12 AM6/23/21
to oTree help & discussion
In the attached logs is the entire error code of a player. There were no other indications of an error.
Reply all
Reply to author
Forward
0 new messages