fiware-orion

Cancel Subscription on Cygnus

徘徊边缘 提交于 2019-12-06 06:21:01
I have a subscription made to an entity's attribute to a MySql sink. The problem is that while I was testing my rest service to do a subscription if the data was not yet persisted, i made a ton of subscriptions. Now every time I do an update on the entity's attribute what happens is that the value is persisted a lot of times. Is there anyway of deleting a subscription without the subscriptionID? Yes, it is. First, you can list the existing subscriptions with the GET /v2/subscriptions operation (have a look to the draft NGSIv2 specification ). Once you have the IDs the unsubscribeContext

How to configure the Fiware PEP WILMA proxy to use a Keyrock and Orion instance on my own servers

我与影子孤独终老i 提交于 2019-12-06 02:09:11
I've spent most of the day trying to configure the Fiware PEP proxy Wilma to secure an Orion Context Broker i have running on a development server. The documentation here: http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/PEP_Proxy_- Wilma -_Installation_and_Administration_Guide is not clear. Here is my setup: A Fiware Keyrock instance running on server1, port 3000 A PEP Proxy running on server 1 An Orion Context Broker running on server2, port 1026 The manual states to edit the config.js script. Here is what i changed (Stackoverflow prevents me from entering url's so replace

ContextBroker subscriptions Error

寵の児 提交于 2019-12-04 15:09:57
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", "attrs": [ "temperature", "pressure" ], "attrsFormat": "legacy", "http": { "url": "http://localhost:5050

Orion Context Broker works half of the times

北战南征 提交于 2019-12-04 04:59:38
问题 I've installed Orion Context Broker 0.23.0 and it behaves rare: it only works half of the times. For instance, when trying to retrieve the version I get this error message: $ curl "http://localhost:1026/version" curl: (52) Empty reply from server $ curl "http://localhost:1026/version" <orion> <version>0.23.0</version> <uptime>15 d, 22 h, 13 m, 18 s</uptime> <git_hash>f5d76a6f11736d52402e63a4aa0ba990bff7f5eb</git_hash> <compile_time>Fri Jul 10 13:21:42 CEST 2015</compile_time> <compiled_by

ECONNRESET when opening a large number of connection in small time period

ぐ巨炮叔叔 提交于 2019-12-02 14:03:28
问题 I have situation where I want to create large number of entities on orion. I am using docker version of Orion and mongo with this docker-compose. version: "3" services: mongo: image: mongo:3.4 volumes: - /data/docker-mongo/db:/data/db - /data/docker-mongo/log/mongodb.log:/var/log/mongodb/mongod.log command: --nojournal orion: image: fiware/orion volumes: - /data/docker-mongo/log/contextBroker.log:/tmp/contextBroker.log links: - mongo ports: - "1026:1026" command: -dbhost mongo Now problems

How do I guarantee unique subscriptions in Orion Context Broker?

不想你离开。 提交于 2019-12-02 13:51:53
问题 In my setup I have one application that should subscribe to a specific kind of context change. The application currently perform subscription at startup time. However if I restart the application, the subscription is duplicated. To overcome this issue I started to keep track of subscriptions in a database, so that I have an association between my application id and the latest subscription id. Is there any way to achieve similar result in Orion (let's call it like "named subscriptions"),

Rush installation and integration with Orion Context Broker

泄露秘密 提交于 2019-12-02 13:09:05
问题 After having running the listener and one time a consumer in the Rush, I run: contextBroker -rush localhost:5001 I made sure to use Orion 0.17 instead of 0.14 and what It's shown after enter to the /version url is: <orion> <version>0.17.0</version> <uptime>0 d, 0 h, 12 m, 14 s</uptime> <git_hash>127793ff921b37a6a570cd315ddce9a3ec541ccf</git_hash> <compile_time>Fri Nov 28 09:41:22 CET 2014</compile_time> <compiled_by>fermin</compiled_by> <compiled_in>centollo</compiled_in> </orion> Now Rush

No connection between Freeboard's data source for Orion and Context Broker

痞子三分冷 提交于 2019-12-02 06:31:10
问题 I've been trying to connect Freeboard to visualize context information from OCB, however came across difficulties that prevent me from receiving any data from there. My thinking is that there is a problem with connecting Freeboard to OCB, because in OCB's subscription list there are no any new entries, and datasource in Freeboard shows that it has never been updated. OCB is turned on as a docker container. Freeboards run in docker host. I tried setting the ip as ip that I extracted from

Orion Context Broker HTTPS for subscribers

喜夏-厌秋 提交于 2019-12-02 06:17:48
问题 Very simply question: Does the Orion Context Broker support SSL for subscribers: Ex.: Can the callback URL for subscriptions be https://mysimpleexample.com/notify I've tried this (using a trusted certificate!), and this does not seem to work for me. That being said, I've not run the Orion Context Broker using the -https option. However, looking at the manual, this option seems to be for using SSL on the context broker http server, and have nothing to do with client subscriptions. Edit: I did

ECONNRESET when opening a large number of connection in small time period

时间秒杀一切 提交于 2019-12-02 05:27:10
I have situation where I want to create large number of entities on orion. I am using docker version of Orion and mongo with this docker-compose. version: "3" services: mongo: image: mongo:3.4 volumes: - /data/docker-mongo/db:/data/db - /data/docker-mongo/log/mongodb.log:/var/log/mongodb/mongod.log command: --nojournal orion: image: fiware/orion volumes: - /data/docker-mongo/log/contextBroker.log:/tmp/contextBroker.log links: - mongo ports: - "1026:1026" command: -dbhost mongo Now problems happens when I want to upload 2000 entities (opening new connection for each, I know it can be done