Cannot start service node-odm-1


#1

Hey,
I’ve update ODM, but I can’t start the program. The console gives following message:
[04]: Hyper-V Virtual Ethernet Adapter
[05]: Hyper-V Virtual Ethernet Adapter
[07]: Hyper-V Virtual Ethernet Adapter
[08]: Hyper-V Virtual Ethernet Adapter
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Detected Windows 10 with Hyper-V support
Initializing console…
Checking if current user is in docker-users group
User is in docker-users group
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
80061a99d02a redis “docker-entrypoint.s…” 37 minutes ago Up 2 minutes 6379/tcp broker
Client: Docker Engine - Community
Version: 18.09.1
API version: 1.39
Go version: go1.10.6
Git commit: 4c52b90
Built: Wed Jan 9 19:34:26 2019
OS/Arch: windows/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 18.09.1
API version: 1.39 (minimum version 1.12)
Go version: go1.10.6
Git commit: 4c52b90
Built: Wed Jan 9 19:41:49 2019
OS/Arch: linux/amd64
Experimental: false
Press Start WebODM to launch
Checking for MS Edge Zone…
Zones are OK
Press Start WebODM to launch
E:\programma’s\WebODM Manager>cd WebODM/
E:\programma’s\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 broker …
Starting worker …
Starting webapp …
e[3Ae[2K
Starting broker … e[32mdonee[0m
e[3Be[5Ae[2K
Starting db … e[31merrore[0m
e[5Be[1Ae[2K
Starting webapp … e[31merrore[0m
e[1Be[2Ae[2K
Starting worker … e[31merrore[0m
e[2Be[4Ae[2K
Starting node-odm-1 … e[31merrore[0m
e[4B
ERROR: for db Cannot start service db: driver failed programming external connectivity on endpoint db (3825d916477f2f7ff5c304d8787888c78018cc1c259a5e10e949a08fb3608304): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:32803:tcp:172.19.0.3:5432: input/output error
ERROR: for node-odm-1 Cannot start service node-odm-1: driver failed programming external connectivity on endpoint node-odm-1 (c9db5122f2565473349c273210d0f408707eec8f1fd51d61fbbbd87c91ce3218): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:32813:tcp:172.19.0.4:3000: input/output error
E:\programma’s\WebODM Manager\WebODM>exit 0
WebODM has started. You can close this window now. WebODM will continue running.
Windows named pipe error: Het systeem kan het opgegeven bestand niet vinden. (code: 2)
E:\programma’s\WebODM Manager>cd WebODM/
E:\programma’s\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
Windows named pipe error: Het systeem kan het opgegeven bestand niet vinden. (code: 2)
Windows named pipe error: Het systeem kan het opgegeven bestand niet vinden. (code: 2)
E:\programma’s\WebODM Manager\WebODM>exit 1
Error: docker-compose exited with code: 1
E:\programma’s\WebODM Manager>cd WebODM/
E:\programma’s\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
Windows named pipe error: Het systeem kan het opgegeven bestand niet vinden. (code: 2)
Windows named pipe error: Het systeem kan het opgegeven bestand niet vinden. (code: 2)
E:\programma’s\WebODM Manager\WebODM>exit 1
Error: docker-compose exited with code: 1
E:\programma’s\WebODM Manager>cd WebODM/
E:\programma’s\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
Windows named pipe error: Het systeem kan het opgegeven bestand niet vinden. (code: 2)
Windows named pipe error: Het systeem kan het opgegeven bestand niet vinden. (code: 2)
E:\programma’s\WebODM Manager\WebODM>exit 1
Error: docker-compose exited with code: 1
E:\programma’s\WebODM Manager>cd WebODM/
E:\programma’s\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 broker …
Starting worker …
Starting webapp …
e[4Ae[2K
Starting node-odm-1 … e[32mdonee[0m
e[4Be[5Ae[2K
Starting db … e[32mdonee[0m
e[5Be[3Ae[2K
Starting broker … e[32mdonee[0m
e[3Be[2Ae[2K
Starting worker … e[32mdonee[0m
e[2Be[1Ae[2K
Starting webapp … e[32mdonee[0m
E:\programma’s\WebODM Manager\WebODM>exit 0
e[1B
WebODM has started. You can close this window now. WebODM will continue running.
What an I doing wrong?
Thanks for your help!
Jan


#2

Check that you have no other services running on port 3000 and 5432 (restart the computer for good measure), also try to press the “Update” button from the WebODM Manager interface?


#3

After the update ODM works perfect again! The ports were not occupied.
Thanks Piero!