I am running HA 2022.4.1 and since morning I am facing this error, “failed to call service system_log/write” after that HA becomes inaccessible, until I physically restart it. https://www.codepile.net/pile/KryRP0An
I’m having a similar problem since upgrading to 2022.4. I’m running HASIO on a Rasberry Pi 4 (note - I only run production releases, never a release candidate). Every 2 days or so, the UI would become inaccessible until I toggle power on the RP4. The server is completely inaccessible via web browser. I can access the server via the HA IOS app, but the Dashboards don’t show up. Instead, I see a blank screen with the “settings” icon on the lower right. Sometimes, the messesge “NSURELerrorDomain -1004” would appear.
Since I automatically click update whenever a new release becomes available, I don’t know exactly which version of core or HA OS this problem started. All I know is that the problem is happening frequently with the latest release versions as of 4/10/2022 (2022.4.1; HS OS 7.6)
Anyone find a solution to this issue? I get it on two different tablets when I wake them up with motion using Fully Kiosk. There’s no issues being reported in the logbook or system/logs. Doesn’t appear to be any negative effects except for the warning popping up on the frontend lower left corner.
Same issue here. Updated to last version and that message pops out and brake all the tablet that I have wall mounted. Someone that have a solution please
Running Home Assistant Core 2023.9.2 running on Mac mini M1. I hadn’t used HA in a while so updated to the latest version. I noticed that it would (seemingly) randomly hang and the webUI would be inacessable until I restarted HA. It has been like this for around 1 week, but only today did I notice the message failed to call service system_log/write in the lower left corner of the webUI, and immediatly after this HA was inaccessable. Going to try and disable all integrations and re-enable one by one incase there is a culprit.
So I’m pretty sure I figured out what made my instance become inaccessible.
I had a Galaxy Tablet with Fully Kiosk Browser & Lockdown installed so I could use it as a remote which would show when motion was detected by the tablet camera. After uninstalling this my HA instance hasn’t experieced the failed to call service system_log/write error followed by the inability to access the webUI.
It’s been nearly 2 days of constant uptime, whereas before it would be only a matter of 1-2 hours before it would stall.
Yeah, it was Fully Kiosk that I uninstalled from the tablet. That’s not to say that Fully Kiosk it’self is actually the issue… it could be another integration combined with Fully Kiosk… and removing one OR the other would fix it. But for now, with FK uninstalled from the tablet it hasn’t went down once.
I’d be interested to hear if anybody else uninstalled FK did it also fix for them.
So I have been able to isolate the issue to the Screensaver function in Fully Kiosk. When turned on and using a third party app, after about 10 minutes of no motion, I wake it and the screen vibrates twice and gives me the log/write error. When I chose to not “Use Another App”, there is no error or vibration on wake-up. I’m not sure why the time is relevant, but it otherwise won’t trigger until at least approximately 10 minutes elapses.
More testing. When setting Auto Reload in Fully Kiosk to 600 seconds, the error doesn’t occur though it does refresh the Home Assistant interface at such time. This has me believing it has to do with the idle function of the tablet.
Hmm
I need to monitor this more closely. I was pretty sure, in the past, that this occurred both on my tablet (running fully kiosk) and my cellphone running the official ha app.
Cannot reproduce it on my cell currently.
But if it does, while fully may be part of the issue, it might not be the only culprit. At least in my case.
