Re: Fineract 1.5.0 to 1.6.0 upgrade

[Kelvin Ikome]

Okay,

Thanks, Aleks, Arnold.

We have begun the work for 1.6 tag

On Mon, Mar 7, 2022 at 10:55 AM Aleksandar Vidakovic <
chee...@monkeysintown.com> wrote:

> Hi Kelvin,
>
> ... you can't do that anymore (pulling from develop immediately)... you
> have to first upgrade your instance (aka database schema with Fineract
> 1.6.0... the release that is... exactly that version)... and only after
> that you can do the upgrade with the current develop branch (we try to keep
> this as error free as possible, but develop is considered unstable until we
> release).
>
> Hope that helps.
>
> Cheers,
>
> Aleks
>
> On Mon, Mar 7, 2022 at 10:15 AM Kelvin Ikome  wrote:
>
>> Hi Arnold,
>>
>> We pulled in from the develop branch
>>
>> On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics 
>> wrote:
>>
>>> Hi Kelvin, Sifiso,
>>>
>>> *Kelvin: *
>>> Could you please share a little more info which version of Fineract
>>> you're trying to use?
>>>
>>> The thing is, the latest release version (1.6.0) doesn't have Liquibase
>>> at all, it still runs Flyway migrations. Only the develop branch (later to
>>> be 1.7.0) got switched to Liquibase.
>>>
>>> *Sifiso:*
>>> Could you please start another thread on your problems? A database
>>> upgrade seems to be another thing to take care of. Also, make sure to share
>>> the kind of errors you're experiencing.
>>>
>>> Best,
>>> Arnold
>>>
>>> On Mon, Mar 7, 2022 at 8:59 AM  wrote:
>>>
 Hi Kelvin,



 We are actually in the same predicament as you. However we have
 upgraded our database from MySQL 5.7 as advised to MariaDB 10.6. If we use
 data from version 18.03.01 it fails to migrate our data. If we use
 databases running on 1.5.0 release it completes the startup but the system
 login fails.



 Let’s hear from the others what challenges they’ve experienced, maybe
 there is a workaround already.



 Regards,

 Sifiso



 *From:* Kelvin Ikome 
 *Sent:* Monday, 07 March 2022 9:29 AM
 *To:* dev@fineract.apache.org
 *Subject:* Fineract 1.5.0 to 1.6.0 upgrade



 Hi everyone,



 We have upgraded from Fineract 1.5.0 to 1.6.0.

 After dropping the flyway migrations table (schema_version), Liquibase
 runs it's own migrations which fails (in recreating tables which already
 exist) because we are aiming to re-use DB with existing data from Fineract
 1.5.0.



 Any ideas on how to address this would be greatly appreciated.



 Kind regards



 --

 *Kelvin Ikome*
 Chief Executive Officer

 [image: facebook icon]  [image:
 twitter icon]  [image: youtube icon]
  [image:
 linkedin icon] 


 *t:*
 *m:*
 *e:*
 *a:*

 +(237) 677-666-659
 kel...@ciniter.com
 Ciniter, Molyko, Buea, South West, Cameroon
 *www.ciniter.com* 



>>>
>>
>> --
>> Kelvin Ikome
>> Chief Executive Officer [image: facebook icon]
>>  [image: twitter icon]
>>  [image: youtube icon]
>>  [image:
>> linkedin icon] 
>>
>>
>> t:
>> m:
>> e:
>> a: +(237) 677-666-659
>> kel...@ciniter.com
>> Ciniter, Molyko, Buea, South West, Cameroon
>> www.ciniter.com
>>
>

-- 
Kelvin Ikome
Chief Executive Officer [image: facebook icon]
 [image: twitter icon]
 [image: youtube icon]
 [image: linkedin
icon] 


t:
m:
e:
a: +(237) 677-666-659
kel...@ciniter.com
Ciniter, Molyko, Buea, South West, Cameroon
www.ciniter.com

Discussion patch release eg 1.6.1

[James Dailey]

Given the significant changes now in dev branch, I think that we should
have a separate email thread for any critical changes to 1.6.

That is, for any security critical or similarity critical issues, there
should be a potential for a patch update.  Fineract Version 1.6.1.  (Only
if needed, I may be getting ahead of myself.)

If someone sees an issue that cannot wait for a version 1.7 stable release,
please speak up.  Or better yet, propose the changes.

PROPOSAL
Because we haven’t previously discussed a patch release, let agree that as
a matter of policy, such changes will not automatically make it into 1.7.
They may be cherry picked by the release manager IFF they don’t break the
build.

(By the way, I think for a number of reasons, projects and operational
people would be advised to upgrade to at least 1.5 if not 1.6)

Thanks



