SOLVED - Error: Invalid value for '--hard-coded-contacts <hard-coded-contacts>'

Hi !

I have a fresh built of sn_node and sn_api but things do not go welll when I test,
here are the version of the binaries, then the command I use and the result :

sn_cli 0.18.0
sn_node 0.26.11
sn_authd 0.1.0

safe mode run-baby-fleming --testing

Creating '/home/richard/.safe/node/baby-fleming-nodes' folder
Storing nodes' generated data at /home/richard/.safe/node/baby-fleming-nodes
Launching local Safe network...
Launching with node executable from: /home/richard/.safe/node/sn_node
Version: sn_node 0.26.11
Network size: 11 nodes
Launching genesis node (#1)...
Connection info directory: "/home/richard/.safe/node/node_connection_info.config"
Genesis node contact info: [[
  "127.0.0.1:12000"
]]
Common node args for launching the network: ["-vv", "--idle-timeout-msec", "5500", "--keep-alive-interval-msec", "4000", "--local"]
No RUST_LOG override provided
Launching node #2...
error: Invalid value for '--hard-coded-contacts <hard-coded-contacts>': invalid type: sequence, expected socket address at line 1 column 1
Launching node #3...
error: Invalid value for '--hard-coded-contacts <hard-coded-contacts>': invalid type: sequence, expected socket address at line 1 column 1
Launching node #4...
error: Invalid value for '--hard-coded-contacts <hard-coded-contacts>': invalid type: sequence, expected socket address at line 1 column 1
Launching node #5...
error: Invalid value for '--hard-coded-contacts <hard-coded-contacts>': invalid type: sequence, expected socket address at line 1 column 1
Launching node #6...
error: Invalid value for '--hard-coded-contacts <hard-coded-contacts>': invalid type: sequence, expected socket address at line 1 column 1
Launching node #7...
error: Invalid value for '--hard-coded-contacts <hard-coded-contacts>': invalid type: sequence, expected socket address at line 1 column 1
Launching node #8...
error: Invalid value for '--hard-coded-contacts <hard-coded-contacts>': invalid type: sequence, expected socket address at line 1 column 1
Launching node #9...
error: Invalid value for '--hard-coded-contacts <hard-coded-contacts>': invalid type: sequence, expected socket address at line 1 column 1
Launching node #10...
error: Invalid value for '--hard-coded-contacts <hard-coded-contacts>': invalid type: sequence, expected socket address at line 1 column 1
Launching node #11...
error: Invalid value for '--hard-coded-contacts <hard-coded-contacts>': invalid type: sequence, expected socket address at line 1 column 1
Done!
Setting up authenticator against local Safe network...
[2021-02-12T20:08:31Z DEBUG sn_api::api::authd_client::authd_client_api] Creating new authd client for endpoint https://localhost:33000
[2021-02-12T20:08:31Z DEBUG sn_api::api::authd_client::authd_client_api] Attempting to start authd from '/home/richard/.safe/authd/sn_authd' ...
Starting SAFE Authenticator daemon (sn_authd)...
sn_authd started (PID: 31275)
[2021-02-12T20:08:32Z TRACE sn_api::api::authd_client::authd_client_api] SafeAuthdClient instance being dropped...
[2021-02-12T20:08:36Z DEBUG sn_api::api::authd_client::authd_client_api] Creating new authd client for endpoint https://localhost:33000
Sending request to authd to create a Safe...
[2021-02-12T20:08:36Z DEBUG sn_api::api::authd_client::authd_client_api] Attempting to create a Safe using remote authd...
[2021-02-12T20:08:36Z INFO  sn_api::api::common] Sending 'create' request to SAFE Authenticator on https://localhost:33000 ...
[2021-02-12T20:08:36Z TRACE sn_api::api::authd_client::authd_client_api] SafeAuthdClient instance being dropped...
Error: AuthdError: ClientError: No nodes/peers found defined for bootstrapping
richard@bombadil:~/safenet$ [2021-02-12T20:08:41Z DEBUG sn_api::api::authd_client::authd_client_api] Creating new authd client for endpoint https://localhost:33000
Sending action request to authd to unlock the Safe...
[2021-02-12T20:08:41Z DEBUG sn_api::api::authd_client::authd_client_api] Attempting to unlock a Safe on remote authd...
[2021-02-12T20:08:41Z INFO  sn_api::api::common] Sending 'unlock' request to SAFE Authenticator on https://localhost:33000 ...
[2021-02-12T20:08:41Z TRACE sn_api::api::authd_client::authd_client_api] SafeAuthdClient instance being dropped...
Error: AuthdError: ClientError: No nodes/peers found defined for bootstrapping

Any help would be appreciated !

Richard

1 Like

Can you try following these instructions?

2 Likes

Thank you JPL,

Actually, I don’t use the install script, I’d rather like build from sources,
here are the commands I use to build and install (branch master on both)

cd /home/richard/safenet/sn_node
cargo clean
git checkout -- Cargo.lock
git pull origin master
cargo build --release
strip target/release/sn_node
cp -f target/release/sn_node /home/richard/.safe/node/
 
cd /home/richard/safenet/sn_api
cargo clean
git pull origin master
cargo build --release
strip target/release/sn_authd
strip target/release/safe
cp -f target/release/sn_authd /home/richard/.safe/authd/
cp -f target/release/safe /home/richard/.safe/

@Aragorn you’ll need the branch of this PR for CLI and authd which are compatible with master branch of sn_node: feat(cli): command to configure networks in the config by providing a list of IP and ports by bochaco · Pull Request #710 · maidsafe/sn_api · GitHub

7 Likes

Thank you @bochaco it works :slight_smile:

sn_cli 0.18.0
sn_node 0.26.11
sn_authd 0.1.0
safe mode run-baby-fleming --testing
Creating '/home/richard/.safe/node/baby-fleming-nodes' folder
Storing nodes' generated data at /home/richard/.safe/node/baby-fleming-nodes
Launching local Safe network...
Launching with node executable from: /home/richard/.safe/node/sn_node
Version: sn_node 0.26.11
Network size: 11 nodes
Launching genesis node (#1)...
Connection info directory: /home/richard/.safe/node/node_connection_info.config
Genesis node contact info: ["127.0.0.1:12000"]
Common node args for launching the network: ["-vv", "--idle-timeout-msec", "5500", "--keep-alive-interval-msec", "4000", "--local"]
No RUST_LOG override provided
Launching node #2...
Launching node #3...
Launching node #4...
Launching node #5...
Launching node #6...
Launching node #7...
Launching node #8...
Launching node #9...
Launching node #10...
Launching node #11...
Done!
Setting up authenticator against local Safe network...
Starting SAFE Authenticator daemon (sn_authd)...
sn_authd started (PID: 15959)
Sending request to authd to create a Safe...
Safe was created successfully!
richard@bombadil:~/safenet$ Sending action request to authd to unlock the Safe...
Safe unlocked successfully
Authorising CLI application...
Waiting for authorising response from authd...
Safe CLI app was successfully authorised
Credentials were stored in /home/richard/.safe/cli/credentials

For the record, I’ve opened the pull request, clicked on Commits and gone to the last commit at the bottom of the page. Then clicked on <> (Browse the repository at this point in the history). And download Zip (Code)

Again, Thanks a lot !

8 Likes

Glad it’s working. Is that a typo though? Should be safe node

1 Like

you’re right @JPL I just “echo” the command here (with a typo), not the command itself :slight_smile:

1 Like

I could not start Auth from latest master last night. Expected?

Will building from this branch remedy my issue?

1 Like

Hi @Savage
sn_node has been released on v0.27.0, about an hour ago (?)
everything is fine, the tests on keys are ok
but i have issue with single file download here…

sn_cli 0.19.1
sn_authd 0.1.1
sn_node 0.27.0

4 Likes