I'm seeing occasional occurrences of 'Malformed "D" message received.",
and I don't think it's an actual database problem, because it seems to
be related to system load and query complexity. (I'm running PostgreSQL
and Archiveopteryx on an old Dell 2850.)
A very repeatable way of triggering this is to enter (I use Gnus as a
MUA) a mail group where I've marked ('!') a lot of messages over time
for permanent keeping, so that I'm forcing the fetching of header
information for a large number of messages of varying ages. AOX will
then log the error message, and I'll get a message list in Gnus that
shows all the messages, but without Subject: fields. To work around it,
I can, instead, start by just fetching the last few messages, exit the
group, fetch a larger number, and so, in three or four iterations of
this, end up able to get everything in one go.
Because of this, I'm suspecting timeout problems as the real reason.
Is there something I can do to get more complete information from AOX
about what's actually happening here?
Log samples from a few days ago (AOX logs in UTC, pgsql in CEST):
Sep 27 07:39:37 barsoom Archiveopteryx: 668/6 Malformed "D" message received.
(on backend 1)
Sep 27 07:39:37 barsoom Archiveopteryx: 668/2/2/93004/1/2 Malformed "D" message
received.
Sep 27 09:39:37 barsoom postgres[1953]: [26-1] user=aox db=archiveopteryx LOG:
could not send data to client: Broken pipe
Sep 27 09:39:37 barsoom postgres[1953]: [26-2] user=aox db=archiveopteryx
STATEMENT: select hf.message, hf.part, hf.position, fn.name, hf.value from
header_fields hf join field_names fn on (hf.field=fn.id) where
hf.message=any($1) order by hf.message, hf.part
Sep 27 09:39:37 barsoom postgres[1953]: [27-1] user=aox db=archiveopteryx
FATAL: connection to client lost
Sep 27 09:39:37 barsoom postgres[1953]: [27-2] user=aox db=archiveopteryx
STATEMENT: select hf.message, hf.part, hf.position, fn.name, hf.value from
header_fields hf join field_names fn on (hf.field=fn.id) where
hf.message=any($1) order by hf.message, hf.part
-tih
--
Most people who graduate with CS degrees don't understand the significance
of Lisp. Lisp is the most important idea in computer science. --Alan Kay
