Closed marc-hanheide closed 2 years ago
This is a problem particularly in docker containers, I have found, which have a HOSTNAME
set to the docker network IP (e.g. 172.x.x.x
, while localhost is 127.0.0.1
. So, there it fails, but also in other systems that follow this scheme.
could a new release be made for this, as the previous indeed cause some issues for users?
A new release is on my todo list :)
Here is a patch to a common problem: the mongo process binds to
$HOSTNAME
which may be set to something else than localhost. Then controller here tries to shut it down by connecting to localhost, where it will not be reached and the mongo server process hangs around. This fixes 2 things:_mongo_host
is use to trigger the shutdownbind_to_host
isFalse
then it now bind to all interfaces (as one would expect, I'd argue)