Daniele Santoro added a comment - 11/Jul/18 11:03 AM Dear, I've forwarded your ticket to the second level support. In particular you can refer to joaquin.salvachua@upm.es for Cygnus support and to fdelavega@fi.upm.es for CKAN support.

Daniele Santoro added a comment - 11/Jul/18 11:05 AM The issue has been emailed: Time sent: 11/Jul/18 11:05 AM To: *fdelavega@conwet.com * with subject: *( HELP-14397 ) [Fiware-lab-help] FIWARE MAG2 Cygnus support * From FIWARE JIRA - Main Help Desk ---- ------------------------------------------------------------------------------- Comments: Daniele Santoro - Today 11:03 AM ------------------ Dear, I've forwarded your ticket to the second level support. In particular you can refer to joaquin.salvachua@upm.es for Cygnus support and to fdelavega@fi.upm.es for CKAN support. ------------------------ Issue id: HELP-14397 Description: Dear FIWARE help desk We are working at FrontierCities2 MAG2 project but we have some issue with Cygnus GE. In particular, our idea is to gather data from Orion GE and to push them into postgreSQL and CKAN by using the Cygnus GE. We installed cygnus v 1.9.0 by means of docker Regarding CKAN (v 2.8.0) we have the Exception reported below: "18/07/10 11:04:36 ERROR flume.SinkRunner: Unable to deliver event. Exception follows. java.lang.IllegalStateException: begin() called when transaction is OPEN! at com.google.common.base.Preconditions.checkState(Preconditions.java:145) at org.apache.flume.channel.BasicTransactionSemantics.begin(BasicTransactionSemantics.java:131) at com.telefonica.iot.cygnus.sinks.NGSISink.processNewBatches(NGSISink.java:482) at com.telefonica.iot.cygnus.sinks.NGSISink.process(NGSISink.java:370) at org.apache.flume.sink.DefaultSinkProcessor.process(DefaultSinkProcessor.java:68) at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147) at java.lang.Thread.run(Thread.java:748)" We tried to find a solution using Google, in particular, we modified the file "agent.conf" to set ckan sink and ckan channel. But, we have still problems. Indeed, during the update of Orion Context Broker the istance "cygnus-ngsi" start the transaction to update the data on our ckan platform but the exception reported above. Instead, regarding postgresql (9.15.13) the istance, before start a transaction, throws this error: "ERROR sinks.NGSISink: CygnusPersistenceError. -, null. Stack trace: [com.telefonica.iot.cygnus.sinks.NGSIPostgreSQLSink.persistAggregation(NGSIPostgreSQLSink.java:504), com.telefonica.iot.cygnus.sinks.NGSIPostgreSQLSink.persistBatch(NGSIPostgreSQLSink.java:231), com.telefonica.iot.cygnus.sinks.NGSISink.processRollbackedBatches(NGSISink.java:390), com.telefonica.iot.cygnus.sinks.NGSISink.process(NGSISink.java:372), org.apache.flume.sink.DefaultSinkProcessor.process(DefaultSinkProcessor.java:68), org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147), java.lang.Thread.run(Thread.java:748)] ". Enclosed I'm sending you our configuration file. Please, May you help us? Thank you a lot. Best regards __________________________________________________________________________________________ You can get more information about our cookies and privacy policies on the following links: http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE Fiware-lab-help mailing list Fiware-lab-help@lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-help [Created via e-mail received from: Antonino Galletta <angalletta@unime.it>] FIWARE Chapter: FIWARE GEri: Status: In Progress --------------------- This email was generated by FIWARE JIRA following an email received into the Main Help Desk.

Andres Muñoz added a comment - 11/Jul/18 12:03 PM HI, I have been checking your conf file and I notice that you have a configuration for other sinks like mongo, mysql, etc. Could you tell me if you also have problems with those sinks?.

Andres Muñoz added a comment - 30/Jul/18 10:56 AM Waiting for feedback

Andres Muñoz added a comment - 09/Aug/18 5:04 PM No feedback from user, close due to inactivity