Mac OSX High Sierra
16GB RAM
14GB + 4Gb for Docker
Latest WebODM
After uploading a 330 image dataset and selecting Fast Ortho, I got an out of memory error and it failed.
I then set the images to be resized to 2048 and tried again just using fast orpho (twice), both times, upon completion the web host seems to crash after clicking “View Map”. The 127.0.0.1:8000 page will not load, no errors, just a spinning loading circle (on Chrome and Safari).
The first time it happened i reset docker and installed WebODM again.
This time, I’m just trying to stop and start the service but it seems to be stuck. Here’s the verbose output (I assume i’m doing verbose wrong, it doesn’t look very informative).
./webodm.sh start --verbose
Checking for docker… OK
Checking for git… OK
Checking for python… OK
Checking for pip… OK
Checking for docker-compose… OK
Starting WebODM…Using the following environment:
Host: localhost
Port: 8000
Media directory: appmedia
SSL: NO
SSL key:
SSL certificate:
SSL insecure port redirect: 80
Celery Broker: redis://brokerMake sure to issue a ./webodm.sh down if you decide to change the environment.
docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml start || docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml up
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
EDIT -
Ok so restarting docker, stopping and then starting the webodm service again fixes it. Though now the project is not showing as finished, it’s actually showing the “offline due to memory” error.
Strange.