yegors
commented
2 hours ago Would need to see the debug log at the time of this occurring. Can you run ctrld in logging mode, reproduce the issue, and post the log? If the log has sensitive info, email it to hello@controld.com and reference this issue.
I have a few routers I've been testing before I roll ctrld to my clients. Both of them seem to have 200% CPU usage from ctrld after a period of 24 hours, and stopping and then starting ctrld seems to resolve the issue (some times), however it has not lately and i have had to unsinstal it for the time being.