--------Tom Lane <tgl@xxxxxxxxxxxxx> wrote-------- Subject: Re: Getting FATAL: terminating connection due to administrator command Date: 15.09.2010 17:40 >Peter Hopfgartner <peter.hopfgartner@xxxxxxxxxx> writes: >> --------Tom Lane <tgl@xxxxxxxxxxxxx> 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 > Ok, I was able to create the packages with the debug info, adapted the script to report SIGTERM sent so any process, see attachment, tested this sending some SIGTERM and seeing them reported by systemtap. Anyway, currently we are not able to reproduce the problem on the server, magically everything seems to work on this machine. The only changes should be the 2 debug-info packages (kernel-debuginfo-common-2.6.18-194.11.3.el5.x86_64.rpm and kernel-xen-debuginfo-2.6.18-194.11.3.el5.x86_64.rpm). In the same time, the problem appeared twice today on our testing server. This suggests to drop the hardware failure hypothesis. I'm running systemtap on the testing server now, too. > regards, tom lane >
Attachment:
sigmon1.stp
Description: Binary data
-- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
