Postgres update from 10 to 15 failed (with fix for: User "dsmrreader" does not have a valid SCRAM secret) about dsmr-reader-docker HOT 6 CLOSED

I suppose this issue can be closed as I included the fix.

from dsmr-reader-docker.

I found the errors in the GUI I lost earlier after I had fixed it

   Process behind schedule: Generate day and hour statistics   (43 minutes ago)
   Process behind schedule: Calculate quarter hour electricity peaks   (43 minutes ago)
   Process behind schedule: Weather update   (43 minutes ago)
   Process behind schedule: Generate consumption data   (46 minutes ago)

from dsmr-reader-docker.

@gctwnl Thanks for your description on how you fixed it. I also needed to upgrade from 10.1 to 15.5 and could not get it to work untill i found your post.

from dsmr-reader-docker.

@gctwnl too bad it caused issues, but good that you were able to fix it, and for sharing this here.

from dsmr-reader-docker.

I just upgraded to v16 and ran into the same.

Actual fix: nano/vi pg_hba.conf
change this line:
host all all all scram-sha-256
into:
host all all all md5

Here some background info: https://www.postgresql.org/docs/14/auth-password.html

edit: this is the default and changed as per the default too. If you have more users, probably good to change db & user dsmrreader to md5 only, while keeping the rest on scram-sha-256.

from dsmr-reader-docker.

Hi I've created a S6 v3 overlay Docker image. I`m currently not using DSMR reader myself, so I'm unable to do some proper testing. Would you mind testing ghcr.io/xirixiz/dsmr-reader-docker:development and share the output?

It's on the pre_release branch now. If everything is working fine, I`ll merge the changes to the main branch

from dsmr-reader-docker.