DHIS2 Metadata Sync error

Hello DHIS team,

we are trying the metadata sync feature but unfortunately it does not seem to work.

Note: on our setup instance2 is going to sync from instance1

What we tried so far:

Case 1:

  • manually import metdata from a json file to instance1

  • upgrade instance1 running v2.22 to v2.24, everything went fine

  • create a ‘metadata version’ on instance1

  • configure instance2 to sync from instance1

  • trigger the sync with the ‘sync now’ button

Case 2:

  • manually import metdata from a json file to instance1

  • upgrade instance1 running v2.22 to v2.24, everything went fine

  • save the dump of instance1’s database

  • restore the dump of instance1’s to instance2’s database

  • create a ‘metadata version’ on instance1

  • configure instance2 to sync from instance1

  • trigger the sync with the ‘sync now’ button

We were following this guide:
https://dhis2.github.io/dhis2-docs/master/en/user/html/dataAdmin_metaDataSync.html

On both cases the sync fails, error logs from instance2 attached.

Any hint on how to get the metadata sync working?

Thanks

err.log (7.91 KB)

Hi,

As per the logs, metadata sync is failing in the importer phase when trying to import metadata.

···

On Fri, Nov 4, 2016 at 8:22 PM, Francesco Palazzini francesco.palazzini@ehealthnigeria.org wrote:

Hello DHIS team,

we are trying the metadata sync feature but unfortunately it does not seem to work.

Note: on our setup instance2 is going to sync from instance1

What we tried so far:

Case 1:

  • manually import metdata from a json file to instance1
  • upgrade instance1 running v2.22 to v2.24, everything went fine
  • create a ‘metadata version’ on instance1
  • configure instance2 to sync from instance1
  • trigger the sync with the ‘sync now’ button

Case 2:

  • manually import metdata from a json file to instance1
  • upgrade instance1 running v2.22 to v2.24, everything went fine
  • save the dump of instance1’s database
  • restore the dump of instance1’s to instance2’s database
  • create a ‘metadata version’ on instance1
  • configure instance2 to sync from instance1
  • trigger the sync with the ‘sync now’ button

We were following this guide:
https://dhis2.github.io/dhis2-docs/master/en/user/html/dataAdmin_metaDataSync.html

On both cases the sync fails, error logs from instance2 attached.

Any hint on how to get the metadata sync working?

Thanks


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Yeah, this is probably related to the same issues we are already investigating.

···

On Mon, Nov 7, 2016 at 12:32 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Hi,

As per the logs, metadata sync is failing in the importer phase when trying to import metadata.


  • ERROR 2016-10-24 11:44:03,758 Exception occurred while trying to import the metadata. object references an unsaved transient instance - save the transient instance before flushing: org.hisp.dhis.dataelement.DataElement

Morten, any suggestions regarding this.

Thanks

Aamer.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Fri, Nov 4, 2016 at 8:22 PM, Francesco Palazzini francesco.palazzini@ehealthnigeria.org wrote:

Hello DHIS team,

we are trying the metadata sync feature but unfortunately it does not seem to work.

Note: on our setup instance2 is going to sync from instance1

What we tried so far:

Case 1:

  • manually import metdata from a json file to instance1
  • upgrade instance1 running v2.22 to v2.24, everything went fine
  • create a ‘metadata version’ on instance1
  • configure instance2 to sync from instance1
  • trigger the sync with the ‘sync now’ button

Case 2:

  • manually import metdata from a json file to instance1
  • upgrade instance1 running v2.22 to v2.24, everything went fine
  • save the dump of instance1’s database
  • restore the dump of instance1’s to instance2’s database
  • create a ‘metadata version’ on instance1
  • configure instance2 to sync from instance1
  • trigger the sync with the ‘sync now’ button

We were following this guide:
https://dhis2.github.io/dhis2-docs/master/en/user/html/dataAdmin_metaDataSync.html

On both cases the sync fails, error logs from instance2 attached.

Any hint on how to get the metadata sync working?

