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

[fiware-askbot] MongoDB-Cygnus Persistence

    Details

      Description

      Created question in FIWARE Q/A platform on 10-12-2018 at 20:12
      Please, ANSWER this question AT https://ask.fiware.org/question/1051/mongodb-cygnus-persistence/

      Question:
      MongoDB-Cygnus Persistence

      Description:
      Using a sensor device (LWM2M) to receive context for historic persistence, all services run using docker-compose. I added Cygnus and set-up all docker-compose definitions. Checking up with Mongodb, device table not created, here the only db have:
      $mongo

      show dbs
      admin 0.000GB
      local 0.000GB
      lwm2miotagent 0.000GB
      orion-smartgondor 0.000GB
      sthsmartgondor 0.000GB
      use sthsmartgondor
      switched to db sthsmartgondor
      show collections
      sth/gardensraspiSensorTV:DeviceDevice.aggr

      I expect to see sth/gardensraspiSensorTV:Device_Device for device table, but not created.

      I am not sure if the IDAS agent is actually receiving data from device, or if received may not be forwarded to Orion. Can someone please help how I can achive my goal, below are the IDAS agent and Orion logs please:

      time=2018-12-07T11:56:58.136Z | lvl=DEBUG | corr=n/a | trans=n/a | op=LWM2MLib.COAPRouter | msg=Handling request with method [POST] on url [/rd/1] with messageId [42655]
      time=2018-12-07T11:56:58.137Z | lvl=DEBUG | corr=n/a | trans=n/a | op=LWM2MLib.UpdateRegistration | msg=Handling update registration request
      time=2018-12-07T11:56:58.137Z | lvl=DEBUG | corr=n/a | trans=n/a | op=LWM2MLib.COAPUtils | msg=Extracting query parameters from request
      time=2018-12-07T11:56:58.138Z | lvl=DEBUG | corr=n/a | trans=n/a | op=LWM2MLib.UpdateRegistration | msg=Updating device register with lifetime [undefined] and address [193.136.33.222].

      {"op":"IOTAgent.LWM2MHandlers","time":"2018-12-07T11:56:58.138Z","lvl":"DEBUG","msg":"Handling update registration of the device"}

      time=2018-12-07T11:56:58.140Z | lvl=DEBUG | corr=715bff5c-5c01-4295-9881-c32cdd193cad | trans=715bff5c-5c01-4295-9881-c32cdd193cad | op=IoTAgentNGSI.MongoDBGroupRegister | srv=n/a | subsrv=n/a | msg=Looking for group params ["resource","apikey"] with queryObj {} | comp=IoTAgent
      time=2018-12-07T11:56:58.145Z | lvl=DEBUG | corr=715bff5c-5c01-4295-9881-c32cdd193cad | trans=715bff5c-5c01-4295-9881-c32cdd193cad | op=IoTAgentNGSI.MongoDBGroupRegister | srv=n/a | subsrv=n/a | msg=Device group for fields [["resource","apikey"]] not found: [{}] | comp=IoTAgent
      time=2018-12-07T11:56:58.146Z | lvl=ERROR | corr=715bff5c-5c01-4295-9881-c32cdd193cad | trans=715bff5c-5c01-4295-9881-c32cdd193cad | op=IoTAgentNGSI.Alarms | srv=n/a | subsrv=n/a | msg=Raising [MONGO-ALARM]:

      {"name":"DEVICEGROUPNOT_FOUND","message":"Couldn\t find device group","code":404}

      | comp=IoTAgent
      time=2018-12-07T11:56:58.147Z | lvl=DEBUG | corr=715bff5c-5c01-4295-9881-c32cdd193cad | trans=715bff5c-5c01-4295-9881-c32cdd193cad | op=IoTAgentNGSI.MongoDBDeviceRegister | srv=n/a | subsrv=n/a | msg=Looking for device with id [raspiSensorTV]. | comp=IoTAgent
      time=2018-12-07T11:56:58.152Z | lvl=ERROR | corr=715bff5c-5c01-4295-9881-c32cdd193cad | trans=715bff5c-5c01-4295-9881-c32cdd193cad | op=IoTAgentNGSI.Alarms | srv=n/a | subsrv=n/a | msg=Releasing [MONGO-ALARM] | comp=IoTAgent

      {"op":"IOTAgent.LWM2MHandlers","time":"2018-12-07T11:56:58.153Z","lvl":"DEBUG","msg":"Preregistered device found."}

      time=2018-12-07T11:56:58.153Z | lvl=DEBUG | corr=n/a | trans=n/a | op=LWM2MLib.UpdateRegistration | msg=Update registration request ended successfully

      {"time":"2018-12-07T11:56:58.204Z","lvl":"DEBUG","msg":"Observers created successfully."}

      Looking like measures sent above, but nothing with mongodb. Also don'e understand the "DEVICEGROUPNOT_FOUND","message":"Couldn\t find device group","code":404} error. I would appreciate step-by-step process, please.

        Activity

        Hide
        backlogmanager Backlog Manager added a comment -

        2018-12-11 09:05|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2018-12-11 09:05|CREATED monitor | # answers= 0, accepted answer= False
        Show
        andres.munoza Andres Muñoz added a comment - answered at https://ask.fiware.org/question/1051/mongodb-cygnus-persistence/

          People

          • Assignee:
            andres.munoza Andres Muñoz
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: