Back again after another extended (non-testing) absence . . can't connect .

Support
1

People,

Here is my starting from scratch script:

#!/bin/bash

safeup update
safenode-manager reset

safenode-manager add \
    --count 8 \
    --owner philip_rhoades \
    --data-dir-path /safe \
    --log-dir-path  /safe \
    --home-network

safenode-manager start --interval 2000
safenode-manager status --details

/safe is on empty 8TB drive with a newly created btrfs volume.

With:

# safe files upload ./BBCintroDVD.mp4

I am getting:

Logging to directory: "/root/.local/share/safe/client/logs/log_2024-10-15_22-31-51"
safe client built with git version: 412b998 / stable / 412b998 / 2024-10-07
Instantiating a SAFE client...
Connecting to the network with 25 peers
__ Could not connect to the network                                                                                                                
Error: 
   0: Could not connect to the network in 30s

Location:
   sn_cli/src/bin/main.rs:136

  ────────────────────────────────── BACKTRACE ───────────────────────────────────
                                _ 3 frames hidden _                               
   4: safe::main::{{closure}}::h19cf98d0abb6915a
      at <unknown source file>:<unknown line>
   5: tokio::runtime::park::CachedParkThread::block_on::hcba030caec052831
      at <unknown source file>:<unknown line>
   6: safe::main::hdea0e89fbae3fa09
      at <unknown source file>:<unknown line>
   7: std::sys::backtrace::__rust_begin_short_backtrace::hb2c3057dc9afb0cf
      at <unknown source file>:<unknown line>
   8: std::rt::lang_start::{{closure}}::h2f2da1aba03e1420
      at <unknown source file>:<unknown line>
   9: std::rt::lang_start_internal::h93b3b742566fb30c
      at <unknown source file>:<unknown line>
  10: main<unknown>
      at <unknown source file>:<unknown line>

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
2

network contacts are offline so you need to specify a peer at the moment if you want to join this one

its something like this and that peer is good for the time being

--peer "/ip4/65.108.69.236/udp/55001/quic-v1/p2p/12D3KooWHyJRcmZ8foHgJhpEhZRZjfkcreMQ2FjMjCLgaPXX3WDP"
2 Likes
3

No improvement unfortunately . .

4

maybe try with this its been a wile since i started a node with a manually specified peer so i may be wrong

--peer="/ip4/65.108.69.236/udp/55001/quic-v1/p2p/12D3KooWHyJRcmZ8foHgJhpEhZRZjfkcreMQ2FjMjCLgaPXX3WDP"

5

I’m confused - that is the same as before?

6

no there is an = in the second one

1 Like
7

No, that didn’t change anything either . . maybe I should just wait till a new testnet starts?

Thanks anyway!

1 Like
8

Did you do safeup of the programs? The latest release came out about a week ago

1 Like
9

Yes, see my script on the OP . .

2 Likes
10

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