Hi Louis, Are you able to login to setup.pl with the pg admin user (normally postgres in the containers) with no company name?Once logged in like that you should see a list of databases present on the cluster.RegardsDavid Godfrey Sent from my Galaxy -------- Original message --------From: Louis <lbmlist@hethcote.com> Date: 15/10/21 02:11 (GMT+08:00) To: lsmbdev <lsmbdev@sbts.com.au> Cc: users@lists.ledgersmb.org Subject: RE: [ledgersmb-users] Problem moving from 1.7.35 to 1.8.13 Ok, I've been trying various iterations of this without success.I have scripted it so that I can replicate with accuracy. Basically I1) Log in to existing tarball instance with a known good username and password2) Log out of tarball instance and shutdown the tarball starman.3) ensure all of previously existing docker instance is removed4) use the docker-compose method of starting postges and lsmb containers.5) do a pg_dump of tarball instance "hethcote" database6) create the same good username and password in the container's postgres and check that the md5sum passwords match.7) copy the pg_dump into the postgres container8) docker exec psql with \i to load the pg_dump from tarball instance to docker instance9) log in using known good username from tarball instance into the docker instance and get a bad username/password message.Is there something I missing?LouisOn Sat, 18 Sep 2021, lsmbdev wrote:> Hi Louis,> > If you have no objections to trying our docker containers I'd suggest doing a backup and, after> installing docker-compose, restore to the containerised setup.> > > Most development work, and many production instance are now using docker containers, so it's> considered to be quite stable and easily supported.> > Regards> David Godfrey > > > Sent from my Galaxy> > > -------- Original message --------> From: Louis <lbmlist@hethcote.com>> Date: 18/9/21 23:43 (GMT+08:00)> To: lsmbdev <lsmbdev@sbts.com.au>> Cc: Louis <lbmlist@hethcote.com>> Subject: RE: [ledgersmb-users] Problem moving from 1.7.35 to 1.8.13> > > This is installed from source. The database has been rolled along since> SQLedger 2.x and migrated to LedgerSMB at the time of the fork. PostgreSQL> itself is at v11 but has rolled along from v6 (don't recall orig version> from the SQLedger days.)> > The hba file has always trusted local socket connections (pause for moment> of shame) so password was blank until the 1.6 series. Since 1.6 password> was just a random character since it was ignored. This is how 1.7.35 has> been working. This is true for postgres as well as my own lbmoore.> > So decades of bad practices have finally caught up to me with 1.8.> > I'm at a loss as to where to start with this mess.> > Louis> > > > On Sat, 18 Sep 2021, lsmbdev wrote:> > > Morning Louis,> >> > The most common cause of this would be using the incorrect credentials with setup.pl> >> > Remember that the username is not a username you use to log into your company.> > In many cases it is simply "postgres"> >> > Is your installation via a container, or did you install from source?> >> > Regards> > David Godfrey > >> > Sent from my Galaxy> >> >> > -------- Original message --------> > From: Louis <lbmlist@hethcote.com>> > Date: 18/9/21 09:28 (GMT+08:00)> > To: users@lists.ledgersmb.org> > Subject: [ledgersmb-users] Problem moving from 1.7.35 to 1.8.13> >> >> > Hey all,> >> > I have not been able to move to the 1.8 series from the 1.7 series. I> > think I must not have authentication correct and the 1.8 is expecting a> > different setup than previous version.> >> > This is a starman installation. I will backup the DB, move the code into> > place and run setup.pl. Setup pops open an error reading:> >> > Localhost:5762 says> >> > Access denied (500): bad username/password> >> > I'm using the same credentials as with 1.7.35.> >> > I can roll back and forth easily, but I don't see what the debug path> > should be.> >> > Any help would be appreciated.> >> > Louis> >> >> > _______________________________________________> > users mailing list -- users@lists.ledgersmb.org> > To unsubscribe send an email to users-leave@lists.ledgersmb.org> >> >> >>