Skip to content

Archive-get fails to fetch wal segments in Remote mode when log-level-file set to ON #178

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

Closed
kuzmindb opened this issue Feb 27, 2020 · 1 comment
Labels
Milestone

Comments

@kuzmindb
Copy link
Contributor

kuzmindb commented Feb 27, 2020

Archive-get fails to fetch wal segments in Remote mode when log-level-file set to ON with error:

ERROR: could not open log file "$log_file.log": No such file or directory

How to reproduce:

  • Set up backup in Remote Mode
  • Set up Continuous WAL Archiving
  • Set up logging to file with pg_probackup set-config -B $backup_dir --instance $instance --log-level-file=INFO
  • Restore backup to a remote server

As a temporary workaround one can either completely disable logging to file or explicitly pass restore command with --log-level-file=OFF option, e.g.
pg_probackup restore -B $backup_dir --instance $instance --remote-user $remote_user --remote-host $remote_host --restore-command='pg_probackup archive-get -B $backup_dir --instance $instance --wal-file-path=%p --wal-file-name=%f --remote-host=$remote_host --remote-user=$remote_user --log-level-file off'

Reported by Artem Dolgih

@gsmolk gsmolk added the bug label Feb 27, 2020
@gsmolk gsmolk added this to the 2.3.0 milestone Feb 27, 2020
@gsmolk gsmolk modified the milestones: 2.3.0, 2.2.8 Mar 2, 2020
@gsmolk
Copy link
Contributor

gsmolk commented Mar 3, 2020

Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants