Error: Safe Node version 0.25.18 does not have sufficient amount of elders on Manjaro ARM?

Support
1

Version cli: 0.17
Node version: 0.25.18
Server: Manjaro-ARM
Modifications: Nodes running on LAN ipv4.

Steps

node run-baby-fleming
auth restart
auth create --test-coins

sn_authd.log

INFO 2021-01-05T08:29:51.302873039+01:00 [/home/folaht/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.44.6/src/connection_manager.rs:549] Connected to elder: 192.168.178.24:12000
INFO 2021-01-05T08:29:51.302886465+01:00 [/home/folaht/.cargo/registry/src/github.com-1ecc6299db9ec823/quinn-0.6.1/src/connection.rs:228] drive; id=2
WARN 2021-01-05T08:29:51.303014074+01:00 [/home/folaht/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.44.6/src/connection_manager.rs:568] Connected to only 2 elders.
INFO 2021-01-05T08:29:51.303135590+01:00 [/home/folaht/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.44.6/src/connection_manager.rs:592] Listening for incoming connections started
INFO 2021-01-05T08:29:51.304780972+01:00 [/home/folaht/.cargo/registry/src/github.com-1ecc6299db9ec823/quinn-0.6.1/src/connection.rs:228] drive; id=2
ERROR 2021-01-05T08:29:51.304772601+01:00 [sn_authd/requests/create.rs:55] Error occurred when trying to create a Safe: [Error] ClientError - Unexpected: Could not connect to sufficient elders.
ERROR 2021-01-05T08:29:51.304874637+01:00 [sn_authd/requests/mod.rs:120] Error when processing incoming 'create' request with id 2981648741: [Error] ClientError - Unexpected: Could not connect to sufficient elders.
4 Likes
2

I had that once, did not report as I was frantically stopping and starting networks and put it down to being my fault.

1 Like
3

reinstalling somehow magically did the trick. I have no idea why.

2 Likes
4

I can report seeing this as well at stupid o’clock last night.
At te time I put it down to trying to mess with nodes on 3 different machines and creating a safe on the wrong ssh terminal - at night - in the dark and terminally fatigued.

So I’ll keep a closer look out for this and see if it pops up again

1 Like
5

Yes I was pretty sure it was user error but now with 3 reports, perhaps not.

1 Like
6

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