-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backup problem #23
Comments
What's the error you see when you run the backup delete command for the same? |
No errors, but unknown backup is persent |
I see. Maybe a bug of show command. What do you see as output of the following?
|
|
Thanks for the extra info. I didn't think enough before asking you for that. It is possible that a
Now, I have to say that something may be wrong with the delete command as well. We might find some file with invalid content (seeing START_TIME='1970-01-01 01:00:00' in the above output would be enough). |
There is no invalid data in ini files. |
Hmm, mystery deepens. That backup entry in show output is starting to look like a phantom entry. If it does not originate from some corrupt |
Hi. I did strace, hope it help:
|
Any help? |
Sorry, got swamped up in some other work. Anyway, if I remember correctly the last time I looked at the |
postgres@backup:~$ PGDATA=/var/lib/postgresql/9.4/main BACKUP_PATH=/var/backup ARCLOG_PATH=/var/lib/postgresql/9.4/archive /usr/lib/postgresql/9.4/bin/pg_rman 2016-04-05 06:30:02 |
I think you missed to type |
|
I reproduced a similar problem.
Empty backup.ini file causes this issue.
related? |
Thank you, problem is fixed. |
So was there an empty |
Yes, I was deleted empty backup.ini and problem fixed. |
If backup.ini contains invalid word, pg_rman outputs WARNING message.
But if empty case, pg_rman say nothing. It seem to me that pg_rman outputs warning message if backup.ini is empty or other invalid state. |
@bwtakacy Agreed! As mentioned to @ooyamams offline, multiple questions come to mind:
|
About the first question, I comes to think it can be happen.
If pg_rman aborts just after fopen I think there can remain a empty file. |
I see, thanks. Instead of looking for ways to prevent ending up with an empty |
Hi. I have problem with backup:
I can't remove 1970-01-01 01:00:00
I want remove all errors backups but keep valid
Please help me
The text was updated successfully, but these errors were encountered: