ion to the server was lost. Attempting reset: Failed.
The geometry looks like:
POINT(nan nan)
Regards,
Peter Hopfgartner
R3 GIS Srl - GmbH
http://www.r3-gis.com
Tom Lane wrote
Subject: Re: [GENERAL] Getting FATAL: terminating connection due to
administrator command
Date: 15.
"Frank Ch. Eigler" wrote
Subject: Re: Getting FATAL: terminating connection due to administrator command
Date: 16.09.2010 22:59
>
>Peter Hopfgartner writes:
>
>> [...]
>> > >http://sourceware.org/systemtap/examples/process/sigmon.stp
>
>> Now we had the error, but systemtap did n
> Is there any other way [than SystemTap] I can attack this issue
> [figuring out who sent a SIGTERM]? Attach GDB?
gdb won't tell you who sent the signal.
I don't really see any specific reason why sigmon.stp wouldn't show a SIGTERM if
one was sent.
An alternative could be to use auditd with
Peter Hopfgartner writes:
> [...]
> > >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
Tom Lane wrote
Subject: Re: [GENERAL] Getting FATAL: terminating connection due to
administrator command
Date: 16.09.2010 18:49
>Peter Hopfgartner writes:
>> Tom Lane wrote
>>> Peter Hopfgartner writes:
>>>> Now we had the error
Peter Hopfgartner writes:
> Tom Lane wrote
>> Peter Hopfgartner writes:
>>> Now we had the error, but systemtap did not report any SIGTERM. Is it
>>> possible to have this error without a SIGTERM being involved?
>>
>> Hmph. I would have said not, but ...
>>
>> What PG version
Tom Lane wrote
Subject: Re: [GENERAL] Getting FATAL: terminating connection due to
administrator command
Date: 16.09.2010 17:37
>Peter Hopfgartner writes:
>> Now we had the error, but systemtap did not report any SIGTERM. Is it
>> possible to have this error wi
Peter Hopfgartner writes:
> Now we had the error, but systemtap did not report any SIGTERM. Is it
> possible to have this error without a SIGTERM being involved?
Hmph. I would have said not, but ...
What PG version is this exactly?
regards, tom lane
--
Sent via pgsql-
Peter Hopfgartner wrote
Subject: Re: [GENERAL] Getting FATAL: terminating connection due to
administrator command
Date: 16.09.2010 16:56
>Tom Lane wrote
>
>Subject: Re: [GENERAL] Getting FATAL: terminating connection due to
>administrator comm
Tom Lane wrote
Subject: Re: [GENERAL] Getting FATAL: terminating connection due to
administrator command
Date: 15.09.2010 17:40
>Peter Hopfgartner writes:
>> Tom Lane wrote
>>> This is a result of something sending SIGTERM to the backend p
Tom Lane wrote
Subject: Re: [GENERAL] Getting FATAL: terminating connection due to
administrator command
Date: 15.09.2010 17:40
>Peter Hopfgartner writes:
>> Tom Lane wrote
>>> This is a result of something sending SIGTERM to the backend p
"Joshua J. Kugler" writes:
> On Wednesday 15 September 2010, Peter Hopfgartner elucidated thus:
>> The server is a rather bare bone server for web mapping, so basically
>> PostgreSQL/PostGIS, Apache, PHP, Tomcat and little other stuff. The
>> Dell software was the only which did not come from
>> C
On Wednesday 15 September 2010, Peter Hopfgartner elucidated thus:
> The server is a rather bare bone server for web mapping, so basically
> PostgreSQL/PostGIS, Apache, PHP, Tomcat and little other stuff. The
> Dell software was the only which did not come from
> CentOS/EPEL/argeo/in-house RPM pack
Peter Hopfgartner writes:
> Tom Lane 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
Tom Lane wrote
Subject: Re: [GENERAL] Getting FATAL: terminating connection due to
administrator command
Date: 15.09.2010 16:07
>Peter Hopfgartner writes:
>> Since some days we are getting the above message.
>> Also in the PostgreSQL logs we get:
>>
On 15/09/2010 10:07 PM, Tom Lane wrote:
The server is from Dell, Dell's hardware monitoring, OpenManage, says that the
hardware, in particular memory and disk, are ok.
Never dealt with OpenManage before, but you should cast a wary eye
upon any Dell-specific software on the machine.
(A bit o
Peter Hopfgartner writes:
> Since some days we are getting the above message.
> Also in the PostgreSQL logs we get:
> FATAL: terminating connection due to administrator command
This is a result of something sending SIGTERM to the backend process.
I have heard reports of "load management" softwa
On Wed, Sep 15, 2010 at 02:55:39PM +0200, Peter Hopfgartner wrote:
> Where could I start to troubleshoot this problem.
First with staff, then with unauthorized access, then with
failover software.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 134
Hi
Since some days we are getting the above message.
The system is a current CentOS 5.5, x86_64, Postgresql 8.4 as it comes with the
packages postgresql84, postgresql84-libs etc. PostGIS is enabled, as it comes
from http://www.argeo.org/linux/argeo-el.
The error message appears from time to ti
19 matches
Mail list logo
