Access denied when using webODM 1.9.2 native

WebODM
#1

I’m getting an access denied error during the meshing stage using webODM native windows install 1.9.2. This is with a very small test data set that I did run successfully on 1.9.0, though I’m not sure if that was the reason. If I run the dem2mesh in command line it also throws an access denied error. Any thoughts?

This is the output from where the error occurs:
[INFO] Creating mesh from DSM: C:\WebODM\resources\app\apps\NodeODM\data\ff4f99e5-e83f-4f98-b6ec-0affd777c5f7\odm_meshing\tmp\mesh_dsm.tif
[INFO] running “C:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\dem2mesh” -inputFile “C:\WebODM\resources\app\apps\NodeODM\data\ff4f99e5-e83f-4f98-b6ec-0affd777c5f7\odm_meshing\tmp\mesh_dsm.tif” -outputFile “C:\WebODM\resources\app\apps\NodeODM\data\ff4f99e5-e83f-4f98-b6ec-0affd777c5f7\odm_meshing\odm_25dmesh.dirty.ply” -maxTileLength 2000 -maxVertexCount 200000 -maxConcurrency 8 -verbose
Access is denied.
[WARNING] dem2mesh failed, retrying with lower concurrency (4) in case this is a memory issue
[INFO] running “C:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\dem2mesh” -inputFile “C:\WebODM\resources\app\apps\NodeODM\data\ff4f99e5-e83f-4f98-b6ec-0affd777c5f7\odm_meshing\tmp\mesh_dsm.tif” -outputFile “C:\WebODM\resources\app\apps\NodeODM\data\ff4f99e5-e83f-4f98-b6ec-0affd777c5f7\odm_meshing\odm_25dmesh.dirty.ply” -maxTileLength 2000 -maxVertexCount 200000 -maxConcurrency 4 -verbose
Access is denied.
[WARNING] dem2mesh failed, retrying with lower concurrency (2) in case this is a memory issue
[INFO] running “C:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\dem2mesh” -inputFile “C:\WebODM\resources\app\apps\NodeODM\data\ff4f99e5-e83f-4f98-b6ec-0affd777c5f7\odm_meshing\tmp\mesh_dsm.tif” -outputFile “C:\WebODM\resources\app\apps\NodeODM\data\ff4f99e5-e83f-4f98-b6ec-0affd777c5f7\odm_meshing\odm_25dmesh.dirty.ply” -maxTileLength 2000 -maxVertexCount 200000 -maxConcurrency 2 -verbose
Access is denied.
[WARNING] dem2mesh failed, retrying with lower concurrency (1) in case this is a memory issue
[INFO] running “C:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\dem2mesh” -inputFile “C:\WebODM\resources\app\apps\NodeODM\data\ff4f99e5-e83f-4f98-b6ec-0affd777c5f7\odm_meshing\tmp\mesh_dsm.tif” -outputFile “C:\WebODM\resources\app\apps\NodeODM\data\ff4f99e5-e83f-4f98-b6ec-0affd777c5f7\odm_meshing\odm_25dmesh.dirty.ply” -maxTileLength 2000 -maxVertexCount 200000 -maxConcurrency 1 -verbose
Access is denied.

===== Dumping Info for Geeks (developers need this to fix bugs) =====
Child returned 1
Traceback (most recent call last):
File “C:\WebODM\resources\app\apps\ODM\stages\odm_app.py”, line 89, in execute
self.first_stage.run()
File “C:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 340, in run
self.next_stage.run(outputs)
File “C:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 340, in run
self.next_stage.run(outputs)
File “C:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 340, in run
self.next_stage.run(outputs)
[Previous line repeated 3 more times]
File “C:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 321, in run
self.process(self.args, outputs)
File “C:\WebODM\resources\app\apps\ODM\stages\odm_meshing.py”, line 66, in process
mesh.create_25dmesh(tree.filtered_point_cloud, tree.odm_25dmesh,
File “C:\WebODM\resources\app\apps\ODM\opendm\mesh.py”, line 40, in create_25dmesh
mesh = dem_to_mesh_gridded(os.path.join(tmp_directory, ‘mesh_dsm.tif’), outMesh, maxVertexCount, verbose, maxConcurrency=max(1, available_cores))
File “C:\WebODM\resources\app\apps\ODM\opendm\mesh.py”, line 115, in dem_to_mesh_gridded
raise e
File “C:\WebODM\resources\app\apps\ODM\opendm\mesh.py”, line 103, in dem_to_mesh_gridded
system.run(’"{bin}" -inputFile “{infile}” ’
File “C:\WebODM\resources\app\apps\ODM\opendm\system.py”, line 106, in run
raise SubprocessException(“Child returned {}”.format(retcode), retcode)
opendm.system.SubprocessException: Child returned 1

===== Done, human-readable information to follow… =====

1 Like
#2

Can you please provide system specs, processing parameters, and link to the data) dronedb.app or otherwise)?

#3

I’m using a 2021 Dell XPS 13 i7 11th gen with 16gb ram. The error happens regardless of the parameters chosen. I’m using a very small data set of just 9 images. It’s my test dataset. I’ve processed it many times across many platforms, including webodm running on our linux server and webodm windows native 1.9.0 and there are no issues there. Something else is going on, I just can’t figure out what. I haven’t tried downgrading webodm to 1.9.0, but I’ll try that too. Here’s a link to the data: https://we.tl/t-BSKGT0xVWj

1 Like
#4

Okay uninstalling, rebooting and installing 1.9.0 didn’t work either. Uninstalled a second time, reinstalled 1.9.2 and ran a different dataset with different settings. This time I got the access denied here:
Working on atlas 37 100%… done.
Finalizing texture atlases… done. (Took: 0s)
Building objmodel:
Saving model… done.
Whole texturing procedure took: 226.601s
[INFO] Writing MVS Textured file in: C:\WebODM\resources\app\apps\NodeODM\data\3231ebde-c831-4d5f-943f-dc73d1683dee\odm_texturing_25d\odm_textured_model_geo.obj
[INFO] running “C:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\texrecon” “C:\WebODM\resources\app\apps\NodeODM\data\3231ebde-c831-4d5f-943f-dc73d1683dee\opensfm\undistorted/reconstruction.nvm” “C:\WebODM\resources\app\apps\NodeODM\data\3231ebde-c831-4d5f-943f-dc73d1683dee\odm_meshing\odm_25dmesh.ply” “C:\WebODM\resources\app\apps\NodeODM\data\3231ebde-c831-4d5f-943f-dc73d1683dee\odm_texturing_25d\odm_textured_model_geo” -d gmi -o gauss_clamping -t none --no_intermediate_results --nadir_mode
Access is denied.

===== Dumping Info for Geeks (developers need this to fix bugs) =====
Child returned 1
Traceback (most recent call last):
File “C:\WebODM\resources\app\apps\ODM\stages\odm_app.py”, line 89, in execute
self.first_stage.run()
File “C:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 340, in run
self.next_stage.run(outputs)
File “C:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 340, in run
self.next_stage.run(outputs)
File “C:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 340, in run
self.next_stage.run(outputs)
[Previous line repeated 4 more times]
File “C:\WebODM\resources\app\apps\ODM\opendm\types.py”, line 321, in run
self.process(self.args, outputs)
File “C:\WebODM\resources\app\apps\ODM\stages\mvstex.py”, line 108, in process
system.run(’"{bin}" “{nvm_file}” “{model}” “{out_dir}” ’
File “C:\WebODM\resources\app\apps\ODM\opendm\system.py”, line 106, in run
raise SubprocessException(“Child returned {}”.format(retcode), retcode)
opendm.system.SubprocessException: Child returned 1

===== Done, human-readable information to follow… =====

[ERROR] Uh oh! Processing stopped because of strange values in the reconstruction. This is often a sign that the input data has some issues or the software cannot deal with it. Have you followed best practices for data acquisition? See https://docs.opendronemap.org/flying.html
100 - done.

I’m wondering if it’s got something to do with windows security or folder permissions or something like that?

1 Like
#5

Could be. I’ve not hit this issue yet. Do you use an antivirus software other than Windows Defender?

I’ll try to reproduce when I’m back at my windows desktop.

#6

I think I found the problem, it’s our office security policy. I saw this in the Windows Defender protection history:

image
image859×835 23.9 KB

Total pain, but at lease I know what I’m up against now. I’ll have to talk to our tech team to whitelist webodm.

1 Like
#7

Thanks for confirming! Odd they blocked it… Wonder if they heuristic’d on the RAM/CPU/disk usage of it…

#8

I’ll try find out. It did work for the first 24 hours, so it’s possible they detected the CPU usage.

Anyway, I excluded the folder and the dataset processed perfectly.

I must say, I was always a big fan of ODM. I did a presentation on it to the UN Open GIS group a couple of months back, and Stephen Mathers was there. At the end he asked me for my wishlist, and my biggest ask was a double click native install on windows. I said it as a joke because I knew how hard it was, but here it is…

Don’t know if it was always on the cards or if Stephen listened to my request, but I was blown away when I came across the blog post yesterday. It’s really outstanding work, well done to you and the whole team!

I also asked for an export to kmz, we use it a lot in emergencies. I see it’s there now too! At the moment webODM can’t save the kmz directly, but I can find it in the data directory, so I’m sure it won’t take long to get added to webodm.

1 Like
#9

Glad to hear you’ve been with us for a while!

Yeah, I think the native installs are a huge UX win for everyone!

Maybe Stephen put a bug in Piero’s ear, haha.

#10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.