All nodes in "error" state?

This usually indicates the permissioning server has gone offline. We have identified 2 reasons why this has been happening more frequently.

  1. We had switched to teams of 2, rather than 3.
  2. There is an bug in the scheduling algorithm.

We will be switching back to teams of 3 very soon so it will happen less often and we are working to fix the bug in the scheduling algorithm.

We apologize for the inconvenience this causes node operators.

Node operators may be required to restart the node and gateway process manually when this occurs.

Thanks for clarifying, Keith!

1 Like