| From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
|---|---|
| To: | raghu ram <raghuchennuru(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Streaming Replication Server Crash |
| Date: | 2012-10-22 07:02:22 |
| Message-ID: | 5084EF7E.5080809@ringerc.id.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-10-22 12:52:38 | Re: [ADMIN] Streaming Replication Server Crash |
| Previous Message | Craig Ringer | 2012-10-22 02:47:54 | Re: Database in psql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2012-10-22 07:05:57 | Re: Somewhat automated method of cleaning table of corrupt records for pg_dump |
| Previous Message | Scott Ribe | 2012-10-21 17:11:11 | Re: variadic function, query "in", help with syntax/function |