By using AWS re:Post, you agree to the Terms of Use
/Aurora postgresql major version upgrade from 9.6 to 10.18/

Aurora postgresql major version upgrade from 9.6 to 10.18

0

Seeing some errors in the Postgresql log file. But other than these reported errors, the db instance is working fine and applications have no issues connecting, reading and writing to db instance.

We want some help from AWS to verify if these errors require any further action. Thanks.

2021-12-07T03:29:32.000Z

Copy 2021-12-07 03:29:32 UTC::@:8182:WARNING: unrecognized configuration parameter "rds.adaptive_autovacuum" 2021-12-07 03:29:32 UTC::@:8182:WARNING: unrecognized configuration parameter "rds.adaptive_autovacuum"

2021-12-07T03:29:32.000Z

Copy 2021-12-07 03:29:32 UTC::@:8182:WARNING: unrecognized configuration parameter "rds.enable_plan_management" 2021-12-07 03:29:32 UTC::@:8182:WARNING: unrecognized configuration parameter "rds.enable_plan_management"

2021-12-07T03:29:32.000Z 2021-12-07 03:29:32 UTC::@:8182:LOG: database system is shut down Postgres Shared Memory Value: 51704012800 bytes LOG: skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf"

2021-12-07T03:29:35.000Z 2021-12-07 03:29:35 UTC::@:8776:WARNING: unrecognized configuration parameter "rds.adaptive_autovacuum"

2021-12-07T03:29:35.000Z 2021-12-07 03:29:35 UTC::@:8776:WARNING: unrecognized configuration parameter "rds.enable_plan_management"

2021-12-07T03:29:35.000Z 2021-12-07 03:29:35 UTC::@:8776:LOG: redirecting log output to logging collector process

2021-12-07T03:29:35.000Z 2021-12-07 03:29:35 UTC::@:8776:HINT: Future log output will appear in directory "/rdsdbdata/log/error".

2021-12-07T03:38:49.000Z 2021-12-07 03:38:49 UTC::@:8777:LOG: skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf"

2021-12-07T03:51:10.000Z 2021-12-07 03:51:10 UTC::@:29750:LOG: setting shmemname /mnt/hugetlbfs/aurora-postgres-buffer-cache

2021-12-07T03:51:10.000Z 2021-12-07 03:51:10 UTC::@:29743:LOG: Waiting for runtime initialization complete...

2021-12-07T03:51:11.000Z 2021-12-07 03:51:11 UTC:local:rdsadmin@rdsadmin:30193:FATAL: the database system is starting up

2021-12-07T03:51:11.000Z 2021-12-07 03:51:11 UTC::@:30192:LOG: database system was interrupted; last known up at 2021-12-07 03:50:57 UTC

2021-12-07T03:51:11.000Z 2021-12-07 03:51:11 UTC::@:30192:LOG: Outbound recovery is not required

2021-12-07T03:51:12.000Z 2021-12-07 03:51:12 UTC:local:rdsadmin@rdsadmin:30220:FATAL: the database system is starting up

2021-12-07T03:51:13.000Z 2021-12-07 03:51:13 UTC::@:29743:LOG: database system is ready to accept connections

2021-12-07T03:55:10.000Z 2021-12-07 03:55:10 UTC::@:29743:LOG: received SIGHUP, reloading configuration files

2021-12-07T03:55:10.000Z 2021-12-07 03:55:10 UTC::@:29743:LOG: parameter "unix_socket_permissions" cannot be changed without restarting the server

2021-12-07T03:55:10.000Z 2021-12-07 03:55:10 UTC::@:29743:LOG: parameter "apg_critical_insights_enabled" changed to "on"

2021-12-07T03:55:10.000Z 2021-12-07 03:55:10 UTC::@:29743:LOG: configuration file "/rdsdbdata/config/postgresql.conf" contains errors; unaffected changes were applied

2021-12-07T09:48:09.000Z 2021-12-07 09:48:09 UTC:10.201.11.180(61119):postgresrds@spam:17324:LOG: could not receive data from client: Connection timed out

asked 5 months ago86 views
1 Answers
0

I don't see any issues. "rds.adaptive_autovacuum", "rds.enable_plan_management" are RDS specific parameters and thus came up as warnings. Just make sure to run ANALYZE on databases after major version upgrades to make sure pg_statistics has fresh stats of tables. As always, if you have any issues in upgrading RDS databases, please feel free to open up a support case.

answered 5 months ago
  • I ran the ANALYZE command. Most of the tables completed successfully except for a few:

    We are not quite sure as to how the superuser can be created. Please clarify. Thanks.

    2021-12-07T04:00:51.000Z 2021-12-07 04:00:51 UTC:10.201.11.180(61119):postgresrds@spam:17324:WARNING: skipping "pg_database" --- only superuser can analyze it

    2021-12-07T04:00:51.000Z 2021-12-07 04:00:51 UTC:10.201.11.180(61119):postgresrds@spam:17324:WARNING: skipping "pg_db_role_setting" --- only superuser can analyze it

    2021-12-07T04:00:51.000Z 2021-12-07 04:00:51 UTC:10.201.11.180(61119):postgresrds@spam:17324:WARNING: skipping "pg_tablespace" --- only superuser can analyze it

    2021-12-07T04:00:51.000Z 2021-12-07 04:00:51 UTC:10.201.11.180(61119):postgresrds@spam:17324:WARNING: skipping "pg_pltemplate" --- only superuser can analyze it

    2021-12-07T04:00:51.000Z 2021-12-07 04:00:51 UTC:10.201.11.180(61119):postgresrds@spam:17324:WARNING: skipping "pg_auth_members" --- only superuser can analyze it

    2021-12-07T04:00:51.000Z 2021-12-07 04:00:51 UTC:10.201.11.180(61119):postgresrds@spam:17324:WARNING: skipping "pg_shdepend" --- only superuser can analyze it

    2021-12-07T04:00:51.000Z 2021-12-07 04:00:51 UTC:10.201.11.180(61119):postgresrds@spam:17324:WARNING: skipping "pg_shdescription" --- only superuser can analyze it

    2021-12-07T04:00:52.000Z 2021-12-07 04:00:52 UTC:10.201.11.180(61119):postgresrds@spam:17324:WARNING: skipping "pg_replication_origin" --- only superuser can analyze it

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions