fiware-cygnus

CKAN Resource URL empty

由 让人想犯罪 __ 提交于 2019-12-11 04:35:44
问题 I'm integrating Orion and Cygnus_Ngsi with CKAN. I have configured in Cygnus the CKAN sink as following: cygnus-ngsi.sinks.ckan-sink.channel = ckan-channel cygnus-ngsi.sinks.ckan-sink.type = com.telefonica.iot.cygnus.sinks.NGSICKANSink cygnus-ngsi.sinks.ckan-sink.api_key = ba753aae-7c1f-XXXX-XXXXX-cf893100ab53 cygnus-ngsi.sinks.ckan-sink.ckan_host = ckan host cygnus-ngsi.sinks.ckan-sink.ckan_port = 8080 cygnus-ngsi.sinks.ckan-sink.orion_url = http://orion ip:1026 cygnus-ngsi.sinks.ckan-sink

How I specify the Fiware-Service and Fiware-ServicePath fields at Orion that set the name of MySQL database and table in Cygnus?

由 一个人想着一个人 提交于 2019-12-11 03:04:44
问题 So far I have configured ContextBroker to send data to Cygnus which in turn saves data by default names in database. But what if I want to target a specific database with a specific table? I know I have to set: dbName=<fiware-service> tableName=<fiware-servicePath>_<entityId>_<entityType> I dont know where that file is, and I know it isnt in /etc/sysconfig/contextBroker because that folder doesnt exist. EDIT1: here is my updatecontext: (curl localhost:1026/NGSI10/updateContext -s -S --header

Orion does not notify Cygnus (timeout error)

由 浪子不回头ぞ 提交于 2019-12-11 02:25:17
问题 Orion appears not to be able to reach Cygnus, and gives the following warning (I have hidden the IP's): WARNING@13:33:21 AlarmManager.cpp[303]: Raising alarm NotificationError Y.Y.Y.Y:5050/notify: (curl_easy_perform failed: Timeout was reached) I first created an entity, then made a subscription, and subsequently updated the entity. For information, here is the entire debug logging from startup of the contextBroker: INFO@13:31:51 contextBroker.cpp[1808]: Startup completed INFO@13:32:51

Fiware Cygnus: no data have been persisted in CKAN

由 不想你离开。 提交于 2019-12-10 22:45:00
问题 I am trying to use cygnus with CKAN, but no data have been persisted in CKAN when the attribute is JSON type. First, I send information to Orion: Accept: application/json X-AUTH-TOKEN: <mytoken> Fiware-Service: PapelClubDemo Fiware-ServicePath: /events/leonliterario { "contextElements": [ { "type": "Events", "isPattern": "false", "id": "thisweek", "attributes": [ { "name": "schedule", "type": "json", "value": [{"title": "Presentación Viva Mi Gente","date": "2015-11-30","location": "Salón de

Connectivity problems between FILAB VMs and Cosmos global instance

由 眉间皱痕 提交于 2019-12-10 19:39:10
问题 I have the same kind of connectivity problem discussed in the question "Cygnus can not persist data on Cosmos global instance". However, I have found no solution after read it. Nowadays, I have recently deployed two virtual machines in FILAB (both VMs contain Orion ContextBroker 0.26.1 and Cygnus 0.11.0). When I try to persist data on Cosmos via Cygnus, I get the following error message (the same in both VMs) : 2015-12-17 19:03:00,221 (SinkRunner-PollingRunner-DefaultSinkProcessor) [ERROR -

Subscription status change after post

由 最后都变了- 提交于 2019-12-10 18:16:04
问题 After successfully installed Cygnus connector and testing the creation of subscriptions. With bellow files: agent_1.conf cygnus-ngsi.sources = http-source cygnus-ngsi.sinks = hdfs-sink cygnus-ngsi.channels = hdfs-channel cygnus-ngsi.sources.http-source.type = org.apache.flume.source.http.HTTPSource cygnus-ngsi.sources.http-source.channels = hdfs-channel cygnus-ngsi.sources.http-source.port = 5050 cygnus-ngsi.sources.http-source.handler = com.telefonica.iot.cygnus.handlers.NGSIRestHandler

HTTPS notification doesn't reach cygnus

由 本秂侑毒 提交于 2019-12-08 05:10:01
问题 Orion version is 2.1.0 Orion is started in HTTPS using the -https option We use the "HTTPS" protocol schema in URL in our subscriptions --> reference" : "https://cygnus.domain.com/notify" When we insert an Entity matching the subscription, the Entity is created in Orion, but not in STH. However Orion Logs return: Notification Successfully Sent to https://cygnus.domain.com:443/notify If we use the "HTTP" protocol schema in URL in our subscriptions it works If we use curl to notify dirctly

Automatic creation of the hive tables on cosmos

由 二次信任 提交于 2019-12-07 14:01:26
问题 I have an Orion context broker and i use cygnus(0.6) to send data to my cosmos account. Cygnus creates correctly the txt file with the data on my cosmos, but it does not create the tables for hive. I would query my data through an hive client. Is there a configuration paramater to set in cygnus.conf to do that? How can i solve? 回答1: I found myself with the same issue and found the problem. Check this: Cygnus release/0.6.0 does not create Hive extended tables 来源： https://stackoverflow.com

HTTPS notification doesn't reach cygnus

由 為{幸葍}努か 提交于 2019-12-07 09:33:42
Orion version is 2.1.0 Orion is started in HTTPS using the -https option We use the "HTTPS" protocol schema in URL in our subscriptions --> reference" : " https://cygnus.domain.com/notify " When we insert an Entity matching the subscription, the Entity is created in Orion, but not in STH. However Orion Logs return: Notification Successfully Sent to https://cygnus.domain.com:443/notify If we use the "HTTP" protocol schema in URL in our subscriptions it works If we use curl to notify dirctly Cygnus in HTTP or HTTPS it works Orion Logs bellow: time=Friday 22 Feb 11:24:28 2019.158Z | lvl=INFO |

ContextBroker subscriptions Error

由 别来无恙 提交于 2019-12-06 12:00:48
问题 I've updated cygnus from version 0.13 to 1.7.0 by installing NGSI following this tutorial: https://github.com/telefonicaid/fiware-cygnus/tree/master/cygnus-ngsi Error the subscription [ { "id": "59d38a92dbaa1e477aef9c00", "description": "A subscription to get info about pruebas", "status": "failed", "subject": { "entities": [ { "id": "pruebas", "type": "pruebas" } ], "condition": { "attrs": [ "pressure" ] } }, "notification": { "timesSent": 2, "lastNotification": "2017-10-03T13:03:43.00Z",
订阅 fiware-cygnus