Thanks


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

This should have been fixed now, please try it out and report back to us (give our servers 30+ min to build a new war file)

···

On Mon, Nov 7, 2016 at 12:39 PM, Morten Olav Hansen morten@dhis2.org wrote:

Yeah, this is probably related to the same issues we are already investigating.

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Nov 7, 2016 at 12:32 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Hi,

As per the logs, metadata sync is failing in the importer phase when trying to import metadata.


  • ERROR 2016-10-24 11:44:03,758 Exception occurred while trying to import the metadata. object references an unsaved transient instance - save the transient instance before flushing: org.hisp.dhis.dataelement.DataElement

Morten, any suggestions regarding this.

Thanks

Aamer.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Fri, Nov 4, 2016 at 8:22 PM, Francesco Palazzini francesco.palazzini@ehealthnigeria.org wrote:

Hello DHIS team,

we are trying the metadata sync feature but unfortunately it does not seem to work.

Note: on our setup instance2 is going to sync from instance1

What we tried so far:

Case 1:

  • manually import metdata from a json file to instance1
  • upgrade instance1 running v2.22 to v2.24, everything went fine
  • create a ‘metadata version’ on instance1
  • configure instance2 to sync from instance1
  • trigger the sync with the ‘sync now’ button

Case 2:

  • manually import metdata from a json file to instance1
  • upgrade instance1 running v2.22 to v2.24, everything went fine
  • save the dump of instance1’s database
  • restore the dump of instance1’s to instance2’s database
  • create a ‘metadata version’ on instance1
  • configure instance2 to sync from instance1
  • trigger the sync with the ‘sync now’ button

We were following this guide:
https://dhis2.github.io/dhis2-docs/master/en/user/html/dataAdmin_metaDataSync.html

On both cases the sync fails, error logs from instance2 attached.

Any hint on how to get the metadata sync working?

Thanks


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Hi,

thanks for the support, but it still does not work.

Logs attached.

Thanks

err2.log (18.2 KB)

···

On Mon, Nov 7, 2016 at 8:37 AM, Morten Olav Hansen morten@dhis2.org wrote:

This should have been fixed now, please try it out and report back to us (give our servers 30+ min to build a new war file)

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Nov 7, 2016 at 12:39 PM, Morten Olav Hansen morten@dhis2.org wrote:

Yeah, this is probably related to the same issues we are already investigating.

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Nov 7, 2016 at 12:32 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Hi,

As per the logs, metadata sync is failing in the importer phase when trying to import metadata.


  • ERROR 2016-10-24 11:44:03,758 Exception occurred while trying to import the metadata. object references an unsaved transient instance - save the transient instance before flushing: org.hisp.dhis.dataelement.DataElement

Morten, any suggestions regarding this.

Thanks

Aamer.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Fri, Nov 4, 2016 at 8:22 PM, Francesco Palazzini francesco.palazzini@ehealthnigeria.org wrote:

Hello DHIS team,

we are trying the metadata sync feature but unfortunately it does not seem to work.

Note: on our setup instance2 is going to sync from instance1

What we tried so far:

Case 1:

  • manually import metdata from a json file to instance1
  • upgrade instance1 running v2.22 to v2.24, everything went fine
  • create a ‘metadata version’ on instance1
  • configure instance2 to sync from instance1
  • trigger the sync with the ‘sync now’ button

Case 2:

  • manually import metdata from a json file to instance1
  • upgrade instance1 running v2.22 to v2.24, everything went fine
  • save the dump of instance1’s database
  • restore the dump of instance1’s to instance2’s database
  • create a ‘metadata version’ on instance1
  • configure instance2 to sync from instance1
  • trigger the sync with the ‘sync now’ button

We were following this guide:
https://dhis2.github.io/dhis2-docs/master/en/user/html/dataAdmin_metaDataSync.html

On both cases the sync fails, error logs from instance2 attached.

Any hint on how to get the metadata sync working?

