Re: Backend exited with signal 14?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Boes <jboes(at)nexcerpt(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Backend exited with signal 14?
Date: 2003-05-22 21:32:16
Message-ID: 10913.1053639136@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Jeff Boes <jboes(at)nexcerpt(dot)com> writes:
> We had a production server crash last night. The postmaster log is given
> below:
> 2003-05-22 03:16:22 [26031] DEBUG: server process (pid 16661) was
> terminated by signal 14

It's really hard to see how that could happen. There is no point in the
lifespan of a backend where there is not a valid signal handler for
SIGALRM --- it inherits SIG_IGN from the postmaster, and changes that
to a normal handler routine before it ever enables the alarm anyway.

Color me baffled ... is it possible this is a kernel or glibc bug?

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Bruce Momjian 2003-05-22 21:35:17 Re: logging modifying statements only
Previous Message Larry Rosenman 2003-05-22 21:02:06 Re: audit trail