question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG]1006 (connection closed abnormally [internal]), no reason

See original GitHub issue
2021-10-22T22:07:37.643 daemon __main__                   : ERROR    Unexpected exception trying to send to websocket: code = 1006 (connection closed abnormally [internal]), no reason Traceback (most recent call last):
  File "asyncio\windows_events.py", line 457, in finish_recv
OSError: [WinError 64] The specified network name is no longer available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "websockets\protocol.py", line 827, in transfer_data
  File "websockets\protocol.py", line 895, in read_message
  File "websockets\protocol.py", line 971, in read_data_frame
  File "websockets\protocol.py", line 1047, in read_frame
  File "websockets\framing.py", line 105, in read
  File "asyncio\streams.py", line 723, in readexactly
  File "asyncio\streams.py", line 517, in _wait_for_data
  File "asyncio\proactor_events.py", line 280, in _loop_reading
  File "asyncio\windows_events.py", line 812, in _poll
  File "asyncio\windows_events.py", line 461, in finish_recv
ConnectionResetError: [WinError 64] The specified network name is no longer available

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "Lib\site-packages\chia\daemon\server.py", line 208, in safe_handle
  File "websockets\protocol.py", line 555, in send
  File "websockets\protocol.py", line 803, in ensure_open
websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason

This error prevails even though I uninstall reinstall Chia 1.2.9 any way to fix this?

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
moonlitbugscommented, Oct 31, 2021

This looks to be a duplicate of #2810 (and a bunch of other duplicates as well, all closed). Chiming in a “me too” here, except that Chia is running on Linux and not Windows.

In my case, Chia is running inside a small LXC (Linux container). Restarting the container “fixed” the issue, at least temporarily. There is nothing helpful in the Chia debug.log file beyond the endless backtraces.

I do note that chia_full_node is consuming a lot of memory, more than 1.1g resident and 1.5g virtual. On a small VM, that’s dangerously close to putting it into swap space, and/or triggering the “OOM Killer” (Linux’s low-memory panic mechanism).

1reaction
github-actions[bot]commented, Dec 19, 2021

This issue has not been updated in 14 days and is now flagged as stale. If this issue is still affecting you and in need of further review, please comment on it with an update to keep it from auto closing in 7 days.

Read more comments on GitHub >

github_iconTop Results From Across the Web

1006 Connection closed abnormally error with python 3.7 ...
it means that the TCP connection was lost. As a consequence, the WebSocket connection was closed without receiving a close frame, ...
Read more >
1006 connection closed code but stream never restarts
WARNING [stream.py:224] websocket error, restarting connection: code = 1006 (connection closed abnormally [internal]), no reason.
Read more >
code = 1006 (connection closed abnormally [internal]), no ...
This message rarely occurs, mostly the experiment works without errors. The error occurs at the following point of the experiment. All 15 ...
Read more >
What Is Meant By Channels Error 1006? - Pusher
When a WebSocket connection is closed without a "close frame", the pusher-js library emits an error with code 1006. Usually this is caused...
Read more >
Websocket closes unexpectedly with error 1006
From my experience the error 1006 occurs when the connection on the client side is ... code = 1006 (connection closed abnormally [internal]),...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found