Homeassistant install wont deploy

MrJoki007

Dabbler
Joined
Jul 15, 2018
Messages
45
Hello,
right now i have a TrueCharts Homeassistant install with the version 2022.12.8_18.0.23.
Because of the change in the TrueCharts repo, it cant be updated anymore and has to be reinstalled.

Now i have the problem, when i want to create a new install, it gets stuck at deploying (1/2).
Ive tried the official Homeassistant app aswell as the new TrueCharts one. Same problem on both.

Ive tried to install another app (Pihole) and that worked without a problem.

Logs of official app:

Application Name:offhassPod Name:offhass-home-assistant-postgres-77c5894b6b-n5mnwContainer Name:home-assistant-postgres
2023-08-14 13:21:20.831465+00:002023-08-14T13:21:20.831465019Z
2023-08-14 13:21:20.831621+00:00PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-08-14 13:21:20.831651+00:002023-08-14T13:21:20.831651469Z
2023-08-14 13:21:21.569673+00:002023-08-14 13:21:21.568 UTC [1] LOG: starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2023-08-14 13:21:21.569788+00:002023-08-14 13:21:21.569 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-08-14 13:21:21.569819+00:002023-08-14 13:21:21.569 UTC [1] LOG: listening on IPv6 address "::", port 5432
2023-08-14 13:21:22.037574+00:002023-08-14 13:21:22.036 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-08-14 13:21:22.082496+00:002023-08-14 13:21:22.082 UTC [28] LOG: database system was shut down at 2023-08-14 13:20:30 UTC
2023-08-14 13:21:22.109903+00:002023-08-14 13:21:22.109 UTC [1] LOG: database system is ready to accept connections
2023-08-14 13:21:37.977357+00:002023-08-14 13:21:37.971 UTC [67] FATAL: password authentication failed for user "root"
2023-08-14 13:21:37.977483+00:002023-08-14 13:21:37.971 UTC [67] DETAIL: Role "root" does not exist.
2023-08-14 13:21:37.977544+00:00Connection matched pg_hba.conf line 99: "host all all all md5"

Fehler​

Received 400 response code from '/api/v1/namespaces/ix-offhass/pods/offhass-home-assistant-58589d779c-ngmkx/log?follow=true×tamps=true&timeoutSeconds=1800&container=home-assistant&tailLines=500'

Application Name:offhassPod Name:offhass-home-assistant-58589d779c-ngmkxContainer Name:init-postgresdb
2023-08-14 13:21:20.773790+00:00offhass-home-assistant-postgres:5432 - no response
2023-08-14 13:21:20.773920+00:00waiting for postgres
2023-08-14 13:21:22.906829+00:00offhass-home-assistant-postgres:5432 - no response
2023-08-14 13:21:22.906936+00:00waiting for postgres
2023-08-14 13:21:25.071894+00:00offhass-home-assistant-postgres:5432 - no response
2023-08-14 13:21:25.073057+00:00waiting for postgres
2023-08-14 13:21:27.194801+00:00offhass-home-assistant-postgres:5432 - no response
2023-08-14 13:21:27.195711+00:00waiting for postgres
2023-08-14 13:21:29.605683+00:00offhass-home-assistant-postgres:5432 - no response
2023-08-14 13:21:29.605787+00:00waiting for postgres
2023-08-14 13:21:31.614504+00:00offhass-home-assistant-postgres:5432 - no response
2023-08-14 13:21:31.615874+00:00waiting for postgres
2023-08-14 13:21:33.734663+00:00offhass-home-assistant-postgres:5432 - no response
2023-08-14 13:21:33.736122+00:00waiting for postgres
2023-08-14 13:21:35.855083+00:00offhass-home-assistant-postgres:5432 - no response
2023-08-14 13:21:35.855819+00:00waiting for postgres
2023-08-14 13:21:37.977677+00:00offhass-home-assistant-postgres:5432 - accepting connections

Application Name:offhassPod Name:offhass-home-assistant-58589d779c-ngmkxContainer Name:init-configs
2023-08-14 13:21:38.858244+00:00configuration.yaml exists.
2023-08-14 13:21:38.861913+00:00configuration.yaml already contains recorder
 

JoeArny

Cadet
Joined
Aug 20, 2023
Messages
1
I'm having the same issue and I was wondering if this has something to do with the fact that I'm using a HDD pool, due to the system requirement in here:


Are you using HDD pool too?
 

Black_Duck

Explorer
Joined
Oct 8, 2022
Messages
61
Hi
The first log is the database pod - that looks okay.
I can't see what's wrong from the second log.....
Did you "Enable Custom Host Path for Home Assistant Configuration Storage Volume" in you app setup? (i.e. are your config files in a pool?).
If so you will need to Disable Host Path Safety Checks. You can do that by going to "APPS", in top right go to "Settings" then "Advance Settings", then click on the check-box for "Enable Host Path Safety Checks". You will get a warning message.
 

MrJoki007

Dabbler
Joined
Jul 15, 2018
Messages
45
I'm having the same issue and I was wondering if this has something to do with the fact that I'm using a HDD pool, due to the system requirement in here:


Are you using HDD pool too?
Im using a ssd as a boot device.
But all my data including the apps are on a hdd pool.
 

MrJoki007

Dabbler
Joined
Jul 15, 2018
Messages
45
Hi
The first log is the database pod - that looks okay.
I can't see what's wrong from the second log.....
Did you "Enable Custom Host Path for Home Assistant Configuration Storage Volume" in you app setup? (i.e. are your config files in a pool?).
If so you will need to Disable Host Path Safety Checks. You can do that by going to "APPS", in top right go to "Settings" then "Advance Settings", then click on the check-box for "Enable Host Path Safety Checks". You will get a warning message.
I tried everything.
The current app with all settings set to standard values.
 

