Hello community! It’s been a pleasure reading the forum the last couple of weeks.
Here is an issue I cannot resolve no matter how many times I tried.
Set up: Native installation on esxi server Ubuntu 16.04.06 (from ready-to-go installation script provided by webodm). 16gb ram (around 10-12gb usable) 100gb hdd.
The following has been tried in 2 different datasets around 250-300images/dataset using gcp.
Processing runs smoothly untill reaching post-processing when something really strange appears to be happening.
We get the message
Postprocessing: done (•̀ᴗ•́)و!
It has been stuck there for over 20hours. The strange thing is that when I click refresh to the page the timer starts counting from 00:39:51 which is the time the post-processing has successfully finished and compressing all.zip has started.
I have tried cancelling the task and starting over from the last step but with no luck.
I can find the all.assets(1.9gb) using SFTP but i cannot see the 3d/2d model on the webodm interface and I don’t know if the assets are processed correctly as the task does not finishes.
I have also tried to process another dataset in lighting network and similar behavior there as well. In lighting webpage everything seems to have finished and I can download all.zip but in my local server again the timer shows 02:26:06 and when refreshing it starts from there again.
Is there any solution to this? Could it be a server-related issue rather than webodm?
Is there any workaround I can make this work? I am unsure if we can use webodm if we cannot bound gcp files, even in the wgs84 coords system. We even tried the wgs84 and again failed.
The gcp file header used for wgs84 is the following: