Keaton Adams schrieb:
Any ideas on how to debug these types of error messages?
Apr 30 01:36:02 mxlqa401 postgres[23600]: [3-1] FATAL: invalid frontend
message type 77
Apr 30 01:36:02 mxlqa401 postgres[23601]: [3-1] LOG: unexpected EOF on client
connection
Apr 30 01:36:02 mxlqa401 postgres[23602]: [3-1] LOG: unexpected EOF on client
connection
Apr 30 01:36:13 mxlqa401 postgres[23631]: [3-1] FATAL: invalid frontend
message type 77
Apr 30 01:36:13 mxlqa401 postgres[23632]: [3-1] LOG: unexpected EOF on client
connection
Apr 30 01:36:13 mxlqa401 postgres[23633]: [3-1] LOG: unexpected EOF on client
connection
Apr 30 01:36:24 mxlqa401 postgres[23664]: [3-1] FATAL: invalid frontend
message type 77
Apr 30 01:36:24 mxlqa401 postgres[23666]: [3-1] LOG: unexpected EOF on client
connection
Apr 30 01:36:24 mxlqa401 postgres[23665]: [3-1] LOG: unexpected EOF on client
connection
Apr 30 01:36:35 mxlqa401 postgres[23696]: [3-1] FATAL: invalid frontend
message type 77
Apr 30 01:36:35 mxlqa401 postgres[23698]: [3-1] LOG: unexpected EOF on client
connection
Apr 30 01:36:35 mxlqa401 postgres[23697]: [3-1] LOG: unexpected EOF on client
connection
Apr 30 01:36:46 mxlqa401 postgres[23728]: [3-1] FATAL: invalid frontend
message type 77
Apr 30 01:36:46 mxlqa401 postgres[23730]: [3-1] LOG: unexpected EOF on client
connection
Apr 30 01:36:46 mxlqa401 postgres[23729]: [3-1] LOG: unexpected EOF on client
connection
Maybe some monitoring software that doesn't speak
the Postgres protocol? The connects seem to occur
quite regularly every 11 seconds...
You might want to configure the log output format to include
the IP address/host name of the creator of these messages
(log_line_prefix in postgresql.conf, "%h"). Or use a packet
sniffer like wireshark.
Ciao,
Thomas
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
