Details
-
Type: extRequest
-
Status: Closed
-
Priority: Blocker
-
Resolution: Done
-
Fix Version/s: Sprint 4.1.3
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
HD-Chapter:IoT
-
HD-Enabler:IDAS
Description
Hello,
i have downloaded the code from github and compiled the code for the mqtt IoTAgent.
After that i have build the RPM and installed the Base the UL2.0 and MQTT ones.
./ini_iotagent.sh: line 2: 4455 Segmentation fault (core dumped) /usr/local/iot/bin/iotagent -i 192.168.2.114 -p 80 -v DEBUG -d /usr/local/iot/lib -c /etc/iot/config.json
I have tested the mosquitto broker and it is working well with the mosquitto_sub/pub i can see that i receive the payload i send on local mqtt broker.
i am joining in attach the entire Log of the execution of the IoTAgent.
This is my ini_iotagent.sh :
export LD_LIBRARY_PATH=/usr/local/iot/lib /usr/local/iot/bin/iotagent -i 192.168.2.114 -p 80 -v DEBUG -d /usr/local/iot/lib -c /etc/iot/config.json
This is my config.json:
{ "resources": [ { "resource": "/iot/kuraResources", "options": { "ConfigFile": "/etc/iot/MqttService.xml", "FileName": "MqttService" } } ], "timezones": "/etc/iot/date_time_zonespec.csv", "storage": { "type": "mongodb", "dbname": "iot" }, "ngsi_url": { "cbroker": "http://192.168.2.118:1026", "updateContext": "/NGSI10/updateContext", "registerContext": "/NGSI9/registerContext", "queryContext": "/NGSI10/queryContext" }, "timeout": 11, "dir_log": "/var/log/" }
This is the service i create :
curl -X POST 'http://192.168.2.114/iot/services' \ -i \ -H "Content-Type: application/json" \ -H "Fiware-Service: kura" \ -H "Fiware-ServicePath: /kurapath" \ -d '{"services": [{"apikey": "egmkey", "entity_type": "enocean", "cbroker": "htpp://192.168.2.118:1026", "resource": "/iot/kuraResources" }]}'
Tell me if you need other info.
But please it has been more than 3 months now i try to get mqtt in IDAS to work, help me!
I am wiling to make a Skype call /screen share in order to understannnnnnnnnnnn whdat is going wrong. Even a phone call would be great!!
The segfault apears only when he tries to connect to the MQTT broker.
This is the Broker Log :