Safe auth create --test-coins error on Ipv4 LAN: [Error] AuthdError - [Error] AuthenticatorError - Failed to store Safe on a Map: Data error -> Unexpected error: Cannot send zero-value transfers

@folaht are you clearing your node data between runs here?

I can repro this locally, attempting to re-create an existing account. It fails due to a bug w/ not checking that an account already exists on create I think.

If you clear your data, or try with a different account, I think you’ll get further.

2 Likes

Node data on the server or client?

node data (10 chars)

Like this?

$ rm -rf ~/.safe/node/local-test-network/
[folaht@Rezosur-uq node]$ safe auth create --test-coins
Passphrase: 
Password: 
Sending request to authd to create a Safe...
[2020-12-21T10:19:57Z ERROR safe] sn_cli error: [Error] AuthdError - [Error] AuthenticatorError - Failed to store Safe on a Map: Unexpected: CmdError received: Transfer(TransferValidation(Unexpected("NetworkData error: Error on Node network: out of order msg, debit counter: 0, current counter: 0")))
[folaht@Rezosur-uq node]$ rm -rf ~/.safe/node/baby-fleming-nodes/
[folaht@Rezosur-uq node]$ safe auth create --test-coins
Passphrase: 
Password: 
Sending request to authd to create a Safe...
[2020-12-21T10:20:14Z ERROR safe] sn_cli error: [Error] AuthdError - [Error] ClientError - Data error -> Unexpected error: Could not get history for key PublicKey::Ed25519(d91e4b..)

[update]

I killed all the nodes and restarting them and that worked.

4 Likes

Yup. I’m able to get in w/ fresh details. But can repro your error. So for now that’s a wee workaround.

I’m working on detecting pre-existing accounts now.

2 Likes

I just created a file that should be accessible via LAN :slight_smile:
Created on the server and I just cat it on the server.
Let’s see if I can read it on the client computer.

2 Likes

Nice.

There’s some reports of PUT fails (well, out of order transfers), which is what I’m trying to get to just now. Let me know how you get on :+1:

3 Likes

Oh wait, whoops. This is the wrong thread.

This is refernence to this issue, where the steps are similar, but where client and server are the same machine.

With client I tried this:

client

$ safe node killall
$ rm -rf ~/.safe/node/local-test-network/
$ rm -rf ~/.safe/node/baby-fleming-nodes/
$ safe auth restart
Stopping SAFE Authenticator daemon (sn_authd)...
Success, sn_authd (PID: 348595) stopped!
Starting SAFE Authenticator daemon (sn_authd)...
sn_authd started (PID: 349304)
Success, sn_authd restarted!
[folaht@pjehrsohmehj node]$ safe auth create --test-coins
Passphrase: 
Password: 
Sending request to authd to create a Safe...
[2020-12-21T10:34:43Z ERROR safe] sn_cli error: [Error] AuthdError - [Error] ClientError - QuicP2P error: Unexpected("No nodes for bootstrapping found")

I’ll try deleting the server node data and then try everything again on the client.

[update]

Same error.

server

[folaht@Rezosur-uq safe]$ safe cat safe://hyryyryhg51kjgarri3bea798qt4oa8sitaqsz7budy83pmx1mqwyzs7j3cnra
Files of FilesContainer (version 0) at "safe://hyryyryhg51kjgarri3bea798qt4oa8sitaqsz7budy83pmx1mqwyzs7j3cnra":
+-----------+------------+------+----------------------+----------------------+--------------------------------------------------------------------+
| Name      | Type       | Size | Created              | Modified             | Link                                                               |
+-----------+------------+------+----------------------+----------------------+--------------------------------------------------------------------+
| /file.txt | text/plain | 13   | 2020-12-21T10:27:31Z | 2020-12-21T10:27:31Z | safe://hy8oycyxp9kd3cf7iwoje8jddyu9fioo7ksxxs3mgesxowr6mkeb8oxjqsa |
+-----------+------------+------+----------------------+----------------------+--------------------------------------------------------------------+
[folaht@Rezosur-uq safe]$ safe node killall
Success, all processes instances of sn_node were stopped!
[folaht@Rezosur-uq safe]$ rm -rf ~/.safe/node/baby-fleming-nodes/
[folaht@Rezosur-uq safe]$ cat ~/.safe/node/
node_connection_info.config  sn_node                      
[folaht@Rezosur-uq safe]$ safe node run-baby-fleming
Creating '/home/folaht/.safe/node/baby-fleming-nodes' folder
Storing nodes' generated data at /home/folaht/.safe/node/baby-fleming-nodes
Launching local Safe network...
Launching with node executable from: /home/folaht/.safe/node/sn_node
Network size: 8 nodes
Launching genesis node (#1)...
Genesis node contact info: ["192.168.178.24:12000"]
Launching node #2...
Launching node #3...
Launching node #4...
Launching node #5...
Launching node #6...
Launching node #7...
Launching node #8...
Done!

client

[folaht@pjehrsohmehj node]$ safe node killall
[2020-12-21T10:34:18Z ERROR safe] sn_cli error: Failed to stop nodes (sn_node) processes: sn_node: aucun processus trouvé
[folaht@pjehrsohmehj node]$ cat ~/.safe/node/
node_connection_info.config  sn_node       
[folaht@pjehrsohmehj node]$ safe auth restart
Stopping SAFE Authenticator daemon (sn_authd)...
Success, sn_authd (PID: 348595) stopped!
Starting SAFE Authenticator daemon (sn_authd)...
sn_authd started (PID: 349304)
Success, sn_authd restarted!
[folaht@pjehrsohmehj node]$ safe auth create --test-coins
Passphrase: 
Password: 
Sending request to authd to create a Safe...
[2020-12-21T10:34:43Z ERROR safe] sn_cli error: [Error] AuthdError - [Error] ClientError - QuicP2P error: Unexpected("No nodes for bootstrapping found")

with “no nodes for bootstrapping” your bet bet is to kill the network and relaunch it. That’s generally (at least in my experience) a sign that startup has gone wrong somehow.

1 Like

Kill the network?
I cleaned and restarted the nodes on the server side.
I cleaned and restarted the nodes on the client side and restarted auth.

I was able to do safe node join on the client by the way.

I guess I’ll have to kill everything on the client side and start again.

Are you running nodes on two machines? It’s not clear to me what you have running on the client side beyond the client itself?

If you’re consistently seeing No nodes for bootstrapping found at the client, it may be worth a go yep. (Also worth checking you node config ip/port are correct)

No. I’m only running nodes on the server.
I just tried cleaning everything on both ends, like this:

server

$ safe node killall
$ safe auth stop
$ rm -rf ~/.safe && cd ~/safe/sn_node-0.25.15/ && cargo build --release --features=simulated-payouts -- && cd ../sn_api-0.16.0/sn_cli && cargo build --release --features=simulated-payouts -- && cd ../sn_authd && cargo build --release --features=simulated-payouts -- && mkdir -p ~/.safe/authd ~/.safe/cli ~/.safe/node && mv ~/safe/sn_api-0.16.0/target/release/sn_authd ~/.safe/authd/ && mv ~/safe/sn_api-0.16.0/target/release/safe ~/.safe/cli/ && mv ~/safe/sn_node-0.25.15/target/release/sn_node ~/.safe/node
$ safe node run-baby-fleming
Creating '/home/folaht/.safe/node/baby-fleming-nodes' folder
Storing nodes' generated data at /home/folaht/.safe/node/baby-fleming-nodes
Launching local Safe network...
Launching with node executable from: /home/folaht/.safe/node/sn_node
Network size: 8 nodes
Launching genesis node (#1)...
Genesis node contact info: ["192.168.178.24:12000"]
Launching node #2...
Launching node #3...
Launching node #4...
Launching node #5...
Launching node #6...
Launching node #7...
Launching node #8...
Done!

client

$ safe node killall
$ safe auth stop
$ rm -rf ~/.safe && cd ~/safe/sn_api-0.16.0/sn_cli && cargo build --release --features=simulated-payouts -- && mkdir -p ~/.safe/cli && mv ~/safe/sn_api-0.16.0/target/release/safe ~/.safe/cli/
$ safe auth install
$ safe node install
$ echo \"192.168.178.24:12000\" | tee ~/.safe/node/node_connection_info.config
$ safe node join
$ safe auth start
$ safe auth create --test-coins
2 Likes

I’m not sure what you mean by killing the network.

Ah sorry. That’s what I meant :point_up_2:

So looks like you’re doing everything right with that. :thinking: not sure what’s causing this for you all of a sudden I’m afraid.

This is really odd because yesterday I had this working.

1 Like

Indeed. That’s what makes me think it’s startup. Can you publish your genesis node logs and we can see if there’s anything suspect there?

I found the issue.

floating point `192.168`, expected socket address
-- echo "192.168.178.24:12000" 
++ echo \"192.168.178.24:12000\"

what was it?

I’m now back at the same issue again.

sn_authd.log

ERROR 2020-12-21T12:45:45.824521848+01:00 [sn_authd/requests/create.rs:55] Error occurred when trying to create a Safe: [Error] AuthenticatorError - Failed to store Safe on a Map: Data error -> Unexpected error: Cannot send zero-value transfers
INFO 2020-12-21T12:45:45.824525587+01:00 [/home/maidsafe/.cargo/registry/src/github.com-1ecc6299db9ec823/quinn-0.6.1/src/connection.rs:228] drive; id=4
ERROR 2020-12-21T12:45:45.824593059+01:00 [sn_authd/requests/mod.rs:120] Error when processing incoming 'create' request with id 1708150519: [Error] AuthenticatorError - Failed to store Safe on a Map: Data error -> Unexpected error: Cannot send zero-value transfers
INFO 2020-12-21T12:45:45.824694491+01:00 [/home/maidsafe/.cargo/registry/src/github.com-1ecc6299db9ec823/quinn-0.6.1/src/connection.rs:228] drive; id=0
INFO 2020-12-21T12:45:45.825235584+01:00 [/home/maidsafe/.cargo/registry/src/github.com-1ecc6299db9ec823/quinn-0.6.1/src/connection.rs:228] drive; id=0
INFO 2020-12-21T12:45:45.825338535+01:00 [sn_authd/authd.rs:161] Response sent, request 1708150519 complete

[update]

I succeeded getting through creating testcoins!
I now have a different issue.

2 Likes

This topic was automatically closed after 60 days. New replies are no longer allowed.