Then I granted the permissions with: echo "GRANT ALL PRIVILEGES ON SCHEMA public TO oc_abinoam " | sudo docker-compose exec -T db psql -U nextcloud When comparing to my actual server the line oc_abinoam=C/pg_database_owner at public schema was missing. Public | pg_database_owner | pg_database_owner=UC/pg_database_owner+| standard public schema Pg_toast | nextcloud | | reserved schema for TOAST tables Pg_catalog | nextcloud | nextcloud=UC/nextcloud +| system catalog schema ![]() Information_schema | nextcloud | nextcloud=UC/nextcloud +| Name | Owner | Access privileges | Description 16:03 $ docker-compose exec db psql -U nextcloud I then used psql on the new container to check schema permissions. var/www/html/3rdparty/doctrine/dbal/src/Connection.php line 1814ĭoctrine\DBAL\Driver\API\PostgreSQL\ExceptionConverter->convert(, ) ![]() LINE 1: CREATE TABLE oc_calendar_appt_configs (id BIGSERIAL NOT NULL.Ġ. My exact error messages at the logs were: Erro: Doctrine\DBAL\Exception\DriverException: An exception occurred while executing a query: SQLSTATE: Insufficient privilege: 7 ERROR: permission denied for schema public I ended up spinning up a fresh docker-compose based to use it for comparisons with my actual sever. I’ve had the same issue when trying to install an app (preview_generator). I did some quick tests and everything seems to be running ok.Įxception: Database error when running migration 25000Date20220602190540 for app coreĪn exception occurred while executing a query: SQLSTATE: Insufficient privilege: 7 ERROR: permission denied for schema public So I just issued an “ALTER” postgresql command so it “reencrypts” the same password.Įcho "ALTER USER oc_abinoam WITH PASSWORD '' " | sudo docker-compose exec -T db psql -U nextcloud Sudo docker-compose exec app less config/config.php 'dbname' => 'nextcloud', So I had a look and found out that the custom user “oc_abinoam”'s password is saved in config/config.php Then I got the same error message about lacking of a valid SCRAM secret.ĭb_1 | 02:16:13.015 UTC FATAL: password authentication failed for user "oc_abinoam"ĭb_1 | 02:16:13.015 UTC DETAIL: User "oc_abinoam" does not have a valid SCRAM secret.Īs, I also guessed it could be something related to a change in the method postgresql use to encrypt the passwords. # Edit docker-compose.yml to rename db_15 service to db and remove the old db service # (so it doesn't overwrite the original db) # with the new postgresql version in a different folder Then I tried to upgrade the postgresql from version 12 to 15 by dumping the previous db with pg_dumpall and restoring it with psql.Īs far as I remember the commands were: # Edit docker-compose.yml to create a a new db_15 service I have succesfully upgraded NextCloud from version 22 to 27 (one major version at a time). There is no log to show, since nextcloud doesn’t start at all.Īs anybody been able to upgrade its db from v13 to v14 and v15 ? ![]() ![]() Is this the first time you’ve seen this error? (Y/N): Each time I tryu to upgrade from pgsql v13 to v15 So when I update from postgres v13 to v15, I get the “Internal Server error” on my browser.Īnd in syslog I get the following error message : Dec 18 17:32:00 Nuage nextcloud-postgres\: 16:32:00.114 UTC \ FATAL: password authentication failed for user "oc\_feydreva"ĭec 18 17:32:00 Nuage nextcloud-postgres\: 16:32:00.114 UTC \ DETAIL: User "oc\_feydreva" does not have a valid SCRAM secret. This time, I would like to upgrade from postgres 13 to postgres 15īut it seems the password encryption changed from V13 to V14(and V15) I m running postgres 13, and try to follow all upgrade of nextcloud and postgres. I am running Nextcloud on container using the following ansible script : Operating system and version (eg, Ubuntu 20.04): Ubuntu 20.04.5 LTSĪpache or nginx version (eg, Apache 2.4.25): nginx 1.23.2
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |