Nope… 
But… try to type top… the CPU it looks like is doing something?
What CPU hw has ur node?
6 core CPU - something is happening:
I think still syncing… but it takes to much…
Try to restart the node
sudo systemctl restart cnode
sudo systemctl status cnode
Already did a couple of times. Still the same result:
“Failed to query protocol-parameters from node, not yet fully started?” bothers me the most. What does that mean?
I have changed back and restarted the nodes. I will let you know.
1 Like
Ok, let’s try to start it manually with the old cnode.sh script
sudo systemctl stop cnode
create a tmux session
create new-session -s test
and inside tmux go to scripts folder and type ls -l
look for the cnode.sh_bkpxxxx script and run
./cnode.sh_bkpxxxx
What is the output? Same message?
Two of my relay nodes already restarted with high CPU problems. I have 2 vcpu and 8 gb.
Same message: 
What do u mean… how is the cpu?
Ok… type nano env… how is the socket line?
CPU was at 106%. then i get the message that says is can’t connect to the node and restarts.
I think the CPU will be higher till the node will sync…
journalctl -e -f -u cnode.service
do u see the kill message?
Try to uncomment the socket line by deleting the # from the begining and start again the node
No luck:
Try nano ~ /.bashrc
show me the last lines
Everything looks fine… start the node and wait more time
All right! Node is running. I will keep it running over night. If it’s not working tomorrow, I’m afraid I will have to rollback to 1.25.1 and wait for next version (1.26.2)… Thanks for your help!
1 Like