0

I have been stuck at epoch 299 for a long time now, it randomly stops around hash e15.. or sometimes gets lucky and stop at around e1f...

I have 16g ram, 16g swap, i7 octa core, ubuntu 20.04.2 lts

my Cardano Node is up-to-date & version 1.30.1

Anyone encountered this as well?

-- Logs begin at Wed 2021-11-10 06:50:18 PST, end at Sat 2021-11-13 23:36:19 PST. -- Nov 13 05:30:58 almneri cardano_db_sync[28054]: [db-sync-node:Warning:59] [2021-11-12 21:30:58.83 UTC] validateEpochRewards: rewards spendable in epoch 299 expected total of 333428375.000492 ADA but got 6517346> Nov 13 05:31:11 almneri cardano_db_sync[28054]: Epoch No: 299 Nov 13 05:31:11 almneri cardano_db_sync[28054]: dbMap length: 848262 Nov 13 05:31:11 almneri cardano_db_sync[28054]: ledgerMap length: 848262 Nov 13 05:31:11 almneri cardano_db_sync[28054]: diffMap length: 31428

(skipping repetitive logs until tail)

Nov 13 05:31:11 sogekingu1 cardano_db_sync[28054]: e15111b170e88783117820c31947a492baf917f87e25a92169c779e187 (335606, 3): [(RwdMember,DbLovelace 262990),(RwdTreasury,DbLovelace 36308),(RwdTreasury,DbLovelace 3630> Nov 13 05:31:11 sogekingu1 cardano_db_sync[28054]: e15112393169014c7bb6049763cee397aa96bc4c4e54824e0624a42b72 (4154757, 3): [(RwdMember,DbLovelace 3511017),(RwdTreasury,DbLovelace 321870),(RwdTreasury,DbLovelace 3> Nov 13 05:31:11 sogekingu1 cardano_db_sync[28054]: e15116c8b85f4ef12743e615590d99fc399b67ae28244147a9725f2289 (1786702, 3): [(RwdMember,DbLovelace 1614830),(RwdTreasury,DbLovelace 85936),(RwdTreasury,DbLovelace 85> Nov 13 05:31:22 sogekingu1 systemd[1]: cardano_db_sync.service: Main process exited, code=exited, status=1/FAILURE Nov 13 05:31:22 sogekingu1 systemd[1]: cardano_db_sync.service: Failed with result 'exit-code'. Nov 13 05:31:27 sogekingu1 systemd[1]: cardano_db_sync.service: Scheduled restart job, restart counter is at 97. Nov 13 05:31:27 sogekingu1 systemd[1]: Stopped Cardano DB Sync. Nov 13 05:31:27 sogekingu1 systemd[1]: Started Cardano DB Sync.

2
  • What is the cardano-db-sync version? Nov 13, 2021 at 19:51
  • Can you check journalctl -k and see if something is killing it? There could be a ulimit it's exceeding that needs tweaked in your systemd unit. Dec 14, 2021 at 14:49

1 Answer 1

0

Off the top of my head I'd say maybe it has something to do with your using Ubuntu 20.01 instead of 20.04. Maybe unlikely but I think most nodes run on 20.04 it could be a "fix" of sorts.

1
  • 1
    ohh sorry, I accidentally put 20.01, face palm Yea i am using 20.04 Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal Thanks for pointing it out!
    – Vigossive
    Nov 13, 2021 at 17:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.