[Backlogmanager] [FIWARE-JIRA] (HELP-16722) [fiware-askbot] FIWARE QuantumLeap Sanity Check failed: QuantumLeap can't get changed data from Orion

Fernando Lopez (JIRA) jira-help-desk at jira.fiware.org
Tue May 19 11:06:00 CEST 2020


     [ https://jira.fiware.org/browse/HELP-16722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez resolved HELP-16722.
-----------------------------------
    Resolution: Done

> [fiware-askbot] FIWARE QuantumLeap Sanity Check failed: QuantumLeap can't get changed data from Orion
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HELP-16722
>                 URL: https://jira.fiware.org/browse/HELP-16722
>             Project: Help-Desk
>          Issue Type: Monitor
>            Reporter: Backlog Manager
>            Assignee: Backlog Manager
>              Labels: QuantumLeap, Subscription, orion
>
> Created question in FIWARE Q/A platform on 04-05-2020 at 15:05
> {color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/1141/fiware-quantumleap-sanity-check-failed-quantumleap-cant-get-changed-data-from-orion/
> +Question:+
> FIWARE QuantumLeap Sanity Check failed: QuantumLeap can't get changed data from Orion
> +Description:+
> I checked quantumLeap Sanity Check in both virtualMachine(virtualBox with Ubuntu) and production server(CentOS). With the same docker-compose.yml, the sanity check is sucessfully on virtualManchine, but failed on Production server, it's really strange, could anyone can help me? Thank you very much.
> The steps of sanity check is followed as https://quantumleap.readthedocs.io/en..., I pasted below.
> The difference of results is only at step 7. On virtualMachine, I can get the updated data from quantumLeap:
> {
>   "attrName": "precipitation",
>   "entityId": "air_quality_observer_be_001",
>   "index": [
>         "2020-05-03T11:18:14.000",
>         "2020-05-03T11:18:55.000"
>   ],
>   "values": [
>         0.0,
>         100.0
>   ]
> }
> But on production server, the result is:
> {
>   "description": "No records were found for such query.",
>   "error": "Not Found"
> }
> Note:
> These commands in the sanity check steps are copied to terminal, so there will be no typos.
> the difference of result is only at step 7. I deleted the old images on both virtualMachine and production server to let the latested images are pulled.
> There was a fiware-base system(orion,mongoDB,IoTAgents,quantumLeap,CrateDB,Grafana) runing on production server and everything was fine. But one week ago, the hard disk on the server was full and exhausted, and all containers are down. I cleaned some huge log files and free some space, then I bring up the fiware-base system and found that there is no data shown on Grafana. After checked, I found the reason is QuantumLeap did not store data into crateDB, but I'm not sure the root cause is orion or quantumLeap. So I decide to do the sanity check as the quantumLeap documents suggested. That's the story.
> BTW, the subscription of quantumLeap can be get from orion, but I can't get the changed data from quantumLeap. Why the newest changed data is not synchronized to quantumLeap?
> Sanity check steps:
> Check Orion version
> curl -X GET http://0.0.0.0:1026/version -H 'Accept: application/json'
> Check QuantumLeap version
> curl -X GET http://0.0.0.0:8668/version -H 'Accept: application/json'
> Create an Orion Subscription for "QuantumLeap"
> curl -X POST \
> 'http://0.0.0.0:8668/v2/subscribe?orionUrl=http://orion:1026/v2&quantumleapUrl=http://quantumleap:8668/v2&entityType=AirQualityObserved' \
> -H 'Accept: application/json'
> Check you cat get such subscription from Orion
> curl -X GET http://0.0.0.0:1026/v2/subscriptions \
> -H 'Accept: application/json'
> Insert an entity of AirQualityObserved into Orion
> curl -X POST \
> 'http://0.0.0.0:1026/v2/entities?options=keyValues' \
> -H 'Accept: application/json' \
> -H 'Content-Type: application/json' \
> -d '{
>     "id": "air_quality_observer_be_001",
>     "type": "AirQualityObserved",
>     "address": {
>         "streetAddress": "IJzerlaan",
>         "postOfficeBoxNumber": "18",
>         "addressLocality": "Antwerpen",
>         "addressCountry": "BE"
>     },
>     "dateObserved": "2017-11-03T12:37:23.734827",
>     "source": "http://testing.data.from.smartsdk",
>     "precipitation": 0,
>     "relativeHumidity": 0.54,
>     "temperature": 12.2,
>     "windDirection": 186,
>     "windSpeed": 0.64,
>     "airQualityLevel": "moderate",
>     "airQualityIndex": 65,
>     "reliability": 0.7,
>     "CO": 500,
>     "NO": 45,
>     "NO2": 69,
>     "NOx": 139,
>     "SO2": 11,
>     "CO_Level": "moderate",
>     "refPointOfInterest": "null"
> }'
> Update the precipitation value of the same entity in Orion.
> curl -X PATCH \
> http://0.0.0.0:1026/v2/entities ... (more)



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)


More information about the Backlogmanager mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy