Hey,
I got the logs, would you be so kind and also read them? I see a lot of Thread issues. What can cause such a behaviour? I also saw that a custom component which I use seems not good (deutsche Bahn) what is your impression?
Here is the full log file : Fault Log · GitHub
Sorry, i’ve already spend to much time in vane , would you be so kind to try to exclude/disable this integration, and see if that helps you
Yes my impressions is either delete this integration, or try to re-download, but as im more surprised that you actually had something in the .fault file, AND that i.e ( schiene.py ) keeps requesting external info, i would definitely ditch this integration ( PS , ive never missed a train in my life, a bus maybe, but a new one is coming in ever 10-15min, it has worked like that for 100 years )
And after disable/delete this integration, please run … ha host update , ha core update , ha supervisor update from/in the proxmox HA-CLI … And delete your 3 homeassistan-db-files
Really that files also? I did all steps and I also checked for updates. And last but not least I I did a repair command which finished fines.
What happen if I deleted those files?
you loose your stored history-data, meaning records of events/states, but as i assume you have some kind of purge-settings, maybe default 10days, of history … nothing else happens, when you restart immediately after the DB-files are recreated, Without any bad/faulty info.
You might also want to look at your paho-mqtt integration, as you might have a faulty/bad configured device there
I don’t have MQTT my self, but i would be concerned about the mixed-up environment
/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py
/usr/local/lib/python3.11/site-packages/paho/mqtt/client.p
And Worse is , did you just update from a fairly old HA version `?
As the fault log shows A-Lot references to OS -Core files
/usr/local/lib/python3.10/site-packages/sqlalchemy
/usr/local/lib/python3.10/site-packages/scapy/supersocket.py
etc. etc.
I had the impression that 3.10 was not only deprecated , but also removed, and no longer supported in Ha-Os
Did you just recently, like now updated from a fairly old ha-os/core version ?
Nope, I update this instance 2weeks after a new release is available. I will do a full re-install. If this issue still exists.
Can I remove the fault log to only keep the newest entries?
Yes delete your log-files as well
Honestly, the first 900 rows in .fault-file are python3.10 ! … so they might just be very old entries
I wonder how larger that fault-log file was/is … and whether you ever Reboot !, and not just restart, when you are facing OS / Connection errors
PS: after deleting db and logfiles, the Reboot" not just restart , and check the homeassistant-fault-log … if there is ANY entries, you still have serious issues
Deleted all files did a full reboot. .fault is empty. Let’s see if the backup today works fine and the VM is running normally.
So far so good 
, but please also change your Topic-header, as it’s in installation/home-assistant-os(might be right) but the header gives the impression The OS is so unstable, when in fact it’s your installation which is/was unstable
In short people ( Lots of people) could actually just have replied to your Topic — It’s Not ! 
let’s see how long it lasts…
Well a lot of posts in this thread while I slept.
The errors do look like they are created by the OS. But it is hard to say. I hope whatever you have done has worked.
A couple of things to note for the future.
This thread became derailed because the dns issue (the red error) is nothing to do with the other stuff. Please try to keep one thread, one issue.
Hey @boheme61 … 3d and its stable let’s see if this crash will occur again. I think the dns issue I will create a new thread for it.