2017-07-17 19:06:34.660901 Unable to bind to 0.0.0.0:11211 on this computer. Bitcoin Core is probably already running.
test_runner.py and test_framework.py are very careful to not re-use ports for p2p and rpc interfaces on different nodes/tests, so perhaps another process was bound to 11211. Googling for port 11211 shows that it's memcached's default port.
Should be easy to test whether port 11211 causes problems by pushing a branch with port_seed() changed.
fanquake added the label Tests on Jul 21, 2017
laanwj
commented at 12:11 PM on July 27, 2017:
member
Most intermittent failures with ports could be avoided by using UNIX sockets for testing, too bad that that didn't make it.
MarcoFalke added the label Priority Low on Nov 10, 2017
MarcoFalke
commented at 9:55 PM on November 10, 2017:
member
The most simple work around would be to stop picking 11211:
diff --git a/test/functional/test_framework/util.py b/test/functional/test_framework/util.py
index acca72aa8..43f689df5 100644
--- a/test/functional/test_framework/util.py
+++ b/test/functional/test_framework/util.py
@@ -164,5 +164,5 @@ def satoshi_round(amount):
MAX_NODES = 8
# Don't assign rpc or p2p ports lower than this
-PORT_MIN = 11000
+PORT_MIN = 11222
# The number of ports to "reserve" for p2p and rpc, each
PORT_RANGE = 5000
laanwj removed the label Priority Low on Dec 6, 2017
MarcoFalke
commented at 8:04 PM on April 11, 2018:
member
@jnewbery Do you think this issue is worth to tackle/keep open?
jnewbery added the label Up for grabs on Apr 11, 2018
jnewbery
commented at 8:14 PM on April 11, 2018:
member
Setting 'Up for grabs'. Next steps, for anyone who wants this:
confirm that it really is port 11211 that causes problems.
fix using Marco's workaround or some other way.
jnewbery closed this on Apr 11, 2018
MarcoFalke removed the label Up for grabs on Jun 3, 2018
This is a metadata mirror of the GitHub repository
bitcoin/bitcoin.
This site is not affiliated with GitHub.
Content is generated from a GitHub metadata backup.
generated: 2026-05-19 06:54 UTC