[HELP-15498] [fiware-stackoverflow] IoTAgent unable to send notification to Orion CB - JIRA

Details

Type: Monitor
Status: Closed
Priority: Major
Resolution: Done
Affects Version/s: None
Fix Version/s: 2021
Component/s: FIWARE-TECH-HELP
Labels:
- fiware
- fiware-orion

Source URL:
https://stackoverflow.com/questions/54886967/iotagent-unable-to-send-notification-to-orion-cb
HD-Enabler:
IDAS

Description

Created question in FIWARE Q/A platform on 26-02-2019 at 14:02
Please, ANSWER this question AT https://stackoverflow.com/questions/54886967/iotagent-unable-to-send-notification-to-orion-cb

Question:
IoTAgent unable to send notification to Orion CB

Description:
I can confirm my LwM2M client is sending observation to the IoTAgent, I can also see the IoTAgent trying to forward observed measure to Orion CB, but failed with following log:

Below is what the Orion CB reports in its log:

{ listDatabases: 1 }

)
time=Tuesday 26 Feb 13:35:28 2019.447Z | lvl=INFO | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=connectionOperations.cpp[94]:collectionQuery | msg=Database Operation Successful (query: {})
time=Tuesday 26 Feb 13:35:28 2019.447Z | lvl=INFO | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=connectionOperations.cpp[94]:collectionQuery | msg=Database Operation Successful (query: {})
time=Tuesday 26 Feb 13:36:28 2019.450Z | lvl=INFO | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=connectionOperations.cpp[701]:runCollectionCommand | msg=Database Operation Successful (command:

{ listDatabases: 1 }

)

Any idea why this error, what is causing it?

Activity

Ascending order - Click to sort in descending order

Backlog Manager created issue - 26/Feb/19 3:06 PM

Hide

Permalink

Backlog Manager added a comment - 26/Feb/19 3:06 PM

2019-02-26 15:06|CREATED monitor | # answers= 0, accepted answer= False

Show

Backlog Manager added a comment - 26/Feb/19 3:06 PM 2019-02-26 15:06|CREATED monitor | # answers= 0, accepted answer= False

Backlog Manager made changes - 26/Feb/19 3:06 PM

Field	Original Value	New Value
Component/s		FIWARE-TECH-HELP [ 10278 ]

Backlog Manager made changes - 26/Feb/19 6:06 PM

Status

Open [ 1 ]

In Progress [ 3 ]

Hide

Permalink

Backlog Manager added a comment - 26/Feb/19 6:06 PM

2019-02-26 18:05|UPDATED status: transition Answer| # answers= 1, accepted answer= False

Show

Backlog Manager added a comment - 26/Feb/19 6:06 PM 2019-02-26 18:05|UPDATED status: transition Answer| # answers= 1, accepted answer= False

Backlog Manager made changes - 26/Feb/19 9:05 PM

Resolution		Done [ 10000 ]
Status	In Progress [ 3 ]	Closed [ 6 ]

Hide

Permalink

Backlog Manager added a comment - 26/Feb/19 9:06 PM

2019-02-26 21:05|UPDATED status: transition Finish| # answers= 1, accepted answer= True

Show

Backlog Manager added a comment - 26/Feb/19 9:06 PM 2019-02-26 21:05|UPDATED status: transition Finish| # answers= 1, accepted answer= True

Fernando Lopez made changes - 28/Feb/19 10:45 AM

Assignee

Backlog Manager [ backlogmanager ]

Fernando Lopez made changes - 28/Feb/19 10:46 AM

