Thread: : postgres: archiver process failed on 0000000100000F72000000F0
Hello,
WAL Archive process in our production is not working.
[postgres@hostname]$ ps -ef | grep archive
postgres 12077 16015 0 10:19 pts/4 00:00:00 grep archive
postgres 31126 27607 0 Nov10 ? 00:01:18 postgres: archiver process failed on 0000000100000F72000000F0
I see WAL files getting accumulated in pg_xlog location and the status in "archive_status" is shown as ".ready".
Is there anyway we can only restart archiving process without disturbing the actual cluster ?
Actually, we had killed a process using "kill -9 " and the db went into recovery mode and was back up and running.
We have no issues with the application as well.
postgres=# select pg_is_in_recovery();
pg_is_in_recovery
-------------------
f
(1 row)
Please help to resolve this !
Thanks
VB
Thanks
VB
On Fri, Nov 11, 2011 at 9:58 PM, Venkat Balaji <venkat.balaji@verse.in> wrote:
Hello,WAL Archive process in our production is not working.[postgres@hostname]$ ps -ef | grep archivepostgres 12077 16015 0 10:19 pts/4 00:00:00 grep archivepostgres 31126 27607 0 Nov10 ? 00:01:18 postgres: archiver process failed on 0000000100000F72000000F0I see WAL files getting accumulated in pg_xlog location and the status in "archive_status" is shown as ".ready".Is there anyway we can only restart archiving process without disturbing the actual cluster ?Actually, we had killed a process using "kill -9 " and the db went into recovery mode and was back up and running.We have no issues with the application as well.postgres=# select pg_is_in_recovery();pg_is_in_recovery-------------------f(1 row)Please help to resolve this !ThanksVB
On Fri, Nov 11, 2011 at 09:58:56PM +0530, Venkat Balaji wrote: - Hello, - - WAL Archive process in our production is not working. - - [postgres@hostname]$ ps -ef | grep archive - postgres 12077 16015 0 10:19 pts/4 00:00:00 grep archive - postgres 31126 27607 0 Nov10 ? 00:01:18 postgres: archiver process - failed on 0000000100000F72000000F0 - - I see WAL files getting accumulated in pg_xlog location and the status in - "archive_status" is shown as ".ready". - - Is there anyway we can only restart archiving process without disturbing - the actual cluster ? - - Actually, we had killed a process using "kill -9 " and the db went into - recovery mode and was back up and running. - - We have no issues with the application as well. - - postgres=# select pg_is_in_recovery(); - - pg_is_in_recovery - ------------------- - f - (1 row) - - Please help to resolve this ! If you fix the problem causing the archiver process to fail it will start processing the logs again. check your postgres logs and check your archive_command in your postgresql.conf and make sure that everything is correct there. Dave