public inbox for [email protected]help / color / mirror / Atom feed
Standby server crashes in master and REL9_5_STABLE branches 4+ messages / 3 participants [nested] [flat]
* Standby server crashes in master and REL9_5_STABLE branches @ 2015-09-30 07:15 [email protected] 0 siblings, 1 reply; 4+ messages in thread From: [email protected] @ 2015-09-30 07:15 UTC (permalink / raw) To: [email protected] Hi, Today, I found that standby server crashes with latest code of master branch and REL9_5_STABLE branch. This happens not always but sometimes after doing pg_start_backup and pg_stop_backup for master server. The below error messages were shown in standby server log: FATAL: could not access status of transaction 9009 DETAIL: Could not read from file "pg_commit_ts/0000" at offset 90112: Success. CONTEXT: xlog redo Transaction/COMMIT: 2015-09-30 15:52:41.924141+09 LOG: startup process (PID 23199) exited with exit code 1 LOG: terminating any other active server processes Before this FATAL, there were some INFO but annoying messages: LOG: file "pg_commit_ts/0000" doesn't exist, reading as zeroes CONTEXT: xlog redo Transaction/COMMIT: 2015-09-30 15:47:14.747566+09; inval msgs: catcache 49 catcache 49 catcache 49 catcache 49 I cannot explain why but this crash seems to disappear if I moved HEAD to before commit 6b61955135e94b39d85571fdbb0c5a749af767f1. Regards, ======== Takashi Ohnishi [email protected] -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Standby server crashes in master and REL9_5_STABLE branches @ 2015-09-30 07:30 Michael Paquier <[email protected]> parent: [email protected] 0 siblings, 2 replies; 4+ messages in thread From: Michael Paquier @ 2015-09-30 07:30 UTC (permalink / raw) To: [email protected]; +Cc: PostgreSQL mailing lists <[email protected]>; Masao Fujii <[email protected]>; Alvaro Herrera <[email protected]>; Petr Jelinek <[email protected]> On Wed, Sep 30, 2015 at 4:15 PM, <[email protected]> wrote: > FATAL: could not access status of transaction 9009 > DETAIL: Could not read from file "pg_commit_ts/0000" at offset 90112: > Success. > CONTEXT: xlog redo Transaction/COMMIT: 2015-09-30 15:52:41.924141+09 > LOG: startup process (PID 23199) exited with exit code 1 > LOG: terminating any other active server processes > > I cannot explain why but this crash seems to disappear if I moved HEAD to > before commit 6b61955135e94b39d85571fdbb0c5a749af767f1. > Even if I have the feeling that Alvaro, Petr and/or Fujii-san already know what is going on, do you have a backtrace at hand? -- Michael ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Standby server crashes in master and REL9_5_STABLE branches @ 2015-09-30 08:51 [email protected] parent: Michael Paquier <[email protected]> 1 sibling, 0 replies; 4+ messages in thread From: [email protected] @ 2015-09-30 08:51 UTC (permalink / raw) To: [email protected]; [email protected]; +Cc: [email protected]; [email protected]; [email protected] No, I do not have a backtrace. I 'm sorry about using misleading word ‘crash’. The standby server did not cause process crash. It exited abnormally. Regards, ====== Takashi Ohnishi [email protected] From: Michael Paquier [mailto:[email protected]] Sent: Wednesday, September 30, 2015 4:30 PM To: SPS 大西 高史(三技術) <[email protected]> Cc: PostgreSQL mailing lists <[email protected]>; Masao Fujii <[email protected]>; Alvaro Herrera <[email protected]>; Petr Jelinek <[email protected]> Subject: Re: [HACKERS] Standby server crashes in master and REL9_5_STABLE branches On Wed, Sep 30, 2015 at 4:15 PM, <[email protected]<mailto:[email protected]>> wrote: FATAL: could not access status of transaction 9009 DETAIL: Could not read from file "pg_commit_ts/0000" at offset 90112: Success. CONTEXT: xlog redo Transaction/COMMIT: 2015-09-30 15:52:41.924141+09 LOG: startup process (PID 23199) exited with exit code 1 LOG: terminating any other active server processes I cannot explain why but this crash seems to disappear if I moved HEAD to before commit 6b61955135e94b39d85571fdbb0c5a749af767f1. Even if I have the feeling that Alvaro, Petr and/or Fujii-san already know what is going on, do you have a backtrace at hand? -- Michael ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Standby server crashes in master and REL9_5_STABLE branches @ 2015-09-30 11:45 Alvaro Herrera <[email protected]> parent: Michael Paquier <[email protected]> 1 sibling, 0 replies; 4+ messages in thread From: Alvaro Herrera @ 2015-09-30 11:45 UTC (permalink / raw) To: Michael Paquier <[email protected]>; +Cc: [email protected]; PostgreSQL mailing lists <[email protected]>; Masao Fujii <[email protected]>; Petr Jelinek <[email protected]> Michael Paquier wrote: > On Wed, Sep 30, 2015 at 4:15 PM, <[email protected]> wrote: > > > FATAL: could not access status of transaction 9009 > > DETAIL: Could not read from file "pg_commit_ts/0000" at offset 90112: > > Success. > > CONTEXT: xlog redo Transaction/COMMIT: 2015-09-30 15:52:41.924141+09 > > LOG: startup process (PID 23199) exited with exit code 1 > > LOG: terminating any other active server processes > > > > I cannot explain why but this crash seems to disappear if I moved HEAD to > > before commit 6b61955135e94b39d85571fdbb0c5a749af767f1. Sigh. Will fix. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2015-09-30 11:45 UTC | newest] Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2015-09-30 07:15 Standby server crashes in master and REL9_5_STABLE branches [email protected] 2015-09-30 07:30 ` Michael Paquier <[email protected]> 2015-09-30 08:51 ` [email protected] 2015-09-30 11:45 ` Alvaro Herrera <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox