Container not reachable after hard power off, Raspi 3B+

angelnu / docker-ccu

Script to create a docker container with the CCU2 firmware

Apache License 2.0

32 stars 13 forks source link

Container not reachable after hard power off, Raspi 3B+ #32

Closed klepptor closed 5 years ago

klepptor commented 5 years ago

Hi!

Many thx for providing the CCU3 as Docker image!

I successfully used deploy.sh to start the container using this "settings" file, I only changed the REGA_PORT to avoid a conflict with an existing nginx installation.

grafik

This setup worked fine until I tried to import a RaspberryMatic backup. The container consumed all CPU and RAM ressources of my Raspi 3 B+ and didn't finish for one hour+. I decided to turn off power.

Now the container isn't reachable any more by port 85 (nor any other).

I already tried undeploy.sh/deploy.sh and manually removed (hopefully) all remaining docker remains, but withot success. The container starts, but isn't reachable.

ccu

klepptor commented 5 years ago

Seems as if docker binds the container only to the ipv6 adress!?!?!? grafik

angelnu commented 5 years ago

Did you remove the docker volume after undeploy.sh? From your screenshot at Afterwards a new deploy.sh should bring you back to where you were.

If you try again to restore a backup and it hangs then it is useful to find out what process is the one consuming all the CPU. I did time ago restore a backup myself and it did work but it is not a scenario I test regularly.

klepptor commented 5 years ago

I just tried again:

undeploy.sh docker volume prune docker container prune docker image prune deploy.sh with my modified settings file

No luck! Still no open 0.0.0.0:85 that points to the containers :80

grafik

Maybe it's a docker problem!? I think I read about it somewhere else...

I think I will try a fresh raspbian installation to check...

angelnu commented 5 years ago

Is the docker container starting successfully? Can you please post docker logs ccu and docker inspect ccu?

klepptor commented 5 years ago

docker logs ccu

grafik

docker inspect ccu inspect_ccu.txt

from the process list: grafik

angelnu commented 5 years ago

It is hanging on detecting the type of adapter. This is usually a failed fw update or an older version of the ccu container.

Can you try with the latest version? What type of Homematic Adapter do you have?

If it still fails then there are some options:

manually reflash the adapter
killing the hanging process

klepptor commented 5 years ago

Tried with the latest container version on an fresh raspbian image, no luck.

The adapter (HM-MOD-RPI-PCB) works fine under raspberrymatic on the same raspi.

I'll give up here and maybe try again in a few months when I have more time again...