New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
overrun, tx size:151508 #63
Comments
I have a 10 node mesh up and under some circumstances I can also get one of my mesh points displaying this message which does corelate with the rest of the network to stalling. I'm wondering if having them all in the same room is part of the problem. Any advice on how to keep one bad apple from spoiling the rest? |
Dear @synaption, Thank you for your questions.
Could you try with the latest package and share the result? Best regards, |
So I got around to looking at this again. Suppressing the log does not really solve the problem. This log info appears when the network is not functioning. Currently None of the nodes will connect. The CPU seems to be set at my devices max frequency by default. I think all the devices are spamming up the network trying to connect at the same time. I could have them start more gracefully one by one, but I would have to script that since I don't have ssh access without the network functioning properly.
|
Under heavy or moderate use, the mesh point portal is showing the message
overrun, tx size:151508
many times. Sometimes this causes the network to stall. Sometimes it is ok. It seems like some devices may be worse than other which could point to a hardware issue. I am wondering if there is a way to solve this. Perhaps by increasing the size of whatever is overrunning.The text was updated successfully, but these errors were encountered: