Fixing problems with postgreSQL wal archives
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.
postgresql vacuum wal
asked 1 min ago
GumuliokasGumuliokas
133
add a comment |
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.
postgresql vacuum wal
asked 1 min ago
GumuliokasGumuliokas
133
add a comment |
0
0
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.
postgresql vacuum wal
asked 1 min ago
GumuliokasGumuliokas
133
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.
postgresql vacuum wal
postgresql vacuum wal
asked 1 min ago
GumuliokasGumuliokas
133
asked 1 min ago
GumuliokasGumuliokas
133
asked 1 min ago
GumuliokasGumuliokas
133
asked 1 min ago
GumuliokasGumuliokas
133
asked 1 min ago
GumuliokasGumuliokas
133
133
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f227868%2ffixing-problems-with-postgresql-wal-archives%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f227868%2ffixing-problems-with-postgresql-wal-archives%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
