search

flcontainers / guacamole

A Docker Container for Apache Guacamole, a client-less remote desktop gateway. It supports standard protocols like VNC, RDP, and SSH over HTML5. For x64, arm64 and ppc64le.
https://hub.docker.com/r/flcontainers/guacamole
GNU General Public License v3.0
322 stars 60 forks source link

Bug: Regularly get error after login #85

Closed jamess60 closed 12 months ago

jamess60 commented 1 year ago

Hi

When I attempt to log in to guac, I get an error (see screenshot). This is the second time this has happened, first time around, I couldnt fix a fix other than redeploying the container.

Screenshot 2023-07-07 at 18 16 37

Here are the container logs:

Running startup scripts Preparing Config Folder Applied owners rights on Postgres folder... DB lock removed... Running Postgres Starting Postgres... Running Guacamole server Post startup DB scripts Running postgres init Running postgres init PostgreSQL Database directory appears to contain a database; Skipping initialization guacd[31]: INFO: Guacamole proxy daemon (guacd) version 1.5.2 started guacd[31]: INFO: Listening on host 0.0.0.0, port 4822 2023-07-07 16:14:17.722 BST [30] LOG: starting PostgreSQL 13.11 on x86_64-alpine-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit 2023-07-07 16:14:17.723 BST [30] LOG: listening on IPv4 address "127.0.0.1", port 5432 2023-07-07 16:14:17.723 BST [30] LOG: could not bind IPv6 address "::1": Address not available 2023-07-07 16:14:17.723 BST [30] HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry. 2023-07-07 16:14:17.726 BST [30] LOG: listening on Unix socket "/run/postgresql/.s.PGSQL.5432" 2023-07-07 16:14:17.732 BST [59] LOG: database system was interrupted; last known up at 2023-07-06 22:25:22 BST 2023-07-07 16:14:17.810 BST [59] LOG: database system was not properly shut down; automatic recovery in progress 2023-07-07 16:14:17.830 BST [59] LOG: redo starts at 0/16C4D08 2023-07-07 16:14:17.830 BST [59] LOG: invalid record length at 0/16C4D40: wanted 24, got 0 2023-07-07 16:14:17.830 BST [59] LOG: redo done at 0/16C4D08 2023-07-07 16:14:17.863 BST [30] LOG: database system is ready to accept connections database port open... Finishing Configuration guacamole database already up-to-date. Nothing applied... Running Tomcat Tomcat started. container started Running startup scripts Preparing Config Folder Applied owners rights on Postgres folder... DB lock removed... Running Postgres Starting Postgres... Running Guacamole server Post startup DB scripts Running postgres init guacd[31]: INFO: Guacamole proxy daemon (guacd) version 1.5.2 started guacd[31]: INFO: Listening on host 0.0.0.0, port 4822 Running postgres init PostgreSQL Database directory appears to contain a database; Skipping initialization 2023-07-07 17:15:59.976 BST [30] LOG: starting PostgreSQL 13.11 on x86_64-alpine-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit 2023-07-07 17:15:59.976 BST [30] LOG: listening on IPv4 address "127.0.0.1", port 5432 2023-07-07 17:15:59.976 BST [30] LOG: could not bind IPv6 address "::1": Address not available 2023-07-07 17:15:59.976 BST [30] HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry. 2023-07-07 17:15:59.982 BST [30] LOG: listening on Unix socket "/run/postgresql/.s.PGSQL.5432" 2023-07-07 17:15:59.993 BST [58] LOG: database system was interrupted; last known up at 2023-07-07 16:14:17 BST 2023-07-07 17:16:00.119 BST [58] LOG: database system was not properly shut down; automatic recovery in progress 2023-07-07 17:16:00.132 BST [58] LOG: redo starts at 0/16C4DB8 2023-07-07 17:16:00.132 BST [58] LOG: invalid record length at 0/16C4DF0: wanted 24, got 0 2023-07-07 17:16:00.132 BST [58] LOG: redo done at 0/16C4DB8 2023-07-07 17:16:00.163 BST [30] LOG: database system is ready to accept connections database port open... Finishing Configuration guacamole database already up-to-date. Nothing applied... Running Tomcat Tomcat started. container started

MaxWaldorf commented 1 year ago

postgres doesn't seem to be correctly started... Check permissions and if you have another instance running. Especially if you bind to host

MaxWaldorf commented 1 year ago

Make sure you close the first instance before restarting (or it will fail since postgres isn't done closing)

jamess60 commented 1 year ago

Given that postgres is bundled inside the container, I have little control over it. The user running the container owns the postgres directory, I just 777'd it also (for testing).

Sadly didnt seem to help - any other ideas?