Challenge overlap

[whenlambomoon]

Challenge overlap

[firsttubr]

on discord there seems to be others with same issue and when I pick a random node running 0.2.0 and look at the challenge results most are having same issue. The ones on 0.1.0 seem to be fine.

Does this known issue apply? HorizenOfficial/nodetracker#40

[avrossi]

I'm having the same problem since I did the update to 0.2.0. I rebooted my VPS and that stoped the previous challenge. When I send myself a challenge it always passes no problem. But when I receive my daily challenge from the server I get the same error you are getting. Not sure what is going on.

[zammtech]

I'm getting the same error too.

[333miiko]

Could you try stop the containers to trigger a new downtime event. The challenge should expire by itself, if not it's a bug with their tracker. ``` systemctl stop zen-node systemctl stop zen-secnodetracker ``` After that you may start it up again: ``` systemctl start zen-node systemctl start zen-secnodetracker ``` Go to the securenode tracker website and click send challenge by email.

…

On Tue, Jan 16, 2018 at 4:29 AM zammtech ***@***.***> wrote: I'm getting the same error too. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#50 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AfowZfhv6nsU_UtY62Q1E0fyMLhfdoyBks5tK4r4gaJpZM4RedgC> .

[firsttubr]

I did that, then sent a challenge. First one passed, second one is stuck on "wait" after 38 min. When the next challenge is sent tomorrow I'm guessing it will probably give same error of previous challenge still running.

[333miiko]

Seems like there is a similar method floating around discord, my instructions above would apply to this:

[discord] <psyrax, UTC +11> APP [8:16 AM]
For those with a failed challenge timeout exception or previous challenge still running, please try this:

Restart of the tracker by completely stopping the tracker for 10 seconds then restarting it, a challenge may be automatically sent to the node, if not then used the manual-manual process.

Before running through this, please ensure there are are no open challenges in the wait state

Get your node t-address using
zen-cli listaddresses
then either run
https://securenodes.your_region.zensystem.io/node_t_addres/node_id/send
or run
https://securenodes2.your_region.zensystem.io/node_t_addres/node_id/send
depending if you are homed on the suffixed 2 servers

[333miiko]

You can go to the securenode tracker website to send the challenge, or just remember for the command above it is:

docker exec -it zen-node gosu user zen-cli listaddresses

[cuzner]

@333miiko - They've updated master for secnodetracker with a fix for this issue.

Tracker app version: 0.2.1

You can probably close this now.

[333miiko]

Thanks for the notification. New securenode tracker version is now being built now for v0.2.1-beta

To upgrade:

systemctl restart zen-secnodetracker