Cardano-node 1.35.4 error- help! **unsupported and unverified version of `cardano-node` with......P2P

Staking & Delegation Operate a Stake Pool
64

download is working great…looks like only an hr left!

1 Like
65

your are welcome, anytime… cheers

save the command sudo journalctl -e -f -u cardano-node
basically its showing exactly what the problem is when the node fail

1 Like
66

awesome! thx!

67

SOLVED. thx to Alexd1985!
downloaded wrong version of files from git.
dont create directories or put anything in db.
change file paths instead of moving files… :slight_smile:

68

curl -o - https://downloads.csnapshots.io/snapshots/mainnet/$(curl -s https://downloads.csnapshots.io/snapshots/mainnet/mainnet-db-snapshot.json| jq -r ..file_name ) | lz4 -c -d - | tar -x -C /home/cardano/cnode/

shouldnt the chaindata be saved in the DB dir? how does it know this? (ubu noob)

69

/home/cardano/cnode/db ?

70

nope because it will download the db folder together with the files inside

1 Like
71

ok thanks for clarification!

1 Like
72

ok, i figured out whats happening…sync never reaches 100% on relay and stay at 100%, it replays and starts all over.

Feb 13 21:48:34 r1 cardano-node[563017]: [r1:cardano.node.ChainDB:Info:5] [2023-02-14 04:48:34.04 UTC] Validating chunk no. 3878 out of 3878. Progress: 99.97%
Feb 13 21:48:35 r1 cardano-node[563017]: [r1:cardano.node.ChainDB:Info:5] [2023-02-14 04:48:35.03 UTC] Found a valid last location at chunk 3878 with tip 95fbd0579274e304d61a976b09f9b6ccbcc3ceba4ec4ad30cdf707b06c0a6198@83783494.
Feb 13 21:48:35 r1 cardano-node[563017]: [r1:cardano.node.ChainDB:Info:5] [2023-02-14 04:48:35.03 UTC] Opened imm db with immutable tip at 95fbd0579274e304d61a976b09f9b6ccbcc3ceba4ec4ad30cdf707b06c0a6198 at slot 83783494 and chunk 3878
Feb 13 21:48:35 r1 cardano-node[563017]: [r1:cardano.node.ChainDB:Info:5] [2023-02-14 04:48:35.03 UTC] Started opening Volatile DB
Feb 13 21:48:39 r1 cardano-node[563017]: [r1:cardano.node.ChainDB:Info:5] [2023-02-14 04:48:39.19 UTC] Opened vol db
Feb 13 21:48:39 r1 cardano-node[563017]: [r1:cardano.node.ChainDB:Info:5] [2023-02-14 04:48:39.19 UTC] Started opening Ledger DB
Feb 13 21:50:54 r1 cardano-node[563017]: [r1:cardano.node.ChainDB:Info:5] [2023-02-14 04:50:54.19 UTC] Replaying ledger from snapshot at 6635be1db00fe95303fcf4e3bbee9403d4a261d9adc4cc17fa21e741d2a539eb at slot 83773953
Feb 13 21:50:54 r1 cardano-node[563017]: [r1:cardano.node.ChainDB:Info:5] [2023-02-14 04:50:54.25 UTC] Replayed block: slot 83773992 out of 83783494. Progress: 0.41%

like a loop.
what should i do next?
:frowning:

73

also, what would you consider to be high performace relay hardware without being overkill? ram/ssd speed/single core performance?
single 2.5G ethernet network or two? 10Gb? one directly to BP and one directly to gateway?

is your pool cloudbased or BM?
thoughts?

74

Min 16G RAM and 250G ssd (blockchain size is growing)
100 MB internet should be fine
My pool is hybrid… VPS + VDS + BM

1 Like
75

Have you got enough storage?

76

yes…iam only 18% of ssd capacity. :slight_smile:

1 Like
77

do i have to stop node to use this command?

sudo journalctl -e -f -u cardano-node

seems like node will validate chunks…get to 99%…then start over again…from 0%…

loop. repeat. no stop error.

have you seen this before?
not sure how to troubleshoot this behavior.

78

u don’t need it… but if u type the command do u see something wrong? Messages like “killed or killing”

1 Like
79

ok at 99% its almost done…then goes back to 0 and starts validating again! so it is never synced. infinite loop.

Feb 13 15:12:33 r1 cardano-node[52671]: [r1:cardano.node.ChainDB:Info:5] [2023-02-13 22:12:33.90 UTC] Validated chunk no. 3877 out of 3878. Progress: 99.97%
Feb 13 15:12:33 r1 cardano-node[52671]: [r1:cardano.node.ChainDB:Info:5] [2023-02-13 22:12:33.90 UTC] Validating chunk no. 3878 out of 3878. Progress: 99.97%
Feb 13 15:12:35 r1 cardano-node[52671]: [r1:cardano.node.ChainDB:Info:5] [2023-02-13 22:12:35.15 UTC] Found a valid last location at chunk 3878 with tip b2c9145f87e4dc3884d7c49f4583dcc19985d2d824b0>
Feb 13 15:12:35 r1 cardano-node[52671]: [r1:cardano.node.ChainDB:Info:5] [2023-02-13 22:12:35.15 UTC] Opened imm db with immutable tip at b2c9145f87e4dc3884d7c49f4583dcc19985d2d824b03b0313c8019f819>
Feb 13 15:12:35 r1 cardano-node[52671]: [r1:cardano.node.ChainDB:Info:5] [2023-02-13 22:12:35.16 UTC] Started opening Volatile DB
Feb 13 15:12:39 r1 cardano-node[52671]: [r1:cardano.node.ChainDB:Info:5] [2023-02-13 22:12:39.65 UTC] Opened vol db
Feb 13 15:12:39 r1 cardano-node[52671]: [r1:cardano.node.ChainDB:Info:5] [2023-02-13 22:12:39.65 UTC] Started opening Ledger DB
Feb 13 15:13:09 r1 cardano-node[52671]: [r1:cardano.node.ChainDB:Info:5] [2023-02-13 22:13:09.06 UTC] Closed Immutable DB.
Feb 13 15:13:09 r1 cardano-node[52671]: Shutting down…
Feb 13 15:13:09 r1 systemd[1]: cardano-node.service: Main process exited, code=exited, status=130/n/a
Feb 13 15:13:09 r1 systemd[1]: cardano-node.service: Failed with result ‘exit-code’.
Feb 13 15:13:09 r1 systemd[1]: cardano-node.service: Consumed 50min 50.345s CPU time.
Feb 13 15:13:14 r1 systemd[1]: cardano-node.service: Scheduled restart job, restart counter is at 1.
Feb 13 15:13:14 r1 systemd[1]: Stopped Cardano Node Service.
Feb 13 15:13:14 r1 systemd[1]: cardano-node.service: Consumed 50min 50.345s CPU time.
Feb 13 15:13:14 r1 systemd[1]: Started Cardano Node Service.
Feb 13 15:13:14 r1 cardano-node[117634]: Node configuration: NodeConfiguration {ncSocketConfig = SocketConfig {ncNodeIPv4Addr = Last {getLast = Just 0.0.0.0}, ncNodeIPv6Addr = Last {getLast = Nothi>
Feb 13 15:13:15 r1 cardano-node[117634]: Listening on http://127.0.0.1:12798
Feb 13 15:13:15 r1 cardano-node[117634]: [r1:cardano.node.basicInfo.protocol:Notice:5] [2023-02-13 22:13:15.06 UTC] Byron; Shelley

80

What is the hardware configuration ?

81

13700/32GbRam/1TBssd