Title: RE: [GENERAL] postmaster going down own its on
hi,
i noticed the script, and at places it says
received fast shutdown request<2006-04-10 10:25:05
IST%>LOG: aborting any active transactions<2006-04-10 10:25:05
IST%idle>FATAL: terminating connection due to a
Title: RE: [GENERAL] postmaster going down own its on
hi,
i noticed the script, and at places it says
received fast shutdown request<2006-04-10 10:25:05
IST%>LOG: aborting any active transactions<2006-04-10 10:25:05
IST%idle>FATAL: terminating connection due to a
On Sat, Apr 08, 2006 at 08:02:04PM +0530, surabhi.ahuja wrote:
>
> the scenario in which the above took place was somewhat like this
> we have a script to stop some of the processes running in the background.
>
> this script was run, and all the processes got stopped
>
> then another script will
Title: RE: [GENERAL] postmaster going down own its on
the scenario in which the above took place was somewhat like this
we have a script to stop some of the processes running in the background.
this script was run, and all the processes got stopped
then another script will start these
Douglas McNaught <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> writes:
>> Could be. The actual standard use of SIGTERM is to kill processes
>> belonging to your terminal process group when you log out.
> I thought that was SIGHUP?
Doh. Not enough caffeine absorbed yet.
As penance,
Tom Lane <[EMAIL PROTECTED]> writes:
> Martijn van Oosterhout writes:
>> On Fri, Apr 07, 2006 at 03:03:09PM +0100, Richard Huxton wrote:
>>> What would be sending SIGTERM to a backend?
>
>> The only other thing I've ever heard of is some systems do a sigterm
>> when you pass a quota limit?
>
> Co
Martijn van Oosterhout writes:
> On Fri, Apr 07, 2006 at 03:03:09PM +0100, Richard Huxton wrote:
>> What would be sending SIGTERM to a backend?
> The only other thing I've ever heard of is some systems do a sigterm
> when you pass a quota limit?
Could be. The actual standard use of SIGTERM is t
On Fri, Apr 07, 2006 at 03:03:09PM +0100, Richard Huxton wrote:
> >I'm not sure it's that--the OOM killer uses SIGKILL which would take
> >down the server before it could write that log entry.
>
> Hmm... (tests it) you're right. What would be sending SIGTERM to a backend?
The only other thing I'v
Douglas McNaught wrote:
Richard Huxton writes:
surabhi.ahuja wrote:
hi, is it possible for postmaster to go doen on its own?
all what the logs say is FATAL: terminating connection dur to
administrator's command.
Someone or something is issuing a kill command. It couldn't be the
infamous Linu
Richard Huxton writes:
> surabhi.ahuja wrote:
>> hi, is it possible for postmaster to go doen on its own?
>> all what the logs say is FATAL: terminating connection dur to
>> administrator's command.
>
> Someone or something is issuing a kill command. It couldn't be the
> infamous Linux out-of-mem
surabhi.ahuja wrote:
hi, is it possible for postmaster to go doen on its own?
all what the logs say is FATAL: terminating connection dur to
administrator's command.
Someone or something is issuing a kill command. It couldn't be the
infamous Linux out-of-memory handler, could it? Check your sy
It's not normal. What's the installation? OS, applications connecting to the server, etc. On Apr 7, 2006, at 8:20 AM, surabhi.ahuja wrote:hi, is it possible for postmaster to go doen on its own? all what the logs say is FATAL: terminating connection dur to administrator's command. thanks, regar
hi, is it possible for postmaster to go doen on its
own?
all what the logs say is FATAL: terminating
connection dur to administrator's command.
thanks,
regards
Surabhi
13 matches
Mail list logo