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] Node fails to start on Windows 10 with 64 cores (with workaround) #17967

Open
fizpawiz opened this issue May 3, 2024 · 4 comments
Open
Labels
bug Something isn't working stale-issue flagged as stale and will be closed in 7 days if not updated

Comments

@fizpawiz
Copy link

fizpawiz commented May 3, 2024

What happened?

I have a Threadripper 3970x with 64 cores. On 2.2.1, I was farming fine. On 2.3.0 the farmer will no longer start.

Per discussion on Keybase, I tried setting full_node/reserved_cores to 10 (from default of zero) in the config.yaml, and it resolved the issue.

Version

2.3.0

What platform are you using?

Windows

What ui mode are you using?

GUI

Relevant log output

2024-05-02T14:27:29.822 full_node chia.server.start_service: ERROR    fatal uncaught exception: ValueError: max_workers must be <= 61
Traceback (most recent call last):
  File "chia\util\log_exceptions.py", line 20, in log_exceptions
  File "chia\server\start_service.py", line 323, in async_run
  File "asyncio\runners.py", line 44, in run
  File "asyncio\base_events.py", line 649, in run_until_complete
  File "chia\server\start_full_node.py", line 85, in async_main
  File "chia\server\start_service.py", line 197, in run
  File "contextlib.py", line 199, in __aenter__
  File "chia\server\start_service.py", line 214, in manage
  File "contextlib.py", line 619, in enter_async_context
  File "contextlib.py", line 199, in __aenter__
  File "chia\full_node\full_node.py", line 266, in manage
  File "chia\consensus\blockchain.py", line 146, in create
  File "concurrent\futures\process.py", line 614, in __init__
ValueError: max_workers must be <= 61
@fizpawiz fizpawiz added the bug Something isn't working label May 3, 2024
@fizpawiz fizpawiz changed the title [Bug] Node fails to start on Windows 10 with 64 cores [Bug] Node fails to start on Windows 10 with 64 cores (with workaround) May 3, 2024
@altendky
Copy link
Contributor

altendky commented May 3, 2024

Fix being added back in #17958. Was incorrectly removed in #17409 first released in 2.3.0rc1. This is specific to Windows and CPUs with more than 61 cores.

@SoftStoneDevelop
Copy link

I have the same problem, I'll have to roll back to 2.2.1

@altendky
Copy link
Contributor

altendky commented May 5, 2024

While this does need to be fixed, do note the small configuration adjustment that can work around this.

setting full_node/reserved_cores to 10

Copy link
Contributor

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.

@github-actions github-actions bot added the stale-issue flagged as stale and will be closed in 7 days if not updated label May 20, 2024
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