| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mark Alliban" <MarkA(at)idnltd(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postmaster crashes |
| Date: | 2001-02-14 23:36:44 |
| Message-ID: | 28391.982193804@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Mark Alliban" <MarkA(at)idnltd(dot)com> writes:
> pq_recvbuf: unexpected EOF on client connection
> Server process (pid 2087) exited with status 139 at Tue Feb 13 15:38:08 2001
> Terminating any active server processes...
> Server processes were terminated at Tue Feb 13 15:38:08 2001
> Reinitializing shared memory and semaphores
> The first line appears many times (once every few minutes) but doesn't cause
> a problem. However the server then exits and the database is down.
The unexpected-EOF messages are probably unrelated to the crash. What
Postgres version are you running? There should be a corefile left from
the crashed backend --- can you get a stack trace from it? How about
running the postmaster with -d2 to log queries, so that you can see what
queries were being executed at the time of the crash?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Leon Sol Levy | 2001-02-14 23:56:30 | creating assertions in functions |
| Previous Message | Jan Wieck | 2001-02-14 23:22:10 | Re: Re: tmp_pg_shadow |