Operator - error - Failed to submit challenges from chain

Support
, ,
1

Issue Report

After running node as an operator constantly getting the following error: Failed to submit challenges from chain at block (0, ) - see screen. Is this error critical? What is the reason?

Environment

  • **Operating System: Win10, Intel (QQLT) @4800Hz, 16Gb Ram @2666Mhz, 1Tb Nvme
  • **Pulsar/Advanced CLI/Docker: Advanced, running as operator

Problem

After running node as an operator constantly getting the following error: Failed to submit challenges from chain at block (0, ) - see screen. Is this error critical? What is the reason?

see screenshot

IMG_0937
IMG_09371062×492 117 KB

2

Please post logs as text, not screenshots, it is hard to see and impossible to search.

Also did you start operator from scratch rather than adding arguments to previously synced node?

@ved probably something for you to look at.

1 Like
3

Yes, sure. I’ve moved the path previously used to other place and start syncing from clear list. I’ve used domain ID 1 and synced the node . The only thing I did not the way was stated in official manual is that I’ve generate the key and insert key only after I’ve synced it to 100%. After that I’ve started the node, sync it again to 100% and successfully register as operator.

Unfortunately I cannot provide text logs as I run with >> \log.txt but it returns me with empty log file. But I can add to the said above that i see in log “produced bundle” “complete bundle” info (example can be also found on the screen).

4

Hi! Thanks for reporting. We are aware of this problem and have a GitHub issue to look into it. The message is harmless and all operators see it (though not operator/farmers). Please subscribe on GitHub to make sure you’re kept up to date on progress. Relayer is not able to fetch messages to be relayed from Consensus chain · Issue #2257 · subspace/subspace · GitHub

1 Like