hmm did you ran ./prereqs.sh first?
Will 1.27 still mint blocks for the near future? I ask because I’m a small pool in the situation where some AWESOME person who has delegated ~100k Ada to my pool. I’m trying to minimize downtime but I do plan on upgrading my nodes and then updating to 1.29. I just want to be sure I can secure my 1st block I’m lucky enough to to be slotted in e290; OR do I need to update everything immediately and cross my fingers that the update goes smoothly ??? Thanks!
U need 1.29.0 starting with epoch 290 (Alonzo) which will begin in ~ 2 hours; try to uograde one relay first… then the producer
1 Like
Thanks @Alexd1985 for the reply. I will get on to updating ASAP and plan to be referencing your guide. Cheers!
I have 8 GiB Azure nodes… I can add an SSD swap , but is that really the requirement? 8.1 GB RAM
I saw on mine ~9,1G, but if u don’t have issues it’s fine
1 Like
Hi Had this stuck in starting mode and my solution was this.
I noticed that the alonzo mainnet json file was different from the day I downloaded it for the relays and the day I downloaded it for the BP node. This was causing a hash conflict. Once I gave all nodes the same alonzo json file everything worked.
1 Like
I think that I have done everything in this thread but my relays still show ‘starting’ and I have no In/Out Peers. When I first setup the relays and producer, I changed the port. Any chance that has anything to do with it. I did upgrade my equipment: 8 CPU and 16GB Ram. Any thoughts would be appreciated.
CPU is running at nearly 100% but memory is almost nothing.
Type journalctl -e -f -u cnode and show me the output
– Reboot –
Sep 13 18:52:03 vps-33644252 cnode[1150]: Listening on http://127.0.0.1:12798
Sep 13 19:06:08 vps-33644252 cnode[13587]: Listening on http://127.0.0.1:12798
Here are a couple of lines before the reboot:
Sep 13 10:29:52 vps-33644252 cnode[1753990]: Listening on http://127.0.0.1:12798
Sep 13 10:41:59 vps-33644252 cnode[1753902]: /opt/cardano/cnode/scripts/cnode.sh: line 57: 1753990 Killed cardano-node “${CPU_RUNTIME[@]}” run --topology “${TOPOLOGY}” --config “${CONFIG}” --database-path “${DB_DIR}” --socket-path “${CARDANO_NODE_SOCKET_PATH}” --port ${CNODE_PORT} “${host_addr[@]}”
Sep 13 10:42:16 vps-33644252 cnode[1754366]: Listening on http://127.0.0.1:12798
Sep 13 11:54:40 vps-33644252 cnode[1754276]: /opt/cardano/cnode/scripts/cnode.sh: line 57: 1754366 Killed cardano-node “${CPU_RUNTIME[@]}” run --topology “${TOPOLOGY}” --config “${CONFIG}” --database-path “${DB_DIR}” --socket-path “${CARDANO_NODE_SOCKET_PATH}” --port ${CNODE_PORT} “${host_addr[@]}”
Sep 13 11:54:58 vps-33644252 cnode[1755182]: Listening on http://127.0.0.1:12798
I think the producer re-sync the db and it shluld start… see the same on journalctl -e -f -u cnode commnad?
killed it means probably not enough MEM… can u show me how much RAM has the Producer?
All of the nodes have 16gb
The Producer is using no CPU and no memory. The relays appear to be pegging the CPU but not using any memory
– Reboot –
Sep 13 13:22:05 vps-90c078d4 cnode[695]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 13 13:22:07 vps-90c078d4 cnode[896]: Listening on http://127.0.0.1:12798
Sep 13 13:24:15 vps-90c078d4 cnode[695]: /opt/cardano/cnode/scripts/cnode.sh: line 60: 896 Killed cardano-node “${CPU_RUNTIME[@]}” run --topology “${TOPOLOGY}” --config “${CONFIG}” --database-path “${DB_DIR}” --socket-path “${CARDANO_NODE_SOCKET_PATH}” --shelley-kes-key “${POOL_DIR}/${POOL_HOTKEY_SK_FILENAME}” --shelley-vrf-key “${POOL_DIR}/${POOL_VRF_SK_FILENAME}” --shelley-operational-certificate “${POOL_DIR}/${POOL_OPCERT_FILENAME}” --port ${CNODE_PORT} “${host_addr[@]}”
Sep 13 13:24:21 vps-90c078d4 cnode[1191]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 13 13:24:22 vps-90c078d4 cnode[1272]: Listening on http://127.0.0.1:12798
Sep 13 13:25:57 vps-90c078d4 cnode[1386]: Listening on http://127.0.0.1:12798
Sep 13 13:42:59 vps-90c078d4 cnode[1386]: Shutting down…
Sep 13 17:30:40 vps-90c078d4 cnode[5594]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 13 17:30:41 vps-90c078d4 cnode[5679]: Listening on http://127.0.0.1:12798
Sep 13 17:33:29 vps-90c078d4 cnode[5679]: Shutting down…
Sep 13 17:33:40 vps-90c078d4 cnode[6249]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 13 17:33:41 vps-90c078d4 cnode[6337]: Listening on http://127.0.0.1:12798
Sep 13 18:06:36 vps-90c078d4 cnode[6337]: Shutting down…
– Reboot –
Sep 13 18:16:22 vps-90c078d4 cnode[945]: Listening on http://127.0.0.1:12798
All nodes have the same issue? Since when do u have this issue?
Yes. All nodes appear to be behaving exactly the same. I did the upgrade from 1.27 to 1.29 this morning. Everything was working before then.
Ok, and did u downloaded also the scrips? Try on one relay
cd ~/tmp
./prereqs.sh - f
Then go to modify again the env (cnode port) and the topology updater (custom peers)
Then restart the node and wait more minutes
If not working then perhaps u need to resync the db
I have done the prereqs.sh - f. Which node do I the db-sync on?