Closed bsqrl closed 7 years ago
I had a similar issue where the VM (Debian 9 running in ESXi 6.5) would freeze at 100% CPU and had to be reset. What linux kernel are you running? I was able to capture the start of the kernel BUG log output so with that, combined with what I read here, I changed my NIC from VMXNET3 to E1000e and the issue went away. Sorry if this isn't the same issue as yours, but maybe it'll help.
I am using the most recent kernel from the Debian repository: SMP Debian 4.9.30-2+deb9u1
I'll take a look at the NIC settings as soon as I have access to the machine and eventually change them (if necessary).
Now I had the chance to test the suggested workaround. I can say that it works for me. Strange behaviour but it seems not be a Home Assistant problem. So this issue can be closed.
Tank you very much.
OS and other stuff: I am running home assisstant on a Debian 8 based system in a virtual environment. The unifi controller software that is used is the lastest available version (I tested older versions and ran into same problems).
Home Assistant release (
hass --version
): 0.47.1Python release (
python3 --version
): 3.5.3Component/platform: Unifi device tracker
Description of problem: If I use the unifi device tracker, the whole system gets in a weird state after a while (~10 minutes): The machine gets stuck, takes 100% CPU on one core and doesn't respond anymore.
Expected: Don't make the whole machine stuck.
Problem-relevant
configuration.yaml
entries and steps to reproduce:Commenting out the corresponding part of the config, home assistant and the whole system works fine for hours.
Traceback (if applicable):
Additional info: I don't have any useful additional info. If one needs specific information I surely do my best to provide it.