Code 1 failure for everything

Hey Team,
Very new here, and been following a good few tutorials and videos…

I have installed WebODM via Docker. I can get the server running no worries, and have and a look around the WebGUI using Chrome.

I have tried to make a very basic Ortho map with 62 images taken on a P4 @ 4000x3000px

The VM is running with 8gb ram and 50gb storage. I know RAM is low, but i dont see it failing due to that? especially with only 16 images…

The initial map failed after Structure From Motion / MVS.

I’ve tried a smaller data set with 16 images also, and many different ‘option settings’ when uploading.
Everything results in a failure at the same point. And this below is what the console is spitting out.

Data set here: https://drive.google.com/open?id=1FxnZhs6S25HaBvkngnUI3Gm2A7LI8oE1

any help here would be A1, thanks in advance!

Capture

CONSOLE (not in its entirety - Thats in a txt file in dropbox…)
[INFO] Running dense reconstruction. This might take a while. Please be patient, the process is not dead or hung.
[INFO] Process is running
[DEBUG] running /code/SuperBuild/src/elibs/mve/apps/dmrecon/dmrecon -s2 --progress=silent --local-neighbors=2 --force /var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/mve
MVE Depth Map Reconstruction (built on May 7 2019, 14:24:11)
Initializing scene with 12 views…
Initialized 12 views (max ID is 11), took 3ms.
Reading Photosynther file (12 cameras, 22637 features)…
Reconstructing all views…
Reconstruction took 859656ms.
Saving views back to disc…
Saving views to MVE files… done.
[DEBUG] running /code/SuperBuild/src/elibs/mve/apps/scene2pset/scene2pset -F2 “/var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/mve” “/var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/mve/mve_dense_point_cloud.ply”
MVE Scene to Pointset (built on May 7 2019, 14:24:29)
Using depthmap “depth-L2” and color image “undist-L2”
Initializing scene with 12 views…
Initialized 12 views (max ID is 11), took 2ms.
Processing view “0001” (with colors)…
Processing view “0000” (with colors)…
Processing view “0002” (with colors)…
Processing view “0003” (with colors)…
Processing view “0004” (with colors)…
Processing view “0005” (with colors)…
Processing view “0006” (with colors)…
Processing view “0007” (with colors)…
Processing view “0008” (with colors)…
Processing view “0009” (with colors)…
Processing view “0010” (with colors)…
Processing view “0011” (with colors)…
Writing final point set (1795569 points)…
Writing PLY file (1795569 verts, with colors, with normals, with confidences, with values, 0 faces)…
done.
[INFO] Running ODM MVE Cell - Finished
[INFO] Running ODM FilterPoints Cell
[INFO] Filtering point cloud (statistical, meanK 16, standard deviation 2.5)
[INFO] Keeping only points with > 0.6 confidence
[DEBUG] running /code/build/bin/odm_filterpoints -inputFile /var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/mve/mve_dense_point_cloud.ply -outputFile /var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/odm_filterpoints/point_cloud.ply -sd 2.5 -meank 16 -confidence 0.6
[INFO] Running ODM FilterPoints Cell - Finished
[INFO] Running ODM Meshing Cell
[DEBUG] Writing ODM Mesh file in: /var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/odm_meshing/odm_mesh.ply
[DEBUG] running /code/SuperBuild/src/PoissonRecon/Bin/Linux/PoissonRecon --in /var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/odm_filterpoints/point_cloud.ply --out /var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/odm_meshing/odm_mesh.dirty.ply --depth 9 --pointWeight 4 --samplesPerNode 1.0 --threads 2 --linearFit
[DEBUG] running /code/build/bin/odm_cleanmesh -inputFile /var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/odm_meshing/odm_mesh.dirty.ply -outputFile /var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/odm_meshing/odm_mesh.ply -removeIslands -decimateMesh 100000
[DEBUG] Writing ODM 2.5D Mesh file in: /var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/odm_meshing/odm_25dmesh.ply
[DEBUG] ODM 2.5D DSM resolution: 0.12575
[INFO] Created temporary directory: /var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/odm_meshing/tmp
[INFO] Creating DSM for 2.5D mesh
[DEBUG] running pdal info /var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/odm_filterpoints/point_cloud.ply > /tmp/tmpup76UW.json
[INFO] Point cloud bounds are [minx: -47.77138519, maxx: 51.76947784] [miny: -39.08366776, maxy: 38.43909836]
[INFO] DEM resolution is (792, 617), max tile size is 2048, will split DEM generation into 1 tiles
[INFO] Generating /var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/odm_meshing/tmp/mesh_dsm_r0.177837355468_x0_y0.tif (max, radius: 0.177837355468, resolution: 0.12575)
[DEBUG] running pdal pipeline -i /tmp/tmpJqeub0.json > /dev/null 2>&1
[WARNING] DEM processing failed with multiple threads, let’s retry with a single thread…
[INFO] Generating /var/www/data/8105438d-5d9d-4fd0-a0df-409ca70d096c/odm_meshing/tmp/mesh_dsm_r0.177837355468_x0_y0.tif (max, radius: 0.177837355468, resolution: 0.12575)
[DEBUG] running pdal pipeline -i /tmp/tmpjSsRCN.json > /dev/null 2>&1
Traceback (most recent call last):
File “/code/run.py”, line 47, in
plasm.execute(niter=1)
File “/code/scripts/odm_meshing.py”, line 102, in process
method=‘poisson’ if args.fast_orthophoto else ‘gridded’)
File “/code/opendm/mesh.py”, line 35, in create_25dmesh
max_workers=available_cores
File “/code/opendm/dem/commands.py”, line 172, in create_dem
process_one(q)
File “/code/opendm/dem/commands.py”, line 114, in process_one
pdal.run_pipeline(d, verbose=verbose)
File “/code/opendm/dem/pdal.py”, line 162, in run_pipeline
out = system.run(’ ‘.join(cmd) + ’ > /dev/null 2>&1’)
File “/code/opendm/system.py”, line 36, in run
raise Exception(“Child returned {}”.format(retcode))
Exception: Child returned 139


DOCKER
broker | 1:M 23 May 2019 04:14:14.047 * 100 changes in 300 seconds. Saving…
broker | 1:M 23 May 2019 04:14:14.049 * Background saving started by pid 23
broker | 23:C 23 May 2019 04:14:14.083 * DB saved on disk
broker | 23:C 23 May 2019 04:14:14.085 * RDB: 0 MB of memory used by copy-on-write
webapp | WARNING Not Found: /api/projects/1/tasks/d757567f-92da-4008-9cf4-9c7f49829abf/
webapp | [2019-05-23 04:14:53 +0000] [76] [INFO] Autorestarting worker after current request.
webapp | [2019-05-23 04:14:53 +0000] [76] [INFO] Worker exiting (pid: 76)
webapp | [2019-05-23 04:14:54 +0000] [77] [INFO] Booting worker with pid: 77
broker | 1:M 23 May 2019 04:14:14.150 * Background saving terminated with success
broker | 1:M 23 May 2019 04:19:15.036 * 100 changes in 300 seconds. Saving…
broker | 1:M 23 May 2019 04:19:15.037 * Background saving started by pid 24
broker | 24:C 23 May 2019 04:19:15.061 * DB saved on disk
broker | 24:C 23 May 2019 04:19:15.064 * RDB: 0 MB of memory used by copy-on-write
webapp | INFO Initializing GRASS engine using /usr/bin/grass76
webapp | [2019-05-23 04:21:29 +0000] [77] [INFO] Autorestarting worker after current request.
webapp | [2019-05-23 04:21:29 +0000] [77] [INFO] Worker exiting (pid: 77)
webapp | [2019-05-23 04:21:30 +0000] [78] [INFO] Booting worker with pid: 78
broker | 1:M 23 May 2019 04:19:15.138 * Background saving terminated with success
broker | 1:M 23 May 2019 04:24:16.042 * 100 changes in 300 seconds. Saving…
broker | 1:M 23 May 2019 04:24:16.043 * Background saving started by pid 25
broker | 25:C 23 May 2019 04:24:16.082 * DB saved on disk
broker | 25:C 23 May 2019 04:24:16.084 * RDB: 0 MB of memory used by copy-on-write
broker | 1:M 23 May 2019 04:24:16.145 * Background saving terminated with success
broker | 1:M 23 May 2019 04:29:17.068 * 100 changes in 300 seconds. Saving…
broker | 1:M 23 May 2019 04:29:17.069 * Background saving started by pid 26
broker | 26:C 23 May 2019 04:29:17.097 * DB saved on disk
broker | 26:C 23 May 2019 04:29:17.100 * RDB: 0 MB of memory used by copy-on-write
webapp | INFO Initializing GRASS engine using /usr/bin/grass76
webapp | [2019-05-23 04:29:54 +0000] [78] [INFO] Autorestarting worker after current request.
webapp | [2019-05-23 04:29:54 +0000] [78] [INFO] Worker exiting (pid: 78)
webapp | [2019-05-23 04:29:54 +0000] [79] [INFO] Booting worker with pid: 79
broker | 1:M 23 May 2019 04:29:17.169 * Background saving terminated with success
broker | 1:M 23 May 2019 04:34:18.044 * 100 changes in 300 seconds. Saving…
broker | 1:M 23 May 2019 04:34:18.045 * Background saving started by pid 27
broker | 27:C 23 May 2019 04:34:18.072 * DB saved on disk
broker | 27:C 23 May 2019 04:34:18.074 * RDB: 0 MB of memory used by copy-on-write
webapp | INFO Initializing GRASS engine using /usr/bin/grass76
webapp | [2019-05-23 04:37:32 +0000] [79] [INFO] Autorestarting worker after current request.
webapp | [2019-05-23 04:37:32 +0000] [79] [INFO] Worker exiting (pid: 79)
webapp | [2019-05-23 04:37:33 +0000] [80] [INFO] Booting worker with pid: 80
broker | 1:M 23 May 2019 04:34:18.147 * Background saving terminated with success
broker | 1:M 23 May 2019 04:39:19.095 * 100 changes in 300 seconds. Saving…
broker | 1:M 23 May 2019 04:39:19.096 * Background saving started by pid 28
broker | 28:C 23 May 2019 04:39:19.120 * DB saved on disk
broker | 28:C 23 May 2019 04:39:19.122 * RDB: 0 MB of memory used by copy-on-write
worker | [2019-05-23 04:11:19,078: INFO/ForkPoolWorker-1] Processing… Task [Test] (5c763c87-4d97-4557-ab90-460b11e56fb6)
worker | INFO Processing status: 30 for Task [Test] (5c763c87-4d97-4557-ab90-460b11e56fb6)
broker | 1:M 23 May 2019 04:39:19.197 * Background saving terminated with success
broker | 1:M 23 May 2019 04:44:20.008 * 100 changes in 300 seconds. Saving…

Heyyy it’s Nick from the Tron. Hello from Wellington!

Files look fine to me: https://dev.aerosurvey.co.nz/public.cgi?S=341&T=e25c3347-2b79-4452-af92-ceb2d4dd8bab

I suspect that you’re running out of RAM. Have you monitored it while you’re running a job?

Hey man,
Thanks for that. I believed the data se was ok, as I’ve used the same set with Drone Deploy to make the same map, so I thought it would be a simple test. Seems strange I’d run out of ram with a sample of 16 images?
Hmm. Yeah, I’ve tried to monitor it while its processing, and everything to me seems to be ticking over nicely until it just… stops.
Anyway, Thanks for your help on it, I might give aerosurvey a go tho, that looks neat for not too bad while I suss out ODM…
Cheers!

I had this issue recently, all my projects were returning error code 1 “min num of features” …turns out it could have been something to do with me quitting docker and reopening it without stopping webodm between projects.

Stop webodm, update it (might aswell!) then run it again.
./webodm.sh stop
./webodm.sh update
./webodm.sh start

Try again

1 Like