Port already in use errors in existing project #46683
-
Hi all, I have an existing Quarkus project that has been under development for 2 years, and was working fine until 2 days ago. I have checked out the 1 week old tagged release that is currently running in production, in a new directory; I have restarted the machine; of course lsof -i : doesn't report anything running on those ports, neither before nor after quarkus has failed. Everything is under source control so all maven versions & extensions are identical to what was working fine one week ago... I am at a loss trying to figure out what could be going on - any suggestions? I have a vague suspicion that Quarkus itself it trying to bind to the port twice, but I can't even figure out where to put my breakpoints since all I get are async failure handlers reporting the error with no details as to where it happened (I did enable debug / trace logging with no success). I have been stuck on this for half a day, so any help would be really appreciated! Environment:
quarkus:dev:
Running a single @QuarkusTest test:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
/cc @geoand (kotlin) |
Beta Was this translation helpful? Give feedback.
Jeez, this is simply a misleading log message. I have an entry in /etc/hosts to bind hostnames to my local network address to support my nginx / https dev setup, and I forgot to update that when switching to a new wifi network.
I have
quarkus.http.host=macbook
and
/etc/hosts: 192.168.1.11 macbook macbook-admin ...
192.168.1.11 is unreachable, and yet I get "Port already bound":(
Caused by: io.quarkus.runtime.QuarkusBindException: Port(s) already bound: 8089: Can't assign requested address