Hi
added
LOG_LEVEL: debug
not sure how much you want
28-Sep-2025 07:51:15.936 INFO [main]
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
["http-nio-8080"]
28-Sep-2025 07:51:15.956 INFO [main]
org.apache.catalina.startup.Catalina.start Server startup in [8270]
milliseconds
07:51:28.439 [http-nio-8080-exec-5] DEBUG o.a.i.t.jdbc.JdbcTransaction -
Opening JDBC Connection
07:51:28.442 [http-nio-8080-exec-5] DEBUG
o.a.g.a.j.DynamicallyAuthenticatedDataSource - Creating new database
connection for pool.
07:51:28.548 [http-nio-8080-exec-5] WARN
o.a.g.e.AuthenticationProviderFacade - The "postgresql" authentication
provider has encountered an internal error which will halt the
authentication
process. If this is unexpected or you are the developer of this
authentication provider, you may wish to enable debug-level logging. If
this is expected and you wish to ignore such failures
in the future, please set "skip-if-unavailable: postgresql" within your
guacamole.properties.
07:51:28.549 [http-nio-8080-exec-5] DEBUG o.a.g.event.EventLoggingListener
- Empty authentication attempt (login screen initialization) from
[192.168.10.172, 192.168.11.31] failed:
### Error querying database. Cause: org.postgresql.util.PSQLException: The
connection attempt failed.
### The error may exist in
org/apache/guacamole/auth/jdbc/user/UserMapper.xml
### The error may involve
org.apache.guacamole.auth.jdbc.user.UserMapper.selectOne
### The error occurred while executing a query
### Cause: org.postgresql.util.PSQLException: The connection attempt
failed.
07:51:28.557 [http-nio-8080-exec-5] ERROR o.a.g.rest.RESTExceptionMapper -
Unexpected internal error:
### Error querying database. Cause: org.postgresql.util.PSQLException: The
connection attempt failed.
### The error may exist in
org/apache/guacamole/auth/jdbc/user/UserMapper.xml
### The error may involve
org.apache.guacamole.auth.jdbc.user.UserMapper.selectOne
### The error occurred while executing a query
### Cause: org.postgresql.util.PSQLException: The connection attempt
failed.
07:51:28.557 [http-nio-8080-exec-5] DEBUG o.a.g.rest.RESTExceptionMapper -
Unexpected error in REST endpoint.
org.apache.ibatis.exceptions.PersistenceException:
### Error querying database. Cause: org.postgresql.util.PSQLException: The
connection attempt failed.
### The error may exist in
org/apache/guacamole/auth/jdbc/user/UserMapper.xml
### The error may involve
org.apache.guacamole.auth.jdbc.user.UserMapper.selectOne
### The error occurred while executing a query
### Cause: org.postgresql.util.PSQLException: The connection attempt
failed.
at
org.apache.ibatis.exceptions.ExceptionFactory.wrapException(ExceptionFactory.java:30)
at
org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:156)
at
org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:147)
<cut the stack trace>
Caused by: org.postgresql.util.PSQLException: The connection attempt failed.
at
org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:358)
at
org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:54)
aused by: java.net.UnknownHostException: postgres
at
java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:567)
at
java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:751)
at org.postgresql.core.PGStream.createSocket(PGStream.java:243)
at org.postgresql.core.PGStream.<init>(PGStream.java:98)
Caused by: java.net.UnknownHostException: postgres
at
java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:567)
at
java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:751)
so it seems like postgres is not resolving ??
from guacamole container
cat /etc/hosts
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
127.0.1.1 guacamole.lan1.hme1.samad.com.au guacamole
192.168.11.121 host.containers.internal host.docker.internal
10.88.3.160 476f6bfd0afb guacamole_guacamole_1
from the postgres container
cat /etc/hosts
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
127.0.1.1 guacamole.lan1.hme1.samad.com.au guacamole
192.168.11.121 host.containers.internal host.docker.internal
10.88.3.159 67e8b96f2a40 guacamole_postgres_1
also I'm looking at migrating from docker-compose file to quadlets
On Sat, Sep 27, 2025 at 11:06 PM Nick Couchman <[email protected]> wrote:
> On Sat, Sep 27, 2025 at 6:54 AM Keyzer Suze <[email protected]> wrote:
>
>> Hi
>> I'm new to containers
>> I'm running this on proxmox lxc -> debian -> podman
>> I'm using this docker-compose.yml
>> ...
>> But recently I tried again and its failing .
>>
>> 23:37:08.696 [http-nio-8080-exec-7] WARN
>> o.a.g.e.AuthenticationProviderFacade - The "postgresql" authentication
>> provider has encountered an internal error which will halt the
>> authentication process. If this is unexpected or you are the developer of
>> this authentication provider, you may wish to enable debug-level logging.
>> If this is expected and you wish to ignore such failures in the future,
>> please set "skip-if-unavailable: postgresql" within your
>> guacamole.properties.
>> 23:37:08.709 [http-nio-8080-exec-7] INFO
>> o.a.g.a.b.s.InMemoryAuthenticationFailureTracker - Authentication has
>> failed for address "192.168.10.172" (current total failures: 1/5).
>> 23:37:08.710 [http-nio-8080-exec-7] ERROR o.a.g.rest.RESTExceptionMapper
>> - Unexpected internal error:
>> ### Error querying database. Cause: org.postgresql.util.PSQLException:
>> The connection attempt failed.
>> ### The error may exist in
>> org/apache/guacamole/auth/jdbc/user/UserMapper.xml
>> ### The error may involve
>> org.apache.guacamole.auth.jdbc.user.UserMapper.selectOne
>> ### The error occurred while executing a query
>> ### Cause: org.postgresql.util.PSQLException: The connection attempt
>> failed.
>>
>>
> This really looks like something has stopped working in your Postgres DB
> container, so might be worth verifying that. Otherwise, if you can set the
> environment variable LOG_LEVEL to "debug" for the guacamole container and
> give it another go, maybe it'll yield some more useful information.
>
>
>>
>> I'm thinking it can't connect and this is a podman issue - but I also
>> notice there as a new image pushed to docker.io - i did try the previous
>> version same issue ...
>>
>>
> The push of the later image to the Docker Hub is probably just dependency
> updates for the underlying Linux container - we haven't changed the
> released version of Guacamole since the 1.6.0 release, so nothing that
> you're seeing has changed in the Guacamole code.
>
> -Nick
>
