Website does not acknowledge completed challenges
reppolice opened this issue · comments
It's been about a week now that https://securenodes2.eu.zensystem.io/nodes/2068/detail is showing daily challenge "blackouts", which however is not what I am seeing on my node. I should point out my server is over-specified and never really missed a challenge or got offline. I did install the Intel patches but I suspect the "bad magic" happened on your side. Here's today's log on my server
2018-03-23 21:07:06 GMT -- Elapsed challenge time=30 status=executing
2018-03-23 21:07:16 GMT -- Elapsed challenge time=40 status=executing
2018-03-23 21:07:26 GMT -- Elapsed challenge time=50 status=executing
2018-03-23 21:07:36 GMT -- Elapsed challenge time=60 status=executing
2018-03-23 21:07:46 GMT -- Elapsed challenge time=70 status=executing
2018-03-23 21:07:56 GMT -- Elapsed challenge time=80 status=executing
2018-03-23 21:07:58 GMT -- Challenge submit: success
2018-03-23 21:07:58 GMT -- Challenge result:success seconds:81.918269724
2018-03-23 21:07:58 GMT -- Challenge response received by ts2.na
2018-03-23 21:08:00 GMT -- Clearing timer
2018-03-23 21:08:04 GMT -- Stats received by ts2.na
2018-03-23 21:09:18 GMT -- Challenge response received by ts2.na
2018-03-23 21:13:00 GMT -- Stat check: connected to:ts2.na blocks:278292 peers:13 bal:0.55160681 isValidBal:true queueDepth:0 lastChalBlock:278290 lastExecSec:79.96
2018-03-23 21:13:00 GMT -- Stats received by ts2.na
2018-03-23 21:14:04 GMT -- Stats received by ts2.na
2018-03-23 21:19:00 GMT -- Stat check: connected to:ts2.na blocks:278293 peers:13 bal:0.55160681 isValidBal:true queueDepth:0 lastChalBlock:278290 lastExecSec:79.96
2018-03-23 21:19:00 GMT -- Stats received by ts2.na
2018-03-23 21:20:04 GMT -- Stats received by ts2.na
^[[B^[[B^[[B^[[B^[[B^[[B2018-03-23 21:25:00 GMT -- Stat check: connected to:ts2.na blocks:278305 peers:13 bal:0.55160681 isValidBal:true queueDepth:0 lastChalBlock:278290 lastExecSec:79.96
2018-03-23 21:25:00 GMT -- Stats received by ts2.na
2018-03-23 21:26:04 GMT -- Stats received by ts2.na
2018-03-23 21:31:00 GMT -- Stat check: connected to:ts2.na blocks:278316 peers:13 bal:0.55160681 isValidBal:true queueDepth:0 lastChalBlock:278290 lastExecSec:79.96
2018-03-23 21:31:00 GMT -- Stats received by ts2.na
It appears from your log that you have two trackers running. Each stat check should have one response from the server and there is an extra entry.
If using pm2 run: pm2
There should only be one tracker running.
If there is more than one Run:
pm2 stop 1
pm2 delete 1
pm2 save
If only one or not using pm2 run 'top' and look for 2 processes with a description that includes 'node'.
I had indeed two processes running at that moment, but I also had the impression I had the problem with one tracker, and simply manually started a tracker after a reboot because the autostart was taking a few seconds more than I wanted! But I seem to be back to the same behavior without manually starting any trackers. Besides, I cannot figure out if it is a bug or a feature that a second tracker would interfere. Of course a second tracker "should not" be running, but how could your server ignore a completed challenge anyway!
One tracker is overwriting the results of the other and throws all the timing and results off.
Just make sure only one tracker starts on a reboot and only one stays running and the node should send results correctly.
Well, for all I know from ps -aux and such, one tracker has been running this week, but still got hit with several outages, particularly "allowed reply variance exceeded" . To the naked eye it does not look like I have any variance to speak of.
Compare the Reply column with the Run column. They should be within 10 second of each other. If the Reply time is about twice the Run time it usually means there are two trackers running.
Close due to inactivity.