Opened 16 years ago
Closed 16 years ago
#26 closed defect (fixed)
No third node can join
Reported by: | Christoph Mayer | Owned by: | Christoph Mayer |
---|---|---|---|
Priority: | blocker | Milestone: | Release of 0.2.0 |
Component: | Foundation | Version: | 0.1.0 |
Keywords: | Cc: |
Description (last modified by )
In the PingPong sample, somehow no third node can join
Change History (8)
comment:1 by , 16 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
comment:2 by , 16 years ago
Resolution: | duplicate |
---|---|
Status: | closed → reopened |
comment:3 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
comment:4 by , 16 years ago
Description: | modified (diff) |
---|
comment:5 by , 16 years ago
Milestone: | → Release of 0.2.0 |
---|
comment:6 by , 16 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:7 by , 16 years ago
Owner: | changed from | to
---|---|
Status: | reopened → new |
comment:8 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The problem is solved, and it is now somehow duplicate of #29. (1) there was a real but, as the config file given port number was not taken into account when doing a join, it always took the default. And when two nodes run on the same host, both try to bind to the default which fails for the later one. (2) this is now duplicate of #29.