UPDATE CARDANO NODE to 1.29.0 - FOR CNTOOLS users

Based on https://github.com/input-output-hk/cardano-node/issues/2350, the actual full consequences of such change are not quite clear.

ran prereqs and updated all the software that was out of date after running the script. Re-ran the build command

$CNODE_HOME/scripts/cabal-build-all.sh -l

but still have the error at the same point: This is the 4th attempt, I even expanded the drive thinking it might be a space issue.

I have same issue here, i gave both relay and BP 2 hours starting then check backā€¦
Hope they work

Just logging my troubles here, too.

The upgrade to 1.29.0 was fantabulous and the nodes were fine for days. Then, today I ran into the issue of 0 mempool, 0 transactions processed, and the only INs to my relays were my own relays. I confirmed all relays are accessible on the proper port. I did a whole bunch of troubleshooting (including stuff from above). So, now I am just waiting and hoping.

Relays have 12 GB RAM and BP has 16 GB RAM.

then must be an issue with topology_Updaterā€¦ go to cd $CNODE_HOME/logs
nano topology_Updaterā€¦ and show me the last messages

the relay canā€™t be reachedā€¦ check for IP or dns if something changed

https://pool.vet/#001

I was able to telnet to the port of both local relays from a remote machine, so ports and port-forwarding are okay.

FWIW, here is the log from one of the relay. The other relay is about the same.

ā€“ Reboot ā€“
Sep 06 04:03:51 relay-th1 cnode[1425]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 06 04:04:10 relay-th1 cnode[1523]: Listening on http://127.0.0.1:12798
Sep 06 10:22:31 relay-th1 cnode[1523]: Shutting downā€¦
Sep 06 10:23:15 relay-th1 cnode[581191]: Listening on http://127.0.0.1:12798
Sep 06 11:36:45 relay-th1 cnode[581191]: Shutting downā€¦
Sep 06 11:36:58 relay-th1 cnode[691960]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 06 11:36:59 relay-th1 cnode[692052]: Listening on http://127.0.0.1:12798
Sep 06 11:39:12 relay-th1 cnode[692380]: Listening on http://127.0.0.1:12798
Sep 06 12:01:34 relay-th1 cnode[716750]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 06 12:01:36 relay-th1 cnode[716820]: Listening on http://127.0.0.1:12798
Sep 06 12:24:00 relay-th1 cnode[748608]: Listening on http://127.0.0.1:12798

ok, and now try journalctl -e -f -u cnode

Sep 06 12:01:32 relay-th1 systemd[1]: Started Cardano Node.
Sep 06 12:01:34 relay-th1 cnode[716750]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 06 12:01:36 relay-th1 cnode[716820]: Listening on http://127.0.0.1:12798
Sep 06 12:23:16 relay-th1 systemd[1]: Stopping Cardano Nodeā€¦
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: State ā€˜stop-sigtermā€™ timed out. Killing.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716750 (bash) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716820 (cardano-node) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716821 (ghc_ticker) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716822 (cardano-node:w) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716823 (cardano-node:w) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716824 (n/a) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716825 (n/a) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716826 (n/a) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716827 (cardano-node:w) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716828 (cardano-node:w) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716829 (n/a) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716830 (n/a) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716831 (n/a) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716832 (n/a) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716833 (cardano-node:w) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 740191 (n/a) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Main process exited, code=killed, status=9/KILL
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Killing process 716833 (cardano-node:w) with signal SIGKILL.
Sep 06 12:23:21 relay-th1 systemd[1]: cnode.service: Failed with result ā€˜timeoutā€™.
Sep 06 12:23:21 relay-th1 systemd[1]: Stopped Cardano Node.
Sep 06 12:23:57 relay-th1 systemd[1]: Started Cardano Node.
Sep 06 12:24:00 relay-th1 cnode[748608]: Listening on http://127.0.0.1:12798

killing not ok, letā€™s test the MEM. go to config.json and set the MemPooltrace to false
save the file and restart the nodeā€¦ wait and check if now will start

Node has been running since I posted, but 0 mempool and 0 transactions, still.

aaa, okā€¦ so itā€™s up, but did u checked the messages from logs (for topology_Updater?)
you donā€™t have any processed TX because u donā€™t have other public nodes connected to your relays

Right-o! Just waiting as I mentioned in my post. :slight_smile:

I canā€™t connect to your nodes

H:>telnet relay-th1.cardanoistheway.com 40105
Connecting To relay-th1.cardanoistheway.comā€¦Could not open connection to the host, on port 40105: Connect failed

H:>nslookup relay-th1.cardanoistheway.com
Server: sagemcom
Address: 192.168.1.1

Non-authoritative answer:
Name: relay-th1.cardanoistheway.com.office.intern
Addresses: 86.35.3.192
86.35.3.193

Interesting. I tested using ip after confirming ip resolves correctly.

but u registered with the DNS, so test the DNS

Ha! ISP must have recently issued a new ip which hasnā€™t yet propagated. Changing to 1/2 hour from 1 hour.

exactly, when u will have this issue in the future check the IP-> DNS translation
If u have a friend close to you with a pool ash him to add your relays IP manually to custom_peers inside the topology updater
this way he will stay connected always to you , if the IP will not change

:+1: Will do. Thank you.

Unfortunately, Iā€™m in a ā€œpioneerā€ country. Nobody around. :slight_smile:

1 Like

thank alex! got my 1 relay, and BP up with this guide! great work as alwaysā€¦ gonna have to upgrade the ram on my other node since i only have 8gb on that once before trying 1.29. thanks again!

1 Like

set the TraceMempool to false, you will not see TX processed anymore but at least your node wii be up and running