LarsR

Guru
Joined
Oct 23, 2020
Messages
719
have you switched the postgress backend from the old included one to the new seperate app?
before intalling any app that uses postgress and prometheus, you need to either migrate to the new seperate
cloudnative-pg and prometheus operators, or remove the old ones and install the new standalone apps before installing any app that requires postgress and prometheus.
See Migration guide or use:
k3s kubectl delete --grace-period 30 --v=4 -k https://github.com/truecharts/manifests/delete2 to remove old postress
k3s kubectl delete --grace-period 30 --v=4 -k https://github.com/truecharts/manifests/delete3 to remove old prometheus

then install the stand alone apps from truecharts and then install homeassistant.
 

MrJoki007

Dabbler
Joined
Jul 15, 2018
Messages
45
have you switched the postgress backend from the old included one to the new seperate app?
before intalling any app that uses postgress and prometheus, you need to either migrate to the new seperate
cloudnative-pg and prometheus operators, or remove the old ones and install the new standalone apps before installing any app that requires postgress and prometheus.
See Migration guide or use:
k3s kubectl delete --grace-period 30 --v=4 -k https://github.com/truecharts/manifests/delete2 to remove old postress
k3s kubectl delete --grace-period 30 --v=4 -k https://github.com/truecharts/manifests/delete3 to remove old prometheus

then install the stand alone apps from truecharts and then install homeassistant.
Right now i have a homeassistant install with the truecharts app with version 2022.12.8_18.0.23.
Because of the change of truecharts, this app cannot be updated to a newer version.

Since this was the secound time, i have to install truecharts apps again, i wanted to switch away from them.
 

sos_nz

Explorer
Joined
Mar 17, 2023
Messages
58
i wanted to switch away from them.
Install HAOS in a VM under SCALE.

You get the full version, ability to restore backups etc:
 

Black_Duck

Explorer
Joined
Oct 8, 2022
Messages
61
Ive postet all of the four logs, that i can view in the webinterface.
What log do you mean?
The logs you have posted are the Container Logs within the pods.
But you have the situation of "Deploying (1/2)" which means the home assistant pod is not up yet.
Need to find out why it's stuck deploying the pod (i.e why Kubernetes has not completed deploying the pod)
  • on the Apps page ("Installed Applications"), click on the "Home Assistant" box (around the word "Up to Date")
  • You should get a window pop up looking something like this:
  • Application Events.jpg
  • tap the "Application Events" and check if there are any errors in the log.
  • tap on "Container Images" to see what is deployed and what is not.
 

MrJoki007

Dabbler
Joined
Jul 15, 2018
Messages
45
The logs you have posted are the Container Logs within the pods.
But you have the situation of "Deploying (1/2)" which means the home assistant pod is not up yet.
Need to find out why it's stuck deploying the pod (i.e why Kubernetes has not completed deploying the pod)
  • on the Apps page ("Installed Applications"), click on the "Home Assistant" box (around the word "Up to Date")
  • You should get a window pop up looking something like this:
  • View attachment 69551
  • tap the "Application Events" and check if there are any errors in the log.
  • tap on "Container Images" to see what is deployed and what is not.
Oh ok, didnt know this page:

Application Events
2023-08-21 19:47:22
Back-off pulling image "homeassistant/home-assistant:2023.8.3"
2023-08-21 19:47:22
Failed to pull image "homeassistant/home-assistant:2023.8.3": rpc error: code = Unknown desc = context deadline exceeded

Container Images
homeassistant/home-assistant:2023.8.3 Up to date
postgres:13.1 Up to date
 

Black_Duck

Explorer
Joined
Oct 8, 2022
Messages
61
Oh ok, didnt know this page:

Application Events
2023-08-21 19:47:22
Back-off pulling image "homeassistant/home-assistant:2023.8.3"
2023-08-21 19:47:22
Failed to pull image "homeassistant/home-assistant:2023.8.3": rpc error: code = Unknown desc = context deadline exceeded

Container Images
homeassistant/home-assistant:2023.8.3 Up to date
postgres:13.1 Up to date
This is a Kubernetes error to do with downloading the docker image. Basically, it's timed out while trying to download it. The image is about 500M. Is your network slow?
 

Black_Duck

Explorer
Joined
Oct 8, 2022
Messages
61
Do you know how to fix it?
Kubernetes is not my forte. You could try googling the "Failed to pull image context deadline exceeded". Theres a few options there - sadly none of them simple. I'd be looking to see why you cant download 500M in 60 seconds (I think that's Kubernetes timeout).....
 

sfatula

Guru
Joined
Jul 5, 2022
Messages
608
Do you know how to fix it?
You can "fix" it by going to Apps -> Manage Docker Images and then click pull image. Image name is homeassistant/home-assistant, image tag is 2023.8.3. I honestly think that's a Scale bug the deadline. Works fine every time from pull image screen. Then you can start the app again. You might still get an error, but it won't be that error!

I moved away from Truecharts many months ago, either using IX apps (1) or using the big blue button to launch docker images. There is nothing Truecharts provided that I can't get from the original dockers.
 
Last edited:

MrJoki007

Dabbler
Joined
Jul 15, 2018
Messages
45
You can "fix" it by going to Apps -> Manage Docker Images and then click pull image. Image name is homeassistant/home-assistant, image tag is 2023.8.3. I honestly think that's a Sclae bug the deadline. Works fine every time from pull image screen. Then you can start the app again. You might still get an error, but it won't be that error!

I moved away from Truecharts many months ago, either using IX apps (1) or using the big blue button to launch docker images. There is nothing Truecharts provided that I can't get from the original dockers.
Thank you.
That fixed my problem
 
Top