[
https://issues.apache.org/jira/browse/GUACAMOLE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064509#comment-17064509
]
Douglas Heriot commented on GUACAMOLE-919:
------------------------------------------
Using pgbouncer seems to have solved the issue for me. It's interesting I can
see in the pgbouncer logs from a few hours after using Guacamole:
{code:java}
2020-03-22 16:40:42.176 UTC [1] LOG S-0x562e8b466510:
guacamole/guacamole@10.10.0.236:5432 closing because: server conn crashed?
(age=12690s)2020-03-22 16:40:42.176 UTC [1] LOG C-0x562e8b403b70:
guacamole/guacamole@172.19.0.4:36364 closing because: server conn crashed?
(age=12336s)2020-03-22 16:40:42.176 UTC [1] WARNING C-0x562e8b403b70:
guacamole/guacamole@172.19.0.4:36364 pooler error: server conn crashed?
{code}
A quick Google search for that error seems to suggest this can be replicated by
unplugging a network cable between application and database (pretty much what
we're seeing on the tcpdump - no replies from database).
Adding the defaultNetworkTimeout option sounds like a sensible fix to handle
that case.
> An I/O error occurred while sending to the backend
> --------------------------------------------------
>
> Key: GUACAMOLE-919
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-919
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-jdbc-postgresql
> Affects Versions: 1.0.0
> Reporter: Mechanix
> Assignee: Nick Couchman
> Priority: Minor
> Attachments: image-2020-01-27-15-19-26-634.png
>
>
> Hi,
> we use guacamole with postgresql and openid extension. Guacamole and guacd is
> deployed inside a k8s cluster.
> For some reason, the authentication doesn't succeed sporadically; there is
> only a blank page and this error message in the guacamole log:
> *[pool-1-thread-1] WARN o.a.i.d.pooled.PooledDataSource - Execution of ping
> query 'SELECT 1' failed: An I/O error occurred while sending to the backend.*
> I suspect there is a weird timeout happening between guacamole and postgresql
> but couldn't figure out why.
> Any hints are much appreciated. Thanks
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
