Upload GeoTiff Error You can't execute queries until the end of the 'atomic' block

Question

Upload GeoTiff Error You can't execute queries until the end of the 'atomic' block

jeff-bradley opened this issue a year ago · 10 comments

Expected Behavior

Upload Geotiff file successfully

Actual Behavior

Error of "An error occurred in the current transaction. You can't execute queries until the end of the 'atomic' block.. Request: None"

Steps to Reproduce the Problem

Download and unzip wildlife areas https://sitewindright.s3.amazonaws.com/KeyWildlifeAreas_Solar_GT_20210907.zip
Upload Geotiff to geonode
Upload Fails

Specifications

GeoNode version: 4.1
Installation type (vanilla, geonode-project): Vanilla
Installation method (manual, docker): docker
Platform: Windows WSL Ubuntu 22
Additional details: ExecutionRequest

{
          "exec_id": "5e0c56a8-98c7-40ab-b9f6-915426202776",
          "status": "failed",
          "func_name": "rollback",
          "created": "2023-09-01T14:54:11.136364Z",
          "finished": "2023-09-01T14:54:15.553520Z",
          "last_updated": "2023-09-01T14:54:15.553538Z",
          "input_params": {
              "files": {
                  "tif_file": "/mnt/volumes/statics/uploaded/tmp8s7iro8f/KeyWildlifeAreas_Solar_GT_20210907.tif",
                  "base_file": "/mnt/volumes/statics/uploaded/tmp8s7iro8f/KeyWildlifeAreas_Solar_GT_20210907.tif"
              },
              "total_layers": 1,
              "store_spatial_file": true,
              "handler_module_path": "importer.handlers.geotiff.handler.GeoTiffFileHandler",
              "skip_existing_layers": false,
              "overwrite_existing_layer": false
          },
          "output_params": {
              "errors": [
                  "Task: importer.create_geonode_resource raised an error during actions for layer: import: An error occurred in the current transaction. You can't execute queries until the end of the 'atomic' block.. Request: None"
              ],
              "failed_layers": [
                  "import"
              ]
          },
          "step": "importer.rollback",
          "log": "An error occurred in the current transaction. You can't execute queries until the end of the 'atomic' block.. Request: None",
          "name": "KeyWildlifeAreas_Solar_GT_20210907.tif",
          "action": "import",
          "source": "upload",
          "user": 1000,
          "geonode_resource": null,
          "link": "http://localhost/api/v2/executionrequest/5e0c56a8-98c7-40ab-b9f6-915426202776"
      },

Answer 1 · 2023-09-01T15:30:08.000Z

Hi @jeff-bradley
Did you try with a different GeoTiff or always happen?
Just to understand if is something related to the GeoTiff or to the import flow

Answer 2 · 2023-09-01T15:58:01.000Z

Hello @mattiagiupponi
I was able to successfully load a very small test geotiff, but I received the error on both the wind and solar from these downloads
https://sitewindright.s3.amazonaws.com/KeyWildlifeAreas_Wind_GT_20211113.zip
https://sitewindright.s3.amazonaws.com/KeyWildlifeAreas_Solar_GT_20210907.zip

Answer 3 · 2023-09-01T16:24:47.000Z

Ok is not happening on all GeoTiff (which is a good point)
I try in local and looks like that the importer is extracting as CRS EPSG:5070 which is not one of the default accepted format.
@giohappy do you have any hints on this? how should we proceed?

Answer 4 · 2023-09-01T16:29:17.000Z

Thanks @mattiagiupponi I was able to load the GeoTiff after I transformed it to EPSG:3857

Answer 5 · 2023-09-01T17:26:21.000Z

Thanks @mattiagiupponi I was able to load the GeoTiff after I transformed it to EPSG:3857

Great news, I'll keep this open waiting an input from @giohappy. Then we can close the issue

Answer 6 · 2023-09-04T09:25:01.000Z

I've reopened and tranfered the issue inside the importer repo.

@mattiagiupponi in case of unsupported CRS a more informative error should be returned by the importer.
"An error occurred in the current transaction. You can't execute queries until the end of the 'atomic' block. Request: None" is very cryptic, to say the least :)

Answer 7 · 2023-09-04T12:08:40.000Z

May I ask if adding additional CRSs in Geoserver would also solve this problem? As described here: https://docs.geoserver.org/2.23.x/en/user/configuration/crshandling/customcrs.html

But I agree, that a better error message is key here ;)

Answer 8 · 2023-09-05T10:50:24.000Z

@jeff-bradley after some troubleshooting we found that the problem is with the CRS assigned to the Geotiff. It's not EPSG:5070 but ESRI:102039. Geoserver doesn't parese this CRS correctly (to be investigated why) but it creates the layer: Everything is fine if we reproject the original tiff to EPSG:5070.

We are going to open an issue for the importer to trigger a rollback if Geoserver fails at returning a valid CRS before pubslighing the dataset in GeoNode.

Answer 9 · 2023-09-11T14:37:28.000Z

I just merge a PR which will raise a clear error if the Srid is not recognied correctly.
At least should be more clear the issue instead of the "atomic block" exception

Answer 10 · 2023-09-26T09:27:46.000Z

This was resolved via #198