On Mon, Mar 7, 2022 at 10:01 AM VICTOR MANUEL ROMERO RODRIGUEZ <
victor.rom...@fintecheando.mx> wrote:

> Hello,
>
> Using the CLI for getting the fineract version 1.6.0
>
> git clone -b 1.6.0 --single-branch https://github.com/apache/fineract.git
>
> Regards
>
> El lun, 7 mar 2022 a las 9:32, Bharath Gowda ()
> escribió:
>
>> Hello Everyone,
>>
>> Happy to see many community members upgrading to Fineract 1.6
>>
>> Below are a few Upgrade notes for users who are facing upgrading issues
>>
>> 1. Fineract 1.6 Release tag (without  Liquibase   ) is  here
>> 
>>
>> 2. Avoid Upgrading for any version below 1.6 to the latest develop branch
>> directly
>>
>> 3. Always upgrade to Fineract 1.6 (*point-1*) and then update to develop
>> branch (for smoother Liquibase upgrades)
>>
>> 4. Required prerequisites for Fineract 1.6 is
>> Mysql 8 / MariaDB 10.6
>> Java >= 17
>>
>> 5. Fineract 1.6 doesn't run on Mysql 5.7, please upgrade to the latest
>> version mentioned in* step 4*
>>
>>
>> @Francis Guchie  please share other points that
>> you have observed during the upgrade
>>
>>
>> We will come up with an official upgrade document on the latest release
>> along with the Mifos UI release which is around the corner :)
>>
>> Hope this email helps until then :)
>>
>>
>>
>>
>> Regards,
>> Bharath
>> Lead Implementation Analyst | Mifos Initiative
>> Skype: live:cbharath4| Mobile: +91.7019635592
>> http://mifos.org  
>> 
>>
> --
Sent from Gmail Mobile

Re: Fineract 1.6 Upgrade Notes

[VICTOR MANUEL ROMERO RODRIGUEZ]

Hello,

Using the CLI for getting the fineract version 1.6.0

git clone -b 1.6.0 --single-branch https://github.com/apache/fineract.git

Regards

El lun, 7 mar 2022 a las 9:32, Bharath Gowda () escribió:

> Hello Everyone,
>
> Happy to see many community members upgrading to Fineract 1.6
>
> Below are a few Upgrade notes for users who are facing upgrading issues
>
> 1. Fineract 1.6 Release tag (without  Liquibase   ) is  here
> 
>
> 2. Avoid Upgrading for any version below 1.6 to the latest develop branch
> directly
>
> 3. Always upgrade to Fineract 1.6 (*point-1*) and then update to develop
> branch (for smoother Liquibase upgrades)
>
> 4. Required prerequisites for Fineract 1.6 is
> Mysql 8 / MariaDB 10.6
> Java >= 17
>
> 5. Fineract 1.6 doesn't run on Mysql 5.7, please upgrade to the latest
> version mentioned in* step 4*
>
>
> @Francis Guchie  please share other points that
> you have observed during the upgrade
>
>
> We will come up with an official upgrade document on the latest release
> along with the Mifos UI release which is around the corner :)
>
> Hope this email helps until then :)
>
>
>
>
> Regards,
> Bharath
> Lead Implementation Analyst | Mifos Initiative
> Skype: live:cbharath4| Mobile: +91.7019635592
> http://mifos.org  
> 
>

Fineract 1.6 Upgrade Notes

[Bharath Gowda]

Hello Everyone,

Happy to see many community members upgrading to Fineract 1.6

Below are a few Upgrade notes for users who are facing upgrading issues

1. Fineract 1.6 Release tag (without  Liquibase   ) is  here


2. Avoid Upgrading for any version below 1.6 to the latest develop branch
directly

3. Always upgrade to Fineract 1.6 (*point-1*) and then update to develop
branch (for smoother Liquibase upgrades)

4. Required prerequisites for Fineract 1.6 is
Mysql 8 / MariaDB 10.6
Java >= 17

5. Fineract 1.6 doesn't run on Mysql 5.7, please upgrade to the latest
version mentioned in* step 4*


@Francis Guchie  please share other points that
you have observed during the upgrade


We will come up with an official upgrade document on the latest release
along with the Mifos UI release which is around the corner :)

Hope this email helps until then :)




Regards,
Bharath
Lead Implementation Analyst | Mifos Initiative
Skype: live:cbharath4| Mobile: +91.7019635592
http://mifos.org  

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Aleksandar Vidakovic]

Hi Kelvin,

... you can't do that anymore (pulling from develop immediately)... you
have to first upgrade your instance (aka database schema with Fineract
1.6.0... the release that is... exactly that version)... and only after
that you can do the upgrade with the current develop branch (we try to keep
this as error free as possible, but develop is considered unstable until we
release).

Hope that helps.

Cheers,

Aleks

On Mon, Mar 7, 2022 at 10:15 AM Kelvin Ikome  wrote:

> Hi Arnold,
>
> We pulled in from the develop branch
>
> On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics 
> wrote:
>
>> Hi Kelvin, Sifiso,
>>
>> *Kelvin: *
>> Could you please share a little more info which version of Fineract
>> you're trying to use?
>>
>> The thing is, the latest release version (1.6.0) doesn't have Liquibase
>> at all, it still runs Flyway migrations. Only the develop branch (later to
>> be 1.7.0) got switched to Liquibase.
>>
>> *Sifiso:*
>> Could you please start another thread on your problems? A database
>> upgrade seems to be another thing to take care of. Also, make sure to share
>> the kind of errors you're experiencing.
>>
>> Best,
>> Arnold
>>
>> On Mon, Mar 7, 2022 at 8:59 AM  wrote:
>>
>>> Hi Kelvin,
>>>
>>>
>>>
>>> We are actually in the same predicament as you. However we have upgraded
>>> our database from MySQL 5.7 as advised to MariaDB 10.6. If we use data from
>>> version 18.03.01 it fails to migrate our data. If we use databases running
>>> on 1.5.0 release it completes the startup but the system login fails.
>>>
>>>
>>>
>>> Let’s hear from the others what challenges they’ve experienced, maybe
>>> there is a workaround already.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Sifiso
>>>
>>>
>>>
>>> *From:* Kelvin Ikome 
>>> *Sent:* Monday, 07 March 2022 9:29 AM
>>> *To:* dev@fineract.apache.org
>>> *Subject:* Fineract 1.5.0 to 1.6.0 upgrade
>>>
>>>
>>>
>>> Hi everyone,
>>>
>>>
>>>
>>> We have upgraded from Fineract 1.5.0 to 1.6.0.
>>>
>>> After dropping the flyway migrations table (schema_version), Liquibase
>>> runs it's own migrations which fails (in recreating tables which already
>>> exist) because we are aiming to re-use DB with existing data from Fineract
>>> 1.5.0.
>>>
>>>
>>>
>>> Any ideas on how to address this would be greatly appreciated.
>>>
>>>
>>>
>>> Kind regards
>>>
>>>
>>>
>>> --
>>>
>>> *Kelvin Ikome*
>>> Chief Executive Officer
>>>
>>> [image: facebook icon]  [image:
>>> twitter icon]  [image: youtube icon]
>>>  [image:
>>> linkedin icon] 
>>>
>>>
>>> *t:*
>>> *m:*
>>> *e:*
>>> *a:*
>>>
>>> +(237) 677-666-659
>>> kel...@ciniter.com
>>> Ciniter, Molyko, Buea, South West, Cameroon
>>> *www.ciniter.com* 
>>>
>>>
>>>
>>
>
> --
> Kelvin Ikome
> Chief Executive Officer [image: facebook icon]
>  [image: twitter icon]
>  [image: youtube icon]
>  [image:
> linkedin icon] 
>
>
> t:
> m:
> e:
> a: +(237) 677-666-659
> kel...@ciniter.com
> Ciniter, Molyko, Buea, South West, Cameroon
> www.ciniter.com
>

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Kelvin Ikome]

Hi Arnold,

We pulled in from the develop branch

On Mon, Mar 7, 2022 at 10:13 AM Arnold Galovics 
wrote:

> Hi Kelvin, Sifiso,
>
> *Kelvin: *
> Could you please share a little more info which version of Fineract you're
> trying to use?
>
> The thing is, the latest release version (1.6.0) doesn't have Liquibase at
> all, it still runs Flyway migrations. Only the develop branch (later to be
> 1.7.0) got switched to Liquibase.
>
> *Sifiso:*
> Could you please start another thread on your problems? A database upgrade
> seems to be another thing to take care of. Also, make sure to share the
> kind of errors you're experiencing.
>
> Best,
> Arnold
>
> On Mon, Mar 7, 2022 at 8:59 AM  wrote:
>
>> Hi Kelvin,
>>
>>
>>
>> We are actually in the same predicament as you. However we have upgraded
>> our database from MySQL 5.7 as advised to MariaDB 10.6. If we use data from
>> version 18.03.01 it fails to migrate our data. If we use databases running
>> on 1.5.0 release it completes the startup but the system login fails.
>>
>>
>>
>> Let’s hear from the others what challenges they’ve experienced, maybe
>> there is a workaround already.
>>
>>
>>
>> Regards,
>>
>> Sifiso
>>
>>
>>
>> *From:* Kelvin Ikome 
>> *Sent:* Monday, 07 March 2022 9:29 AM
>> *To:* dev@fineract.apache.org
>> *Subject:* Fineract 1.5.0 to 1.6.0 upgrade
>>
>>
>>
>> Hi everyone,
>>
>>
>>
>> We have upgraded from Fineract 1.5.0 to 1.6.0.
>>
>> After dropping the flyway migrations table (schema_version), Liquibase
>> runs it's own migrations which fails (in recreating tables which already
>> exist) because we are aiming to re-use DB with existing data from Fineract
>> 1.5.0.
>>
>>
>>
>> Any ideas on how to address this would be greatly appreciated.
>>
>>
>>
>> Kind regards
>>
>>
>>
>> --
>>
>> *Kelvin Ikome*
>> Chief Executive Officer
>>
>> [image: facebook icon]  [image:
>> twitter icon]  [image: youtube icon]
>>  [image:
>> linkedin icon] 
>>
>>
>> *t:*
>> *m:*
>> *e:*
>> *a:*
>>
>> +(237) 677-666-659
>> kel...@ciniter.com
>> Ciniter, Molyko, Buea, South West, Cameroon
>> *www.ciniter.com* 
>>
>>
>>
>

-- 
Kelvin Ikome
Chief Executive Officer [image: facebook icon]
 [image: twitter icon]
 [image: youtube icon]
 [image: linkedin
icon] 


t:
m:
e:
a: +(237) 677-666-659
kel...@ciniter.com
Ciniter, Molyko, Buea, South West, Cameroon
www.ciniter.com

Re: Fineract 1.5.0 to 1.6.0 upgrade

[Arnold Galovics]

Hi Kelvin, Sifiso,

*Kelvin: *
Could you please share a little more info which version of Fineract you're
trying to use?

The thing is, the latest release version (1.6.0) doesn't have Liquibase at
all, it still runs Flyway migrations. Only the develop branch (later to be
1.7.0) got switched to Liquibase.

*Sifiso:*
Could you please start another thread on your problems? A database upgrade
seems to be another thing to take care of. Also, make sure to share the
kind of errors you're experiencing.

Best,
Arnold

On Mon, Mar 7, 2022 at 8:59 AM  wrote:

> Hi Kelvin,
>
>
>
> We are actually in the same predicament as you. However we have upgraded
> our database from MySQL 5.7 as advised to MariaDB 10.6. If we use data from
> version 18.03.01 it fails to migrate our data. If we use databases running
> on 1.5.0 release it completes the startup but the system login fails.
>
>
>
> Let’s hear from the others what challenges they’ve experienced, maybe
> there is a workaround already.
>
>
>
> Regards,
>
> Sifiso
>
>
>
> *From:* Kelvin Ikome 
> *Sent:* Monday, 07 March 2022 9:29 AM
> *To:* dev@fineract.apache.org
> *Subject:* Fineract 1.5.0 to 1.6.0 upgrade
>
>
>
> Hi everyone,
>
>
>
> We have upgraded from Fineract 1.5.0 to 1.6.0.
>
> After dropping the flyway migrations table (schema_version), Liquibase
> runs it's own migrations which fails (in recreating tables which already
> exist) because we are aiming to re-use DB with existing data from Fineract
> 1.5.0.
>
>
>
> Any ideas on how to address this would be greatly appreciated.
>
>
>
> Kind regards
>
>
>
> --
>
> *Kelvin Ikome*
> Chief Executive Officer
>
> [image: facebook icon]  [image:
> twitter icon]  [image: youtube icon]
>  [image:
> linkedin icon] 
>
>
> *t:*
> *m:*
> *e:*
> *a:*
>
> +(237) 677-666-659
> kel...@ciniter.com
> Ciniter, Molyko, Buea, South West, Cameroon
> *www.ciniter.com* 
>
>
>

Re: SMS Gateway failing to run

[Mexina Daniel]

Hi Arnold

Thank you for your response.

The URL has not changed from the time it was working, and I have checked 
it is still correct.


Regarding to their services, the same service is used in another server 
which use the same platform and it is working fine, I have tested even 
in my local computer and the messagegateway ran successfully.


Kind Regards

--

Mexina Daniel

Chief Executive Officer

Singo Africa Limited

Email:
mexina@singo.africa

Company Website:
https://singo.africa

Amala Website:
https://amala.co.tz

KopaSmart
https://kopasmart.app

Mobile:
+255 71 211 0791

Address:
Magomeni Usalama, Watumishi House, 1st Floor

P.O.BOX 78908 | 14121 Dar es Salaam

 [1] [2] [3] [4]

On 04-03-2022 12:50, Arnold Galovics wrote:


Hi Mexina,

Which fineract version are you running?

I took a quick look at the logs you attached and there's this piece:

Exception in thread "pool-6-thread-1" 
org.springframework.web.client.HttpClientErrorException$NotFound: 404 
Not Found: [Apache Tomcat/7.0.82 - Error 
report