After some testing . . general feedback .

Support
1

People,

Here is my startup script:

#!/bin/bash

safeup update
safenode-manager reset

safenode-manager add \
    --count x \
    --owner philip_rhoades \
    --data-dir-path /safe \
    --log-dir-path  /safe \
    --home-network \
    --rewards-address 0x70A7eF684ABE92cD7b5bbF4f0E74bb0b7b9ADB2c \
    evm-arbitrum-sepolia

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

I have tried counts of: 1,2,4,8,12,20 and 40 and left the setup running for at least hours - frequently 10+ hours and what I get is fairly consistent according to node-launchpad:

  • Node #1 is always stuck at “ADDED”
  • Other nodes always go to “RUNNING” but some change to “STOPPED” after some hours.
  • ALL the counters except for “Peers” never change from zero.

So, I guess I am still missing something? I can download files but the nodes never do any work . .

Thanks.

2 Likes
2

Are you sure about that
--data-dir-path
and
--log-dir-path

being /safe ?

That implies there is a directory at / that is owned by the user running the command but that would be unusual for either a non privileged user or a mount point as you aren’t starting the nodes using sudo so they won’t be services.

3

/–owner should not be there anymore.

4

Yep - it is a dedicated 8TB drive:

drwxr-xr-x. 1 safe  safe      1696 2024-11-01 22:54 .
dr-xr-xr-x. 1 root  root       232 2024-10-15 19:32 ..

on a dedicated SAFE computer and the services are run as root.

5

Oh ok, fair enough. Sounds like you know what you are doing!

I wonder about that use of the --owner flag as @tobbetj pointed out. It’s not needed. You wouldn’t think having it there would cause a problem but maybe try removing it.

1 Like
6

No improvement unfortunately . . I also tried adding “–upnp” but that didn’t make any difference either . .