From: | Mark Aufflick <mark(at)pumptheory(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM) |
Date: | 2003-01-28 04:13:38 |
Message-ID: | E05F3582-3276-11D7-9B20-000393C10932@pumptheory.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
DEBUG: server process (pid 971) was terminated by signal 14
DEBUG: terminating any other active server processes
seems to be happening every day or so.
The server log doesn't indicate any problems more innocuous than the
occasional unexpected EOF on client connections, a few 'adding missing
FROM-clause' and a stack of name truncation log entries.
The clients are AOLServer/OpenACS and a perl daemon that forks off a
handful of children (which only access two tables).
Both plpgsql and plperlu are used (plperlu is used for one trigger
function to post a single https form that sends an sms message, and
record the result body).
I have trolled the mail list archives and the only similar deaths I
have found are under cygwin, but I am running a fully up2date redhat
7.2 box (with custom compiled 7.2.3 from sources as of a month ago).
Any ideas would be greatly appreciated!
Cheers,
Mark.
--
Mark Aufflick
e: mark(at)pumptheory(dot)com
w: www.pumptheory.com
p: +61 438 700 647
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-01-28 04:42:17 | Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM) |
Previous Message | Stephan Szabo | 2003-01-28 01:35:57 | Re: Documentation needs significant improvement |