Facebook
Twitter- Server operating system version
- Ubuntu 22.04
- Plesk version and microupdate number
- Plesk Obsidian 18.0.67 Update #3
Having issues with a postgres database after migrating to new server. This is a moodle application, the symptom is a setup screen after the migration rather than the migrated site, this indicates that moodle can't find it's path, config or database tables. After verifying the path and config some investigation into the database indicates the user does not have permission to read the database objects. I am migrating from postgres 10 to postgres 14, it appears user permissions are not migrated correctly.
- Logging into the new postgres 14 database on the new server as postgres, I can see the users and database setup. I can see and query the migrated database as postgres.
- Logging into the postgres database as the application user (<username>_mood) I can list databases, users and connect to the application database but not list or query tables.
- Creating a NEW user VIA the plesk gui, the new user can log in, see and list objects, but still cannot list or query objects in the application database (That they have been explicitly assigned to)
To be clear, migrated or newly created postgres users cannot access objects in a migrated database.
Has anyone seen and have a solution?
- Logging into the new postgres 14 database on the new server as postgres, I can see the users and database setup. I can see and query the migrated database as postgres.
- Logging into the postgres database as the application user (<username>_mood) I can list databases, users and connect to the application database but not list or query tables.
- Creating a NEW user VIA the plesk gui, the new user can log in, see and list objects, but still cannot list or query objects in the application database (That they have been explicitly assigned to)
To be clear, migrated or newly created postgres users cannot access objects in a migrated database.
Has anyone seen and have a solution?
