0

i just took over working postgre sql server, and i noticed in the logs, that are in: /var/log/postgresql/postgresql-9.4-main.log spitting out this warnings:

cp: cannot stat 'pg_xlog/000000010000033C00000081': No such file or directory
2019-01-22 19:35:31 EET [7540-502339] LOG:  archive command failed with exit code 1
2019-01-22 19:35:31 EET [7540-502340] DETAIL:  The failed archive command was: test ! -f /wal_archive/000000010000033C00000081 && cp pg_xlog/000000010000033C00000081 /wal_archive/000000010000033C00000081
2019-01-22 19:35:31 EET [7540-502341] WARNING:  archiving transaction log file "000000010000033C00000081" failed too many times, will try again later
cp: cannot stat 'pg_xlog/000000010000033C00000081': No such file or directory
2019-01-22 19:36:32 EET [7540-502342] LOG:  archive command failed with exit code 1
2019-01-22 19:36:32 EET [7540-502343] DETAIL:  The failed archive command was: test ! -f /wal_archive/000000010000033C00000081 && cp pg_xlog/000000010000033C00000081 /wal_archive/000000010000033C00000081
cp: cannot stat 'pg_xlog/000000010000033C00000081': No such file or directory
2019-01-22 19:36:33 EET [7540-502344] LOG:  archive command failed with exit code 1
2019-01-22 19:36:33 EET [7540-502345] DETAIL:  The failed archive command was: test ! -f /wal_archive/000000010000033C00000081 && cp pg_xlog/000000010000033C00000081 /wal_archive/000000010000033C00000081
cp: cannot stat 'pg_xlog/000000010000033C00000081': No such file or directory
2019-01-22 19:36:34 EET [7540-502346] LOG:  archive command failed with exit code 1
2019-01-22 19:36:34 EET [7540-502347] DETAIL:  The failed archive command was: test ! -f /wal_archive/000000010000033C00000081 && cp pg_xlog/000000010000033C00000081 /wal_archive/000000010000033C00000081

oldest file in pg_xlog is

-rw------- 1 postgres postgres 16777216 Dec  3 20:01 00000001000003A20000000F
-rw------- 1 postgres postgres 16777216 Dec  3 20:01 00000001000003A20000000E
-rw------- 1 postgres postgres 16777216 Dec  3 20:00 00000001000003A20000000D
-rw------- 1 postgres postgres 16777216 Dec  3 20:00 00000001000003A20000000C
-rw------- 1 postgres postgres 16777216 Dec  3 19:47 00000001000003A20000000B
-rw------- 1 postgres postgres 16777216 Dec  3 19:35 00000001000003A20000000A

newest are:

-rw------- 1 postgres postgres 16777216 Jan 23 14:59 00000001000003C60000002E
-rw------- 1 postgres postgres 16777216 Jan 23 14:59 00000001000003C60000002F
-rw------- 1 postgres postgres 16777216 Jan 23 15:00 00000001000003C600000030
-rw------- 1 postgres postgres 16777216 Jan 23 15:01 00000001000003C600000031
-rw------- 1 postgres postgres 16777216 Jan 23 15:02 00000001000003C600000032
drwx------ 2 postgres postgres  2031616 Jan 23 15:01 archive_status

it is possible somehow to reset wal_archive procedure? Or just fix what is in log files? As i can see there is missing wal archive block which will be missed.

I am planing also to do full vacuum procedure, but before that i want to start on properly functioning server, i think that wal_archive will produce a lot of data after i begin vaccum.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.