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 problem - harvester/farming stops - GUI green but no eligibility checks

See original GitHub issue

Ubuntu 20.10 Linux 5.8.0-53-generic #60-Ubuntu SMP Thu May 6 07:46:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Chia: 1.1.5 Ryzen 5 3600/32G - node/farmer/harvester/gui running only so practically idle (Load Average 1.5)

I am getting this several times a day now - not sure how long but have had so many other problems it has been buried. No sign of a problem on the GUI other than the “Last Attempted Proof” not updating - of course log file has no more eligible checks after this event

Nothing specifically logged around that region in the log files and the last eligibility check was about 16 seconds earlier . I had previously looked for INFO/WARNI/ERRORS but this does not have a status so had missed it - paging through the log files picked it up

The GUI is running - “Last Attempted Proof” not updating but green otherwise

Last time i looked the farmer/harvester processes were still running - i’ll check NEXT time it happens and report - i won’t have long to wait …

Cleared up chia processes and restarted GUI and all ok now … until the next time

I think it is reasonable to ask why the connection is not retried after it has broken … Is it significant that it is 16 seconds after last eligibility check - around about the next round is expected

One more reason why i have no rewards 😦 Farming status: Farming Total chia farmed: 0.0 Plot count: 1227

2021-05-16T16:00:37.563 daemon __main__                   : INFO     Websocket exception. Closing websocket with chia_harvester code = 1006 (connection closed abnormally [internal]), no reason Traceback (most recent call last):
  File "/home/ianj/1.1.5/chia-blockchain/venv/lib/python3.8/site-packages/websockets/protocol.py", line 827, in transfer_data
    message = await self.read_message()
  File "/home/ianj/1.1.5/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/ianj/1.1.5/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/ianj/1.1.5/chia-blockchain/venv/lib/python3.8/site-packages/websockets/protocol.py", line 1047, in read_frame
    frame = await Frame.read(
  File "/home/ianj/1.1.5/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 "../chia/daemon/server.py", line 172, in safe_handle
    async for message in websocket:
  File "/home/ianj/1.1.5/chia-blockchain/venv/lib/python3.8/site-packages/websockets/protocol.py", line 439, in __aiter__
    yield await self.recv()
  File "/home/ianj/1.1.5/chia-blockchain/venv/lib/python3.8/site-packages/websockets/protocol.py", line 509, in recv
    await self.ensure_open()
  File "/home/ianj/1.1.5/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

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:10 (2 by maintainers)

github_iconTop GitHub Comments

3reactions
djjaeger82commented, Aug 10, 2021

I’m still having this issue on chia and all its forks, I’d like to see a real fix besides manually monitoring and having to restart the farmers/harvesters every few hours.

0reactions
github-actions[bot]commented, Jul 18, 2021

This issue was automatically closed because it has been flagged as stale and subsequently passed 7 days with no further activity.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting connection issues | Socket.IO
Problem: the socket is not able to connect​. Possible explanations: You are trying to reach a plain WebSocket server; The server is not ......
Read more >
iOS 15 WKWebView websocket behaviour - Apple Developer
A test web socket to another server seems to be working. I also notices that a MitM proxy like Charles no longer shows...
Read more >
Firefox's New WebSocket Inspector - the Web developer blog
The WebSocket inspector will be released in Firefox 71, but is ready for you to use in Firefox Developer Edition now.
Read more >
Error with WebSocket - Microsoft Q&A
Set the framework to 6.0 with no Authentication type and the option Configure for HTTPS and ASP.NET Core hosted checked.
Read more >
How We Improved Reliability Of Our WebSocket Connections
This time, the TCP FIN packet would not make it to the UI client. We plugged the Ethernet cable back in and waited...
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