--我在virtualMachine(使用Ubuntu的virtualBox)和生产服务器(CentOS)中检查了quantumLeap是否正常。使用同样的docker-compose.yml,在virtualManchine上的健全检查是成功的,但是在生产服务器上失败了,这真的很奇怪,有人能帮我吗?非常感谢。@Jason
按照https://quantumleap.readthedocs.io/en/latest/admin/check/的步骤检查是否正常,我贴在下面。
结果的差别仅在步骤7。On virtualMachine,我可以从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
]
}
但是在生产服务器上,结果是:
{
"description": "No records were found for such query.",
"error": "Not Found"
}
注:
在正常检查步骤中的这些命令被复制到终端,因此不会有打印。pulled.
同步?
检查步骤:
1.查看Orion版本
curl -X GET http://0.0.0.0:1026/version -H 'Accept: application/json'
2.检查QuantumLeap版本
curl -X GET http://0.0.0.0:8668/version -H 'Accept: application/json'
3.为"QuantumLeap“创建Orion订阅
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'
4.检查你的猫从猎户座获得这样的订阅
curl -X GET http://0.0.0.0:1026/v2/subscriptions \
-H 'Accept: application/json'
5.在猎户座插入一个AirQualityObserved实体
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"
}'
6.更新同一实体在猎户座的降水量。
curl -X PATCH \
http://0.0.0.0:1026/v2/entities/air_quality_observer_be_001/attrs \
-H 'Accept: application/json' \
-H 'Content-Type: application/json' \
-d '{
"precipitation": {
"value": 100,
"type": "Number"
}
}'
7.从quantumLeap查询同一实体的降水变化记录。
curl -X GET \
'http://0.0.0.0:8668/v2/entities/air_quality_observer_be_001/attrs/precipitation?type=AirQualityObserved' \
-H 'Accept: application/json'
码头的部件-Compose.yml:
orion:
image: fiware/orion
hostname: orion
container_name: fiware-orion
depends_on:
- mongo-db
expose:
- "1026"
ports:
- "1026:1026"
networks:
- default
command: -dbhost mongo-db -logLevel ERROR -corsOrigin __ALL
mongo-db:
image: mongo:3.6
hostname: mongo-db
container_name: db-mongo
expose:
- "27017"
ports:
- "27017:27017"
networks:
- default
command: --bind_ip_all --smallfiles
volumes:
- mongo-db:/data
cratedb:
image: crate:3.1.2
hostname: cratedb
container_name: db-crate
expose:
- "4200"
- "4300"
- "5432"
ports:
- "4200:4200"
- "4300:4300"
- "5432:5432"
networks:
- default
command: -Ccluster.name=democluster -Chttp.cors.enabled=true -Chttp.cors.allow-origin="*"
volumes:
- crate-db:/data
quantumleap:
image: smartsdk/quantumleap
hostname: quantumleap
container_name: fiware-quantumleap
expose:
- "8668"
ports:
- "8668:8668"
depends_on:
- cratedb
environment:
- CRATE_HOST=cratedb # host name of CrateDB
没有解决,但有一点线索。。
我从quantumLeap那里得到了一些日志。quantumLeap中有一个机箱客户端,而的原因可能是quantumLeap中的机箱客户端工作不正常。
I将日志粘贴在这里:
crate.client.exceptions.ProgrammingError: SQLActionException[ClusterBlockException: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];]
172.18.1.1 - - [04/May/2020 17:00:33] "POST /v2/notify HTTP/1.1" 500 -
INFO:werkzeug:172.18.1.1 - - [04/May/2020 17:00:33] "POST /v2/notify HTTP/1.1" 500 -
INFO:translators.factory:Backend selected for tenant 'iothouse' is: crate
ERROR:app:Exception on /v2/notify [POST]
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 2446, in wsgi_app
response = self.full_dispatch_request()
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1951, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1820, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/usr/local/lib/python3.6/site-packages/flask/_compat.py", line 39, in reraise
raise value
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1949, in full_dispatch_request
rv = self.dispatch_request()
File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1935, in dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
File "/usr/local/lib/python3.6/site-packages/connexion/decorators/decorator.py", line 48, in wrapper
response = function(request)
File "/usr/local/lib/python3.6/site-packages/connexion/decorators/uri_parsing.py", line 143, in wrapper
response = function(request)
File "/usr/local/lib/python3.6/site-packages/connexion/decorators/validation.py", line 172, in wrapper
response = function(request)
File "/usr/local/lib/python3.6/site-packages/connexion/decorators/validation.py", line 347, in wrapper
return function(request)
File "/usr/local/lib/python3.6/site-packages/connexion/decorators/parameter.py", line 126, in wrapper
return function(**kwargs)
File "/src/ngsi-timeseries-api/src/reporter/reporter.py", line 189, in notify
trans.insert(payload, fiware_s, fiware_sp)
File "/src/ngsi-timeseries-api/src/translators/crate.py", line 189, in insert
fiware_servicepath)
File "/src/ngsi-timeseries-api/src/translators/crate.py", line 297, in _insert_entities_of_type
self.cursor.executemany(stmt, entries)
File "/usr/local/lib/python3.6/site-packages/crate/client/cursor.py", line 67, in executemany
self.execute(sql, bulk_parameters=seq_of_parameters)
File "/usr/local/lib/python3.6/site-packages/crate/client/cursor.py", line 54, in execute
bulk_parameters)
File "/usr/local/lib/python3.6/site-packages/crate/client/http.py", line 328, in sql
content = self._json_request('POST', self.path, data=data)
File "/usr/local/lib/python3.6/site-packages/crate/client/http.py", line 448, in _json_request
_raise_for_status(response)
File "/usr/local/lib/python3.6/site-packages/crate/client/http.py", line 187, in _raise_for_status
error_trace=error_trace)
发布于 2020-05-05 11:42:08
解决了。根本原因是在crateDB。当硬盘解锁时,crateDB就会关闭,每个表都会被设置为只读。即使磁盘空间被释放并且阈值被低估,只读块也不会自动从表中删除。
在crateDB中使用以下命令将readonly标志设置为false后,一切都正常:
SHOW CREATE TABLE <tableName>;
ALTER TABLE <tableName> SET ("blocks.read_only_allow_delete" = FALSE);
https://stackoverflow.com/questions/61575239
复制相似问题