View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000522Pgpool-IIBugpublic2019-06-18 16:122019-09-17 15:20
Reportervan Assigned Topengbo  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionopen 
Product Version4.0.5 
Summary0000522: Error :EOF encountered with frontend
DescriptionHi ,

I am getting following error in Freebsd 4.0.5

019-06-18 07:01:37: pid 2600: ERROR: unable to read data from frontend
2019-06-18 07:01:37: pid 2600: DETAIL: EOF encountered with frontend
2019-06-18 07:01:37: pid 2598: ERROR: unable to read data from frontend
2019-06-18 07:01:37: pid 2598: DETAIL: EOF encountered with frontend
2019-06-18 07:01:37: pid 3590: ERROR: unable to read data from frontend
2019-06-18 07:01:37: pid 3590: DETAIL: EOF encountered with frontend
2019-06-18 07:01:37: pid 3539: ERROR: unable to read data from frontend
2019-06-18 07:01:37: pid 3539: DETAIL: EOF encountered with frontend
2019-06-18 07:01:37: pid 2602: ERROR: unable to read data from frontend
2019-06-18 07:01:37: pid 2602: DETAIL: EOF encountered with frontend



PGPOOL configuration:


backend_hostname0 = 'localhost'
                                   # Host name or IP address to connect to for backend 0
backend_port0 = 5454
                                   # Port number for backend 0
backend_weight0 = 1
                                   # Weight for backend 0 (only in load balancing mode)
backend_flag0 = 'ALWAYS_MASTER'
                                   # Controls various backend behavior
                                   # ALLOW_TO_FAILOVER, DISALLOW_TO_FAILOVER


TagsNo tags attached.

Activities

pengbo

2019-06-18 21:06

developer   ~0002665

Could you show more debug log?

van

2019-06-20 03:42

reporter   ~0002669

