pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
FATAL error frontend message invalid
3+ messages / 3 participants
[nested] [flat]

* FATAL error frontend message invalid
@ 2006-10-20 13:05 Cedric BUSCHINI <cbuschini@carax.com>
  2006-10-20 13:53 ` Re: FATAL error frontend message invalid Achilleas Mantzios <achill@matrix.gatewaynet.com>
  2006-10-20 14:39 ` Re: FATAL error frontend message invalid Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 2 replies; 3+ messages in thread

From: Cedric BUSCHINI @ 2006-10-20 13:05 UTC (permalink / raw)
  To: pgsql-admin

Hello all,

I have a "weird" fatal line in logs:
FATAL:  invalid frontend message type 48

 From what I've found it's from the client (protocol), but I cannot 
figure out what is the problem.

Any one got a clue ?

thx

Ceders




^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: FATAL error frontend message invalid
  2006-10-20 13:05 FATAL error frontend message invalid Cedric BUSCHINI <cbuschini@carax.com>
@ 2006-10-20 13:53 ` Achilleas Mantzios <achill@matrix.gatewaynet.com>
  1 sibling, 0 replies; 3+ messages in thread

From: Achilleas Mantzios @ 2006-10-20 13:53 UTC (permalink / raw)
  To: pgsql-admin

Óôéò ÐáñáóêåõÞ 20 Ïêôþâñéïò 2006 16:05, ï/ç Cedric BUSCHINI Ýãñáøå:
> Hello all,
>
> I have a "weird" fatal line in logs:
> FATAL:  invalid frontend message type 48
>
>  From what I've found it's from the client (protocol), but I cannot
> figure out what is the problem.
>
> Any one got a clue ?
>

Do you run any net management s/w on your network?
Is the FATAL msg periodical at a specific period?
Can you run a net sniffer (like tcpdump) on the pgsql server during 
the (predicted) time of the FATAL msg?

> thx
>
> Ceders
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings

-- 
Achilleas Mantzios



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: FATAL error frontend message invalid
  2006-10-20 13:05 FATAL error frontend message invalid Cedric BUSCHINI <cbuschini@carax.com>
@ 2006-10-20 14:39 ` Tom Lane <tgl@sss.pgh.pa.us>
  1 sibling, 0 replies; 3+ messages in thread

From: Tom Lane @ 2006-10-20 14:39 UTC (permalink / raw)
  To: Cedric BUSCHINI <cbuschini@carax.com>; +Cc: pgsql-admin

Cedric BUSCHINI <cbuschini@carax.com> writes:
> I have a "weird" fatal line in logs:
> FATAL:  invalid frontend message type 48

48 == ASCII '0', so I'm betting that this represents the backend
thinking that a new message starts in the middle of some text.
In other words, most likely the client sent a malformed message.

You need to figure out exactly which client is causing it ---
enabling log_connections and adding ID info to log_line_prefix
may help.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2006-10-20 14:39 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-10-20 13:05 FATAL error frontend message invalid Cedric BUSCHINI <cbuschini@carax.com>
2006-10-20 13:53 ` Achilleas Mantzios <achill@matrix.gatewaynet.com>
2006-10-20 14:39 ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox