Thread: How to begin to debug FATAL: invalid frontend message type 77 error messages?

On Thu, Apr 30, 2009 at 12:16 PM, Keaton Adams <kadams@mxlogic.com> wrote:
> 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

what are you connecting to the database with?  I bet not libpq.

merlin

Keaton Adams wrote:
> Any ideas on how to debug these types of error messages?

Maybe you should start by telling us:

- your PostgreSQL server version
- What platform your server is running on
- Your PostgreSQL client driver type and version ( native libpq? pgodbc?
jdbc? npgsql? etc)
- How you're using the client or client driver

... etc

--
Craig Ringer

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