You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we try to update the database from version 15 to version 16, we get the error:
Performing Consistency Checks
Checking cluster versions ok
failure
Consult the last few lines of "/pgdata/pg16/pg_upgrade_output.d/20231129T083313.457/log/pg_upgrade_server.log" for
the probable cause of the failure.
connection to server on socket "/pgdata/.s.PGSQL.50432" failed: No such file or directory
Is the server running locally and accepting connections on that socket?
could not connect to source postmaster started with the command:
"/usr/pgsql-15/bin/pg_ctl" -w -l "/pgdata/pg16/pg_upgrade_output.d/20231129T083313.457/log/pg_upgrade_server.log" -D "/pgdata/pg15" -o "-p 50432 -b -c listen_addresses='' -c unix_socket_permissions=0700 -c unix_socket_directories='/pgdata'" start
pg_upgrade_server.log
pg_upgrade run on Wed Nov 29 08:33:13 2023
command: "/usr/pgsql-15/bin/pg_ctl" -w -l "/pgdata/pg16/pg_upgrade_output.d/20231129T083313.457/log/pg_upgrade_server.log" -D "/pgdata/pg15" -o "-p 50432 -b -c listen_addresses='' -c unix_socket_permissions=0700 -c unix_socket_directories='/pgdata'" start >> "/pgdata/pg16/pg_upgrade_output.d/20231129T083313.457/log/pg_upgrade_server.log" 2>&1
waiting for server to start....2023-11-29 08:33:13.623 UTC [107] LOG: pgaudit extension initialized
stopped waiting
pg_ctl: could not start server
Examine the log output.
Looks like a bug sclorg/postgresql-container#362
Is it possible to set the POSTGRESQL_UPGRADE_PGUPGRADE_OPTIONS option in the PGUpgrade CRD-entity?
The text was updated successfully, but these errors were encountered:
Hello @dsessler7.
Operator/Upgrade version is postgres-operator-upgrade:ubi8-5.3.2-0.
PosgreSQL version is crunchy-postgres:ubi8-15.3-0.
I can send full upgrade logs on Monday.
Have a nice day.
When we try to update the database from version 15 to version 16, we get the error:
Performing Consistency Checks
Checking cluster versions ok
failure
Consult the last few lines of "/pgdata/pg16/pg_upgrade_output.d/20231129T083313.457/log/pg_upgrade_server.log" for
the probable cause of the failure.
connection to server on socket "/pgdata/.s.PGSQL.50432" failed: No such file or directory
Is the server running locally and accepting connections on that socket?
could not connect to source postmaster started with the command:
"/usr/pgsql-15/bin/pg_ctl" -w -l "/pgdata/pg16/pg_upgrade_output.d/20231129T083313.457/log/pg_upgrade_server.log" -D "/pgdata/pg15" -o "-p 50432 -b -c listen_addresses='' -c unix_socket_permissions=0700 -c unix_socket_directories='/pgdata'" start
pg_upgrade_server.log
pg_upgrade run on Wed Nov 29 08:33:13 2023
command: "/usr/pgsql-15/bin/pg_ctl" -w -l "/pgdata/pg16/pg_upgrade_output.d/20231129T083313.457/log/pg_upgrade_server.log" -D "/pgdata/pg15" -o "-p 50432 -b -c listen_addresses='' -c unix_socket_permissions=0700 -c unix_socket_directories='/pgdata'" start >> "/pgdata/pg16/pg_upgrade_output.d/20231129T083313.457/log/pg_upgrade_server.log" 2>&1
waiting for server to start....2023-11-29 08:33:13.623 UTC [107] LOG: pgaudit extension initialized
stopped waiting
pg_ctl: could not start server
Examine the log output.
Looks like a bug sclorg/postgresql-container#362
Is it possible to set the POSTGRESQL_UPGRADE_PGUPGRADE_OPTIONS option in the PGUpgrade CRD-entity?
The text was updated successfully, but these errors were encountered: