# Crate node checks fail causing errors from QuantumLeap **URL:** \ **Category:** CrateDB\ **Created:** [March 15, 2019, 1:24pm UTC](https://community.cratedb.com/t/crate-node-checks-fail-causing-errors-from-quantumleap/175 "2019-03-15T13:24:41Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![maria](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/maria/32/87_2.png) [@maria](https://community.cratedb.com/u/maria)\ **Post date:** [March 15, 2019, 1:24pm UTC](https://community.cratedb.com/t/crate-node-checks-fail-causing-errors-from-quantumleap/175/1 "2019-03-15T13:24:41Z")
Hello, I want to start experimenting with Fiware QuantumLeap using Crate so I followed the steps in this tutorial [https://quantumleap.readthedocs.io/en/latest/admin/](https://quantumleap.readthedocs.io/en/latest/admin/) to get all the components up and running using docker. Then I followed the steps in this documentation [https://quantumleap.readthedocs.io/en/latest/user/](https://quantumleap.readthedocs.io/en/latest/user/) to store the entity’s values in Crate but I receive the following errors from QuantumLeap when I am trying to update the entity. `quantumleap_1 | INFO:reporter.reporter:Received payload: {'id': 'Room2', 'type': 'Room', 'temperature': {'type': 'Number', 'value': 29.2, 'metadata': {'dateCreated': {'type': 'DateTime', 'value': '2019-03-15T13:00:54.00Z'}, 'dateModified': {'type': 'DateTime', 'value': '2019-03-15T13:19:02.00Z'}}}} quantumleap_1 | INFO:geocoding.geocoding:Cannot add location to entity (type: "Room", id: "Room2"), missing "address" attribute. quantumleap_1 | [2019-03-15 13:19:02,483] ERROR in app: Exception on /v2/notify [POST] quantumleap_1 | Traceback (most recent call last): quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1982, in wsgi_app quantumleap_1 | response = self.full_dispatch_request() quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1614, in full_dispatch_request quantumleap_1 | rv = self.handle_user_exception(e) quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1517, in handle_user_exception quantumleap_1 | reraise(exc_type, exc_value, tb) quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/flask/_compat.py", line 33, in reraise quantumleap_1 | raise value quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1612, in full_dispatch_request quantumleap_1 | rv = self.dispatch_request() quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/flask/app.py", line 1598, in dispatch_request quantumleap_1 | return self.view_functions[rule.endpoint](**req.view_args) quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/connexion/decorators/decorator.py", line 73, in wrapper quantumleap_1 | response = function(request) quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/connexion/decorators/uri_parsing.py", line 117, in wrapper quantumleap_1 | response = function(request) quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/connexion/decorators/validation.py", line 163, in wrapper quantumleap_1 | response = function(request) quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/connexion/decorators/validation.py", line 336, in wrapper quantumleap_1 | return function(request) quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/connexion/decorators/decorator.py", line 44, in wrapper quantumleap_1 | response = function(request) quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/connexion/decorators/parameter.py", line 207, in wrapper quantumleap_1 | return function(**kwargs) quantumleap_1 | File "/src/ngsi-timeseries-api/src/reporter/reporter.py", line 185, in notify quantumleap_1 | trans.insert([payload], fiware_s, fiware_sp) quantumleap_1 | File "/src/ngsi-timeseries-api/src/translators/crate.py", line 183, in insert quantumleap_1 | fiware_servicepath) quantumleap_1 | File "/src/ngsi-timeseries-api/src/translators/crate.py", line 281, in _insert_entities_of_type quantumleap_1 | self.cursor.executemany(stmt, entries) quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/crate/client/cursor.py", line 67, in executemany quantumleap_1 | self.execute(sql, bulk_parameters=seq_of_parameters) quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/crate/client/cursor.py", line 54, in execute quantumleap_1 | bulk_parameters) quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/crate/client/http.py", line 328, in sql quantumleap_1 | content = self._json_request('POST', self.path, data=data) quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/crate/client/http.py", line 448, in _json_request quantumleap_1 | _raise_for_status(response) quantumleap_1 | File "/usr/local/lib/python3.6/site-packages/crate/client/http.py", line 187, in _raise_for_status quantumleap_1 | error_trace=error_trace) quantumleap_1 | crate.client.exceptions.ProgrammingError: SQLActionException[ClusterBlockException: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];]` Which I believe is caused by Crate since I receive the following errors on the Crate Admin UI. ![Screenshot%20from%202019-03-15%2015-12-03](https://us1.discourse-cdn.com/flex020/uploads/crate/original/1X/df47738c992356e89628648aacb83e08687d3cc7.png) I am working on: - Ubuntu 16.04 LTS - Docker version 18.09.3, build 774a1f4 - docker-compose version 1.23.2, build 1110ad01 Am I missing any configurations and I receive these errors? Thank you. ---
**Author:** ![Abduu](https://avatars.discourse-cdn.com/v4/letter/a/43a26b/32.png) [@Abduu](https://community.cratedb.com/u/Abduu)\ **Post date:** [June 5, 2019, 10:25am UTC](https://community.cratedb.com/t/crate-node-checks-fail-causing-errors-from-quantumleap/175/2 "2019-06-05T10:25:09Z")
Hello, I’m facing the same issue and still havent figured out a solution,I have freed space from my disk and excuted the command ` ALTER TABLE ettemphumid SET ("blocks.read_only_allow_delete" = FALSE);` as mentioned in the documentation of the cratedb. I’d really appreciate it if someone can help. > Defines the threshold on which CrateDB enforces a read-only block on every index that has at least one shard allocated on a node with at least one disk exceeding the flood stage. Note, that the read-only blocks are not automatically removed from the indices if the disk space is freed and the threshold is undershot. To remove the block, execute `ALTER TABLE ... SET ("blocks.read_only_allow_delete" = FALSE)` for affected tables (see [blocks.read\_only\_allow\_delete](https://crate.io/docs/crate/reference/en/latest/sql/statements/create-table.html#table-settings-blocks-read-only-allow-delete)).