New Release: Vault Phase 1 (mock vault)

Is anybody else able to run

$ safe_auth --daemon 41805

in one terminal window, and at the same time

$ safe_auth --apps

in another window without getting an error message?

To me it looks like it’s currently not possible to run two instances of safe_auth at the same time. Is this a known problem? @bochaco, @happybeing

I’m on Linux Mint 19.2 Cinnamon.

I haven’t tried since the update and busy today, sorry!

1 Like

This is what I was saying before that I understand it’s a limitation in phase1 vault about number of client connections, I see either with a local vault or shared vault, the second connection is being rejected by the vault. This is the vault’s log:

INFO 2019-09-13T11:55:35Z [src/client_handler.rs:691] 8721e9..: We already have Client(Bls(b9079d..)) on 127.0.0.1:47711. Cancelling the new connection from 127.0.0.1:43933.

and this is the log from safe_auth:

[2019-09-13T11:55:35Z DEBUG quic_p2p::utils] ERROR in communication with peer 127.0.0.1:40576: Connection(ApplicationClosed { reason: ApplicationClose { error_code: 0, reason: b"" } }) - Connection Error: closed by peer: 0. Details: Incoming streams failed
[2019-09-13T11:55:35Z TRACE safe_core::connection_manager::connection_group] 1: Recvd connection failure for 127.0.0.1:40576, Connection was actively cancelled
2 Likes

Thanks! I just haven’t seen this limitation mentioned explicitly anywhere.

2 Likes

No worries, you can see these logs also if you set RUST_LOG=debug (or level info or trace) when running any of the CLIs

2 Likes