[Pgpool-general] [pgpool] Checking postgreSQL log entries after online-recovery

[Mark White]

I've got online recovery working in that one node in a two-node test
cluster can be taken down, an update made to the db through psql on the
pgpool instance, and pcp_recovery_node brings the dead node back into
play, and the update shows on the recovered node when viewed with pgAdmin.

During recovery, postgres is showing FATAL error messages and rsync 
errors (log attached to end of email) which are worrying.

I see another post which says:

> OK, I see it's normal that it asks for files which are not present:
>
> http://developer.postgresql.org/pgdocs/postgres/continuous-
> archiving.html

So maybe everything is fine as it is. Any reassuring comments or
pointers of what to look at would be welcome.


Mark...

---postgresql.log---
2010-06-15 07:19:32 UTC LOG:  incomplete startup packet
2010-06-15 07:19:32 UTC FATAL:  the database system is starting up
rsync: link_stat "/data/main/wal_archive/00000002.history" failed: No
such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1523) [receiver=3.0.6]
2010-06-15 07:19:33 UTC FATAL:  the database system is starting up
2010-06-15 07:19:33 UTC FATAL:  the database system is starting up
2010-06-15 07:19:34 UTC LOG:  restored log file
"0000000200000000000000A1.00000020.backup" from archive
2010-06-15 07:19:34 UTC FATAL:  the database system is starting up
2010-06-15 07:19:34 UTC FATAL:  the database system is starting up
2010-06-15 07:19:35 UTC FATAL:  the database system is starting up
2010-06-15 07:19:35 UTC LOG:  restored log file
"0000000200000000000000A1" from archive
2010-06-15 07:19:35 UTC LOG:  automatic recovery in progress
2010-06-15 07:19:35 UTC LOG:  redo starts at 0/A1000064, consistency
will be reached at 0/A1000080
2010-06-15 07:19:35 UTC LOG:  consistent recovery state reached
2010-06-15 07:19:35 UTC FATAL:  the database system is starting up
2010-06-15 07:19:36 UTC FATAL:  the database system is starting up
2010-06-15 07:19:36 UTC FATAL:  the database system is starting up
2010-06-15 07:19:37 UTC FATAL:  the database system is starting up
2010-06-15 07:19:37 UTC LOG:  restored log file
"0000000200000000000000A2" from archive
2010-06-15 07:19:37 UTC FATAL:  the database system is starting up
2010-06-15 07:19:37 UTC LOG:  incomplete startup packet
2010-06-15 07:19:37 UTC FATAL:  the database system is starting up
2010-06-15 07:19:37 UTC FATAL:  the database system is starting up
rsync: link_stat "/data/main/wal_archive/0000000200000000000000A3"
failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1523) [receiver=3.0.6]
2010-06-15 07:19:38 UTC LOG:  could not open file
"pg_xlog/0000000200000000000000A3" (log file 0, segment 163): No such
file or directory
2010-06-15 07:19:38 UTC LOG:  redo done at 0/A2000064
2010-06-15 07:19:40 UTC LOG:  restored log file
"0000000200000000000000A2" from archive
rsync: link_stat "/data/main/wal_archive/00000003.history" failed: No
such file or directory (2)
2010-06-15 07:19:41 UTC FATAL:  the database system is starting up
2010-06-15 07:19:41 UTC FATAL:  the database system is starting up
rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1523) [receiver=3.0.6]
2010-06-15 07:19:41 UTC LOG:  selected new timeline ID: 3
rsync: link_stat "/data/main/wal_archive/00000002.history" failed: No
such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1523) [receiver=3.0.6]
2010-06-15 07:19:42 UTC LOG:  archive recovery complete
2010-06-15 07:19:42 UTC LOG:  autovacuum launcher started
2010-06-15 07:19:42 UTC LOG:  database system is ready to accept connections