-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]run prover connect to timed out #3122
Comments
Compiling error: error: could not parse/generate dep info at: /home/rootadmin/snarkOS/target/release/deps/version_check-2eacf4551749794c.d Caused by: Caused by: error: failed to write /home/rootadmin/snarkOS/target/release/deps/libzerocopy-b8126872e162cabe.rmeta: No such file or directory (os error 2) error: couldn't create a temp dir: No such file or directory (os error 2) at path "/home/rootadmin/snarkOS/target/release/deps/rmetag8L0NY" error: could not compile error: could not compile error: could not compile error: could not compile |
I reinstalled it and it doesn't generate an error anymore, but it still times out on the connections. 馃Л Starting a prover node on Aleo Mainnet (v0) at 0.0.0.0:4130. 2024-02-25T07:02:11.342571Z DEBUG No connected peers only 4130 opened. |
I encountered the same problem. Welcome to Aleo! We thank you for running a node and supporting privacy. 馃憶 Your Aleo address is aleo1g4736m25xhqjgmrev40hm9k9lj4u4yjrfng8zvr09jm2teuxggrsx4u7ge. 馃Л Starting a prover node on Aleo Mainnet (v0) at 0.0.0.0:4130. 2024-02-27T12:57:45.404901Z DEBUG No connected peers |
me too |
Any solution for this, it's stuck on my node for a couple week |
Bro, did you solve the problem? |
+1 |
馃悰 Bug Report
2024-02-23T15:09:52.110739Z DEBUG No connected peers
2024-02-23T15:09:53.113218Z WARN Unable to connect to '45.55.201.67:4130' - timed out
2024-02-23T15:10:17.113516Z DEBUG No connected peers
2024-02-23T15:10:18.114887Z WARN Unable to connect to '45.55.201.67:4130' - timed out
2024-02-23T15:10:42.114190Z DEBUG No connected peers
2024-02-23T15:10:43.115605Z WARN Unable to connect to '64.23.169.88:4130' - timed out
2024-02-23T15:11:07.115937Z DEBUG No connected peers
2024-02-23T15:11:08.116329Z WARN Unable to connect to '45.55.201.67:4130' - timed out
2024-02-23T15:11:32.116631Z DEBUG No connected peers
2024-02-23T15:11:33.118057Z WARN Unable to connect to '45.55.201.80:4130' - timed out
2024-02-23T15:11:57.117406Z DEBUG No connected peers
2024-02-23T15:11:58.118871Z WARN Unable to connect to '146.190.35.174:4130' - timed out
2024-02-23T15:12:22.119172Z DEBUG No connected peers
2024-02-23T15:12:23.120521Z WARN Unable to connect to '45.55.201.67:4130' - timed out
2024-02-23T15:12:47.120786Z DEBUG No connected peers
2024-02-23T15:12:48.122160Z WARN Unable to connect to '45.55.201.67:4130' - timed out
2024-02-23T15:13:12.121469Z DEBUG No connected peers
2024-02-23T15:13:13.122876Z WARN Unable to connect to '146.190.35.174:4130' - timed out
2024-02-23T15:13:37.123098Z DEBUG No connected peers
2024-02-23T15:13:38.124427Z WARN Unable to connect to '45.55.201.80:4130' - timed out
2024-02-23T15:14:02.124660Z DEBUG No connected peers
2024-02-23T15:14:03.126033Z WARN Unable to connect to '45.55.201.80:4130' - timed out
Steps to Reproduce
setup by the guide. and run ./run-prover.sh
Expected Behavior
port 3030/tcp no open but the OS firewall are closed.
Your Environment
snarkOS Version: mainnet-latest [v2.2.7]
Rust Version:1.74.1
Computer OS:Ubuntu 22.04
The text was updated successfully, but these errors were encountered: