Re: Getting FATAL: terminating connection due to administrator command

--------Peter Hopfgartner <peter(dot)hopfgartner(at)r3-gis(dot)com> wrote--------
Subject: Re: [GENERAL] Getting FATAL: terminating connection due to administrator command
Date: 16.09.2010 16:56

>--------Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote--------
>
>Subject: Re: [GENERAL] Getting FATAL: terminating connection due to
>administrator command
>
>Date: 15.09.2010 17:40
>
>
>
>>Peter Hopfgartner <peter(dot)hopfgartner(at)r3-gis(dot)com> writes:
>
>>> --------Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote--------
>
>>>> This is a result of something sending SIGTERM to the backend process.
>
>>
>
>>> Can I trace where the SIGTERM comes from?
>
>>
>
>>If this is a recent Red-Hat-based release, I think that systemtap could
>
>>probably be used to determine that. There's a script here that solves
>
>>a related problem:
>
>>http://sourceware.org/systemtap/examples/process/sigmon.stp
>

Now we had the error, but systemtap did not report any SIGTERM. Is it possible to have this error without a SIGTERM being involved? As mentioned in a previous mail, I've modified the script to report SIGTERM sent to any process.

Peter