Issue Report Environment Operating system: linux 2023-03-28T04:32:30.853626Z INFO sc_sysinfo: :laptop: CPU architecture: x86_64 2023-03-28T04:32:30.853682Z INFO sc_sysinfo: :laptop: Target environment: gnu 2023-03-28T04:32:30.853697Z INFO sc_sysinfo: :laptop: CPU: DO-Regular 2023-03-28T04:32:…

There is a new version released with the last couple days, please make sure you’ve updated it seems to have solved this problem. Also keep an eye out there is a v2 and v3 version of the file depending on the year of your processor

Hello thanks for reporting! Please check [image] Cannot block the current thread from within a runtime Support Issue Report Environment Operating System: Ubuntu 20.04 CPU Architecture: 3 core amd64 RAM: 4G Storage: 80G Plot Size: 1G Subspace Deployment …

Can you help me to update? I didn’t find instructions on how to do it.

updated like this wget -O subspace-cli https://github.com/subspace/subspace-cli/releases/download/v0.1.11-alpha/subspace-cli-ubuntu-x86_64-v3-v0.1.11-alpha sudo chmod +x subspace-cli sudo mv subspace-cli /usr/local/bin/ sudo systemctl restart subspaced journalctl -u subspaced -f But now here a…

Update post The node either does not start, or it is not clear 2023-03-28T07:04:11.561140Z WARN libp2p_swarm: Incoming connection rejected: ConnectionLimit { limit: 100, current: 100 } 2023-03-28T07:04:11.561184Z WARN libp2p_swarm: Incoming connection rejected: ConnectionLimit { limit: 100, curr…

You can ignore the WARNs they are known and will be gone on next releases also they dont cause any trouble to the working of farmer. What you have is I think your farmer stops with no error like mine [image] Cannot block the current thread from within a runtime Support My …

@Insperative looks like new version fixed the issue please check (v0.1.12) [image] Releases · subspace/subspace-cli The Subspace Network CLI for Nodes and Farmers. Contribute to subspace/subspace-cli development by creating an account on GitHub.

Hello Insperative. We shared an update on the thread you linked :slight_smile:

Hello Fradique. Thanks for help :upside_down_face:

same problem : 2023-03-29T16:22:56.709165Z INFO validate_config:parse_config: subspace_cli::config: close time.busy=57.3µs time.idle=1.87ms 2023-03-29T16:22:56.709218Z INFO validate_config: subspace_cli::config: close time.busy=65.9µs time.idle=1.92ms

Synchronization does not fully reach, the node crashes when starting farming

Support

Insperative March 28, 2023, 6:21pm 8

Yes, now there is no crash problem after the update, but the node does not catch up by 100 blocks. Node can't catch up to 100 units, doesn't fully sync - #3 by Insperative

Topic		Replies	Views
Cannot block the current thread from within a runtime Support	11	870	March 28, 2023
Node can't catch up to 100 units, doesn't fully sync Support nodes	13	612	March 29, 2023
Node occasionally experiences synchronization issues Support	13	412	April 10, 2024
Node stops unexpectedly Support	8	143	June 25, 2024
Thread 'main' panicked at 'Failed to make runtime API call during last archived block search: UnknownBlock Support nodes , cli	10	318	September 17, 2023

Synchronization does not fully reach, the node crashes when starting farming

Related topics