Thread: SignalChildren: sending signal 12

SignalChildren: sending signal 12

From
"Gaetano Mendola"
Date:
Hi today the postmaster ( Postgres 7.3.2 ) sent to all back end the signal
12!!!!

Apr  9 17:20:03 sdr2 postgres[16882]: [420740] DEBUG:  BackendStartup:
forked pid=5217 socket=9
Apr  9 17:20:03 sdr2 postgres[16882]: [420741] DEBUG:  child process (pid
5216) exited with exit code 0
Apr  9 17:20:03 sdr2 postgres[16882]: [420742] DEBUG:  child process (pid
5217) exited with exit code 0
Apr  9 17:20:04 sdr2 postgres[16882]: [420743] DEBUG:  child process (pid
5161) exited with exit code 0
Apr  9 17:20:05 sdr2 postgres[16882]: [420744] DEBUG:  SignalChildren:
sending signal 12 to process 5191
Apr  9 17:20:05 sdr2 postgres[16882]: [420745] DEBUG:  SignalChildren:
sending signal 12 to process 5164
Apr  9 17:20:05 sdr2 postgres[16882]: [420746] DEBUG:  SignalChildren:
sending signal 12 to process 5163
Apr  9 17:20:05 sdr2 postgres[16882]: [420747] DEBUG:  SignalChildren:
sending signal 12 to process 4774
......................
Apr  9 17:20:05 sdr2 postgres[16882]: [420785] DEBUG:  SignalChildren:
sending signal 12 to process 9794
Apr  9 17:20:05 sdr2 postgres[16882]: [420786] DEBUG:  SignalChildren:
sending signal 12 to process 9784
Apr  9 17:20:05 sdr2 postgres[16882]: [420787] DEBUG:  SignalChildren:
sending signal 12 to process 9771
Apr  9 17:20:05 sdr2 postgres[16882]: [420788] DEBUG:  SignalChildren:
sending signal 12 to process 9770
Apr  9 17:20:05 sdr2 postgres[16882]: [420789] DEBUG:  SignalChildren:
sending signal 12 to process 9676



after 10 minutes the disaster:


Apr  9 17:30:01 sdr2 postgres[16882]: [421879] DEBUG:  child process (pid
6020) was terminated by signal 11
Apr  9 17:30:01 sdr2 postgres[16882]: [421880] LOG:  server process (pid
6020) was terminated by signal 11
Apr  9 17:30:01 sdr2 postgres[16882]: [421881] LOG:  terminating any other
active server processes
Apr  9 17:30:01 sdr2 postgres[16882]: [421882] DEBUG:  CleanupProc: sending
SIGQUIT to process 6021
Apr  9 17:30:01 sdr2 postgres[16882]: [421883] DEBUG:  CleanupProc: sending
SIGQUIT to process 6019
Apr  9 17:30:01 sdr2 postgres[16882]: [421884] DEBUG:  CleanupProc: sending
SIGQUIT to process 6011
............
Apr  9 17:30:01 sdr2 postgres[16882]: [421929] DEBUG:  CleanupProc: sending
SIGQUIT to process 10961
Apr  9 17:30:01 sdr2 postgres[16882]: [421930] DEBUG:  CleanupProc: sending
SIGQUIT to process 10959
Apr  9 17:30:01 sdr2 postgres[16882]: [421931] DEBUG:  CleanupProc: sending
SIGQUIT to process 9794
Apr  9 17:30:01 sdr2 postgres[16882]: [421932] DEBUG:  CleanupProc: sending
SIGQUIT to process 9784
Apr  9 17:30:01 sdr2 postgres[16882]: [421933] DEBUG:  CleanupProc: sending
SIGQUIT to process 9771
Apr  9 17:30:01 sdr2 postgres[16882]: [421934] DEBUG:  CleanupProc: sending
SIGQUIT to process 9770
Apr  9 17:30:01 sdr2 postgres[16882]: [421935] DEBUG:  CleanupProc: sending
SIGQUIT to process 9676



Any idea ?


Regards Gaetano


Re: SignalChildren: sending signal 12

From
Tom Lane
Date:
"Gaetano Mendola" <mendola@bigfoot.com> writes:
> Apr  9 17:30:01 sdr2 postgres[16882]: [421879] DEBUG:  child process (pid
> 6020) was terminated by signal 11

Backtrace from core dump, please?

You didn't say what platform you are on, but I'm guessing the signal 12
is SIGUSR2, which would be normal operation.  Being ten minutes before,
it seems unlikely to be related.

            regards, tom lane


Re: SignalChildren: sending signal 12

From
"Mendola Gaetano"
Date:
I found no core on the machine, may be I should configure postgres
in order to generate a core in this case I don't have clue how do it.

The box is a Linux Box

# select version();
                           version
-------------------------------------------------------------
 PostgreSQL 7.3.2 on i686-pc-linux-gnu, compiled by GCC 2.96


regards, gaetano mendola

----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Gaetano Mendola" <mendola@bigfoot.com>
Cc: <pgsql-admin@postgresql.org>
Sent: Wednesday, April 09, 2003 6:11 PM
Subject: Re: [ADMIN] SignalChildren: sending signal 12


> "Gaetano Mendola" <mendola@bigfoot.com> writes:
> > Apr  9 17:30:01 sdr2 postgres[16882]: [421879] DEBUG:  child process
(pid
> > 6020) was terminated by signal 11
>
> Backtrace from core dump, please?
>
> You didn't say what platform you are on, but I'm guessing the signal 12
> is SIGUSR2, which would be normal operation.  Being ten minutes before,
> it seems unlikely to be related.
>
> regards, tom lane
>


Re: SignalChildren: sending signal 12

From
Tom Lane
Date:
"Mendola Gaetano" <mendola@bigfoot.com> writes:
> I found no core on the machine, may be I should configure postgres
> in order to generate a core in this case I don't have clue how do it.

You need to set "ulimit -c unlimited" before launching the postmaster.
It's probably easiest to add that to the startup script you're using.

            regards, tom lane


Re: SignalChildren: sending signal 12

From
"Mendola Gaetano"
Date:
I'll do it after the nex signal 11

:-(


----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Mendola Gaetano" <mendola@bigfoot.com>
Cc: <pgsql-admin@postgresql.org>
Sent: Wednesday, April 09, 2003 6:34 PM
Subject: Re: [ADMIN] SignalChildren: sending signal 12


> "Mendola Gaetano" <mendola@bigfoot.com> writes:
> > I found no core on the machine, may be I should configure postgres
> > in order to generate a core in this case I don't have clue how do it.
>
> You need to set "ulimit -c unlimited" before launching the postmaster.
> It's probably easiest to add that to the startup script you're using.
>
> regards, tom lane