I was able to reproduce the failure, and the problem was simply that
"POSTGRESQL_USER" is not a deprecated variable. It's actually never been
a variable that was ever accepted by a released version of the
"guacamole/guacamole" image.
The variables are:
1. "POSTGRES_USER" (deprecated, replaced with "POSTGRESQL_USERNAME")
2. "POSTGRESQL_USERNAME" (current, chosen for 1:1 predictable
correspondence to property names).
Since there's never been a "POSTGRESQL_USER" variable accepted by the
image, there's no check for this.
With neither of those known environment variables being set, there's
nothing providing the value of the "postgresql-username" property, and
an internal error appears when the PostgreSQL username and password are
retrieved from the configuration.
If you turn on debug-level logging, the details of that error include:
"Caused by: org.apache.guacamole.GuacamoleServerException: Property
postgresql-username is required."
That really should be logged differently (you shouldn't need to dig into
a stack trace to see these details), but this is what's happening and
why there was no warning.
Grepping around as I looked into this, I saw mention of
"POSTGRESQL_USER" in the updated README.md, which is wrong. I'll correct
that as part of the other Docker-related documentation updates for this
change to hopefully avoid causing further confusion.
- Mike
On 10/3/24 6:55 PM, Nathaniel Belles wrote:
Hi Nick,
Thanks for the quick reply. I just pulled those changes and it does not
seem to have made any change. I still do not see any warnings or errors
in the docker logs. Any other ideas?
Thanks.
-Nathaniel Belles
On Oct 3, 2024, at 21:01, Nick Couchman
<vnick_at_apache_org_8yqnwvnp920300_ce2d8...@icloud.com> wrote:
On Thu, Oct 3, 2024 at 20:17 Nathaniel Belles
<mon99keymon99...@gmail.com <mailto:mon99keymon99...@gmail.com>> wrote:
Hey all,
I saw the staging of release of 1.6.0 so I hopped on to try to get
this working in docker because I’m an ARM user and have been
waiting for ARM support. I believe I found a bug but it might not
be specifically related to 1.6.0, I’m just now noticing it. I
built the docker files for guacamole-server and guacamole-client
which both succeeded (thanks for that finally getting integrated!)
but then when I went to start up the compose file I got an error
in the web and went I went to look at the logs it showed me an
error there too. After a while of debugging the issue I (just so
happened to be looking through the environment variable config
scripts for docker and) noticed that the environment variable
POSTGRESQL_USER is deprecated in place of POSTGRESQL_USERNAME but
I never got a warning about it anywhere. I was able to replace the
deprecated environment variable and it resolved the issue but I
wanted to bring it to someone’s attention to save someone else the
couple hours I lost trying to debug the error.
I believe this will be fixed when this pull request is merged:
https://github.com/apache/guacamole-client/pull/1021 <https://
github.com/apache/guacamole-client/pull/1021#issuecomment-2392495220>
If you want, you can grab the changes from that pull request and build
and verify that it does address the issues you're seeing.
-Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org
