#Follow this and show what it says: <

1 messages · Page 1 of 1 (latest)

clear trout
#

@unborn grotto already tried to install profiler, but Home Assistant frontend is not accessible

#

Core crashes leading to me not be able to login into the frontend

unborn grotto
#

Oof. In that case check top -o %MEM and docker stats and perhaps free -h.

clear trout
#

Already checked top. Gonna try docker stats and let you know

unborn grotto
#

Then share what you see 🙂

clear trout
#

Done. The homeassistant container skyrockets in RAM and then gets killed by the OS

#

As i said before the process that makes the container crash is python3 -m homeassistant --config /config, surely a child process of it

#

Supervisor still works but the homeassistant core container does not

#

I don't know if it could be dependent by the HA core version but i have no idea

unborn grotto
#

top -H should show you the hierarchy.

#

I don't know how much RAM you have or how much it uses and what uses how much though. I'd like to see the results of these commands.

clear trout
#

I have 6GB but i've always run that VM with 2GB without any problems. So i would not think the cause is a lack of RAM

#

I've increased it yesterday in an attempt to save it

unborn grotto
#

You can check ha host logs and ha core logs for errors. I'm not sure under which circumstances it would run setuptools.

clear trout
#

Just for info, could this be caused by breaking changes?

#

I don't think they are the fault since i've only updated OS before having this problem, but maybe

unborn grotto
#

I don't have any information to go on. All I know is that python OOMs. Maybe.

clear trout
#

Update:

  • ha core logs just says
[15:23:34] INFO: Home Assistant Core finish process exit code 256
[15:23:34] INFO: Home Assistant Core finish process received signal 9

Which i imagine is the exit code sent from the OS to Docker to stop the container.
The logs before are just informative stuff unrelated to the crash.

  • ha os logs shows nothing useful. But i think host is not the problem: the container gets killed just because it is leaking memory. I'm pretty sure the problem is Home Assistant itself but i have no idea on how to debug it
#

I saw in some thread about py-spy to profile Home Assistant. Might just try that

#

Edit: i can't use py-spy either since it requires me to run some commands into the homeassistant container which i have not enough time to before it crashes 🙃

#

@unborn grotto if you think that could help you i can screen-record top -o %MEM

unborn grotto
#

Sure, why not. top -cH might be more useful though.

clear trout
#

It seems like i can't send videos

hearty marshBOT
#

Please use imgur or other image sharing web sites, and share the link here.

Image posting is blocked in most channels to discourage people from sharing text as images. Sharing text as images assumes that everybody sees the world as you do, which isn't the case. Some people are colour blind, or have visual impairment that means they can't make sense of an image of text.

unborn grotto
#

Might be because of this. Just use a file hoster.

clear trout
#

Uploading on Streamable right now

#

I will record top -cH meanwhile

#

Does top -ch have an option to order by memory usage?

unborn grotto
#

Ordering by memory while showing threads doesn't really work well. But it would be top -Hc -o %MEM

#

Oh wow that "leaks" fast and a lot.

clear trout
#

Definitely ahah

#

I don't really know where to look at anymore

unborn grotto
#

You can try stopping ha with ha core stop and creating a file named safe-mode in the config directory. It "should" start in safe mode then via ha core start.

clear trout
#

Ok this is cool. Was looking on how to enable safe mode for a bit now

unborn grotto
#

Me too but I had to check the code for my answer 😦

clear trout
#

That should definitely be better documented.

#

I think i've found the issue though. Seems to be a misconfigured template sensor

unborn grotto
#

Even the login thing was hidden for a long time. It still kinda is.

clear trout
#

Let me try removing the sensor from config and restarting

#

If that is the problem, i will probably freak out xD

#

Good thing is that HA stays alive in safe mode

unborn grotto
#

I'd probably report that though. Just vacuuming gigs of memory due to this shouldn't happen.

clear trout
#

Still not working after removing the sensor

#

🤔

#

Will re-boot into safe mode and check again

#

Updated: Disabled all HACS integrations and automations and Home Assistant is back up in normal mode.

unborn grotto
#

Now the fun begins to single it out.

clear trout
#

Exactly. I'm 90% sure it is some sort of HACS integration though

#

Could have tried that before wiping half of my HA config out of existence though 😆

#

Fortunately i backed up everything before started tinkering while core was still broken

#

Thank you so much though @unborn grotto , without your hint i probably would have had to re-install everything

#

Probably it could be helpful to document that safe-mode and login things, maybe in a dev-related context in HA docs but still. They could save you a lot of hassle

unborn grotto
#

The docs have a link at the buttom to edit them.

clear trout
#

Yes i am aware of that but i thought that if it is not documented maybe it is by choice. I don't know if that is the case though

unborn grotto
#

I don't know either.

clear trout
#

Good news is i've tracked down the integration causing the problem

#

So i will now restore the full snapshot i took and disable that integration

unborn grotto
#

Which one was it?

#

"full snapshot" sounds weird.

clear trout
clear trout