WebODM has started, yet I cannot visit the web page that runs the app

WebODM
1

Detected Windows 10 with Hyper-V support
Initializing console…
Checking Hyper-V status…
Hyper-V is enabled
SET DOCKER_TLS_VERIFY=1
SET DOCKER_HOST=tcp://10.0.0.7:2376
SET DOCKER_CERT_PATH=C:\docker-webodm\machines\webodm
SET DOCKER_MACHINE_NAME=webodm
SET COMPOSE_CONVERT_WINDOWS_PATHS=true
REM Run this command to configure your shell:
REM @FOR /f “tokens=*” %i IN (‘docker-machine --storage-path C:\docker-webodm env webodm’) DO @%i
Setup env variable: DOCKER_TLS_VERIFY=1
Setup env variable: DOCKER_HOST=tcp://10.0.0.7:2376
Setup env variable: DOCKER_CERT_PATH=C:\docker-webodm\machines\webodm
Setup env variable: DOCKER_MACHINE_NAME=webodm
Setup env variable: COMPOSE_CONVERT_WINDOWS_PATHS=true
Client:
Version: 17.12.0-ce
API version: 1.35
Go version: go1.9.2
Git commit: c97c6d6
Built: Wed Dec 27 20:05:22 2017
OS/Arch: windows/amd64

Server:
Engine:
Version: 18.01.0-ce
API version: 1.35 (minimum version 1.12)
Go version: go1.9.2
Git commit: 03596f5
Built: Wed Jan 10 20:13:12 2018
OS/Arch: linux/amd64
Experimental: false
10.0.0.7
Checking for MS Edge Zone…
Zones are OK
We are ready :slight_smile:
C:\WebODM Manager>cd WebODM/
C:\WebODM Manager\WebODM>docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml start || docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml up
Starting db …
Starting node-odm-1 …
Starting webapp …
e[2Ae[2K
Starting node-odm-1 … e[32mdonee[0m
e[2Be[3Ae[2K
Starting db … e[32mdonee[0m
e[3Be[1Ae[2K
Starting webapp … e[32mdonee[0m
C:\WebODM Manager\WebODM>exit 0
e[1B
WebODM has started. You can close this window now. WebODM will continue running.

I then tried to update, which was successful. Upon starting WebODM again I started WebODM again. The results:
C:\WebODM Manager>cd WebODM/
C:\WebODM Manager\WebODM>git pull origin master
Already up to date.
C:\WebODM Manager\WebODM>docker-compose down --remove-orphans
Stopping db …
e[1Ae[2K
Stopping db … e[32mdonee[0m
From GitHub - OpenDroneMap/WebODM: User-friendly, commercial-grade software for processing aerial imagery. 🛩

  • branch master → FETCH_HEAD
    e[1B
    Removing orphan container “node-odm-1”
    Removing webapp …
    Removing db …
    e[2Ae[2K
    Removing webapp … e[32mdonee[0m
    e[2Be[1Ae[2K
    Removing db … e[32mdonee[0m
    e[1BRemoving network webodm_default
    C:\WebODM Manager\WebODM>docker pull opendronemap/node-opendronemap
    Using default tag: latest
    latest: Pulling from opendronemap/node-opendronemap
    Digest: sha256:92d5c95ea1d5f7b922fb636de35675d8937a23c0decd4ab925410efdabdae64a
    Status: Image is up to date for opendronemap/node-opendronemap:latest
    C:\WebODM Manager\WebODM>docker pull opendronemap/webodm_db
    Using default tag: latest
    latest: Pulling from opendronemap/webodm_db
    Digest: sha256:437e8772fddeb7e740fe38ca8213eaee6b05584104efc6c75eb26f9f7da1da9d
    Status: Image is up to date for opendronemap/webodm_db:latest
    C:\WebODM Manager\WebODM>docker pull opendronemap/webodm_webapp
    Using default tag: latest
    latest: Pulling from opendronemap/webodm_webapp
    85b1f47fba49: Already exists
    ba6bd283713a: Already exists
    817c8cd48a09: Already exists
    47cc0ed96dc3: Already exists
    4a36819a59dc: Already exists
    27ec8f120354: Already exists
    0a0552c62961: Already exists
    19b2dad3e54d: Already exists
    c1cf33620ed9: Already exists
    e565a546a005: Already exists
    b4d1c8f20d74: Already exists
    50b5fe5c3a22: Already exists
    8b9779484170: Already exists
    ed1cb68bb3b4: Already exists
    e8ae801abb83: Already exists
    37e3fead366e: Pulling fs layer
    7a88fc6fbc21: Pulling fs layer
    f140f687f44c: Pulling fs layer
    c4b931995cce: Pulling fs layer
    186c9d152f27: Pulling fs layer
    4b96b61addcf: Pulling fs layer
    c4b931995cce: Waiting
    186c9d152f27: Waiting
    4b96b61addcf: Waiting
    740f91555b64: Pulling fs layer
    0ebadf25d3f6: Pulling fs layer
    222e6bcfe232: Pulling fs layer
    740f91555b64: Waiting
    0ebadf25d3f6: Waiting
    ad29ebecc394: Pulling fs layer
    222e6bcfe232: Waiting
    ad29ebecc394: Waiting
    7a88fc6fbc21: Verifying Checksum
    7a88fc6fbc21: Download complete
    C:\WebODM Manager>cd WebODM/
    C:\WebODM Manager\WebODM>docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml start || docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml up
    Starting db …
    Starting node-odm-1 …
    Starting webapp …
    e[3Ae[2K
    Starting db … e[32mdonee[0m
    e[3Be[2Ae[2K
    Starting node-odm-1 … e[32mdonee[0m
    e[2Be[1Ae[2K
    Starting webapp … e[32mdonee[0m
    e[1BNo containers to start
    Creating network “webodm_default” with the default driver
    Creating db …
    Creating node-odm-1 …
    e[3Ae[2K
    Creating db … e[32mdonee[0m
    e[3Be[3Ae[2K
    Creating node-odm-1 … e[32mdonee[0m
    e[3BCreating webapp …
    e[3Ae[2K
    Creating webapp … e[32mdonee[0m
    Attaching to db, node-odm-1, webapp
    e[36mdb |e[0m LOG: database system was shut down at 2018-02-25 15:55:40 UTC
    e[36mdb |e[0m LOG: MultiXact member wraparound protections are now enabled
    e[36mdb |e[0m LOG: database system is ready to accept connections
    e[33mnode-odm-1 |e[0m info: No tasks dump found
    e[33mnode-odm-1 |e[0m info: Checking for orphaned directories to be removed…
    e[32mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[32mwebapp exited with code 127
    e[0me[35mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[35mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[35mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[35mwebapp exited with code 127
    e[0me[31mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[31mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[31mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[31mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[31mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[31mwebapp exited with code 127
    e[0me[34mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[34mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[34mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[34mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[34mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[34mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[34mwebapp |e[0m /bin/bash: /webodm/wait-for-postgres.sh: No such file or directory
    e[34mwebapp exited with code 127

I am still getting an unable to connect screen from both chrome and firefox. Firewall is down, as per instructions. All of this was done with the Manager app.

2

Hey @adavi149 thanks for reporting the problem.

Could you try the following?

  • From the Maintenance tab, press “Open Shell”
  • Type: docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml down
  • Press enter.
  • Close WebODM Manager.
  • Rename the C:\WebODM Manager\WebODM directory to C:\WebODM Manager\WebODM_backup.
  • Start WebODM Manager.
3

It worked! Thank you.

1 Like