this is the situation… is normal?
yeah, also u can search for pools with the same staked amount and check how often they are producing blocks
I see u have enough IN peers, but u mist check the CPU, I see it’s over 90% on your Relay
Question: do u check the leaderlog each epoch?
no I think I never check, how could I check the leaderlog?
my server are vm machine, to fix the cpu problem could I increase the number of processor?
Davide
now it says 60%
You are using coincashew or cntools guide?
For CPU, perhaps u will need to take in consideration an upgrade in near future
coincashew
For CPU I could add some to the virtual machine?
Should be fine for the moment… now, on coincashew guide u have a chapter
18.12 Slot Leader Schedule - Find out when your pool will mint blocks
It’s the first time when u ran, have patience to sync (CNCLI sync not the node); you should see 100%
all the operations of 18.12 has to be made on the relay, correct?
U will need the vrf file
170K
10k in pledge
It’s fine… u will need a high luck but yeah… can take weeks, months til a new block… but to be sure that u don’t lose any block assigned try to run leaderlog with 1,5 days before the new epoch start
on the producer node if I launch the cncli give me connection refused
/usr/local/bin/cncli sync --host 127.0.0.1 --port 6000 --no-service
cncli version 4.0.1
Hi Alex,
another error
did you know why?
Cheers
Davide
probably you will need the latest cncli version
same error with 4.0.4
can u share the glive? Did u started the port with port 6000?