search

michaelshobbs / dokku-logspout

Logspout plugin for Dokku
62 stars 23 forks source link

Dokku logspout breaking my app #37

Open Loschcode opened 2 years ago

Loschcode commented 2 years ago

Everything was working smooth and today, without any change in my codebase and configuration whatsoever, I couldn't rebuild or ship new versions

-----> Cleaning up...
-----> Building bloodbath-api from herokuish
-----> Adding BUILD_ENV to build environment...
       BUILD_ENV added successfully
docker: Error response from daemon: driver failed programming external connectivity on endpoint logspout (353daab00d197d1dac52a7b379fbfa3b8533d668266122b8048dd884cb9baf6f): Bind for 127.0.0.1:18000 failed: port is already allocated.
2021/12/07 17:31:38 exit status 125
2021/12/07 17:31:38 exit status 1
2021/12/07 17:31:38 exit status 1

No matter what command I use it crashes

dokku logspout:start
docker: Error response from daemon: driver failed programming external connectivity on endpoint logspout (d67f3357caacb1011f893c5792a6013b81f5f3142edfa1b9bfe0d85a394ae337): Bind for 127.0.0.1:18000 failed: port is already allocated

What am I supposed to do? I've no idea how to troubleshoot this system.

michaelshobbs commented 2 years ago

it looks like something is already running on port 18000. you can run something like the following then post that output here.

$ netstat -lnpt | grep 18000
tcp        0      0 127.0.0.1:18000         0.0.0.0:*               LISTEN      2112
$ ps auxwww | grep 2112

additionally you might try removing the logspout container (i.e. dokku logspout:destroy) and deploying again: