You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked the log file. The core thing here is that the bot never fully starts up. That is indeed due to the failure of RMB communication associated with this error
We see on each attempt of the bot to start that it adds one node successfully using the same RMB relay before failing repeatedly on the second node. So there is some successful RMB communication happening
I also checked on the rate limiting implementation for RMB. It looks like it only drops messages with an error, it isn't supposed to drop connections entirely if the user tries to send too many messages
All nodes included in this config are currently up in the dashboard, so we can possibly rule out the suspicion of the nodes being unhealthy before being added to the farmerbot. Also, the --continue-power-on-error is already included in the script that was used to set up.
What happened?
Farm ID : 195
The client reported that his Nodes managed by Farmerbot did not shut down.
Upon reviewing the log file, we found that the farmerbot was not starting up due to the following error:
Some additional notes by @scottyeager:
Log File :
farmerbot_16enuun.log
which network/s did you face the problem on?
Main
Twin ID/s
No response
Version
No response
Node ID/s
626, 548, 547(Offline currently) - 3038(Online)
Farm ID/s
195
Contract ID/s
No response
Relevant log output
The text was updated successfully, but these errors were encountered: