Hi Anold, I restarted the instance and requests are getting replies now on the remote instance. I am still getting the SQLExceptions
Thanks again for your help. On Wed, May 18, 2022 at 12:48 PM Kigred Developer < kigred.develo...@gmail.com> wrote: > Hi Anold, > > FYI this is what I have done so far: > 1. cloned the 1.6 and 1.7 branches > 2. run the server using (bootRun) starting with 1.6 and then 1.7 locally. > 3. The log looks okay. (attached, named bootRunOuput.txt) > 4. I have tried to use the platform locally (see log onRunningSomeQueries). > Much as there are some exceptions in the second log, the queries get > proper responses. > > So I backup these local instances and restore them to the remote server: > On running the remote instance I get similar exceptions in catalina.out > For some reason I am not able to reproduce the exceptions I was getting > earlier about migrations. > > My problem right now is that my requests are failing. > > > On Wed, May 18, 2022 at 10:29 AM Arnold Galovics <arn...@apache.org> > wrote: > >> Hi Wilfred, >> >> I'm glad you tried it out locally and even happier that the upgrade >> worked. >> >> Generally speaking the upgrade path should be as you said it. First to >> 1.6 and then 1.7. Now, I'd say it's much better if you deploy Fineract 1.6 >> onto your server to upgrade the 1.5 database and then do an immediate >> deployment there to upgrade from 1.6 to 1.7. >> >> Regarding the problem you're experiencing, we've never tried to do it >> this way (at least I don't know about anyone). Whether the database schema >> is in its latest state, it's managed by the databasechangelog table created >> by Liquibase. Technically speaking, I don't see a reason why this wouldn't >> work though so do you mind sharing some logs? >> >> Best, >> Arnold >> >> On Wed, May 18, 2022 at 6:29 AM Kigred Developer < >> kigred.develo...@gmail.com> wrote: >> >>> Dear Devs, >>> >>> I am trying to upgrade a multi tenant server from 1.5 to 1.7 but I think >>> my approach is not correct and I seek guidance. This is what I have tried: >>> 1. Took backup of fineract_tenants and each of the tenants databases and >>> upgraded them locally by running them through 1.6 and then 1.7. This step >>> is successful and I am able to test things locally. >>> 2. So I took the upgraded fineract_tenants and tenants databases >>> (backups) and restore them to them to the remote server. >>> 3. I replaced the war file with the one built with fineract 1.7 and >>> tried to run fineract using tomcat. >>> >>> This fails as fineract tries to upgrade (by running some migrations) all >>> over again. Exceptions are encountered since columns that fineract tries to >>> insert or rename are no longer in the tables. >>> What step can I take at this point? >>> >>> Regards. >>> Wilfred >>> >>