Thanks


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Ok, I think we need quite a bit more information before we can help you debug this. Are you able to share the metadata you are working on? (privately)

···

On Mon, Nov 7, 2016 at 7:11 PM, Francesco Palazzini francesco.palazzini@ehealthnigeria.org wrote:

Hi,

thanks for the support, but it still does not work.

Logs attached.

Thanks

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Nov 7, 2016 at 8:37 AM, Morten Olav Hansen morten@dhis2.org wrote:

This should have been fixed now, please try it out and report back to us (give our servers 30+ min to build a new war file)

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Nov 7, 2016 at 12:39 PM, Morten Olav Hansen morten@dhis2.org wrote:

Yeah, this is probably related to the same issues we are already investigating.

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Nov 7, 2016 at 12:32 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Hi,

As per the logs, metadata sync is failing in the importer phase when trying to import metadata.


  • ERROR 2016-10-24 11:44:03,758 Exception occurred while trying to import the metadata. object references an unsaved transient instance - save the transient instance before flushing: org.hisp.dhis.dataelement.DataElement

Morten, any suggestions regarding this.

Thanks

Aamer.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Fri, Nov 4, 2016 at 8:22 PM, Francesco Palazzini francesco.palazzini@ehealthnigeria.org wrote:

Hello DHIS team,

we are trying the metadata sync feature but unfortunately it does not seem to work.

Note: on our setup instance2 is going to sync from instance1

What we tried so far:

Case 1:

  • manually import metdata from a json file to instance1
  • upgrade instance1 running v2.22 to v2.24, everything went fine
  • create a ‘metadata version’ on instance1
  • configure instance2 to sync from instance1
  • trigger the sync with the ‘sync now’ button

Case 2:

  • manually import metdata from a json file to instance1
  • upgrade instance1 running v2.22 to v2.24, everything went fine
  • save the dump of instance1’s database
  • restore the dump of instance1’s to instance2’s database
  • create a ‘metadata version’ on instance1
  • configure instance2 to sync from instance1
  • trigger the sync with the ‘sync now’ button

We were following this guide:
https://dhis2.github.io/dhis2-docs/master/en/user/html/dataAdmin_metaDataSync.html

On both cases the sync fails, error logs from instance2 attached.

Any hint on how to get the metadata sync working?

Thanks


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Hi Francesco,

Just thinking if you are facing this issue due to upgrade. Did you run the upgrade in a sequential manner from 2.22 to 2.24 by following the upgrade scripts wherever applicable? Did you try syncing from an instance(>=2.24) which is not upgraded?

Thanks

···

On Mon, Nov 7, 2016 at 5:46 PM, Morten Olav Hansen morten@dhis2.org wrote:

Ok, I think we need quite a bit more information before we can help you debug this. Are you able to share the metadata you are working on? (privately)

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Nov 7, 2016 at 7:11 PM, Francesco Palazzini francesco.palazzini@ehealthnigeria.org wrote:

Hi,

thanks for the support, but it still does not work.

Logs attached.

Thanks

On Mon, Nov 7, 2016 at 8:37 AM, Morten Olav Hansen morten@dhis2.org wrote:

This should have been fixed now, please try it out and report back to us (give our servers 30+ min to build a new war file)

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Nov 7, 2016 at 12:39 PM, Morten Olav Hansen morten@dhis2.org wrote:

Yeah, this is probably related to the same issues we are already investigating.

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Nov 7, 2016 at 12:32 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Hi,

As per the logs, metadata sync is failing in the importer phase when trying to import metadata.


  • ERROR 2016-10-24 11:44:03,758 Exception occurred while trying to import the metadata. object references an unsaved transient instance - save the transient instance before flushing: org.hisp.dhis.dataelement.DataElement

Morten, any suggestions regarding this.

Thanks

Aamer.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Fri, Nov 4, 2016 at 8:22 PM, Francesco Palazzini francesco.palazzini@ehealthnigeria.org wrote:

Hello DHIS team,

we are trying the metadata sync feature but unfortunately it does not seem to work.

Note: on our setup instance2 is going to sync from instance1

What we tried so far:

Case 1:

  • manually import metdata from a json file to instance1
  • upgrade instance1 running v2.22 to v2.24, everything went fine
  • create a ‘metadata version’ on instance1
  • configure instance2 to sync from instance1
  • trigger the sync with the ‘sync now’ button

Case 2:

  • manually import metdata from a json file to instance1
  • upgrade instance1 running v2.22 to v2.24, everything went fine
  • save the dump of instance1’s database
  • restore the dump of instance1’s to instance2’s database
  • create a ‘metadata version’ on instance1
  • configure instance2 to sync from instance1
  • trigger the sync with the ‘sync now’ button

We were following this guide:
https://dhis2.github.io/dhis2-docs/master/en/user/html/dataAdmin_metaDataSync.html

On both cases the sync fails, error logs from instance2 attached.

Any hint on how to get the metadata sync working?

Thanks


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Just thinking if you are facing this issue due to upgrade. Did you run the
upgrade in a sequential manner from 2.22 to 2.24 by following the upgrade
scripts wherever applicable? Did you try syncing from an instance(>=2.24)
which is not upgraded?

I have not run any upgrade script, I will try that first.
I was trying to sync from a new 2.24 instance.

Will keep you informed.

Thank you
Francesco

···

Thanks

On Mon, Nov 7, 2016 at 5:46 PM, Morten Olav Hansen <morten@dhis2.org> > wrote:

Ok, I think we need quite a bit more information before we can help you
debug this. Are you able to share the metadata you are working on?
(privately)

--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org

On Mon, Nov 7, 2016 at 7:11 PM, Francesco Palazzini < >> francesco.palazzini@ehealthnigeria.org> wrote:

Hi,
thanks for the support, but it still does not work.

Logs attached.

Thanks

On Mon, Nov 7, 2016 at 8:37 AM, Morten Olav Hansen <morten@dhis2.org> >>> wrote:

This should have been fixed now, please try it out and report back to
us (give our servers 30+ min to build a new war file)

--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org

On Mon, Nov 7, 2016 at 12:39 PM, Morten Olav Hansen <morten@dhis2.org> >>>> wrote:

Yeah, this is probably related to the same issues we are already
investigating.

--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org

On Mon, Nov 7, 2016 at 12:32 PM, Aamer Mohammed < >>>>> aamerm@thoughtworks.com> wrote:

Hi,

As per the logs, metadata sync is failing in the importer phase when
trying to import metadata.
----------
* ERROR 2016-10-24 11:44:03,758 Exception occurred while trying to
import the metadata. object references an unsaved transient instance - save
the transient instance before flushing: org.hisp.dhis.dataelement.Data
Element
----------
Morten, any suggestions regarding this.

Thanks
Aamer.

On Fri, Nov 4, 2016 at 8:22 PM, Francesco Palazzini < >>>>>> francesco.palazzini@ehealthnigeria.org> wrote:

Hello DHIS team,
we are trying the metadata sync feature but unfortunately it does
not seem to work.

Note: on our setup instance2 is going to sync from instance1

What we tried so far:
Case 1:
- manually import metdata from a json file to instance1
- upgrade instance1 running v2.22 to v2.24, everything went fine
- create a 'metadata version' on instance1
- configure instance2 to sync from instance1
- trigger the sync with the 'sync now' button

Case 2:
- manually import metdata from a json file to instance1
- upgrade instance1 running v2.22 to v2.24, everything went fine
- save the dump of instance1's database
- restore the dump of instance1's to instance2's database
- create a 'metadata version' on instance1
- configure instance2 to sync from instance1
- trigger the sync with the 'sync now' button

We were following this guide:
https://dhis2.github.io/dhis2-docs/master/en/user/html/dataA
dmin_metaDataSync.html

On both cases the sync fails, error logs from instance2 attached.

Any hint on how to get the metadata sync working?

Thanks

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp