From: Craig Ringer <ringerc@ringerc.id.au>
To: raghu ram <raghuchennuru@gmail.com>
Cc: pgsql-admin@postgresql.org, pgsql-general <pgsql-general@postgresql.org>
Subject: Re: Streaming Replication Server Crash
Date: Mon, 22 Oct 2012 15:02:22 +0800
Message-ID: <5084EF7E.5080809@ringerc.id.au> (raw)
In-Reply-To: <CALnrrJQ81icyt7EpzPwPuXPK0SbSv4+C8uyA=6Nwqh+mLw2hOw@mail.gmail.com>
References: <CALnrrJQ81icyt7EpzPwPuXPK0SbSv4+C8uyA=6Nwqh+mLw2hOw@mail.gmail.com>
On 10/19/2012 04:40 PM, raghu ram wrote:
> Hi All,
>
> We have configured Streaming Replication b/w Primary and Standby server
> and Pgpool-II load balancing module diverting
> SELECT statements to Standby server. As per our observations, Standby
> server crashed during peak hours on today and error message as follows
> 2012-10-19 12:26:46 IST [1338]: [18-1] user=,db= LOG: server process
> (PID 15565) was terminated by signal 10
>
> 2012-10-19 12:26:46 IST [1338]: [19-1] user=,db= LOG: terminating any
> other active server processes
That's odd. SIGUSR1 (signal 10) shouldn't terminate PostgreSQL.
Was the server intentionally sent SIGUSR1 by an admin? Do you know what
triggered the signal?
Are you running any procedural languages other than PL/PgSQL, or any
custom C extensions? Anything that might have unwittingly cleared the
signal handler for SIGUSR1?
--
Craig Ringer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ringerc@ringerc.id.au, raghuchennuru@gmail.com, pgsql-general@postgresql.org
Subject: Re: Streaming Replication Server Crash
In-Reply-To: <5084EF7E.5080809@ringerc.id.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox