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 "1006" between Daemon and Wallet - RPi4B

See original GitHub issue

What happened?

The software (CLI) is extremely unstable running on my Raspberry Pi 4 model B - 4GB

Version

1.2.11

What platform are you using?

Linux

What ui mode are you using?

CLI

Relevant log output

2021-11-14T12:06:07.534 daemon chia.daemon.server         : INFO     Websocket exception. Closing websocket with chia_wallet code = 1006 (connection closed abnormally [internal]), no reason Traceback (most recent call last):
  File "/home/ubuntu/chia-blockchain/venv/lib/python3.9/site-packages/websockets/protocol.py", line 827, in transfer_data
    message = await self.read_message()
  File "/home/ubuntu/chia-blockchain/venv/lib/python3.9/site-packages/websockets/protocol.py", line 895, in read_message
    frame = await self.read_data_frame(max_size=self.max_size)
  File "/home/ubuntu/chia-blockchain/venv/lib/python3.9/site-packages/websockets/protocol.py", line 971, in read_data_frame
    frame = await self.read_frame(max_size)
  File "/home/ubuntu/chia-blockchain/venv/lib/python3.9/site-packages/websockets/protocol.py", line 1047, in read_frame
    frame = await Frame.read(
  File "/home/ubuntu/chia-blockchain/venv/lib/python3.9/site-packages/websockets/framing.py", line 105, in read
    data = await reader(2)
  File "/usr/lib/python3.9/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/ubuntu/chia-blockchain/chia/daemon/server.py", line 195, in safe_handle
    async for message in websocket:
  File "/home/ubuntu/chia-blockchain/venv/lib/python3.9/site-packages/websockets/protocol.py", line 439, in __aiter__
    yield await self.recv()
  File "/home/ubuntu/chia-blockchain/venv/lib/python3.9/site-packages/websockets/protocol.py", line 509, in recv
    await self.ensure_open()
  File "/home/ubuntu/chia-blockchain/venv/lib/python3.9/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

Issue Analytics

State:
Created 2 years ago
Comments:14 (2 by maintainers)

Top GitHub Comments

1reaction

emlowecommented, Dec 10, 2021

I recommend to check for out of memory killer message (OOM) sudo journalctl | grep -i oom It may be that you are running out of memory and the OS is killing off node - this appears to be what is happening from the log entries.

We currently recommend you add in 1Gb of swap space, but you may need to run as much as 2Gb swap

0reactions

emlowecommented, Dec 16, 2021

I’m going to close this issue. Note we do hope to reduce the memory footprint to better work within a 4GB system, but for now adding the swap space is the best approach to keep running.