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

[‫mohamed amin‬ ‫]

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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20180216/94f534fa/attachment.html>