Pedro D.'s profile - activity

overview network karma followed questions activity

2018-08-09 12:46:35 +0200	received badge	● Famous Question (source)
2018-07-10 14:32:27 +0200	received badge	● Enthusiast
2018-07-10 14:32:27 +0200	received badge	● Notable Question (source)
2018-07-09 19:08:31 +0200	commented answer	Strange Comet issues Hello Jason, thank you for your suggestion. I have corrected that issue as you can see here (https://github.com/PedroD/comet_demo/blob/master/demo_coordinator/src/main/kotlin/Main.kt#L86). However, when requested, Comet still returns an empty array in its HTTP responses.
2018-06-27 14:54:24 +0200	received badge	● Famous Question (source)
2018-06-15 20:39:58 +0200	commented answer	Strange Comet issues Hello Martel, I tried your suggestion but I am getting the exact same behaviour. Here you can take a look at the JSON of my Comet's subscription request using V1: https://github.com/PedroD/comet_demo/blob/master/demo_coordinator/src/main/kotlin/Main.kt#L86
2018-06-14 22:25:26 +0200	received badge	● Notable Question (source)
2018-06-11 18:36:36 +0200	commented answer	Strange Comet issues Thanks, I'll try that.
2018-06-11 18:35:50 +0200	commented answer	Strange Comet issues Yes, I tried that as well. But it is very strange because even then it gives the same errors. As you can see here I am already doing that in the example (https://github.com/PedroD/comet_demo/blob/master/demo_coordinator/src/main/kotlin/Main.kt#L103). May I be missing something fundamental to Comet?
2018-06-11 15:25:29 +0200	received badge	● Popular Question (source)
2018-06-11 10:33:10 +0200	received badge	● Popular Question (source)
2018-06-09 13:25:21 +0200	received badge	● Editor (source)
2018-06-09 13:22:59 +0200	asked a question	Strange Comet issues Dear Fiware, I am trying to connect STH Comet to Orion in order to aggregate some events. However I am having some errors: In order to reproduce this errors for you to analyze, I have created this small project that isolates Orion and STH Comet, and reproduces the error in the log messages: https://github.com/PedroD/comet_demo When you run it, you will find log messages. These log messages contain all commands that the coordinator app sends to Orion and STH Comet, so that you don't need to worry about the Kotlin project's source. In sum, the issues we are having are: 1) Comet is, for some reason, overflowing like this: `sth_1 \| time=2018-06-09T11:04:02.626Z \| lvl=WARN \| corr=n/a \| trans=n/a \| op=OPER_STH_DB_LOG \| from=n/a \| srv=n/a \| subsrv=n/a \| comp=STH \| msg=The size in bytes of the namespace for storing the aggregated data ("sth_sensei_service" plus "sth_/sensei,/sensei,/sensei,/sensei,/sensei,/sensei,/sensei,/sensei,/sensei,/sensei_PersonDetection_PersonDetection.aggr", 138 bytes) is bigger than 120 bytes` 2) Comet is for some reason, having issues persisting some data in mongo, despite that the coordinator only tries to register the entities once: `sth_1 \| time=2018-06-09T11:04:12.870Z \| lvl=ERROR \| corr=d78056a4-6bd4-11e8-97dd-0242ac120005 \| trans=745ad73e-ebd0-49a4-b843-261981c8f9b2 \| op=OPER_STH_POST \| from=n/a \| srv=sensei_service \| subsrv=/sensei \| comp=STH \| msg=Error when getting the raw data collection for storing:MongoError: a collection 'sth_sensei_service.sth_/sensei_PersonDetection_PersonDetection' already exists` 3) When asked for aggregations, using the url below, Comet returns empty values: URL: `http://sth:8666/STH/v1/contextEntities/type/PersonDetection/id/PersonDetection/attributes/positionX?aggrMethod=sum&aggrPeriod=second&dateFrom=2016-02-01T00:00:00.000Z&dateTo=2019-01-01T23:59:59.999Z` `demo_1 \| Requesting aggregation to Comet: demo_1 \| {"contextResponses":[{"contextElement":{"attributes":[{"name":"positionX","values":[]}],"id":"PersonDetection","isPattern":false,"type":"PersonDetection"},"statusCode":{"code":"200","reasonPhrase":"OK"}}]} demo_1 \| demo_1 \| Comet seems to be sending an empty "values" array. What is going on? demo_1 \|` What is going on? How can we solve these issues? Thanks!
2018-06-06 17:07:41 +0200	asked a question	Connecting Cepheus to Orion Dear Fiware Support Team, I am having the following issue: I want to connect Cepheus to Orion (Orion as a source of events), process some queries and return new events to Orion (this time as destination). Like depicted below: Diagram: https://imgur.com/a/CI43Qis I have tried to configure Cepheus towards this goal, with the following example configuration: { "host": "http://localhost:8080", "in": [ { "type": "PersonDetection", "id": "PersonDetection", "providers": [ { "url": "http://orion:1026", "serviceName": "==SERVICE_NAME==", "servicePath": "==SERVICE_PATH==" } ], "attributes": [ { "name": "tagId", "type": "Integer" }, { "name": "sectorId", "type": "Integer" }, { "name": "positionX", "type": "Float" }, { "name": "positionY", "type": "Float" }, { "name": "ts", "type": "Timestamp" } ] } ], "out": [ { "id": "CellDetection", "type": "CellDetection", "attributes": [ { "name": "cellId", "type": "Integer" }, { "name": "tagId", "type": "Integer" }, { "name": "ts", "type": "Timestamp" } ] } ], "brokers": [ { "url": "http://orion:1026", "serviceName": "==SERVICE_NAME==", "servicePath": "==SERVICE_PATH==" } ], "statements": [ ] } With this configuration I want Cepheus to receive "PersonDetection" events (then run some query) and emit "CellDetection" events. However when Orion emits "PersonDetection" events, I see no logs in the Cepheus console. Which probably means that he's not receiving any events, maybe because he did not subscribe to Orion properly. The only logs generated by Cepheus are the following: epheus_1 \| /usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.cepheus_1 \| 'Supervisord is running as root and it is searching ' cepheus_1 \| 2018-06-05 18:19:12,362 CRIT Supervisor running as root (no user in config file)cepheus_1 \| 2018-06-05 18:19:12,362 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsingcepheus_1 \| 2018-06-05 18:19:12,378 INFO RPC interface 'supervisor' initialized cepheus_1 \| 2018-06-05 18:19:12,378 CRIT Server 'unix_http_server' running without any HTTP authentication checking cepheus_1 \| 2018-06-05 18:19:12,378 INFO supervisord started with pid 1 cepheus_1 \| 2018-06-05 18:19:13,381 INFO spawned: 'broker' with pid 9 cepheus_1 \| 2018-06-05 18:19:13,384 INFO spawned: 'cep' with pid 10 cepheus_1 \| 2018-06-05 18:19:14,387 INFO success: broker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) cepheus_1 \| 2018-06-05 18:19:14,387 INFO success: cep entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) cepheus_1 \| 2018-06-05 18:19:17.026 INFO 9 --- [ main] com.orange.cepheus.broker.Application : Starting Application on e62b33e4a5c1 with PID 9 (/opt/cepheus/cepheus-broker .jar started by root in /opt/cepheus) cepheus_1 \| 2018-06-05 18:19:17.162 INFO 10 --- [ main] com.orange.cepheus.cep.Application : Starting Application on e62b33e4a5c1 with PID 10 (/opt/cepheus/cepheus-cep. jar started by root in /opt/cepheus) cepheus_1 \| 2018-06-05 18:19:37.016 INFO 9 --- [ main] com.orange.cepheus.broker.Application : Started Application in 20.785 seconds (JVM running for 23.597) cepheus_1 \| 2018-06-05 18:19:37.639 INFO 10 --- [ main] com.orange.cepheus.cep.Application : Started Application in 21.395 seconds (JVM running for 24.211) cepheus_1 \| 2018-06-05 18:20 ... (more)