Can't get rewards after update cardano node 1.34.0

English Community Technical Support
21

hello alex
this is result of command leaderlog and that’s much.
i take somes output such as the following

{
  "no": 21577,
  "slot": 55900330,
  "slotInEpoch": 431530,
  "at": "2022-03-16T14:37:01-07:00"
},
{
  "no": 21578,
  "slot": 55900358,
  "slotInEpoch": 431558,
  "at": "2022-03-16T14:37:29-07:00"
},
{
  "no": 21579,
  "slot": 55900370,
  "slotInEpoch": 431570,
  "at": "2022-03-16T14:37:41-07:00"
},
{
  "no": 21580,
  "slot": 55900412,
  "slotInEpoch": 431612,
  "at": "2022-03-16T14:38:23-07:00"
},
{
  "no": 21581,
  "slot": 55900427,
  "slotInEpoch": 431627,
  "at": "2022-03-16T14:38:38-07:00"
},
{
  "no": 21582,
  "slot": 55900446,
  "slotInEpoch": 431646,
  "at": "2022-03-16T14:38:57-07:00"
},
{
  "no": 21583,
  "slot": 55900456,
  "slotInEpoch": 431656,
  "at": "2022-03-16T14:39:07-07:00"
},
{
  "no": 21584,
  "slot": 55900458,
  "slotInEpoch": 431658,
  "at": "2022-03-16T14:39:09-07:00"
},
{
  "no": 21585,
  "slot": 55900503,
  "slotInEpoch": 431703,
  "at": "2022-03-16T14:39:54-07:00"
},
{
  "no": 21586,
  "slot": 55900506,
  "slotInEpoch": 431706,
  "at": "2022-03-16T14:39:57-07:00"
},
{
  "no": 21587,
  "slot": 55900507,
  "slotInEpoch": 431707,
  "at": "2022-03-16T14:39:58-07:00"
},
{
  "no": 21588,
  "slot": 55900529,
  "slotInEpoch": 431729,
  "at": "2022-03-16T14:40:20-07:00"
},
{
  "no": 21589,
  "slot": 55900564,
  "slotInEpoch": 431764,
  "at": "2022-03-16T14:40:55-07:00"
},
{
  "no": 21590,
  "slot": 55900598,
  "slotInEpoch": 431798,
  "at": "2022-03-16T14:41:29-07:00"
},
{
  "no": 21591,
  "slot": 55900649,
  "slotInEpoch": 431849,
  "at": "2022-03-16T14:42:20-07:00"
},
{
  "no": 21592,
  "slot": 55900666,
  "slotInEpoch": 431866,
  "at": "2022-03-16T14:42:37-07:00"
},
{
  "no": 21593,
  "slot": 55900696,
  "slotInEpoch": 431896,
  "at": "2022-03-16T14:43:07-07:00"
},
{
  "no": 21594,
  "slot": 55900744,
  "slotInEpoch": 431944,
  "at": "2022-03-16T14:43:55-07:00"
},
{
  "no": 21595,
  "slot": 55900755,
  "slotInEpoch": 431955,
  "at": "2022-03-16T14:44:06-07:00"
},
{
  "no": 21596,
  "slot": 55900757,
  "slotInEpoch": 431957,
  "at": "2022-03-16T14:44:08-07:00"
},
{
  "no": 21597,
  "slot": 55900766,
  "slotInEpoch": 431966,
  "at": "2022-03-16T14:44:17-07:00"
},
{
  "no": 21598,
  "slot": 55900773,
  "slotInEpoch": 431973,
  "at": "2022-03-16T14:44:24-07:00"
},
{
  "no": 21599,
  "slot": 55900784,
  "slotInEpoch": 431984,
  "at": "2022-03-16T14:44:35-07:00"
}

]

22

what’s the meaning about that ?

23

this should be the slots assigned to u… but it’s something weird… all slots for 16 March at few seconds differences?

there are more?

did u used ur pool id and the vrf file?

24

i think so, there are for 16 march and there are more

i use my pool id and my vrf file

i convert my total stake and active stake to lovelace. should i use on ada ?

25

Yeah, but also u can use the guide from coincashew (for leaderlog)

26

but i think something weird
after 32.4 % epoch time but i not assign yet to making block or become leader.

what’s your cardano node version, Alex ?

27

here is the guide, u must identify first the slots number, to check if u missed or not…

My version is 1.34.1

If u only uograded the nodes and u didn’t do anything to the files, should be fine…

28

Thank you so much alex for your insight.
i try to execute command slot leader for current epoch and get output such as the following

 SlotNo                          UTC Time              

 55493603                   2022-03-12 04:38:14 UTC
 55499928                   2022-03-12 06:23:39 UTC
 55509676                   2022-03-12 09:06:07 UTC
 55522048                   2022-03-12 12:32:19 UTC
 55564670                   2022-03-13 00:22:41 UTC
 55578243                   2022-03-13 04:08:54 UTC
 55644359                   2022-03-13 22:30:50 UTC
 55671489                   2022-03-14 06:03:00 UTC
 55672297                   2022-03-14 06:16:28 UTC
 55683443                   2022-03-14 09:22:14 UTC
 55698537                   2022-03-14 13:33:48 UTC
 55700886                   2022-03-14 14:12:57 UTC
 55721390                   2022-03-14 19:54:41 UTC
 55731412                   2022-03-14 22:41:43 UTC
 55734100                   2022-03-14 23:26:31 UTC
 55738713                   2022-03-15 00:43:24 UTC
 55741338                   2022-03-15 01:27:09 UTC
 55765604                   2022-03-15 08:11:35 UTC
 55774180                   2022-03-15 10:34:31 UTC
 55792800                   2022-03-15 15:44:51 UTC
 55807850                   2022-03-15 19:55:41 UTC
 55816381                   2022-03-15 22:17:52 UTC
 55825049                   2022-03-16 00:42:20 UTC
 55842569                   2022-03-16 05:34:20 UTC
 55845705                   2022-03-16 06:26:36 UTC
 55869232                   2022-03-16 12:58:43 UTC

is that true ?

29

Ok, this is more reslistic

1 Like
30

you update your cardano node to version 1.34.1 on 326 epoch ?

31

Now try both commands

grep 5.552204 /var/log/syslog
journalctl -u cnode.service -n 100000 | grep 5.552204

32

i didn’t use cnode, Alex
only command from cardano docs

when is the best time to update cardano node?
in an ongoing epoch or before an epoch starts?

33

Or for the last missed block

55578243

grep 5.557824 /var/log/syslog
journalctl -u cnode.service -n 100000 | grep 5.557824

34

did u tried the commands?
u can update the nodes anytime, there is no mandatory time… what else did u did beside the upgrade?

did u replaced/copied some files? Maybe u rotated the KES recently? :thinking: I believe this is the issue (I saw on glive that u rotated recently)… can u rotate again? But before this check the node.counter file… if u type nano or cat node.counter what is the next certificate issued number?
Must be any number greater than 6

35

what’s command that you mean, Alex ?

i update my cardano node from 1.33.0 to 1.34.0 on previous epoch(325) and update KES on previous epoch (325) and hit 3 times execute command for create node.cert.
but i update/rotate KES on relay node and then copy(scp command) to block producer node.
is that wrong way for rotate KES on relay node and copy node.cert to block producer ?

and then i update cardano node from 1.34.0 to 1.34.1 on current epoch(326)

i just do that

36

Ok, the problem is not with the version… is with the KES update

u must also copy to live producer the kes.skey

when u rotated the KES I believe also the kes.skey was refreshed

37

okey
should i rotate again KES ?
and then see the count, right ?

38

Check the count before to rotate… should be > 6

39

is that the recommendation, Alex ?

my count is 05 # int(5) right now

40

pfff not ok… edit to 7 end rotate the KES again… if u go on adapools.org to blocks u will see that the last number used was 6 (opCert)… so next one should be > 6

U can find all these informations inside coincashew guide… rotate the KES

after u rotated the KES, inside node.counter u should see 8