Thread: FATAL error frontend message invalid

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

Στις Παρασκευή 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

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