Re: pg_standby doesnt't work

Hi,

I'm testing serveral days a replication-system with PostgreSQL, but I get allways the same error.

2009-10-25 15:44:45 CET FATAL: XX000: could not restore file "00000001.history" from archive: return code -1073741811

The restore_command is:

restore_command = 'pg_standby.exe -d -s 5 -t C:\pgsql.trigger.5442 w:\wal-archive %f %p %r 2>>pg_log\pg_standby.log'

The system is runnig on WinXP (during this test), the database-version is 8.3.8. I've tried out the pg_standby-version from PG8.4, but there is no difference in the result.

So I can't understand what this return-code means, (and) I've never seen a file named 00000001.history. It definitely doesn't exist on my master and so my archive_command can't replicate to the slave.

This is all content of 'backup_label' out of my base-backup:
START WAL LOCATION: 0/AE000020 (file 0000000100000000000000AE)
CHECKPOINT LOCATION: 0/AE000020
START TIME: 2009-10-25 14:36:25 CET
LABEL: 25102009_1

I can't get information out of pg_standby.log, there is nothing in.

That's the complete pg-log (debug-level 5):
2009-10-25 15:44:45 CET DEBUG: 00000: forked new backend, pid=1220 socket=1312
2009-10-25 15:44:45 CET LOCATION: BackendStartup, .\src\backend\postmaster\postmaster.c:2861
2009-10-25 15:44:45 CET LOG: 00000: database system was interrupted; last known up at 2009-10-25 14:36:25 CET
2009-10-25 15:44:45 CET LOCATION: StartupXLOG, .\src\backend\access\transam\xlog.c:4839
2009-10-25 15:44:45 CET LOG: 00000: starting archive recovery
2009-10-25 15:44:45 CET LOCATION: readRecoveryCommandFile, .\src\backend\access\transam\xlog.c:4377
2009-10-25 15:44:45 CET LOG: 00000: restore_command = 'pg_standby.exe -d -s 5 -t C:\pgsql.trigger.5442 w:\wal-archive %f %p %r 2>>pg_log\pg_standby.log'
2009-10-25 15:44:45 CET LOCATION: readRecoveryCommandFile, .\src\backend\access\transam\xlog.c:4423
2009-10-25 15:44:45 CET DEBUG: 00000: executing restore command "pg_standby.exe -d -s 5 -t C:\pgsql.trigger.5442 w:\wal-archive 00000001.history pg_xlog\RECOVERYHISTORY 000000000000000000000000 2>>pg_log\pg_standby.log"
2009-10-25 15:44:45 CET LOCATION: RestoreArchivedFile, .\src\backend\access\transam\xlog.c:2569
2009-10-25 15:44:45 CET LOG: 00000: loaded library "$libdir/plugins/plugin_debugger.dll"
2009-10-25 15:44:45 CET LOCATION: load_libraries, .\src\backend\utils\init\miscinit.c:1187
2009-10-25 15:44:45 CET FATAL: 57P03: the database system is starting up
2009-10-25 15:44:45 CET LOCATION: ProcessStartupPacket, .\src\backend\postmaster\postmaster.c:1648
2009-10-25 15:44:45 CET DEBUG: 00000: proc_exit(1)
2009-10-25 15:44:45 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc.c:98
2009-10-25 15:44:45 CET DEBUG: 00000: shmem_exit(1)
2009-10-25 15:44:45 CET LOCATION: shmem_exit, .\src\backend\storage\ipc\ipc.c:164
2009-10-25 15:44:45 CET DEBUG: 00000: exit(1)
2009-10-25 15:44:45 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc.c:116
2009-10-25 15:44:45 CET DEBUG: 00000: reaping dead processes
2009-10-25 15:44:45 CET LOCATION: reaper, .\src\backend\postmaster\postmaster.c:2093
2009-10-25 15:44:45 CET DEBUG: 00000: server process (PID 1220) exited with exit code 1
2009-10-25 15:44:45 CET LOCATION: LogChildExit, .\src\backend\postmaster\postmaster.c:2520
2009-10-25 15:44:45 CET FATAL: XX000: could not restore file "00000001.history" from archive: return code -1073741811
2009-10-25 15:44:45 CET LOCATION: RestoreArchivedFile, .\src\backend\access\transam\xlog.c:2639
2009-10-25 15:44:45 CET DEBUG: 00000: proc_exit(1)
2009-10-25 15:44:45 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc.c:98
2009-10-25 15:44:45 CET DEBUG: 00000: shmem_exit(1)
2009-10-25 15:44:45 CET LOCATION: shmem_exit, .\src\backend\storage\ipc\ipc.c:164
2009-10-25 15:44:45 CET DEBUG: 00000: exit(1)
2009-10-25 15:44:45 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc.c:116
2009-10-25 15:44:45 CET DEBUG: 00000: reaping dead processes
2009-10-25 15:44:45 CET LOCATION: reaper, .\src\backend\postmaster\postmaster.c:2093
2009-10-25 15:44:45 CET LOG: 00000: startup process (PID 3820) exited with exit code 1
2009-10-25 15:44:45 CET LOCATION: LogChildExit, .\src\backend\postmaster\postmaster.c:2520
2009-10-25 15:44:45 CET LOG: 00000: aborting startup due to startup process failure
2009-10-25 15:44:45 CET LOCATION: reaper, .\src\backend\postmaster\postmaster.c:2113
2009-10-25 15:44:45 CET DEBUG: 00000: proc_exit(1)
2009-10-25 15:44:45 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc.c:98
2009-10-25 15:44:45 CET DEBUG: 00000: shmem_exit(1)
2009-10-25 15:44:45 CET LOCATION: shmem_exit, .\src\backend\storage\ipc\ipc.c:164
2009-10-25 15:44:45 CET DEBUG: 00000: exit(1)
2009-10-25 15:44:45 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc.c:116
2009-10-25 15:44:46 CET DEBUG: 00000: logger shutting down
2009-10-25 15:44:46 CET LOCATION: SysLoggerMain, .\src\backend\postmaster\syslogger.c:435
2009-10-25 15:44:46 CET DEBUG: 00000: proc_exit(0)
2009-10-25 15:44:46 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc.c:98
2009-10-25 15:44:46 CET DEBUG: 00000: shmem_exit(0)
2009-10-25 15:44:46 CET LOCATION: shmem_exit, .\src\backend\storage\ipc\ipc.c:164
2009-10-25 15:44:46 CET DEBUG: 00000: exit(0)
2009-10-25 15:44:46 CET LOCATION: proc_exit, .\src\backend\storage\ipc\ipc.c:116

thx a lot,

murphy

Hi,

On Mon, Oct 26, 2009 at 12:34 AM, Andreas Schmidt <a(dot)schmidt(at)mdtec(dot)de> wrote:
> I'm testing serveral days a replication-system with PostgreSQL, but I get
> allways the same error.
>
> 2009-10-25 15:44:45 CET FATAL:  XX000: could not restore file
> "00000001.history" from archive: return code -1073741811
>
> The restore_command is:
>
> restore_command = 'pg_standby.exe -d -s 5 -t C:\pgsql.trigger.5442
> w:\wal-archive %f %p %r 2>>pg_log\pg_standby.log'
>
> The system is runnig on WinXP (during this test), the database-version is
> 8.3.8. I've tried out the pg_standby-version from PG8.4, but there is no
> difference in the result.
>
> So I can't understand what this return-code means, (and) I've never seen a
> file named 00000001.history. It definitely doesn't exist on my master and so
> my archive_command can't replicate to the slave.

This is the same problem that was reported before.
http://archives.postgresql.org/pgsql-bugs/2009-08/msg00003.php

The cause is the signals support for pg_standby on win32.
We should get rid of that.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Hi, thank you for your response.
But does this mean, that only WinXP is no supported or doesn't it work at all? I would need it on a Windows2003Server???

Best regards,

murphy

-----Ursprüngliche Nachricht-----
Von: Fujii Masao [mailto:masao(dot)fujii(at)gmail(dot)com]
Gesendet: Montag, 26. Oktober 2009 03:36
An: Andreas Schmidt
Cc: pgsql-admin(at)postgresql(dot)org; PostgreSQL-development
Betreff: Re: [ADMIN] pg_standby doesnt't work

Hi,

On Mon, Oct 26, 2009 at 12:34 AM, Andreas Schmidt <a(dot)schmidt(at)mdtec(dot)de> wrote:
> I'm testing serveral days a replication-system with PostgreSQL, but I get
> allways the same error.
>
> 2009-10-25 15:44:45 CET FATAL:  XX000: could not restore file
> "00000001.history" from archive: return code -1073741811
>
> The restore_command is:
>
> restore_command = 'pg_standby.exe -d -s 5 -t C:\pgsql.trigger.5442
> w:\wal-archive %f %p %r 2>>pg_log\pg_standby.log'
>
> The system is runnig on WinXP (during this test), the database-version is
> 8.3.8. I've tried out the pg_standby-version from PG8.4, but there is no
> difference in the result.
>
> So I can't understand what this return-code means, (and) I've never seen a
> file named 00000001.history. It definitely doesn't exist on my master and so
> my archive_command can't replicate to the slave.

This is the same problem that was reported before.
http://archives.postgresql.org/pgsql-bugs/2009-08/msg00003.php

The cause is the signals support for pg_standby on win32.
We should get rid of that.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Hi,

On Tue, Oct 27, 2009 at 4:53 PM, Andreas Schmidt <a(dot)schmidt(at)mdtec(dot)de> wrote:
> Hi, thank you for your response.
> But does this mean, that only WinXP is no supported or doesn't it work at all? I would need it on a Windows2003Server???

According to the previous post, pg_standby in v8.3.7 would work file.
How about using that?
http://archives.postgresql.org/pgsql-bugs/2009-08/msg00094.php

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Hi,

On Tue, Oct 27, 2009 at 4:53 PM, Andreas Schmidt <a(dot)schmidt(at)mdtec(dot)de> wrote:
> Hi, thank you for your response.
> But does this mean, that only WinXP is no supported or doesn't it work at all? I would need it on a Windows2003Server???

This problem will disappear in the next release (v8.3.9, v8.4.2).
http://archives.postgresql.org/pgsql-committers/2009-11/msg00019.php

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center