That must be AE doing it’s job. That was said to be the cure and she’s finally eeked her way in with some promising results. Was enjoyable just seeing you guys have fun with it.
6 Likes
Is network dead?
Can’t cat anything.
But it may be because of my mistakes.
1 Like
Looks like, I can’t cat either
3 Likes
yeh, always-joinable will be needed to allow folks to join until the nodes fill up.
And you’ll have to build that for now (though if it ends up being helpful we could perhaps provide a precompiled bin for that; just perhaps not on the GH release eg ot avoid confusion).
The other option is setting your nodes to be a few hundred mb and then hoping @Southside does his usual thing. That’ll let the network be joinable fast enough (but then you’ll also run the risk of hitting the storage roof until more nodes come on)
6 Likes
Yeh, the variable for it falls back on a factor of the query timeout still, so if you set SN_CLI_QUERY_TIMEOUT to be longer on PUT you’ll stand more chance of AE flow going all the way.
4 Likes
Let me see if I understand this correctly…
We could not join yesterday simply because the extra nodes were not needed. The network already had plenty storage capacity. The solution is to set the nodes to a a few hundred Mb and wait for me to upload the entire catalogue of live Grateful Dead and Frank Zappa concerts , in .flac format of course. Then the network will cry out for more space and us punters should be able to join as infants and quickly be promoted to adults.
Is that about it?
EDIT:
So then we get to validate that scenario - Its what a test network is for, innit?
3 Likes
3 Likes
What was the end result for the network did she crash or did you take her offline?
Yes I took it down after the reports of not being able to cat any longer.
Just building always-joinable so maybe we can revive it a little later and also try @joshuef advice to put with SN_CLI_QUERY_TIMEOUT
12 Likes
I tried few urls, but do not worked (just downloaded browser and put into it)
THe browser is well out of date - don’t think its been viable for well over a year.
@anon26713768 might announce a new network later with tweaks as suggested above by @joshuef but it will only be accessible from the CLI.
The instructions in the first post of this thread are probably the best place to start if we get a new network soon.
3 Likes
It is running again, can someone try add a node?
I am not sure if joining nodes also need to be built always-joinable @joshuef
new config, so update that first.
1 Like
User_1@DESKTOP-4QAR72F MINGW64 ~
$ RUST_LOG=safe_network=info,qp2p=info ~/.safe/node/sn_node --skip-igd
Starting logging to stdout
Error:
0: Cannot start node (log path: unknown). If this is the first node on the network pass the local address to be used using --first
1: Routing error:: Configuration error: Network's genesis key was not provided.
2: Configuration error: Network's genesis key was not provided.
Location:
sn\src\bin\sn_node.rs:216
Backtrace omitted.
Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
just tried got the following
did you start fresh?
rm -rf $HOME/.safe
curl -so- https://sn-api.s3.amazonaws.com/install.sh | bash
safe node install
yeah i will try again to make sure.
1 Like
I tried connecting with the original instructions and I keep getting in the console output:
join {network_genesis_key=PublicKey …
Sending JoinRequest …
join {network_genesis_key=PublicKey …
Setting Node name to xyz (age XX)
Where the node name keeps rotating and so does the age.
… eventually after few minutes it said encountered timeout waiting 3 mins for retry… then starts repeating the above again.
1 Like
yeah I was getting the same when adding a node!
node standing by to join
I don’t think it is working right, sorry guys. taking it down but will keep trying.
2 Likes
ok i was able to upload a few test files but node joining failed
1 Like