|
Home > Archive > PostgreSQL Administration > October 2006 > FATAL error frontend message invalid
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
FATAL error frontend message invalid
|
|
| Cedric BUSCHINI 2006-10-25, 8:24 am |
| 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
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
| |
| Achilleas Mantzios 2006-10-25, 8:24 am |
| Στις Παρασκευή 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
| |
| Tom Lane 2006-10-25, 8:24 am |
| 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
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
|
|
|
|
|