[chord] When using -j 127.0.0.1, must use -l 127.0.0.1 as well

Emil Sit sit at MIT.EDU
Mon Apr 11 15:20:59 EDT 2005


On Mon, 11 April 2005 at 08:49 (-0700), leon wrote:
> 1113233349.078630 loctable: insert 66a80715013361f6e5435a54893cc87f7a5e65fc,202.115.26.4,10000,0
>  1113233349:078706 myID is 66a80715013361f6e5435a54893cc87f7a5e65fc
> lsd: chord::handleProgram: chord_program_1 (344447)
> lsd: chord::handleProgram: fingers_program_1 (344454)
> lsd: lsd starting up at Mon Apr 11 23:29:09 2005
> lsd:  running with options:
> lsd:   IP/port: 202.115.26.4:10000
> lsd:   vnodes: 1
> lsd:   lookup_mode: 1
> lsd:   ss_mode: -1

This indicates that lsd assumed that you were using your external
IP address instead of your localhost address, even though it is
listening on all interfaces.

Thus, when you connected with vnode for SHA-1(127.0.0.1.10000.0) it
found no one locally with that vnode id which resulted in
the error:
> 1113233349.101313 chord: unknown vnode 9173f7cbbc4f426392eca75f3a45781d292f69c2 for procedure 1 (344447.15).

To get around this, you can either specify -j 202.115.26.4:10000
to instruct lsd to join on the external address, or add the
additional "-l 127.0.0.1" flag to instruct lsd to listen on the
localhost address.

-- 
Emil Sit / MIT CSAIL PDOS / http://pdos.lcs.mit.edu/chord/  



More information about the chord mailing list