Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-13796

[Fiware-tech-help] iot broker issu when conntcting to iot discovery

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None
    • HD-Enabler:
      IoT Broker

      Description

      when i send queryContext request that request is sent to iot discovery but the response is the following
      {"errorCode":

      {"code":404,"reasonPhrase":"CONTEXT ELEMENT NOT FOUND","details":"Discovery response: RECEIVER INTERNAL ERROR (details: Receiver response empty)"}

      ,"contextResponses":[]}when i checked iot discovery i found that iot broker appended "//ngsi9/DiscoverAvailabillity " to the url request to iot discovery ..i put in the config.default file in the uri of ngsi9 the ip of iot discovery http://130.206.177.25:8080/ ?
      that appears in ligs of iot broker////////////////////////////////////osgi> 2018-02-16 12:12:04 INFO RestProviderController:409 <-- NGSI-10 has received request for Context query resource --->2018-02-16 12:12:04 INFO RestProviderController:349 - Impossible to get the Json Request! Please check the error using debug mode.
      2018-02-16 12:12:04 WARN Southbound:819 - Response from remote server empty
      2018-02-16 12:12:04 INFO IotBrokerCore:749 - 0 query Services found////////////////////////////////and the same response when i queryContext
      and the query is
      curl http://130.206.121.137:8060/ngsi10/queryContext s -S --header 'Content-Type: application/json' --header 'Accept: application/json' -d @ <<EOF
      {
      "entities": [

      { "isPattern": false, "id": "sensor6"}

      ]
      }
      EOFand that in the file iotbroker.cofig.local#!/bin/bash
      iotbroker_dirconfig='/home/ubuntu/Aeron/fiwareRelease'
      iotbroker_bundlesconfigurationlocation='/home/ubuntu/Aeron/fiwareRelease/bundleC$
      iotbroker_hsqldbdirectory='//home//ubuntu//Aeron//SQL_database//database//linkDB'
      iotbroker_logfile='/home/ubuntu/Aeron/IoTBroker-runner/logs/iotbroker.log'
      iotbroker_ngsi9uri='http://130.206.121.87.8080'iot discovery hears that query in its logs and appear in that lot discovery logs "URL: http://130.206.121.22:8080//ngsi9/discoverContextAvailability" then what is the problem?
      __________________________________________________________________________________________

      You can get more information about our cookies and privacy policies on the following links:

      Fiware-tech-help mailing list
      Fiware-tech-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-tech-help

      [Created via e-mail received from: =?UTF-8?Q?=E2=80=ABmohamed_amin=E2=80=AC_=E2=80=AB?= <mohamed_amin10010027@yahoo.com>]

        Activity

        Hide
        fcirillo Flavio Cirillo added a comment -

        I suspect a bad behaviour at start up time of the OSGi enviroment.

        Try to follow from scratch the new instructions given here: https://github.com/Aeronbroker/NEConfMan#compilation-procedure

        and then run it following the configuration instructions here: https://github.com/Aeronbroker/NEConfMan#configure-the-nec-confman-with-setup-scripts

        Show
        fcirillo Flavio Cirillo added a comment - I suspect a bad behaviour at start up time of the OSGi enviroment. Try to follow from scratch the new instructions given here: https://github.com/Aeronbroker/NEConfMan#compilation-procedure and then run it following the configuration instructions here: https://github.com/Aeronbroker/NEConfMan#configure-the-nec-confman-with-setup-scripts
        Hide
        fcirillo Flavio Cirillo added a comment -

        Discussion went on and closed on github :https://github.com/Aeronbroker/Aeron/issues/19

        Show
        fcirillo Flavio Cirillo added a comment - Discussion went on and closed on github : https://github.com/Aeronbroker/Aeron/issues/19

          People

          • Assignee:
            fcirillo Flavio Cirillo
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: