Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM)

ok, so that's not it - i'm definitely not trapping SIGALRM (and btw,
this was only in the perl client code, which I don;t see how that could
cause the problem anyway - as opposed to in the plperlu function, which
in any case I am pretty sure was not being called when  the server
crashed)

the log entries are:

DEBUG:  server process (pid 20704) was terminated by signal 14
DEBUG:  terminating any other active server processes
NOTICE:  Message from PostgreSQL backend:
         The Postmaster has informed me that some other backend
         died abnormally and possibly corrupted shared memory.
         I have rolled back the current transaction and am
         going to terminate your database system connection and exit.
         Please reconnect to the database system and repeat your query.
[repeated]
FATAL 1:  The database system is in recovery mode
[repeated]
DEBUG:  all server processes terminated; reinitializing shared memory
and semaphores
DEBUG:  database system was interrupted at 2003-01-29 02:23:14 EST
DEBUG:  checkpoint record is at 0/1267C284
DEBUG:  redo record is at 0/1267C284; undo record is at 0/0; shutdown
FALSE
DEBUG:  next transaction id: 823075; next oid: 134017
DEBUG:  database system was not properly shut down; automatic recovery
in progress
FATAL 1:  The database system is starting up
[repeated]
DEBUG:  redo starts at 0/1267C2C4
DEBUG:  ReadRecord: record with zero length at 0/126B3D80
DEBUG:  redo done at 0/126B3D5C
FATAL 1:  The database system is starting up
[repeated]
DEBUG:  database system is ready

any ideas anyone?

Mark.




with the last NOTICE being repeated for each backend.
On Tuesday, January 28, 2003, at 03:42 PM, Tom Lane wrote:

> Mark Aufflick <mark@pumptheory.com> writes:
>> DEBUG:  server process (pid 971) was terminated by signal 14
>
> Hm, that's SIGALRM on my box, I assume so on yours too.
>
> AFAICT, there is no part of the Postgres code that runs with SIGALRM
> set to default handling: it's either SIG_IGN or the deadlock timer
> handler.
>
>> 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 wonder whether the Perl interpreter is hacking on the SIGALRM
> setting.  That would be pretty unfriendly of it (but I don't think
> Perl quite believes the notion that it might be only a subroutine
> library, and not in full control of the process...)
>
>             regards, tom lane