kercre123 / wire-prod-pod

49 stars 9 forks source link

Cannot start wire-pod on Ubuntu #5

Closed MTrab closed 1 year ago

MTrab commented 1 year ago

I just get this, when I try starting wire-pod on my Ubuntu:

● wire-pod.service - Wire Escape Pod (coqui)
   Loaded: loaded (/lib/systemd/system/wire-pod.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2022-10-07 22:03:09 CEST; 4 days ago
  Process: 37577 ExecStart=/home/malene/wire-pod/chipper/start.sh (code=exited, status=1/FAILURE)
 Main PID: 37577 (code=exited, status=1/FAILURE)

okt 07 22:03:09 escapepod systemd[1]: Started Wire Escape Pod (coqui).
okt 07 22:03:09 escapepod start.sh[37577]: go: module cache not found: neither GOMODCACHE nor GOPATH is set
okt 07 22:03:09 escapepod systemd[1]: wire-pod.service: Main process exited, code=exited, status=1/FAILURE
okt 07 22:03:09 escapepod systemd[1]: wire-pod.service: Failed with result 'exit-code'.

Any ideas?

MTrab commented 1 year ago

Removed everything and started over - now that part works :D

MTrab commented 1 year ago

Aaaaaand - just reinstalled on a RPi, and getting this again. A reinstall doesn't seem to work this time around :(

Lodenk commented 1 year ago

I am having the same issue: Oct 13 17:31:11 escapepod start.sh[3801]: go: module cache not found: neither GOMODCACHE nor GOPATH is set Oct 13 17:31:11 escapepod start.sh[3801]: go: module cache not found: neither GOMODCACHE nor GOPATH is set Oct 13 17:31:11 escapepod start.sh[3801]: go: module cache not found: neither GOMODCACHE nor GOPATH is set

RPI fresh raspian

kercre123 commented 1 year ago

It looks like you are using wire-pod rather than wire-prod-pod, is that correct? May you send the output of ls ~/wire-pod/chipper? This error should not happen if the chipper binary exists in that folder.

MTrab commented 1 year ago

Tried both. Same error weather I use wire-pod or wire-prod-pod.

MTrab commented 1 year ago

Okay - found the solution. You need to login as root and start the service that way. Sudu starting the service isn't enough