I don’t see any errors… can u check the topology file ? cat topology.json do u have peers inside the file?
try again sudo systemctl restart cnode and share the output since the last restart journalctl -e -f -u cnode
Yeah. It’s just my relays in here listed as producers. My relays are synced up just fine.
And I just restarted the node and it looks like the same thing as the screenshot above.
if u type top u should see the CPU ~100% while the node is starting… do you see it?
no ok, something must pe wrong
Yeah. Because yesterday they were fine until I saw “Syncing 100%”
Then I restarted the node, and here I am now. I even tried reinstalling the cnode with your script, but I’m still dealing with this. I’m not entirely sure what’s going on besides it got desynced.
ok, try this…
cd ~/tmp
./prereqs.sh -f
then edit:
- env (CNODE_PORT and uncomment the line)
- topologyUpdater
restart the node and check again
Ayyy, it’s syncing up again! That was it! Sounds like my per-requisites were out of date with the newest cnode version. Maybe that can be a consideration for a pull on your update script.
yeah… I run the prereqs.sh often (once/month) …
Yeah, it slipped my mind that it was something I should be doing. I’ve been compiling a “booklet” of sorts of common problems and regular SPO checklists based on my experiences. Definitely adding this in.
1 Like
I even tried reinstalling the cnode with your script, but I’m still dealing with this.
Type sudo systemctl status cnode