A thread to keep all issues regarding the launchpad TUI together
start here
6 Likes
Run on W10 AMD Ryzen 7 5700G
unpack
at first it does not start at all
Second if I try run as Administrator it works
Than ctrl+g allocate resources (put 100GB)
than ctrl+g and couple minut waiting …looks frozen
3 Likes
First - thoroughly cleanse your box of all traces any previous nodes
Then fire it up - I needed sudo on linux
Hit “O” to start with and allocate disk space - it assumes (for now at least) that we need 5GB per node. That leaves room for a shitload of logging - Enter a multiple of 5 GB
Then hit Ctrl+g to start the nodes.
This is very much a Work in Progress. For instance I expect to see a tuneable delay between node start-up parameter soon.
The previous problem with stdout overwriting some of the screen is pretty much mitigated now. Dunno how the internals work but Id like to see a dedicated area for stdout - if that is feasible
2 Likes
It did something on a background. I will allocate less space and wait longer than.
.
.
.
2024-05-16T20:45:59.300482Z INFO node-launchpad\src\components\home.rs:457: Successfully added service: [“safenode1”, “safenode2”, “safenode3”, “safenode4”, “safenode5”, “safenode6”, “safenode7”, “safenode8”, “safenode9”, “safenode10”, “safenode11”, “safenode12”, “safenode13”, “safenode14”, “safenode15”, “safenode16”, “safenode17”, “safenode18”, “safenode19”, “safenode20”]
2024-05-16T20:45:59.305530Z ERROR sn_transfers\src\wallet\hot_wallet.rs:628: No main key found when loading wallet from path “C:\ProgramData\safenode\data\safenode20\wallet”
2024-05-16T20:55:19.009225Z DEBUG sn_node_manager\src\cmd\node.rs:295: Sleeping for 10 milliseconds
2024-05-16T20:55:49.227330Z ERROR node-launchpad\src\components\home.rs:473: Error while starting services
0: e[91mFailed to start one or more servicese[0m
2024-05-16T20:55:49.227364Z DEBUG node-launchpad\src\app.rs:126: HomeActions(ServiceManagerOperationCompleted)
2024-05-16T20:55:49.227551Z INFO node-launchpad\src\components\home.rs:69: Loaded node registry. Runnign nodes: 20
2024-05-16T20:55:53.585600Z INFO node-launchpad\src\app.rs:97: Got action: Quit
2024-05-16T20:55:53.585622Z DEBUG node-launchpad\src\app.rs:126: Quit
1 Like
Last four raw of logs are same after each restart. Something does not start, so I keep some chunks but 0 networking after all, 0 balance in wallets. But 20nodes grow from less than 3.9GB to 4.2GB
2024-05-17T06:00:18.244734Z ERROR node-launchpad\src\components\home.rs:416: Error while starting services
0: e[91mFailed to start one or more servicese[0m
2024-05-17T06:00:18.244765Z DEBUG node-launchpad\src\app.rs:126: HomeActions(ServiceManagerOperationCompleted)
2024-05-17T06:00:18.250170Z INFO node-launchpad\src\components\home.rs:69: Loaded node registry. Runnign nodes: 20
Every time I restart safenode with mine 20 nodes, it does download few new chunks and than hibernate till next restart.
1 Like
I am failing to start nodes with this tool.
I see this in the logs
2024-05-17T23:19:22.187223Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/reqwest-0.11.27/src/connect.rs:449: starting new connection: https://sn-node.s3.eu-west-2.amazonaws.com/
2024-05-17T23:19:22.187283Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/client/connect/dns.rs:122: resolving host="sn-node.s3.eu-west-2.amazonaws.com"
2024-05-17T23:19:22.235522Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/client/connect/http.rs:542: connecting to 3.5.246.110:443
2024-05-17T23:19:22.257721Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/client/connect/http.rs:545: connected to 3.5.246.110:443
2024-05-17T23:19:22.257767Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustls-0.21.12/src/client/hs.rs:73: No cached session for DnsName("sn-node.s3.eu-west-2.amazonaws.com")
2024-05-17T23:19:22.257862Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustls-0.21.12/src/client/hs.rs:132: Not resuming any session
2024-05-17T23:19:22.279463Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustls-0.21.12/src/client/hs.rs:472: ALPN protocol is Some(b"http/1.1")
2024-05-17T23:19:22.279496Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustls-0.21.12/src/client/hs.rs:615: Using ciphersuite TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
2024-05-17T23:19:22.283161Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustls-0.21.12/src/client/tls12.rs:423: ECDHE curve is ECParameters { curve_type: NamedCurve, named_group: secp256r1 }
2024-05-17T23:19:22.283190Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustls-0.21.12/src/client/tls12.rs:714: Server DNS name is DnsName("sn-node.s3.eu-west-2.amazonaws.com")
2024-05-17T23:19:22.305411Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/proto/h1/io.rs:340: flushed 122 bytes
2024-05-17T23:19:22.427677Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/proto/h1/io.rs:208: parsed 10 headers
2024-05-17T23:19:22.427713Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/proto/h1/conn.rs:224: incoming body is content-length (10028200 bytes)
2024-05-17T23:19:29.986925Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/proto/h1/conn.rs:300: incoming body completed
2024-05-17T23:19:29.986997Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/client/pool.rs:380: pooling idle connection for ("https", sn-node.s3.eu-west-2.amazonaws.com)
2024-05-17T23:19:29.988378Z DEBUG /home/willie/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustls-0.21.12/src/common_state.rs:498: Sending warning alert CloseNotify
2024-05-17T23:19:30.132357Z DEBUG sn_node_manager/src/cmd/node.rs:101: Parsing peers...
2024-05-17T23:19:30.132402Z INFO sn_peers_acquisition/src/lib.rs:91: No peers given
2024-05-17T23:19:30.132410Z INFO sn_peers_acquisition/src/lib.rs:92: The `local-discovery` feature is enabled, so peers will be discovered through mDNS.
2024-05-17T23:19:31.908752Z ERROR node-launchpad/src/components/home.rs:463: Error while adding service
0: Failed to add one or more services
Suggestion: However, any services that were successfully added will be usable.
To me this suggests its not finding peer automagically. I have tried running the command by prepending SAFE_PEERS=/ip4/144.126.233.244/udp/49925/quic-v1/p2p/12D3KooWLM4hrJMZP7DYKQzk6phrSPDTfWvpKy8trmK6JKCukQ8P ./target/release/node-launchpad which I think is a good peer but no joy.
I dont know how to get launchpad to start safenode with --upnp , --home_network or by specifying ports.
EDIT: This functionality isnt here yet
If this was discord I’d post a meme of impatientness but it isn’t so I won’t. Nae luck.
3 Likes
1 Like
I would leave this tool alone for now. Wait for a new testnet and try again. PunchBowl is too flakey right now to draw any conclusions about the TUI.
A new testnet will be along soon, Im sure.
1 Like
Thank you. Best regards, Mark
1 Like
Thank you for trying 
1 Like
Hey, it is probably advisable actually to wait until the new testnet, which will be soon. There is a new version of the TUI with quite a lot of changes. However, if you want to get an idea for what went wrong here, the logs for the TUI go here: C:\Users\<username>\AppData\Roaming\safe\launchpad\logs
If you posted the output, we might be able to see something from that.
3 Likes
Thanks for the help.
3 Likes
Can someone tell me what the node status box above the node list box is supposed to show
1 Like
Probably some vdash-like info fairly soon.
1 Like
Nothing right now.
2 Likes
OK, probably some vdash-like stuff in the fullness of time then
2 Likes
… the service management is not really good to be honest … same issue as with the node-manager too … because my home network can’t stand many nodes (and i’m running some on a rpi alreay) i first started 5 nodes with the launchpad … and then reduced resource allocation for it to stop all but 1 service …
(this is how it looked after stopping the services … and how it looks after a reboot next day too)
as you can see this doesn’t reflect the current state of the system:
there are clearly all 5 nodes running on my machine after a reboot … that activated autostart of all services by default is really a dangerous thing imho and a huge anti-feature …
(on my systems with node-manager on it i have a script that automatically deactivates it after adding a new node to make sure i don’t end up with a fully blocked system [again] …)
so after having done such a stunt the pc will be unusable forever (from this user) until a root manages to remove all the user services …
…this TUI has the potential of ruining perfectly fine linux installations and should come with a huge warning sign …
…i’ll try to get rid of those services now on my system …
oh well - getting rid of everything was easy once i knew what to look for
4 Likes
Can you be more specific here please? What do you mean by “same issue as with the node manager”. What issue?
That has been on my list to address, it’s just difficult to get to everything.
1 Like
just the services not only being started but being “enabled” too (so being in autostart) …
sorry - didn’t want to be too harsh here …
i think it was in the discord channel where we supported a OSX User not long ago who tried the launchpad and didn’t manage to get rid of the services again all by himself … so it happened to a couple of people already and maybe shouldn’t be too far down the list …even if it is not a blocker to the network itself … if there are old nodes ‘just eating up your bandwidth’ without you expecting/noticing it and your system is not blocked at all … this can be problematic enough …