[ https://jira.fiware.org/browse/HELP-15143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=112931#comment-112931 ] Jason Fox commented on HELP-15143: ---------------------------------- Answered on StackOverflow, no further responses. Closing > [fiware-stackoverflow] Client - Agent Information Reporting Error: "DEVICE_GROUP_NOT_FOUND" > ----------------------------------------------------------------------------------------------------- > > Key: HELP-15143 > URL: https://jira.fiware.org/browse/HELP-15143 > Project: Help-Desk > Issue Type: Monitor > Components: FIWARE-TECH-HELP > Reporter: Backlog Manager > Assignee: Jason Fox > Labels: fiware, mongodb > > Created question in FIWARE Q/A platform on 11-12-2018 at 02:12 > {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/53715995/client-agent-information-reporting-error-device-group-not-found > +Question:+ > Client - Agent Information Reporting Error: "DEVICE_GROUP_NOT_FOUND" > +Description:+ > It appears that IoT-Agent isn't receiving measures, Agent's log says device group not found [MONGO-ALARM]. Does anyone understand what this error means or how to fix it? > Agent's log: > time=2018-12-10T16:48:24.824Z | lvl=DEBUG | corr=n/a | trans=n/a | op=LWM2MLib.COAPRouter | msg=Handling request with method [POST] on url [/rd/1] with messageId [24748] > time=2018-12-10T16:48:24.826Z | lvl=DEBUG | corr=n/a | trans=n/a | op=LWM2MLib.UpdateRegistration | msg=Handling update registration request > time=2018-12-10T16:48:24.826Z | lvl=DEBUG | corr=n/a | trans=n/a | op=LWM2MLib.COAPUtils | msg=Extracting query parameters from request > time=2018-12-10T16:48:24.827Z | 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-10T16:48:24.827Z","lvl":"DEBUG","msg":"Handling update registration of the device"} > time=2018-12-10T16:48:24.829Z | lvl=DEBUG | corr=54b6621d-65fd-43db-ac9b-fade34e4d947 | trans=54b6621d-65fd-43db-ac9b-fade34e4d947 | op=IoTAgentNGSI.MongoDBGroupRegister | srv=n/a | subsrv=n/a | msg=Looking for group params ["resource","apikey"] with queryObj {} | comp=IoTAgent > time=2018-12-10T16:48:24.835Z | lvl=DEBUG | corr=54b6621d-65fd-43db-ac9b-fade34e4d947 | trans=54b6621d-65fd-43db-ac9b-fade34e4d947 | op=IoTAgentNGSI.MongoDBGroupRegister | srv=n/a | subsrv=n/a | msg=Device group for fields [["resource","apikey"]] not found: [{}] | comp=IoTAgent > **time=2018-12-10T16:48:24.836Z | lvl=ERROR | corr=54b6621d-65fd-43db-ac9b-fade34e4d947 | trans=54b6621d-65fd-43db-ac9b-fade34e4d947 | op=IoTAgentNGSI.Alarms | srv=n/a | subsrv=n/a | msg=Raising [MONGO-ALARM]: {"name":"DEVICE_GROUP_NOT_FOUND","message":"Couldn\t find device group","code":404} | comp=IoTAgent** > time=2018-12-10T16:48:24.836Z | lvl=DEBUG | corr=54b6621d-65fd-43db-ac9b-fade34e4d947 | trans=54b6621d-65fd-43db-ac9b-fade34e4d947 | op=IoTAgentNGSI.MongoDBDeviceRegister | srv=n/a | subsrv=n/a | msg=Looking for device with id [raspiSensorTV]. | comp=IoTAgent > time=2018-12-10T16:48:24.843Z | lvl=ERROR | corr=54b6621d-65fd-43db-ac9b-fade34e4d947 | trans=54b6621d-65fd-43db-ac9b-fade34e4d947 | op=IoTAgentNGSI.Alarms | srv=n/a | subsrv=n/a | msg=Releasing [MONGO-ALARM] | comp=IoTAgent > {"op":"IOTAgent.LWM2MHandlers","time":"2018-12-10T16:48:24.843Z","lvl":"DEBUG","msg":"Preregistered device found."} > time=2018-12-10T16:48:24.844Z | lvl=DEBUG | corr=n/a | trans=n/a | op=LWM2MLib.UpdateRegistration | msg=Update registration request ended successfully > {"time":"2018-12-10T16:48:24.894Z","lvl":"DEBUG","msg":"Observers created successfully."} > The log above appears everytime the device signals to have sent a measure, but my query for provisioned devices returns empty list: > curl -X GET \ > 'http://localhost:4041/iot/devices' \ > -H 'fiware-service: smartGondor' \ > -H 'fiware-servicepath: /gardens' > {"count":0,"devices":[]} > Any idea please? -- This message was sent by Atlassian JIRA (v6.4.1#64016)
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy