ERROR: A Cardano node is already running, please terminate this node before starting a new one with this script

Staking & Delegation Operate a Stake Pool
26

hey lauris sorry to bother you again how do i know if my producer is really trying to look for a block
all my relays are connected showing in peers. this is how it looks right now and it moves a little from time to time is that corrrect ? i dont want to be waiting if its wrong or if its supposed to always be pumping but it is sync.

┌────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ │
│ CARDANO release: Byron; Shelley Node: Port: 6000 │
│ │
│ Mempool (Bytes): 0 max Mempool (Txs): 0 max │
│ 0 0 version: 1.19.0 │
│ commit: 4814003 │
│ Memory usage: 791.9 MB platform: Linux │
│ 791.9 MB / max 791.9 MB │
│ uptime: 00:03:22 │
│ CPU usage: 100% │
│ 1.0% epoch / slot: 213 / 142051 │
│ block number: 4604818 │
│ Disk R: 28085.3 KB/s Disk W: 535.5 KB/s chain density: 5.1 % │
│ 3.7 KB/s 0.7 KB/s │
│ blocks minted: 0 │
│ Network In: 540.5 KB/s Network Out: 24.7 KB/s slots lead: 0 │
│ 0.1 KB/s 0.8 KB/s slots missed: 0 │
│ cannot lead: 0 │
│ │
│ TXs processed: 0 │
│ │
│ peers: 2 │
│ │
│ │
│ Press Q to quit, L/D to change color theme, P for peer list, Esc return to main screen │
│ │
└────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

27

from what i see, i don’t like that you don’t have any processed TX.

  • to how many relays are your relay nodes connected (check your topology file)?
  • do you have your BP node’s ip in your relays topology file?
  • did you check if relays can connect to your BP node? (telnet test)?

Cheers,
Lauris

1 Like
28

Any good links on youtube about that?
telnet test ill look it up now
i have two relays they all see the producer node likewise and the producer sees my two relay ips

Both relays have producer node IP
nano topology.json

yes all IPs are listed in peers all says ready

i also did that run arguments thingy too

29

in your relay nodes you need ~20+ relay nodes and ideally that your relay nodes are in someones else topology file. I would suggest to set up some topology buddy script, so your relay nodes ip is in some other relays as well.

30

ill look it up thank you soo much!
Sorry for bothering i wanna learn fun stuff i know a little but not that much

any recommend links for buddy scripts for ada in specific?

31

one of the tools:
https://cardano-community.github.io/guild-operators/#/Scripts/topologyupdater

1 Like
33

i kinda understand now you want more peers right & vice versa you want buddies to put you in their topology also with the IP and all that?

sorry for bothering you lauris.

34

yes, you got it right!
and you are not bothering :slight_smile:

let us know if you need anything else.

1 Like
35

Hello everyone,
I had the same issue, where using killall cardano-node or using “Q” on the Live View would not remove the socket file.

Using the cnode.sh script provided with CN Tools was then triggering the error message “ERROR: A Cardano node is already running, please terminate this node before starting a new one with this script.”

I Followed @ADAfrog advice to check the correct path are in the .bashrc file. In my case, I changed it to have the PATH pointing to “~.cabal/bin:$PATH” instead of “~.local/bin:$PATH”.
I’m sure it didn’t hurt, but the socket file is still not deleted when the node is killed.

I noticed however that CN Tools updated their cnode.sh script a few hours ago to handle this more elegantly and remove the socket file as part of the startup process: https://github.com/cardano-community/guild-operators/commit/1d3dd6ba845f481dc5cf3d678acfb256da9ce22a

Updating the CN Tools to get the latest code did the trick for me. I did it by downloading and running the latest prereqs.sh file, see process here: https://cardano-community.github.io/guild-operators/#/basics?id=pre-requisites
You may want to pay attention to the parameter and maybe backup any script or file you have customized beforehand.
Now the node0.socket file is deleted by the cnode.sh script as part of the startup process, so I can use it as a base for running the node as a systemd service without having an error.

I hope this helps someone.

Thanks,

36

[[ -S “$CNODE_HOME/sockets/node0.socket” ]];
rm $CNODE_HOME/sockets/node0.socket

by brother lauris try that make sure nothing is running