#Docker debugging
feral forum
These are separate commands, hence they are in their own code block separated by a ,.
steel plover
First command;
docker logs -t hassio_cli
Error response from daemon: No such container: hassio_cli
journal is abit long , any way to export it?
or any part you need particular?
feral forum
The top has the newest information. It's sorted reverse by date. Just share that for now.
feral forum
q.
Ah. It's cut off. Try journalctl -ru docker.service | less, journalctl -ru hassos-supervisor.service | less.
feral forum
You shared the same picture twice.
feral forum
Now you shared the same ljnk three times.
feral forum
Shows different things now and the old pictures are removed.
I wanted to see that ./run ... ex... message in more detail.
steel plover
Tell me what you need right now,
I ran the 2 commands
2 pictures from the commands
Command 1;
https://imgur.com/9Iy0IAe
command 2;
https://imgur.com/dIFBlHk
feral forum
Try to scroll a bit down with the arrow keys for command 1.
steel plover
ok
how long should I scroll, looks the same all the time
ok found something
Thats something you need?
feral forum
Yeah that's what i wanted to see.
steel plover
🙂
feral forum
Alright. Do a snapshot and we get to work.
steel plover
Did one
feral forum
Show me docker ps -a | grep superv.
steel plover
feral forum
Let me test if what I was trying to do works first.
Okay this is a bit hacky but here we go
systemctl stop hassos-supervisor
docker stop hassio_supervisor hassio_cli
docker rm hassio_supervisor hassio_cli
docker system prune -af
/usr/sbin/hassos-supervisor
Let the last part run until you see hassio_supervisor. Then press CTRL+C and reboot.
steel plover
Will do
rebooting
ah fuck it rebooted to rescure shell, hold on
ok waiting for sueprvisor to start up
feral forum
That procedure should completely recreate the supervisor and the CLI images and containers.
And also remove a bunch of junk, unused networks, images, containers and so on.
steel plover
That is further than I got yesterday, it always crashed on "warn cli emergency" thing
We got an error
System information
error returned from supervisor: System is not ready with state: setup
ha >
feral forum
At least you got the CLI now.
steel plover
yes
feral forum
Check ha supervisor logs.
steel plover
Exact same message;
{"result":"error","message":"System is not ready with state: setup"}
feral forum
That's all it says?
steel plover
yes
feral forum
Because that on its own is not relaly all that helpful.
feral forum
Yeah something is still not right. That should not be in JSON format.
Try ha supervisor repair.
feral forum
Wait a few minutes, then try a reboot again and see if anything changed.
steel plover
ok
Rebooting
what is the command for rebooting inside HA?
successfully rebooted
looks like it was successful? 🙂
Seems like I can access home assistant via the app again and everything looks good!
feral forum
Sorry, was busy. You can run ha host reboot. In the normal shell you can run reboot.
That's great to hear. I strongly recommend you utilize VM snapshots and backups from now on.
- https://www.home-assistant.io/common-tasks/os/#backups
- https://github.com/jcwillox/hass-auto-backup
Make sure you store the backup outside of the VM 🙂
steel plover
I had autobackup to google drive 😦 but it malfunctioned for 2 years apparently...
Now my VMware is crashing and wont let me snapshot.. hahah omg
feral forum
But you use Virtualbox?
steel plover
yes oracle virtualbox
feral forum
Hmm.