Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]我的这个问题困扰我很久了。 #8086

Closed
JustcallmeXiaoLi opened this issue Aug 16, 2021 · 9 comments
Closed

[BUG]我的这个问题困扰我很久了。 #8086

JustcallmeXiaoLi opened this issue Aug 16, 2021 · 9 comments
Labels
bug Something isn't working stale-issue flagged as stale and will be closed in 7 days if not updated

Comments

@JustcallmeXiaoLi
Copy link

Describe the bug

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

Screenshots

Desktop

收割机客户端

  • OS:
  • OS Version/Flavor:
  • CPU:
    钱包机
  • OS:
  • OS Version/Flavor:
  • CPU:

总是提示错误信息为:
2021-08-16T11:00:55.552 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 538, in finish_send
OSError: [WinError 64] 指定的网络名不再可用。

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "websockets\protocol.py", line 1077, in write_frame
File "websockets\protocol.py", line 306, in _drain
File "websockets\protocol.py", line 1077, in write_frame
File "websockets\protocol.py", line 306, in _drain
File "websockets\protocol.py", line 1077, in write_frame
File "websockets\protocol.py", line 306, in _drain
File "websockets\protocol.py", line 1077, in write_frame
File "websockets\protocol.py", line 318, in _drain
File "websockets\protocol.py", line 299, in _drain_helper
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 379, in _loop_writing
File "asyncio\windows_events.py", line 812, in _poll
File "asyncio\windows_events.py", line 542, in finish_send
ConnectionResetError: [WinError 64] 指定的网络名不再可用。

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

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

我根本就没有这个D:\a\chia-blockchain的这个目录,新安装的系统,收割机客户端有25台,总算力大概是4P左右,每天增量为700TB

@JustcallmeXiaoLi JustcallmeXiaoLi added the bug Something isn't working label Aug 16, 2021
@JustcallmeXiaoLi
Copy link
Author

收割机客户端

OS:linux
OS Version/Flavor: ubuntu20.04 server
CPU:2680v2
钱包机
OS:windows
OS Version/Flavor:windows10专业工作站X64
CPU:5950X

@JustcallmeXiaoLi
Copy link
Author

农田,农场,还有农业合作社点了半天都没有反应。

@keliew
Copy link

keliew commented Aug 16, 2021

for the harvester, could you try #8009?

probably it's overloaded and then crashed the daemon/farmer/etc.

could you also turn on log level INFO and try to catch what happens before those errors?

@JustcallmeXiaoLi
Copy link
Author

我的收割机客户端设置的日志等级就是INFO,总是提示2021-08-15T12:26:02.614 harvester chia.harvester.harvester: WARNING Looking up qualities on /mnt/data/d6/plot-k32-2021-08-11-22-44-****************************************.plot took: 5.093957424163818. This should be below 5 seconds to minimize risk of losing rewards.

@keliew
Copy link

keliew commented Aug 17, 2021

I don't think that WARNING is related to the original issue you have.

@elliottback
Copy link
Contributor

I was getting this a lot with python 3.7 and upgrading to a 3.9 docker image resolved it mysteriously.

@keliew
Copy link

keliew commented Aug 18, 2021

Good point. #6703

@github-actions
Copy link
Contributor

github-actions bot commented Sep 2, 2021

This issue has been flagged as stale as there has been no activity on it in 14 days. If this issue is still affecting you and in need of review, please update it to keep it open.

@github-actions github-actions bot added the stale-issue flagged as stale and will be closed in 7 days if not updated label Sep 2, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Sep 9, 2021

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

@github-actions github-actions bot closed this as completed Sep 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale-issue flagged as stale and will be closed in 7 days if not updated
Projects
None yet
Development

No branches or pull requests

3 participants