-
Notifications
You must be signed in to change notification settings - Fork 47
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
UDP Memleak when running multiple parallel instances #52
Comments
Same problem for me.
I also tried all our net-segments with one service but failed as well. |
@margau on what commit are you guys currently running? Please share the result of this command in your mesh-announce directory: |
Currently running on 8deeec1
Our workaround was to increase |
Hello,
our workaround for #49 is running multiple parallel instances of mesh-announce, one per domain:
python3 /opt/mesh-announce/respondd.py -d /opt/mesh-announce/providers -i dom2-br -i dom2-tp -b dom2-bat
(Other Domains with the same scheme)
Basically it works, but unfortunately, after a few hours we have a mem-leak blocking all UDP communication on the system (including fastd): https://prometheus.ffm.freifunk.net/graph?g0.range_input=1h&g0.end_input=2020-01-09%2008%3A44&g0.expr=(node_sockstat_UDP_mem_bytes%7Binstance%3D~%22gw05.*%22%7D%20%2F%201024%20%2F%201024)%20%3E%20100&g0.tab=0
This doesn't happen if we have only one mesh-announce instance running.
As my knowledge with Python and the ThreadingUDPServer is very limited, I currently not sure how to debug this problem.
Python Version is
Python 3.7.3 (default, Apr 3 2019, 05:39:12)
on Stretch5.4.0-1-amd64 #1 SMP Debian 5.4.6-1 (2019-12-27)
Anyone has some ideas?
Thanks!
margau
The text was updated successfully, but these errors were encountered: