Is there a category for troubleshooting?

Looked for a category for troubleshooting problems, but didn’t find one, so I’ll ask here. Please re-direct me if I need to post this elsewhere.

Started having a startup error on WebODM. Couldn’t find a way to attach a file, so have pasted the console print out to the post. Have used the update button on WebODM Manager and rebooted the PC, both a couple of times. Was about to uninstall and re-install WebODM, but thought I’d check in here first.
Apologies for the lengthy post. Thanks for the help. Lemmeknow if there’s a cleaner way to do this:

Hyper-V Requirements: VM Monitor Mode Extensions: Yes
Detected OS with VirtualBox support
Initializing console…
Checking for OpenSSH Client at C:\WINDOWS\system32\OpenSSH\ssh.exe
OpenSSH check passed
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
No default docker-machine, good!
SET DOCKER_TLS_VERIFY=1
SET DOCKER_HOST=tcp://192.168.99.100:2376
SET DOCKER_CERT_PATH=E:\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 E:\docker-webodm env webodm’) DO @%i
Setup env variable: DOCKER_TLS_VERIFY=1
Setup env variable: DOCKER_HOST=tcp://192.168.99.100:2376
Setup env variable: DOCKER_CERT_PATH=E:\docker-webodm\machines\webodm
Setup env variable: DOCKER_MACHINE_NAME=webodm
Setup env variable: COMPOSE_CONVERT_WINDOWS_PATHS=true
Setup env variable: COMPOSE_TLS_VERSION=TLSv1_2
Client:
Version: 18.09.3
API version: 1.39
Go version: go1.12
Git commit: 774a1f4eee
Built: Mon Mar 4 10:36:44 2019
OS/Arch: windows/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 19.03.5
API version: 1.40 (minimum version 1.12)
Go version: go1.12.12
Git commit: 633a0ea838
Built: Wed Nov 13 07:28:45 2019
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.2.10
GitCommit: b34a5c8af56e510852c35414db4c1f4fa6172339
runc:
Version: 1.0.0-rc8+dev
GitCommit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
docker-init:
Version: 0.18.0
GitCommit: fec3683
Press Start WebODM to launch
192.168.99.100
Press Start WebODM to launch
Checking for docker… e[92me[1m OKe[0me[39m
Checking for git… e[92me[1m OKe[0me[39m
Checking for docker-compose… e[92me[1m OKe[0me[39m
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://broker
Default Nodes: 1

Make 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 --scale node-odm=1
Starting broker …
Starting node-odm …
Starting db …
Starting worker …
Starting webapp …
e[5Ae[2K
Starting broker … e[32mdonee[0m
e[5Be[3Ae[2K
Starting db … e[32mdonee[0m
e[3Be[4Ae[2K
Starting node-odm … e[32mdonee[0m
e[4Be[2Ae[2K
Starting worker … e[32mdonee[0m
e[2Be[1Ae[2K
Starting webapp … e[32mdonee[0m
e[1BNo containers to start
readlink /mnt/sda1/var/lib/docker/overlay2: invalid argument
Error: webodm.sh down exited with code: 1

Looks like something got corrupted at some point? you might have to press the “Delete VM” button from the maintenance panel (note this will reset the installation of WebODM and existing processed files will be lost).

That worked perfectly Pierotofy. Thanks… Bob R.

1 Like