Skip to content
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

Error unexpected response #1635

Open
aleksandrkazakovv opened this issue Feb 2, 2024 · 3 comments
Open

Error unexpected response #1635

aleksandrkazakovv opened this issue Feb 2, 2024 · 3 comments

Comments

@aleksandrkazakovv
Copy link

Hello. I have next configuration:
Ubuntu 20.04
wal-g 2.0.1
PostgreSQL 15.5-1 + TimescaleDB 2.9.0
config for backup to local folder:
{ "WALG_FILE_PREFIX": "/tmp/wal-g-test-data", "PGDATA": "/var/lib/postgresql/15/main", "PGHOST": "/var/run/postgresql" }

config backup to s3(minio):
{ "WALG_S3_PREFIX": "s3://walg", AWS_S3_FORCE_PATH_STYLE: "true" "AWS_ENDPOINT": "http://192.168.1.20:9000", "AWS_ACCESS_KEY_ID": "*******", "AWS_SECRET_ACCESS_KEY": "******", "WALG_COMPRESSION_METHOD": "brotli", "WALG_DELTA_MAX_STEPS": "5", "PGDATA": "/var/lib/postgresql/15/main", "PGHOST": "/var/run/postgresql" }
when i start backup to local folder or to s3, i get same errors:
WARNING: 2024/01/31 22:00:38.334769 It seems your archive_command is not configured. This will cause inconsistent backup. Please consider configuring WAL archiving. INFO: 2024/01/31 22:00:38.337134 Running remote backup through Postgres connection. INFO: 2024/01/31 22:00:38.337144 Features like delta backup are disabled, there might be a performance impact. INFO: 2024/01/31 22:00:38.337146 To run with local backup functionalities, supply [db_directory]. INFO: 2024/01/31 22:00:38.339009 Starting remote backup ERROR: 2024/01/31 22:00:38.339145 unexpected response: &{%!t(string=ERROR) %!t(string=ERROR) %!t(string=42601) %!t(string=syntax error) %!t(string=) %!t(string=) %!t(int32=0) %!t(int32=0) %!t(string=) %!t(string=) %!t(string=) %!t(string=) %!t(string=) %!t(string=) %!t(string=) %!t(string=repl_scanner.l) %!t(int32=237) %!t(string=replication_yyerror) map[]}
Can anybody to help me, what does it meen?

@x4m
Copy link
Collaborator

x4m commented Mar 29, 2024

Hi Aleksandr,
Thank you for trying WAL-G. I see that you are using the remote backup feature. This is not the default way to perform a backup. Could you please try using the regular wal-g backup-push command with the %PGDATA% parameter? I suspect that one of the reasons of this issue is that the remote backup may be causing issues with TimescaleDB, but I don't have strong evidence to support this claim.

@sebasmannem Sebastian, could you please have a look at this? The Postgres response seems unusual.

@gerardnico
Copy link

That did the trick. I got the same error thinking that wal-g would use the $PGDATA environment variable by default.

The good command is:

wal-g backup-push $PGDATA

@gerardnico
Copy link

My error was:

INFO: 2024/05/25 08:00:29.935653 Backup will be pushed to storage: default
INFO: 2024/05/25 08:00:29.943235 Running remote backup through Postgres connection.
INFO: 2024/05/25 08:00:29.943270 Features like delta backup and partial restore are disabled, there might be a performance impact.
INFO: 2024/05/25 08:00:29.943286 To run with local backup functionalities, supply [db_directory].
INFO: 2024/05/25 08:00:29.944287 Starting remote backup
ERROR: 2024/05/25 08:00:29.944470 unexpected response: &{%!t(string=ERROR) %!t(string=ERROR) %!t(string=42601) %!t(string=syntax error) %!t(string=) %!t(string=) %!t(int32=0) %!t(int32=0) %!t(string=) %!t(string=) %!t(string=) %!t(string=) %!t(string=) %!t(string=) %!t(string=) %!t(string=repl_scanner.l) %!t(int32=247) %!t(string=replication_yyerror) map[]}

wal-g version:

wal-g version v3.0.0    4689e3ac        2024.05.24_16:45:37     PostgreSQL

Thanks!

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

No branches or pull requests

3 participants