Ah, this one is because you haven’t set up your network with safe networks command, run these commands and then try again to restart authd: Fleming Testnet Stupid Question Thread - #30 by bochaco
I looks like you pasted it with some weird format i cannot read properly, but something going on with your network, sockets, perhaps again some firewall not allowing you to listen to a socket address…
Ok thanks. I will have a play with the settings tomorrow.
I read Address in use in your logs, perhaps you have some other old sn_authd running, or any other process listening and using the same port.
Bingo - thanks @bochaco . I’m obvioulsy too tired tonight - tomorrow’s another day! Cheers
Thanks @JPL , we’ll have to work on authd errors reporting, they are not helpful at the moment
ok thanks.
If this helps, I had some of the problems described above with authd due to old sn_authd processes being running.
killall sn_authd
fixed it
(osx)
Thanks, this worked for me on Linux too
This has been my story the last few times of trying
user@user:~$ safe auth create --test-coins
Passphrase:
Password:
Sending request to authd to create a Safe...
Error: AuthdClientError: [Error] ClientError - Response not received: read error: connection closed: timed out
Logs:
INFO 2021-04-10T15:10:49.659235755+01:00 [sn_authd/requests/mod.rs:77] Processing new incoming request (874075431): ‘create’
INFO 2021-04-10T15:10:49.659325846+01:00 [sn_authd/requests/create.rs:25] Creating a Safe…
INFO 2021-04-10T15:10:49.679340291+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/client/mod.rs:109] Client started for specific pk: PublicKey::Ed25519(83d7ce2dc22c8dc57bccd046f744132bb494d36857e90b01f98d64795ed785ec)
WARN 2021-04-10T15:10:49.679391908+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/config_handler.rs:73] Failed to open config file from ‘/home/user/.safe/client/sn_client.config’: No such file or directory (os error 2)
WARN 2021-04-10T15:10:49.679614352+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.11.7/src/endpoint.rs:235] Ignoring ‘forward_port’ flag from config since IGD has been disabled (feature ‘no-igd’ has been set)
WARN 2021-04-10T15:10:49.886468437+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.133.17:37599
INFO 2021-04-10T15:10:49.958339221+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.142.76:38701
WARN 2021-04-10T15:10:49.958389037+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 1 new_elders.
INFO 2021-04-10T15:10:49.964371710+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.137.198:43750
WARN 2021-04-10T15:10:49.964443280+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 2 new_elders.
INFO 2021-04-10T15:10:49.964604059+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.131.228:40591
WARN 2021-04-10T15:10:49.964645313+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 3 new_elders.
INFO 2021-04-10T15:10:49.964663368+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.55.62:53141
WARN 2021-04-10T15:10:49.964676789+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 4 new_elders.
INFO 2021-04-10T15:10:49.966531+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.131.218:57691
WARN 2021-04-10T15:10:49.966571145+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 5 new_elders.
INFO 2021-04-10T15:10:49.968815442+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.93.86:56133
WARN 2021-04-10T15:10:49.968865353+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 6 new_elders.
INFO 2021-04-10T15:10:49.969744400+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.1.135:58214
WARN 2021-04-10T15:10:50.493972026+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 46.101.1.135:58214
INFO 2021-04-10T15:10:50.563158244+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.138.179:51519
WARN 2021-04-10T15:10:50.563208554+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 1 new_elders.
INFO 2021-04-10T15:10:50.573618037+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 178.62.80.163:57378
WARN 2021-04-10T15:10:50.573670179+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 2 new_elders.
INFO 2021-04-10T15:10:50.575005281+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.48.69:55130
WARN 2021-04-10T15:10:50.575040795+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 3 new_elders.
INFO 2021-04-10T15:10:50.576924792+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.139.28:40613
WARN 2021-04-10T15:10:50.576982444+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 4 new_elders.
INFO 2021-04-10T15:10:50.805170667+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 185.172.165.82:39812
WARN 2021-04-10T15:10:50.805225685+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 5 new_elders.
WARN 2021-04-10T15:12:49.660140025+01:00 [qjsonrpc/src/server_endpoint.rs:160] Failed to read incoming request: timed out
WARN 2021-04-10T15:12:50.498775270+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:523] Failed to connect to Elder @ : ElderConnection
WARN 2021-04-10T15:12:50.498859322+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 5 new_elders.
WARN 2021-04-10T15:12:50.498928275+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:523] Failed to connect to Elder @ : ElderConnection
WARN 2021-04-10T15:12:50.498995910+01:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 5 new_elders.
INFO 2021-04-10T15:13:08.558794044+01:00 [sn_authd/requests/mod.rs:77] Processing new incoming request (2577879957): ‘create’
INFO 2021-04-10T15:13:08.558847072+01:00 [sn_authd/requests/create.rs:25] Creating a Safe…
WARN 2021-04-10T15:15:08.560762594+01:00 [qjsonrpc/src/server_endpoint.rs:160] Failed to read incoming request: timed out
INFO 2021-04-10T15:22:22.182787926+01:00 [sn_authd/requests/mod.rs:77] Processing new incoming request (3089456093): ‘create’
INFO 2021-04-10T15:22:22.182860095+01:00 [sn_authd/requests/create.rs:25] Creating a Safe…
WARN 2021-04-10T15:24:22.184769249+01:00 [qjsonrpc/src/server_endpoint.rs:160] Failed to read incoming request: timed out
I was finally able to join with my node to the testnet, after that, in the process of trying to unlock the authenticator with the command:
safe auth create --test-coins
I got this log:
ERROR 2021-04-10T15:54:09.955862200+02:00 [sn_authd/requests/create.rs:55] Error occurred when trying to create a Safe: AuthenticatorError: Failed to store Safe on a Map: Insufficient balance to complete this operation
ERROR 2021-04-10T15:54:09.955919500+02:00 [sn_authd/requests/mod.rs:120] Error when processing incoming ‘create’ request with id 799086648: AuthenticatorError: Failed to store Safe on a Map: Insufficient balance to complete this operation
INFO 2021-04-10T15:54:09.956559900+02:00 [sn_authd/authd.rs:207] Response sent, request 799086648 complete
INFO 2021-04-10T15:55:04.581136400+02:00 [sn_authd/requests/mod.rs:77] Processing new incoming request (2724072952): ‘status’
INFO 2021-04-10T15:55:04.581199500+02:00 [sn_authd/requests/status.rs:29] Preparing authd status report…
INFO 2021-04-10T15:55:04.581229600+02:00 [sn_authd/requests/status.rs:55] Status report sent: AuthdStatus { safe_unlocked: false, num_auth_reqs: 0, num_notif_subs: 0, authd_version: “0.5.0” }
INFO 2021-04-10T15:55:04.581622400+02:00 [sn_authd/authd.rs:207] Response sent, request 2724072952 complete
by trying to run the same command again, it tells me the ‘Client data already exists’:
INFO 2021-04-10T15:55:24.629031700+02:00 [sn_authd/requests/mod.rs:77] Processing new incoming request (1718066750): ‘create’
INFO 2021-04-10T15:55:24.629103200+02:00 [sn_authd/requests/create.rs:25] Creating a Safe…
INFO 2021-04-10T15:55:24.640947600+02:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/client/mod.rs:109] Client started for specific pk: PublicKey::Ed25519(61bff8a625f77e3f408bb463e5c683f15f997fe064eec2c9489b5a151257fe89)
WARN 2021-04-10T15:55:24.641122700+02:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/config_handler.rs:73] Failed to open config file from ‘/home/loigzorn/.safe/client/sn_client.config’: No such file or directory (os error 2)
WARN 2021-04-10T15:55:24.641588700+02:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.11.7/src/endpoint.rs:235] Ignoring ‘forward_port’ flag from config since IGD has been disabled (feature ‘no-igd’ has been set)
Does anyone know what this could be about?
To my understanding, I should either be able to create test coins or the first error message is misleading and the coins have already been created.
BTW I like this thread a lot already!!
FYI I setup UBUNTU on my host machine and had very similar problems to what I was getting on the UBUNTU VM or windows. I removed any router controls, Parental control web protect etc. Tried through router and hostspot. sometimes i could create keys sometime not.
Hopefully next iteration will improve things for me. I’m giving up until then. 
My experience has been hit and miss too (on Ubuntu 18.04). I did get to the point where I was even running a node, but unfortunately, after a while things stopped working.
I don’t think it’s the Router/NAT because the experience was the same on a machine in the cloud (Ubuntu 20.x).
What is the correct procedure to re-join after shutdown?
Do you just safe node join again?
I was running a node, laptop was put to sleep, so I assume the node went down, although I still had 3 sn_node processes running when turned it back on (why and why 3 of them??).
I did a safe node killall and then safe node join; would that be the right thing to do?
There are no stupid questions, just stupid people… I mean answers… 
>safe keys create --help shows option --pk <pk>: Don't generate a key pair and just use the provided public key
Why if I use it, key pair still generates?
>safe keypair
Key pair generated:
Public Key = 00353bb1f8670854af5aeefa171ac1e37d7ab33d68b53dea6c80e3660b87aff9
Secret Key = a674b1941ccd449c970e1f7e78bba770f060f56267a5c5c57959ec90a06d8e99
>safe keys create --preload 1.5 --pk 00353bb1f8670854af5aeefa171ac1e37d7ab33d68b53dea6c80e3660b87aff9 --pay-with 0b7287c8a0275cf550208260cb7d23848c6a3d429de2b9aa7405c01ff6d4e1d9
New SafeKey created at: "safe://hyryyyyr8gps5aasyb964py9a9ic1kjbnso3fjwxw81nemnbuouw53am8zw"
Preloaded with 1.5 coins
Key pair generated:
Public Key = 87336dbc62c00ffda683f8fd59252422b43254d1f43c8485883384e9bce167bd
Secret Key = e650580ac0f1f6319dd3153eceea93e617d3b7b18877fcede1d35af25f89d7c0
Not sure there is an answer to this question, but what would be the way of reinstalling the auth package?
Possibly without having to delete the (running) node.
I just double checked as it seemed like a bug, but --pk is not supported yet actually: https://github.com/maidsafe/sn_api/blob/master/sn_cli/subcommands/keys.rs#L78
You can just stop/kill any existing authd process with $ safe auth stop or $ killall sn_authd, and then just re-install it with $ safe auth install
This is not really related to the testnet, but a rookie CLI user would like to know:
It’s because ctrl-c and ctrl-v have different common uses in terminals, especially the former (it aborts the active process).
In Linux, it is common to use shift-ctrl-c instead to avoid this. Iirc, Windows uses something less intuitive, but similar.