pantherale0
commented
4 months ago Closing this - not sure what happened, but restoring back to 2024.6.4 also had the same problems so rebuilt the machine it was running on and restored from a backup.
Closed pantherale0 closed 4 months ago
pantherale0
commented
4 months ago Closing this - not sure what happened, but restoring back to 2024.6.4 also had the same problems so rebuilt the machine it was running on and restored from a backup.
francescopeloi
commented
4 months ago I am experiencing something similar since a few days.
I get billions of
2024-07-17 15:30:44.545 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback None() (None)
Traceback (most recent call last):
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
TypeError: 'NoneType' object is not callableuntil the home-assistant.log file fills the hard drive and everything crashes. I cannot find the root cause, it seems to start from nothing, there's no useful log message before the first occurrence of this.
It's an HA instance only for camera control.
cdoepmann
commented
4 months ago I was experiencing the very same issue, very annoying. I then removed everything I didn't necessarily need from my installation (specifically, HACS and AppDeamon) and the issue hasn't occurred for a few days now. I thus suspect HACS or AppDeamon to be the root cause. Do you use these?
francescopeloi
commented
4 months ago My investigation points to Frigate and it's UI component, both coming through HACS. But I haven't found the exact root cause yet.
cdoepmann
commented
4 months ago I'm not using Frigate though, so maybe it's an issue with HACS itself...
pantherale0
commented
4 months ago If it was a problem with frigate or hacs I would expect that I had the same problem when I rebuilt and restored from a backup. Or there would be more of these cases reported.
francescopeloi
commented
4 months ago it's quite clear it's coming from Frigate my end, we might have different issues.
The problem
It appears that core is crashing nearly everyday since 2024.7.x. I'm not sure if its due to a custom integration, or if something else is going on. But after around 24-36 hours of up time, Linux's OOM killer kills
python3which of course takes Home Assistant offline entirety.I've check the logs, but can't see any integrations throwing any errors (apart from what I would expect). I can't upload the logs here as they are too large (I have one from a couple of days ago 10gb in size, another from today 1.5gb in size) but happy to send to someone via other means. I have included a snippet of the logs below around the time core crashes.
The line
ERROR (MainThread) [homeassistant] Error doing job: Exception in callback _SelectorSocketTransport._read_ready() (None)repeats so much it accounts for a good 95% of the log files. And usually < 10ms apart. Almost like something is in a infinite loop.HAOS on Proxmox 8.2.2. To get HA back I need to perform a hard reset (shutdown doesn't work, cli also is not responsive). Screenshot of stats below
comparison with monthly stats:
What version of Home Assistant Core has the issue?
core-2024.7.1
What was the last working version of Home Assistant Core?
core-2024.6.2
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response