❓ [Guacamole Client] "Database no response" support wanted

[Slin-nilS]

Description

Starting the Guacamole Client Plugin failled

Reproduction steps

1. Homeassistant add Plugin
2. Install Guacamole Client
3. START Plugin
4. See error in Plugin LOG

Addon Logs

Log:

-----------------------------------------------------------
 Provided by: https://github.com/alexbelgium/hassio-addons 
-----------------------------------------------------------
/etc/cont-init.d/00-global_var.sh: executing
Timezone set from Etc/UTC to Europe/Berlin
/etc/cont-init.d/01-config_yaml.sh: executing
Wiki here : github.com/alexbelgium/hassio-addons/wiki/Add‐ons-feature-:-add-env-variables
Load environment variables from /config/addons_config/guacamole/config.yaml if existing
---------------------------------------------------------
... no env variables found, exiting
/etc/cont-init.d/01-custom_script.sh: executing
Execute /config/addons_autoscripts/guacamole.sh if existing
---------------------------------------------------------
Wiki here : github.com/alexbelgium/hassio-addons/wiki/Add-ons-feature-:-customisation
... no script found, exiting
/etc/cont-init.d/30-defaults.sh: executing
/etc/cont-init.d/40-postgres.sh: executing
Database already configured
/etc/cont-init.d/50-extensions.sh: executing
Cleaning Extensions from previous Guacamole versions
Cleaning Extensions
Enabling selected extensions
cp: cannot stat '/config/addons_config/guacamole/extensions-available/guacamole-null-1.5.3.jar': No such file or directory
Error : /etc/cont-init.d/50-extensions.sh exiting 1
/etc/cont-init.d/50-folders.sh: executing
/etc/cont-init.d/90-ingress.sh: executing
/etc/cont-init.d/99-run.sh: executing
 
Starting the upstream container
 
s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service syslogd-prepare: starting
s6-rc: info: service syslogd-prepare successfully started
s6-rc: info: service syslogd-log: starting
s6-rc: info: service syslogd-log successfully started
s6-rc: info: service syslogd: starting
s6-rc: info: service syslogd successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun guacamole (no readiness notification)
services-up: info: copying legacy longrun guacd (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun postgres (no readiness notification)
Starting postgres...
Starting guacamole guacd...
/var/run/postgresql:5432 - no response
Waiting for postgres to come up...
guacd[413]: INFO:	Guacamole proxy daemon (guacd) version 1.5.3 started
guacd[413]: INFO:	Listening on host 0.0.0.0, port 4822
s6-rc: info: service legacy-services successfully started
2023-11-12 19:50:30.762 CET [411] LOG:  starting PostgreSQL 13.12 (Ubuntu 13.12-1.pgdg22.04+1) on aarch64-unknown-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2023-11-12 19:50:30.764 CET [411] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2023-11-12 19:50:30.765 CET [411] LOG:  could not bind IPv6 address "::1": Cannot assign requested address
2023-11-12 19:50:30.765 CET [411] HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2023-11-12 19:50:30.771 CET [411] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-11-12 19:50:30.784 CET [429] LOG:  database system was interrupted while in recovery at 2023-11-12 19:50:03 CET
2023-11-12 19:50:30.784 CET [429] HINT:  This probably means that some data is corrupted and you will have to use the last backup for recovery.
2023-11-12 19:50:31.087 CET [429] LOG:  database system was not properly shut down; automatic recovery in progress
2023-11-12 19:50:31.089 CET [429] FATAL:  could not open directory "pg_stat_tmp": No such file or directory
2023-11-12 19:50:31.098 CET [411] LOG:  startup process (PID 429) exited with exit code 1
2023-11-12 19:50:31.098 CET [411] LOG:  aborting startup due to startup process failure
2023-11-12 19:50:31.106 CET [411] LOG:  database system is shut down
/var/run/postgresql:5432 - no response
Waiting for postgres to come up...
Starting postgres...
2023-11-12 19:50:32.233 CET [437] LOG:  starting PostgreSQL 13.12 (Ubuntu 13.12-1.pgdg22.04+1) on aarch64-unknown-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2023-11-12 19:50:32.234 CET [437] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2023-11-12 19:50:32.234 CET [437] LOG:  could not bind IPv6 address "::1": Cannot assign requested address
2023-11-12 19:50:32.234 CET [437] HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2023-11-12 19:50:32.239 CET [437] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-11-12 19:50:32.251 CET [439] LOG:  database system was interrupted while in recovery at 2023-11-12 19:50:31 CET
2023-11-12 19:50:32.251 CET [439] HINT:  This probably means that some data is corrupted and you will have to use the last backup for recovery.
2023-11-12 19:50:32.561 CET [439] LOG:  database system was not properly shut down; automatic recovery in progress
2023-11-12 19:50:32.563 CET [439] FATAL:  could not open directory "pg_stat_tmp": No such file or directory
2023-11-12 19:50:32.572 CET [437] LOG:  startup process (PID 439) exited with exit code 1
2023-11-12 19:50:32.572 CET [437] LOG:  aborting startup due to startup process failure
2023-11-12 19:50:32.580 CET [437] LOG:  database system is shut down
/var/run/postgresql:5432 - no response
Waiting for postgres to come up...
Starting postgres...
/var/run/postgresql:5432 - no response
2023-11-12 19:50:33.734 CET [447] LOG:  starting PostgreSQL 13.12 (Ubuntu 13.12-1.pgdg22.04+1) on aarch64-unknown-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2023-11-12 19:50:33.735 CET [447] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2023-11-12 19:50:33.736 CET [447] LOG:  could not bind IPv6 address "::1": Cannot assign requested address
2023-11-12 19:50:33.736 CET [447] HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
Waiting for postgres to come up...
2023-11-12 19:50:33.742 CET [447] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-11-12 19:50:33.757 CET [450] LOG:  database system was interrupted while in recovery at 2023-11-12 19:50:32 CET
2023-11-12 19:50:33.757 CET [450] HINT:  This probably means that some data is corrupted and you will have to use the last backup for recovery.
2023-11-12 19:50:34.051 CET [450] LOG:  database system was not properly shut down; automatic recovery in progress
2023-11-12 19:50:34.054 CET [450] FATAL:  could not open directory "pg_stat_tmp": No such file or directory
2023-11-12 19:50:34.063 CET [447] LOG:  startup process (PID 450) exited with exit code 1
2023-11-12 19:50:34.063 CET [447] LOG:  aborting startup due to startup process failure
2023-11-12 19:50:34.070 CET [447] LOG:  database system is shut down

Architecture

aarch64

OS

HAos

Specs:

rpi4-64 with ssd Core2023.11.3 Supervisor2023.11.6 Operating System11.2 Frontend20231030.2

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Slin-nilS]

Push. Still current