Fleming Testnet v1 Release - *NOW OFFLINE IN PREPARATION FOR TESTNET V2*

Guys, that’s awesome for us all. We were waiting long time for test release and now it is here, congrats to all participants, they done very hard and precise work here.

I tried the test testnet release but have problem with safe auth unlock step from your tutorial.

Here are my steps:

  1. safe auth install
    safe auth install
    Latest release found: sn_authd v0.5.0
    Downloading https://sn-api.s3.eu-west-2.amazonaws.com/sn_authd-0.5.0-x86_64-unknown-linux-musl.zip
    [00:00:01] [========================================] 7.63MB/7.63MB (0s) Done
    Creating ‘/home/bbx/.safe/authd’ folder
    Installing sn_authd binary at /home/bbx/.safe/authd …
    Setting execution permissions to installed binary ‘/home/bbx/.safe/authd/sn_authd’…
    Done!
  2. safe node install
    Latest release found: sn_node v0.35.2
    Downloading https://sn-node.s3.eu-west-2.amazonaws.com/sn_node-0.35.2-x86_64-unknown-linux-musl.zip
    [00:00:01] [========================================] 10.91MB/10.91MB (0s) Done
    Creating ‘/home/bbx/.safe/node’ folder
    Installing sn_node binary at /home/bbx/.safe/node …
    Setting execution permissions to installed binary ‘/home/bbx/.safe/node/sn_node’…
    Done!
  3. safe networks add fleming-testnet https://sn-node.s3.eu-west-2.amazonaws.com/config/node_connection_info.config
    Network ‘fleming-testnet’ was added to the list. Connection information is located at ‘https://sn-node.s3.eu-west-2.amazonaws.com/config/node_connection_info.config
  4. safe networks switch fleming-testnet
    Switching to ‘fleming-testnet’ network…
    Fetching ‘fleming-testnet’ network connection information from ‘https://sn-node.s3.eu-west-2.amazonaws.com/config/node_connection_info.config’ …
    Successfully switched to ‘fleming-testnet’ network in your system!
    If you need write access to the ‘fleming-testnet’ network, you’ll need to restart authd, unlock a Safe and re-authorise the CLI again
  5. safe node join
    Joining network with contacts {188.166.146.65:36220, 138.68.138.75:59177, 138.68.142.144:55064, 178.62.80.163:57378, 138.68.154.35:49429, 138.68.152.156:51182, 178.62.58.241:42766, 46.101.72.229:52737, 46.101.48.69:55130, 139.59.181.74:12000, 46.101.78.184:41244, 138.68.138.179:51519, 138.68.146.15:34651, 138.68.146.110:58306, 188.166.169.192:47334, 138.68.131.119:50694, 138.68.142.76:38701, 138.68.139.28:40613, 178.62.101.46:59428, 138.68.131.218:57691, 46.101.55.62:53141, 138.68.133.17:37599, 138.68.154.164:44520, 46.101.1.135:58214, 46.101.17.63:38981, 138.68.139.187:33546, 138.68.141.132:36390, 46.101.93.86:56133, 138.68.139.58:38972, 138.68.131.228:40591, 188.166.146.115:41339, 138.68.137.198:43750, 138.68.137.76:34625} …
    Creating ‘/home/bbx/.safe/node/local-node’ folder
    Storing nodes’ generated data at /home/bbx/.safe/node/local-node
    Starting a node to join a Safe network…
    Launching with node executable from: /home/bbx/.safe/node/sn_node
    Version: sn_node 0.35.2
    Using RUST_LOG ‘sn_node=debug’
    Node to be started with contact(s): [“188.166.146.65:36220”,“138.68.138.75:59177”,“138.68.142.144:55064”,“178.62.80.163:57378”,“138.68.154.35:49429”,“138.68.152.156:51182”,“178.62.58.241:42766”,“46.101.72.229:52737”,“46.101.48.69:55130”,“139.59.181.74:12000”,“46.101.78.184:41244”,“138.68.138.179:51519”,“138.68.146.15:34651”,“138.68.146.110:58306”,“188.166.169.192:47334”,“138.68.131.119:50694”,“138.68.142.76:38701”,“138.68.139.28:40613”,“178.62.101.46:59428”,“138.68.131.218:57691”,“46.101.55.62:53141”,“138.68.133.17:37599”,“138.68.154.164:44520”,“46.101.1.135:58214”,“46.101.17.63:38981”,“138.68.139.187:33546”,“138.68.141.132:36390”,“46.101.93.86:56133”,“138.68.139.58:38972”,“138.68.131.228:40591”,“188.166.146.115:41339”,“138.68.137.198:43750”,“138.68.137.76:34625”]
    Launching node…
    Node logs are being stored at: /home/bbx/.safe/node/local-node/sn_node.log
  6. safe auth start
    Creating ‘/home/bbx/.safe/authd/logs’ folder
    Starting SAFE Authenticator daemon (sn_authd)…
    sn_authd started (PID: 3297)
  7. safe auth create --test-coins
    Passphrase:
    Password:
    Sending request to authd to create a Safe…
    Safe was created successfully!
  8. safe auth unlock
    Passphrase:
    Password:
    Sending action request to authd to unlock the Safe…
    Error: AuthdError: ClientError: Requested data not found

I tried restarting safe auth and no changes. Even created the vaults. Help is needed. Thank in advance.
For the step 5 i get the error in log:
[sn_node] ERROR 2021-04-11T10:13:23.884295696+02:00 [src/bin/sn_node.rs:110] Cannot start node due to error: Routing(TryJoinLater)

4 Likes