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] Websocket exception on harvester when plots are moved

See original GitHub issue

Describe the bug This bug was already reported on b27. I’m re-creating it, and giving details on how it happened on my system.

On a server I’m running plotter + harvester (remote).

In config.yaml I have several plot_directories, including:

  • /dest
  • /almost-empty

The server is running a plotter with -d /dest, and from time to time - before that disk gets full - I move several plots to /almost-empty. The move is done via rsync.

While one of those moving scripts was running, the harvester crashed, and the last log shows:

05:48:52.417 daemon src.daemon.server          : INFO     Websocket exception. Closing websocket with chia_harvester code = 1006 (connection closed abnormally [internal]), no reason Traceback (most recent call last):
  File "/home/panzerkunst/chia-blockchain/venv/lib/python3.8/site-packages/websockets/protocol.py", line 827, in transfer_data
    message = await self.read_message()
  File "/home/panzerkunst/chia-blockchain/venv/lib/python3.8/site-packages/websockets/protocol.py", line 895, in read_message
    frame = await self.read_data_frame(max_size=self.max_size)
  File "/home/panzerkunst/chia-blockchain/venv/lib/python3.8/site-packages/websockets/protocol.py", line 971, in read_data_frame
    frame = await self.read_frame(max_size)
  File "/home/panzerkunst/chia-blockchain/venv/lib/python3.8/site-packages/websockets/protocol.py", line 1047, in read_frame
    frame = await Frame.read(
  File "/home/panzerkunst/chia-blockchain/venv/lib/python3.8/site-packages/websockets/framing.py", line 105, in read
    data = await reader(2)
  File "/usr/lib/python3.8/asyncio/streams.py", line 721, in readexactly
    raise exceptions.IncompleteReadError(incomplete, n)
asyncio.exceptions.IncompleteReadError: 0 bytes read on a total of 2 expected bytes

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

Traceback (most recent call last):
  File "/home/panzerkunst/chia-blockchain/src/daemon/server.py", line 149, in safe_handle
    async for message in websocket:
  File "/home/panzerkunst/chia-blockchain/venv/lib/python3.8/site-packages/websockets/protocol.py", line 439, in __aiter__
    yield await self.recv()
  File "/home/panzerkunst/chia-blockchain/venv/lib/python3.8/site-packages/websockets/protocol.py", line 509, in recv
    await self.ensure_open()
  File "/home/panzerkunst/chia-blockchain/venv/lib/python3.8/site-packages/websockets/protocol.py", line 803, in ensure_open
    raise self.connection_closed_exc()
websockets.exceptions.ConnectionClosedError: code = 1006 (connection closed abnormally [internal]), no reason

Expected behavior The harvester can handle moving plots without crashing.

Desktop (please complete the following information):

  • Chia version: 1.0rc2
  • OS: Ubuntu 20.04

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:14 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
mariano54commented, Feb 24, 2021

This is hopefully now fixed by the new chiapos. We will have to confirm on the next testnet

1reaction
hoffmang9commented, Feb 23, 2021

We think we just figured out what is going on. Will attempt to fix.

Read more comments on GitHub >

github_iconTop Results From Across the Web

[BUG] Harvester crashes with socket error after couple of hours
Describe the bug Sometimes I find one my harvesters not talking to the farmer anymore. This happened now several times on different machines ......
Read more >
Harvester network disappearing - Support - Chia Forum
Turned out that although the node, plotting, harvester etc were all showing a green, connected status, my harvester network list was empty. Has ......
Read more >
1006 Connection closed abnormally error with python 3.7 ...
The way I've been testing it is by closing my internet connection, but after a ten second delay it still returns the 1006...
Read more >
WebSocket: error event - Web APIs | MDN
The error event is fired when a connection with a WebSocket has been closed due to an error (some data couldn't be sent...
Read more >
Exceptions - websockets 10.4 documentation
websockets.exceptions defines the following exception hierarchy: ... Like ConnectionClosed , when the connection terminated with an error.
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