2019-06-19 19:00:53: pid 38278: DEBUG: function call walker, function name: "pg_get_expr"
2019-06-19 19:00:53: pid 38278: DEBUG: comparing function name in blacklist/whitelist regex array
2019-06-19 19:00:53: pid 38278: DETAIL: pattern_compare: black_function_list (^nextval$) not matched: pg_get_expr
2019-06-19 19:00:53: pid 38278: DEBUG: comparing function name in blacklist/whitelist regex array
2019-06-19 19:00:53: pid 38278: DETAIL: pattern_compare: black_function_list (^setval$) not matched: pg_get_expr
2019-06-19 19:00:53: pid 38278: DEBUG: comparing function name in blacklist/whitelist regex array
2019-06-19 19:00:53: pid 38278: DETAIL: pattern_compare: black_function_list (^currval$) not matched: pg_get_expr
2019-06-19 19:00:53: pid 38278: DEBUG: comparing function name in blacklist/whitelist regex array
2019-06-19 19:00:53: pid 38278: DETAIL: pattern_compare: black_function_list (^lastval$) not matched: pg_get_expr
2019-06-19 19:00:53: pid 38278: DEBUG: comparing function name in blacklist/whitelist regex array
2019-06-19 19:00:53: pid 38278: DETAIL: pattern_compare: black_function_list (^nextval$) not matched: pg_get_expr
2019-06-19 19:00:53: pid 38278: DEBUG: comparing function name in blacklist/whitelist regex array
2019-06-19 19:00:53: pid 38278: DETAIL: pattern_compare: black_function_list (^setval$) not matched: pg_get_expr
2019-06-19 19:00:53: pid 38278: DEBUG: system catalog walker, checking relation "pg_class"
2019-06-19 19:00:53: pid 38278: DEBUG: do_query: extended:0 query:"SELECT count(*) FROM pg_class AS c, pg_namespace AS n WHERE c.oid = pg_catalog.to_regclass('"pg_class"') AND c.relnamespa
ce = n.oid AND n.nspname = 'pg_catalog'"
2019-06-19 19:00:53: pid 38278: CONTEXT: while searching system catalog, When relcache is missed
2019-06-19 19:00:53: pid 38225: ERROR: unable to read data from frontend
2019-06-19 19:00:53: pid 38225: DETAIL: EOF encountered with frontend
2019-06-19 19:00:53: pid 38225: DEBUG: RESET ALL CONFIG VARIABLES
2019-06-19 19:00:53: pid 38278: DEBUG: system catalog walker, checking relation "pg_namespace"
2019-06-19 19:00:53: pid 38278: DEBUG: do_query: extended:0 query:"SELECT count(*) FROM pg_class AS c, pg_namespace AS n WHERE c.oid = pg_catalog.to_regclass('"pg_namespace"') AND c.relnam
espace = n.oid AND n.nspname = 'pg_catalog'"
2019-06-19 19:00:53: pid 38278: CONTEXT: while searching system catalog, When relcache is missed
2019-06-19 19:00:53: pid 38278: DEBUG: system catalog walker, checking relation "pg_attribute"
2019-06-19 19:00:53: pid 38278: DEBUG: do_query: extended:0 query:"SELECT count(*) FROM pg_class AS c, pg_namespace AS n WHERE c.oid = pg_catalog.to_regclass('"pg_attribute"') AND c.relnam
espace = n.oid AND n.nspname = 'pg_catalog'"
2019-06-19 19:00:53: pid 38278: CONTEXT: while searching system catalog, When relcache is missed
2019-06-19 19:00:53: pid 38278: DEBUG: system catalog walker, checking relation "pg_type"
2019-06-19 19:00:53: pid 38278: DEBUG: system catalog walker, checking relation "pg_attrdef"
2019-06-19 19:00:53: pid 38278: DEBUG: do_query: extended:0 query:"SELECT count(*) FROM pg_class AS c, pg_namespace AS n WHERE c.oid = pg_catalog.to_regclass('"pg_attrdef"') AND c.relnames
pace = n.oid AND n.nspname = 'pg_catalog'"
2019-06-19 19:00:53: pid 38278: CONTEXT: while searching system catalog, When relcache is missed
2019-06-19 19:00:53: pid 38278: DEBUG: could not load balance because systems catalogs are used
2019-06-19 19:00:53: pid 38278: DETAIL: destination = 2 for query= "select n.nspname, c.relname, a.attname, a.atttypid, t.typname, a.attnum, a.attlen, a.atttypmod, a.attnotnull, c.relhasru
les, c.relkind, c.oid, pg_get_expr(d.adbin, d.adrelid), case t.typtype when 'd' then t.typbasetype else 0 end, t.typtypmod, c.relhasoids from (((pg_catalog.pg_class c inner join pg_catalog.
pg_namespace n on n.oid = c.relnamespace and c.oid = 16388) inner join pg_catalog.pg_attribute a on (not a.attisdropped) and a.attnum > 0 and a.attrelid = c.oid) inner join pg_catalog.pg_ty
pe t on t.oid = a.atttypid) left outer join pg_attrdef d on a.atthasdef and d.adrelid = a.attrelid and d.adnum = a.attnum order by n.nspname, c.relname, attnum"
2019-06-19 19:00:53: pid 38278: DEBUG: waiting for query response
2019-06-19 19:00:53: pid 38278: DETAIL: waiting for backend:0 to complete the query
2019-06-19 19:00:53: pid 38278: DEBUG: Bind: waiting for master completing the query

van

2019-06-20 04:19

reporter   ~0002670

Hi pengbo,

This is coming randomly

Some time in the start only its coming
2019-06-19 19:51:14: pid 57161: LOG: pgpool-II successfully started. version 4.0.2 (torokiboshi)
2019-06-19 19:51:14: pid 57161: LOG: node status[0]: 0
2019-06-19 19:51:15: pid 57162: ERROR: unable to read data from frontend
2019-06-19 19:51:15: pid 57162: DETAIL: EOF encountered with frontend
2019-06-19 19:51:16: pid 57166: ERROR: unable to read data from frontend
2019-06-19 19:51:16: pid 57166: DETAIL: EOF encountered with frontend
2019-06-19 19:51:19: pid 57169: ERROR: unable to read data from frontend
2019-06-19 19:51:19: pid 57169: DETAIL: EOF encountered with frontend
2019-06-19 19:51:20: pid 57183: ERROR: unable to read data from frontend
2019-06-19 19:51:20: pid 57183: DETAIL: EOF encountered with frontend
2019-06-19 19:51:22: pid 57193: ERROR: unable to read data from frontend
2019-06-19 19:51:22: pid 57193: DETAIL: EOF encountered with frontend
2019-06-19 19:51:25: pid 57191: ERROR: unable to read data from frontend
2019-06-19 19:51:25: pid 57191: DETAIL: EOF encountered with frontend
2019-06-19 19:51:28: pid 57243: ERROR: unable to read data from frontend
2019-06-19 19:51:28: pid 57243: DETAIL: EOF encountered with frontend
2019-06-19 19:51:28: pid 57259: ERROR: unable to read data from frontend
2019-06-19 19:51:28: pid 57259: DETAIL: EOF encountered with frontend

van

2019-06-20 04:25

reporter   ~0002671

2019-06-19 19:58:40: pid 58961: LOG: pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 59953 statement: " DO $$ BEGIN IF NOT EXISTS ( SELECT 1 FROM pg_class c JOIN pg_namespace n ON n.oid = c.relnamespace WHERE c.relname = 'af_web_uuid_report_first_l4_report_id_index' AND n.nspname = 'public' ) THEN CREATE INDEX af_web_uuid_report_first_l4_report_id_index ON public.af_web_uuid_report_first_l4 (report_id ); END IF; END$$; " message: "relation "public.af_web_uuid_report_first_l4" does not exist"
2019-06-19 19:58:58: pid 58715: ERROR: unable to read data from frontend
2019-06-19 19:58:58: pid 58715: DETAIL: EOF encountered with frontend
2019-06-19 19:59:00: pid 58664: LOG: backend [0]: NOTICE: identifier "perf_wsserviceclassstatstable_pass_through_connection_report_l1_p0" will be truncated to "perf_wsserviceclassstatstable_pass_through_connection_report_l1"
2019-06-19 19:59:18: pid 58394: ERROR: unable to read data from frontend
2019-06-19 19:59:18: pid 58394: DETAIL: EOF encountered with frontend
2019-06-19 19:59:26: pid 58354: ERROR: unable to read data from frontend
2019-06-19 19:59:26: pid 58354: DETAIL: EOF encountered with frontend
2019-06-19 19:59:30: pid 58889: ERROR: unable to read data from frontend
2019-06-19 19:59:30: pid 58889: DETAIL: EOF encountered with frontend
2019-06-19 19:59:42: pid 58556: ERROR: unable to read data from frontend
2019-06-19 19:59:42: pid 58556: DETAIL: EOF encountered with frontend
2019-06-19 19:59:47: pid 59084: ERROR: unable to read data from frontend
2019-06-19 19:59:47: pid 59084: DETAIL: EOF encountered with frontend
2019-06-19 19:59:57: pid 58357: ERROR: unable to read data from frontend
2019-06-19 19:59:57: pid 58357: DETAIL: EOF encountered with frontend
2019-06-19 20:00:01: pid 58774: ERROR: unable to read data from frontend

pengbo

2019-06-20 14:12

developer   ~0002672

I can't find any reason from log?

PostgreSQL's protocol requires clients to send particular packet before they disconnect the connection.
If client disconnects the connection without sending the packet, Pgpool will output "unable to read data from frontend" error.

Could you check if the client connection was terminated abnormally or is unstable network between client and pgpool?

pengbo

2019-08-19 08:58

developer   ~0002792

No response more than one month. Could I close this issue?

Issue History

Date Modified Username Field Change
2019-06-18 16:12 van New Issue
2019-06-18 21:06 pengbo Note Added: 0002665
2019-06-20 03:42 van Note Added: 0002669
2019-06-20 04:19 van Note Added: 0002670
2019-06-20 04:25 van Note Added: 0002671
2019-06-20 13:40 pengbo Status new => assigned
2019-06-20 14:12 pengbo Note Added: 0002672
2019-06-20 14:12 pengbo Status assigned => feedback
2019-08-15 16:31 t-ishii Assigned To => pengbo
2019-08-15 16:31 t-ishii Status feedback => assigned
2019-08-19 08:58 pengbo Note Added: 0002792
2019-09-17 15:20 pengbo Status assigned => closed