#i'm having the same issue too.
1 messages · Page 1 of 1 (latest)
Things I've tried
-
Hitting
homeassistant.local:4357in the browser
Supervisor: Disconnected
Error response from daemon: No such container: hassio_supervisor -
docker logs -t hassio_supervisor
I get
exec /init: input/output error
Oof that's bad. Try journalctl -u docker.service, journalctl -u hassos-supervisor.service.
Invalid unit name "docker.service," escaped as "docker.service\x2c" (maybe you should use systemd-escape7).
Failed to add match 'journalctl': Invalid argument
When i type ha on the CLI
i get this message
Error response from daemon: Container b29d3e.... is not running
so i'm unable to run ha core restart or any ha commands
Something seems to be seriously wrong if simple commands like journalctl don't work.
uhhh.
i wonder if an OS update went wrong
journalctl works fine
journalctl -u docker.service spits out a bunch of logs
what's the most efficient way to share?
i'm on two separate devices.
It sounds like the badly behaving custom integration thing going on. Look at the first pin in the general channel BDraco gave us some diagnostics last night
About that. You typed it in as one long line. These were separate commands. I didn't epect that.
If you use a SSH client then as text, otherwise a picture must have to suffice.
Please use a code share site to share code or logs, for example:
- https://dpaste.org/ (select YAML for the language, and consider picking a longer expiry)
- http://pastie.org/ (select YAML for the language)
- https://paste.debian.net/ (you guessed it, select YAML as the language)
Please don't use Pastebin, since it can randomly add spaces to the main view. Please also don't share text as images since it makes it harder for people to help you. Remember that others may have colour blindness, impaired vision, etc.
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.
journalctl -u docker.service shows me an error message "No such container hassio_supervisor"
not sure if that's our smoking gun.
I know it's a little bit confusing but there's a hassio_supervisor container and a hassos-supervisor service.
Can you show the whole commands you used and the output?
I forgot. You might have to run it like journalctl -eu docker.service to get to the bottom or just press PGDOWN/END.
i ran -r
which shows the logs in reverse
so what you're seeing in those two images are logs in reverse.
That's also an option. I'm just not used to reading logs in reverse.
I helped Superman10 to re-create the supervisor container. It takes a few commands but you could try that? #1228804362231349409 message
Unfortunately I don't see a whole lot of useful things in the logs other than that exec error which I'm not sure what's causing it.
Based on the logs you have aarch64 too so the commands should work the same for you.
Yep.
that's what i was inclined to try
to recreate that missing docker image to begin with.
thanks. i'll try that and let you know.