Hey Again, i'm still not able to handle this error that happens once a day, all containers are up but api request to gqm gets 502 I did get the full postgres query when this usually happened:
postgres_gqm_1 | 2021-10-12T06:55:19.947186314Z 2021-10-12 06:55:19.938 UTC [35] LOG: could not send data to client: Connection reset by peer postgres_gqm_1 | 2021-10-12T06:55:19.947212467Z 2021-10-12 06:55:19.938 UTC [35] STATEMENT: SELECT postgres_gqm_1 | 2021-10-12T06:55:19.947215854Z guacamole_connection.connection_id, postgres_gqm_1 | 2021-10-12T06:55:19.947218656Z guacamole_connection.connection_name, postgres_gqm_1 | 2021-10-12T06:55:19.947221509Z parent_id, postgres_gqm_1 | 2021-10-12T06:55:19.947224165Z protocol, postgres_gqm_1 | 2021-10-12T06:55:19.947226788Z max_connections, postgres_gqm_1 | 2021-10-12T06:55:19.947229387Z max_connections_per_user, postgres_gqm_1 | 2021-10-12T06:55:19.947232302Z proxy_hostname, postgres_gqm_1 | 2021-10-12T06:55:19.947234855Z proxy_port, postgres_gqm_1 | 2021-10-12T06:55:19.947237399Z proxy_encryption_method, postgres_gqm_1 | 2021-10-12T06:55:19.947239993Z connection_weight, postgres_gqm_1 | 2021-10-12T06:55:19.947242599Z failover_only, postgres_gqm_1 | 2021-10-12T06:55:19.947245130Z MAX(start_date) AS last_active postgres_gqm_1 | 2021-10-12T06:55:19.947247726Z FROM guacamole_connection postgres_gqm_1 | 2021-10-12T06:55:19.947250330Z LEFT JOIN guacamole_connection_history ON guacamole_connection_history.connection_id = guacamole_connection.connection_id postgres_gqm_1 | 2021-10-12T06:55:19.947253528Z WHERE guacamole_connection.connection_id IN postgres_gqm_1 | 2021-10-12T06:55:19.947256208Z ( postgres_gqm_1 | 2021-10-12T06:55:19.947258731Z $1::integer postgres_gqm_1 | 2021-10-12T06:55:19.947261284Z , postgres_gqm_1 | 2021-10-12T06:55:19.947263751Z $2::integer postgres_gqm_1 | 2021-10-12T06:55:21.230273860Z , postgres_gqm_1 | 2021-10-12T06:55:21.230276158Z $25400::integer postgres_gqm_1 | 2021-10-12T06:55:21.230278327Z ) postgres_gqm_1 | 2021-10-12T06:55:21.230280533Z GROUP BY guacamole_connection.connection_id Is this helping in any way? My next step is gonna be upgrading the kernel and libs on the host and if that doesn't work to move from docker to kubernetes :( בתאריך יום א׳, 26 בספט׳ 2021 ב-10:45 מאת Regev Batchen < [email protected]>: > Hey, > > I dont have the full psql container query because i tried to do tail of > 20000 lines and it still shows > > postgres_gqm_1 | 2021-09-13T14:59:26.208973521Z , > postgres_gqm_1 | 2021-09-13T14:59:26.208975652Z > $22740::integer > postgres_gqm_1 | 2021-09-13T14:59:26.208977856Z , > postgres_gqm_1 | 2021-09-13T14:59:26.208980045Z > $22741::integer > > docker ps shows containers are healthy even when service is stuck > > Is there a way to add guacamole debug logs? > In the guacd container I have : GUACD_LOG_LEVEL: debug > but for guacamole ? > > It looks like psql did a restart after the big quarry and guacd did too > but something is not working correctly until i restart the guacd and > guacamole and then it works for a day or two, > what else can I check? > I am going to create a bash script to restart containers if service is > stuck because I really don't know what else to do :( > > > > > בתאריך יום ד׳, 22 בספט׳ 2021 ב-22:40 מאת Mike Jumper < > [email protected]>: > >> On Wed, Sep 22, 2021 at 5:45 AM Regev Batchen <[email protected]> wrote: >> >>> Hello, the postgres error happened again. >>> I dont understand why postgrece started to get stuck after i updated to >>> guacamole 1.3 , befor i had an error that it was only get stuck with no sql >>> error. >>> i use psql 12.3 and here are some logs, PLEASE let me know what else i >>> can check and debug? i have 10 more containers on this docker-compose and >>> only guacamole gets stuck. >>> >>> It just stop receiving api request and no logs are written to the guac >>> containers. >>> what causing this SELECT error? >>> >> >> Do you have the full message from the PostgreSQL container? >> >> The log message you see from guacd (Error reading "select") is not >> actually related to the database (which is only used by the webapp, not >> guacd). This is guacd letting you know that a connection to guacd was >> established and then closed during the Guacamole protocol handshake, the >> first message of which happens to be called "select". This is the result of >> a healthcheck ping within Docker and is not an error. >> >> - Mike >> >>
