Outdated Documentation and Swarm doesn't start CLI client

Move
#1

  1. throughout the current documentation/website, cargo run -p libra_swarm is used, which in fact has been renamed to libra-swarm, thus needs update.

  2. I have run into this issue while running cargo run -p libra-swarm -- -s on MacOs: all cargo build are successful, however no CLI client show up, the final stdout is:

     Running `target/debug/libra-swarm -s`
Faucet account created in (loaded from) file "/var/folders/vc/zkm0z46528l5fpgtn1l_bxrh0000gn/T/5a2fa22a978c270f7e5c0e8
04ef4265b/temp_faucet_keys"                                                                                          
Base directory containing logs and configs: Temporary(TempPath { path_buf: "/var/folders/vc/zkm0z46528l5fpgtn1l_bxrh00
00gn/T/c70f37cb79ff3dac15c15fc9edc29bc0", persist: false })
1 Like
#2

You will see the client startup after the client is been built, it may take tens of minutes.

#3

after a while, I got an err:

Faucet account created in (loaded from) file “/var/folders/vc/zkm0z46528l5fpgtn1l_bxrh0000gn/T/ce93c71a2dc6d00e30c65ca
73a8a87f7/temp_faucet_keys”
Base directory containing logs and configs: Temporary(TempPath { path_buf: “/var/folders/vc/zkm0z46528l5fpgtn1l_bxrh00
00gn/T/ec4dc3128fbbf1ff3fefee691641cbb8”, persist: false })
thread ‘main’ panicked at ‘Failed to launch validator swarm: NodeCrash’, src/libcore/result.rs:1165:5
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace.
logs located at “/var/folders/vc/zkm0z46528l5fpgtn1l_bxrh0000gn/T/ec4dc3128fbbf1ff3fefee691641cbb8”

any idea why this might be happening? something wrong with my firewall setting?

1 Like
#4

Sorry, Just realized that I was on master branch, and it works in testnet branch… thanks anyway.

#5

I’m having the same problem but I’m on testnet branch.

#6

I fixed my problem by running ulimit -n 8192 as per this issue.