Re: Why is my Postgre server went in recovery mode all in sudden

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: nikhil raj <nikhilraj474(at)gmail(dot)com>, k(dot)knizhnik(at)postgrespro(dot)ru, pgsql-admin(at)postgresql(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: Why is my Postgre server went in recovery mode all in sudden
Date: 2018-05-09 23:40:53
Message-ID: 1de3f909-7302-23fb-d9f7-0d35be51f6a5@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 05/09/2018 11:31 AM, nikhil raj wrote:
> Hi Team,
>
> I dont have any idea why did my Postgres server crash and it says
>
> timestamp=2018-05-07 00:34:11.209
> EDT,user=,db=,app=,client=,transaction-ID=0,session_start_timestamp=2018-04-26
> 10:08:19 EDT,SQL_state=00000LOG:  worker process: parallel worker for
> PID 2864 (PID 4476) exited with exit code 0
> timestamp=2018-05-07 00:34:11.209
> EDT,user=,db=,app=,client=,transaction-ID=0,session_start_timestamp=2018-04-26
> 10:08:19 EDT,SQL_state=00000LOG:  terminating any other active server
> processes
> timestamp=2018-05-07 00:34:11.209
> EDT,user=postgres,db=Ozalo,app=[unknown],transaction-ID=0,session_start_timestamp=2018-05-07
> 00:32:46 EDT,SQL_state=00000LOG:  duration: 0.331 ms  bind <unnamed>:
> SELECT "repository"."c_token" AS "token", "repository"."c_path" AS "path"
>
>      FROM
>
>     t_e20so1_repository AS "repository" INNER JOIN
> t_e20so1_document_bigint AS "documentbigint" ON
> "repository"."c_repositoryid" = "documentbigint"."c_value"
>
>       WHERE  "documentbigint"."c_documentid" = 201989
>
>     AND  "documentbigint"."c_fieldid" =
> 'b035afc8-439f-4f2c-a9ae-e054052511fd'
> timestamp=2018-05-07 00:34:11.210 EDT,user=postgres,db=
> Ozalo,app=[unknown],transaction-ID=0,session_start_timestamp=2018-05-07
> 00:32:46 EDT,SQL_state=00000LOG:  duration: 0.061 ms  execute <unnamed>:
> SELECT "repository"."c_token" AS "token", "repository"."c_path" AS "path"
>  FROM
>  t_zs01_sys_dm AS "repository" INNER JOIN t_e20so1_document_bigint AS
> "documentbigint" ON  "repository"."c_repositoryid" =
> "documentbigint"."c_value"
>       WHERE  "documentbigint"."c_documentid" = 201989
>     AND  "documentbigint"."c_fieldid" =
> 'b035afc8-439f-4f2c-a9ae-e054052511fd'
>
>
> after Some time i was receiving this error
>
>
> timestamp=2018-05-07 00:34:11.218 EDT,user=postgres,db= Ozalo
> ,app=[unknown],transaction-ID=0,session_start_timestamp=2018-05-07
> 00:34:10 EDT,SQL_state=57P02WARNING:  terminating connection because of
> crash of another server process
> timestamp=2018-05-07 00:34:11.218 EDT,user=postgres,db= Ozalo
> ,app=[unknown],transaction-ID=0,session_start_timestamp=2018-05-07
> 00:34:10 EDT,SQL_state=57P02DETAIL:  The postmaster has commanded this
> server process to roll back the current transaction and exit, because
> another server process exited abnormally and possibly corrupted shared
> memory.
> timestamp=2018-05-07 00:34:11.218 EDT,user=postgres,db= Ozalo
> ,app=[unknown],transaction-ID=0,session_start_timestamp=2018-05-07
> 00:34:10 EDT,SQL_state=57P02HINT:  In a moment you should be able to
> reconnect to the database and repeat your command.
>
> timestamp=2018-05-07 00:34:11.357
> EDT,user=,db=,app=,client=,transaction-ID=0,session_start_timestamp=2018-04-26
> 10:08:20 EDT,SQL_state=57P02DETAIL:  The postmaster has commanded this
> server process to roll back the current transaction and exit, because
> another server process exited abnormally and possibly corrupted shared
> memory.
> timestamp=2018-05-07 00:34:11.357
> EDT,user=,db=,app=,client=,transaction-ID=0,session_start_timestamp=2018-04-26
> 10:08:20 EDT,SQL_state=57P02HINT:  In a moment you should be able to
> reconnect to the database and repeat your command.
> timestamp=2018-05-07 00:34:11.379 EDT,user=postgres,db=
> Ozalo,app=[unknown],,transaction-ID=0,session_start_timestamp=2018-05-07
> 00:34:11 EDT,SQL_state=57P03FATAL:  the database system is in recovery mode
> timestamp=2018-05-07 00:34:11.381 EDT,user=postgres,db=
> Ozalo,app=[unknown],transaction-ID=0,session_start_timestamp=2018-05-07
> 00:34:11 EDT,SQL_state=57P03FATAL:  the database system is in recovery mode
>
>
>
> what is the reason it corrupted share memory ?

At this point I don't know. More information is required:

1) What OS and version?

2) System memory size is ?

3) Where was Postgres installed from?

4) What is session_start_timestamp tracking? In other words what does it
match up to here:

https://www.postgresql.org/docs/10/static/runtime-config-logging.html

log_line_prefix

5) What is the process that started 2018-04-26 10:08:19?

6) The query in the log started at 2018-05-07 00:32:46, what is it doing?

>
> what is meant by The postmaster has commanded this server process to
> roll back the current transaction and exit, because another server
> process exited abnormally and possibly corrupted shared memory. ?
>  how much of share memory if its consume  it will crash
>
>  Please can any one help me in this
> or else what is the reason of crash of DB server
>
> Current using 10.3
> |
>  Current Config
>
> max_connections = 5000||
> shared_buffers = 7680MB ||||
> effective_cache_size = 23040MB |||
>
> |maintenance_work_mem = 1920MB min_wal_size = 1GB max_wal_size = 2GB
> checkpoint_completion_target = 0.7 wal_buffers = 16MB
> default_statistics_target = 100 random_page_cost = 1.1
> effective_io_concurrency = 200 max_worker_processes = 16
> max_parallel_workers_per_gather = 8 max_parallel_workers = 16 work_mem =
> 196kB|
>
>
>
> Thanks
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2018-05-09 23:45:03 Re: issues when installing postgres
Previous Message Adrian Klaver 2018-05-09 23:20:28 Re: Error creating plpython3u extension