SYNCTHING CPU USAGE SOFTWARE

Please use something else instead of ultrasecretkey. I have a very large searx.log in here, with this recurring error message: GNU nano 5.4 searx.logĮRROR:searx:cret_key is not changed. I shut the box down completely and left it off for the better part of an hour, but as soon as it was booted back up CPU usage shot back up to 100% and stayed there.ĭoes anyone have any insight into what I can do to troubleshoot this uwsgi service?ĭebian GNU/Linux 11 (bullseye) and FreedomBox version 22.10Īha–thanks for the tip James, looks like you are absolutely right.

I restarted the service from Cockpit, but it immediately shot right back to 95+% CPU usage.

SYNCTHING CPU USAGE SOFTWARE

I looked it up quickly, the software has something to do with building hosting services so I guess that seems important–but also the CPU usage seems like maybe it is not working properly. I didn’t see a temperature gauge, but I did see the CPU is maxed out at 100%:Ī service called uwsgi is holding down some 95% CPU usage. I opened up the Cockpit app to check if there was some kind of temperature gauge I could take a look at, to see if perhaps I was overreacting. I was tidying up the area over by the FreedomBox today and discovered the unit is blazing hot. I have noticed the web portal has been awfully slow but haven’t thought much of it.

I don’t have too much running right now–just Syncthing, miniDLNA, bepasty and Searx–and everything has been working fine. I haven’t been keeping a close eye on my FreedomBox for quite some time, I’ve just been letting it do its thing.

Syncthing cpu usage