HD-Enabler		IDAS [ 10884 ]
Description	Created question in FIWARE Q/A platform on 26-02-2019 at 14:02 {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/54886967/iotagent-unable-to-send-notification-to-orion-cb +Question:+ IoTAgent unable to send notification to Orion CB +Description:+ I can confirm my LwM2M client is sending observation to the IoTAgent, I can also see the IoTAgent trying to forward observed measure to Orion CB, but failed with following log: time=2019-02-26T13:34:47.877Z \| lvl=DEBUG \| corr=n/a \| trans=n/a \| op=LWM2MLib.Registration \| msg=Registration request ended successfully time=2019-02-26T13:34:47.927Z \| lvl=DEBUG \| corr=n/a \| trans=n/a \| op=LWM2MLib.InformationReporting \| msg=Observing value from resource /3303/0/5700 in device [1] time=2019-02-26T13:34:47.947Z \| lvl=ERROR \| corr=519dbe74-0142-48b7-8290-444f86df5053 \| trans=519dbe74-0142-48b7-8290-444f86df5053 \| op=IoTAgentNGSI.DomainControl \| srv=n/a \| subsrv=n/a \| msg=Error: No matching format found \| comp=IoTAgent time=2019-02-26T13:34:47.948Z \| lvl=DEBUG \| corr=519dbe74-0142-48b7-8290-444f86df5053 \| trans=519dbe74-0142-48b7-8290-444f86df5053 \| op=IoTAgentNGSI.DomainControl \| srv=n/a \| subsrv=n/a \| msg=response-time: 79406 \| comp=IoTAgent time=2019-02-26T13:35:02.965Z \| lvl=FATAL \| corr=n/a \| trans=n/a \| op=IoTAgentNGSI.Global \| srv=n/a \| subsrv=n/a \| msg=An unexpected exception has been raised. Ignoring: Error: No matching format found \| comp=IoTAgent time=2019-02-26T13:35:17.981Z \| lvl=FATAL \| corr=n/a \| trans=n/a \| op=IoTAgentNGSI.Global \| srv=n/a \| subsrv=n/a \| msg=An unexpected exception has been raised. Ignoring: Error: No matching format found \| comp=IoTAgent time=2019-02-26T13:35:48.012Z \| lvl=FATAL \| corr=n/a \| trans=n/a \| op=IoTAgentNGSI.Global \| srv=n/a \| subsrv=n/a \| msg=An unexpected exception has been raised. Ignoring: Error: No matching format found \| comp=IoTAgent time=2019-02-26T13:36:03.030Z \| lvl=FATAL \| corr=n/a \| trans=n/a \| op=IoTAgentNGSI.Global \| srv=n/a \| subsrv=n/a \| msg=An unexpected exception has been raised. Ignoring: Error: No matching format found \| comp=IoTAgent time=2019-02-26T13:36:23.059Z \| lvl=FATAL \| corr=n/a \| trans=n/a \| op=IoTAgentNGSI.Global \| srv=n/a \| subsrv=n/a \| msg=An unexpected exception has been raised. Ignoring: Error: No matching format found \| comp=IoTAgent time=2019-02-26T13:36:53.086Z \| lvl=FATAL \| corr=n/a \| trans=n/a \| op=IoTAgentNGSI.Global \| srv=n/a \| subsrv=n/a \| msg=An unexpected exception has been raised. Ignoring: Error: No matching format found \| comp=IoTAgent Below is what the Orion CB reports in its log: time=Tuesday 26 Feb 13:34:47 2019.838Z \| lvl=INFO \| corr=48de7b18-39cb-11e9-8c5b-0242ac1b0006 \| trans=1551188006-596-00000000004 \| from=172.27.0.5 \| srv=smartgondor \| subsrv=/gardens \| comp=Orion \| op=logMsg.h[1916]:lmTransactionEnd \| msg=Transaction ended time=Tuesday 26 Feb 13:35:28 2019.446Z \| lvl=INFO \| corr=N/A \| trans=N/A \| from=N/A \| srv=N/A \| subsrv=N/A \| comp=Orion \| op=connectionOperations.cpp[701]:runCollectionCommand \| msg=Database Operation Successful (command: { listDatabases: 1 }) time=Tuesday 26 Feb 13:35:28 2019.447Z \| lvl=INFO \| corr=N/A \| trans=N/A \| from=N/A \| srv=N/A \| subsrv=N/A \| comp=Orion \| op=connectionOperations.cpp[94]:collectionQuery \| msg=Database Operation Successful (query: {}) time=Tuesday 26 Feb 13:35:28 2019.447Z \| lvl=INFO \| corr=N/A \| trans=N/A \| from=N/A \| srv=N/A \| subsrv=N/A \| comp=Orion \| op=connectionOperations.cpp[94]:collectionQuery \| msg=Database Operation Successful (query: {}) time=Tuesday 26 Feb 13:36:28 2019.450Z \| lvl=INFO \| corr=N/A \| trans=N/A \| from=N/A \| srv=N/A \| subsrv=N/A \| comp=Orion \| op=connectionOperations.cpp[701]:runCollectionCommand \| msg=Database Operation Successful (command: { listDatabases: 1 }) Any idea why this error, what is causing it?	Created question in FIWARE Q/A platform on 26-02-2019 at 14:02 {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/54886967/iotagent-unable-to-send-notification-to-orion-cb +Question:+ IoTAgent unable to send notification to Orion CB +Description:+ I can confirm my LwM2M client is sending observation to the IoTAgent, I can also see the IoTAgent trying to forward observed measure to Orion CB, but failed with following log: time=2019-02-26T13:34:47.877Z \| lvl=DEBUG \| corr=n/a \| trans=n/a \| op=LWM2MLib.Registration \| msg=Registration request ended successfully time=2019-02-26T13:34:47.927Z \| lvl=DEBUG \| corr=n/a \| trans=n/a \| op=LWM2MLib.InformationReporting \| msg=Observing value from resource /3303/0/5700 in device [1] time=2019-02-26T13:34:47.947Z \| lvl=ERROR \| corr=519dbe74-0142-48b7-8290-444f86df5053 \| trans=519dbe74-0142-48b7-8290-444f86df5053 \| op=IoTAgentNGSI.DomainControl \| srv=n/a \| subsrv=n/a \| msg=Error: No matching format found \| comp=IoTAgent time=2019-02-26T13:34:47.948Z \| lvl=DEBUG \| corr=519dbe74-0142-48b7-8290-444f86df5053 \| trans=519dbe74-0142-48b7-8290-444f86df5053 \| op=IoTAgentNGSI.DomainControl \| srv=n/a \| subsrv=n/a \| msg=response-time: 79406 \| comp=IoTAgent time=2019-02-26T13:35:02.965Z \| lvl=FATAL \| corr=n/a \| trans=n/a \| op=IoTAgentNGSI.Global \| srv=n/a \| subsrv=n/a \| msg=An unexpected exception has been raised. Ignoring: Error: No matching format found \| comp=IoTAgent time=2019-02-26T13:35:17.981Z \| lvl=FATAL \| corr=n/a \| trans=n/a \| op=IoTAgentNGSI.Global \| srv=n/a \| subsrv=n/a \| msg=An unexpected exception has been raised. Ignoring: Error: No matching format found \| comp=IoTAgent time=2019-02-26T13:35:48.012Z \| lvl=FATAL \| corr=n/a \| trans=n/a \| op=IoTAgentNGSI.Global \| srv=n/a \| subsrv=n/a \| msg=An unexpected exception has been raised. Ignoring: Error: No matching format found \| comp=IoTAgent time=2019-02-26T13:36:03.030Z \| lvl=FATAL \| corr=n/a \| trans=n/a \| op=IoTAgentNGSI.Global \| srv=n/a \| subsrv=n/a \| msg=An unexpected exception has been raised. Ignoring: Error: No matching format found \| comp=IoTAgent time=2019-02-26T13:36:23.059Z \| lvl=FATAL \| corr=n/a \| trans=n/a \| op=IoTAgentNGSI.Global \| srv=n/a \| subsrv=n/a \| msg=An unexpected exception has been raised. Ignoring: Error: No matching format found \| comp=IoTAgent time=2019-02-26T13:36:53.086Z \| lvl=FATAL \| corr=n/a \| trans=n/a \| op=IoTAgentNGSI.Global \| srv=n/a \| subsrv=n/a \| msg=An unexpected exception has been raised. Ignoring: Error: No matching format found \| comp=IoTAgent Below is what the Orion CB reports in its log: time=Tuesday 26 Feb 13:34:47 2019.838Z \| lvl=INFO \| corr=48de7b18-39cb-11e9-8c5b-0242ac1b0006 \| trans=1551188006-596-00000000004 \| from=172.27.0.5 \| srv=smartgondor \| subsrv=/gardens \| comp=Orion \| op=logMsg.h[1916]:lmTransactionEnd \| msg=Transaction ended time=Tuesday 26 Feb 13:35:28 2019.446Z \| lvl=INFO \| corr=N/A \| trans=N/A \| from=N/A \| srv=N/A \| subsrv=N/A \| comp=Orion \| op=connectionOperations.cpp[701]:runCollectionCommand \| msg=Database Operation Successful (command: { listDatabases: 1 }) time=Tuesday 26 Feb 13:35:28 2019.447Z \| lvl=INFO \| corr=N/A \| trans=N/A \| from=N/A \| srv=N/A \| subsrv=N/A \| comp=Orion \| op=connectionOperations.cpp[94]:collectionQuery \| msg=Database Operation Successful (query: {}) time=Tuesday 26 Feb 13:35:28 2019.447Z \| lvl=INFO \| corr=N/A \| trans=N/A \| from=N/A \| srv=N/A \| subsrv=N/A \| comp=Orion \| op=connectionOperations.cpp[94]:collectionQuery \| msg=Database Operation Successful (query: {}) time=Tuesday 26 Feb 13:36:28 2019.450Z \| lvl=INFO \| corr=N/A \| trans=N/A \| from=N/A \| srv=N/A \| subsrv=N/A \| comp=Orion \| op=connectionOperations.cpp[701]:runCollectionCommand \| msg=Database Operation Successful (command: { listDatabases: 1 }) Any idea why this error, what is causing it?

Fernando Lopez made changes - 27/May/21 10:54 AM

Fix Version/s

2021 [ 12600 ]

Transition

Time In Source Status

Execution Times

Last Executer

Last Execution Date

Open

In Progress

2h 59m

Backlog Manager

26/Feb/19 6:06 PM

In Progress

Closed

2h 59m

Backlog Manager

26/Feb/19 9:05 PM

People

Assignee:

Backlog Manager

Reporter:

Backlog Manager

Votes:

0 Vote for this issue

Watchers:

1 Start watching this issue

Dates

Created:

26/Feb/19 3:06 PM

Updated:

27/May/21 10:54 AM

Resolved:

26/Feb/19 9:05 PM

Agile

View on Board