Relation "jlx_user" does not exist

[fisholo]

Hi all and thanks for work done!
In a fresh install of lizmap-docker-compose (latest git version) I have trouble with the instantiation of the postggresql db.

The key error in docker-compose postgis logs is: ERROR: relation "jlx_user" does not exist at character 350
The lizmap db, with lizmap scheme is empty, no table created.

Thanks for help!

[fisholo]

Maybe the problems area related but I have to comment in configure.sh the function _install-plugin() because make configure report this error:
Configuring environment
Copying files
Creating directories
Creating env file
Creating pg_service.conf
Creating lizmap profiles
Installing lizmap plugin
/src/install-lizmap-plugin.sh: line 7: qgis-plugin-manager: command not found
/src/install-lizmap-plugin.sh: line 8: qgis-plugin-manager: command not found
/src/install-lizmap-plugin.sh: line 9: qgis-plugin-manager: command not found
/src/install-lizmap-plugin.sh: line 10: qgis-plugin-manager: command not found
/src/install-lizmap-plugin.sh: line 11: qgis-plugin-manager: command not found
make: *** [Makefile:17: configure] Error 127

Thanks in advance!

[Gustry]

You should upgrade your QGIS docker images. (docker pull ...)
docker compose pull

I'm not sure we have included qgis-plugin-manager in old QGIS server version as well, so update to at least 3.22.

[lucadelu]

Hi all and thanks for work done! In a fresh install of lizmap-docker-compose (latest git version) I have trouble with the instantiation of the postggresql db.

The key error in docker-compose postgis logs is: ERROR: relation "jlx_user" does not exist at character 350 The lizmap db, with lizmap scheme is empty, no table created.

Thanks for help!

I have the same problem, I updated all the containers but the error is still there. Any idea how to solve or work on it?

[nworr]

It seems your postgresql data were not fully installed, consider deleting the docker volume (should be <branch_name>__postgis_data, it should reinstall properly the db

[Gustry]

Is this issue still relevant ?

[lucadelu]

It happen when you didn't clean up correctly all the directories and volumes involved, I don't think it is still relevant, but maybe add something in the readme could help