[Backlogmanager] [FIWARE-JIRA] (HELP-15811) [fiware-stackoverflow] Orion CB: Can' t Access Entities via /v2/entities endpoint

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-15811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez reassigned HELP-15811:
-------------------------------------

    Assignee: Álvaro Arranz

> [fiware-stackoverflow] Orion CB: Can't Access Entities via /v2/entities endpoint
> ------------------------------------------------------------------------------------
>
>                 Key: HELP-15811
>                 URL: https://jira.fiware.org/browse/HELP-15811
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Álvaro Arranz
>              Labels: fiware, fiware-orion, fiware-wirecloud
>
> Created question in FIWARE Q/A platform on 13-05-2019 at 13:05
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/56111033/orion-cb-cant-access-entities-via-v2-entities-endpoint
> +Question:+
> Orion CB: Can't Access Entities via /v2/entities endpoint
> +Description:+
> While creating a wirecloud wiring using NGSI Source operator, I encountered an error (helpless error) for couple of days, regarding connection to my instance of Orion CB. I can confirm all other NGSI operator settings entered are correct.
> Error creating subscription in the context broker server: Connection Error
> I however, suspect this error has to do with Orion NOT finding the entities to subscribe the NGSI Source operator. This is because I tried accessing Eindhoven's broker (http://212.159.228.70:1026/) and it works, NGSI Source  operator subscription created successfully.
> Equally, I get all entities/attributes in the Eindhoven's broker using:
> Akil$http http://212.159.228.70:1026/v2/entities
> HTTP/1.1 200 OK
> Connection: Keep-Alive
> Content-Length: 15501
> Content-Type: application/json
> Date: Mon, 13 May 2019 10:20:20 GMT
> Fiware-Correlator: b5e5294a-7568-11e9-83c8-0242ac120003
> [
>     {
>         "NO2": {
>             "metadata": {},
>             "type": "Number",
>             "value": 27.5
>         },
>         "Ozon": {
>             "metadata": {},
>             "type": "Number",
>             "value": 59.5
>         },
>         "PM1": {
>             "metadata": {},
>             "type": "Number",
>             "value": 8
>         },
>         "PM10": {
>             "metadata": {},
>             "type": "Number",
>             "value": 12
>         },
>    .
>    .
> }
> ]
> But then I cannot get the entities in my Orion instance using same scenario:
> Akil$ http 193.136.xx.xx:53154/v2/entities
> HTTP/1.1 200 OK
> Connection: Keep-Alive
> Content-Length: 2
> Content-Type: application/json
> Date: Mon, 13 May 2019 10:36:13 GMT
> Fiware-Correlator: ee22e4b2-756a-11e9-afa1-0242ac160007
> []
> Return empty list, whereas I have available 2 FIWARE services: environment and urbansense. The entities I want to access are available with the urbansense fiware-service having /basic fiware-servicepath.
> Service health:
> Akil$ http 193.136.xx.xx:53154/version
> HTTP/1.1 200 OK
> Connection: Keep-Alive
> Content-Length: 345
> Content-Type: application/json
> Date: Mon, 13 May 2019 10:50:13 GMT
> Fiware-Correlator: e32bf3da-756c-11e9-9371-0242ac160007
> {
>     "orion": {
>         "compile_time": "Tue Feb 12 10:51:10 UTC 2019",
>         "compiled_by": "root",
>         "compiled_in": "4f8128ac7b5b",
>         "doc": "https://fiware-orion.rtfd.io/",
>         "git_hash": "7ae8c69b97cd875236b952322a6bd503debbd13d",
>         "release_date": "Tue Feb 12 10:51:10 UTC 2019",
>         "uptime": "6 d, 18 h, 7 m, 6 s",
>         "version": "2.1.0-next"
>     }
> }
> Questions:
> Why can't I access my Orion instance same way I accessed Eindhoven's
> broker? 
> Is this the reason why my wiring for NGSI Source operator
> failed, thus reporting subscription error above?



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)