[Postgres-xl-general] Excessive "Unexpected EOF" errors in GTM proxy log

Michael Misiewicz mmisiewicz at gmail.com
Tue Jan 31 19:42:23 PST 2017


Hi all,

I have a cluster with 18 datanodes, 3 coordinators, and 1 GTM and 1 GTM proxy. I am getting quite a bit of chatter in the GTM proxy log:

1:3925305088:2017-02-01 03:40:14.746 UTC -LOG:  unexpected EOF on client connection
LOCATION:  ReadCommand, proxy_main.c:2049
1:3935794944:2017-02-01 03:40:14.817 UTC -LOG:  unexpected EOF on client connection
LOCATION:  ReadCommand, proxy_main.c:2049
1:3925305088:2017-02-01 03:40:15.037 UTC -LOG:  unexpected EOF on client connection
LOCATION:  ReadCommand, proxy_main.c:2049
1:3935794944:2017-02-01 03:40:15.092 UTC -LOG:  unexpected EOF on client connection
LOCATION:  ReadCommand, proxy_main.c:2049
1:3925305088:2017-02-01 03:40:15.407 UTC -LOG:  unexpected EOF on client connection
LOCATION:  ReadCommand, proxy_main.c:2049

To the point that this is causing log files to overflow. Has anyone seen an error like this before? Near as I can tell things are working right, there’s nothing out of the ordinary in how the cluster is working. My config is: 
#===========================
# Added at initialization, 20170131_22:11:51
nodename = 'gtm_pxy1'
listen_addresses = '*'
port = 20000
gtm_host = '01.bm-datascience-dev.dev.nym2'
gtm_port = 20001
worker_threads = 100
gtm_connect_retry_interval = 1
# End of addition

Michael 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.postgres-xl.org/pipermail/postgres-xl-general-postgres-xl.org/attachments/20170131/bd4021fa/attachment.htm>


More information about the postgres-xl-general mailing list