[chord] unable to bootstrap chord

[Deji Akinyemi]

Hello Frank! Thanks for your reply. keepthefaith does correspond to 
192.168.1.101.
However, just in case I utilized the -l flag as you suggested. Here is 
the result:

------------------------------------
[hnau at keepthefaith hnau]$ lsd -j keepthefaith:50005 -p 50005 -l 
192.168.1.101
=== Configurator::dump
chord.lookup_mode "fingerlike"
chord.ncoords 3
chord.npred 1
chord.nsucc 16
chord.rpc_mode "stp"
chord.server_selection_mode 5
debruijn.logbase 2
dhash.dfrags 7
dhash.efrags 14
dhash.missing_outstanding_max 15
locationtable.maxcache 208
merkle.keyhash_timer 10
merkle.prt_timer 5
merkle.replica_timer 3
merkle.sync_timer 30
chord: running on 192.168.1.101:50005
lsd: CREATED RPC MANAGER
lsd: lsd: created new dhash
 1054148635:458003: creating new vnode: 
755c9c8e156ab7f1894417388d45ce7fb3216ebb
lsd:  1054148635:458679 coords are: 76 -952 349
 1054148635:460573 myID is 755c9c8e156ab7f1894417388d45ce7fb3216ebb
lsd: chord::handleProgram: 344447
lsd: lsd starting up at Wed May 28 15:03:55 2003
lsd:  running with options:
lsd:   IP/port: 192.168.1.101:50005
lsd:   vnodes: 1
lsd:   lookup_mode: 2
lsd:   ss_mode: 1
lsd:  1054148635:477373 Higher-level RPC Failure 2
755c9c8e156ab7f1894417388d45ce7fb3216ebb: join RPC failed: RPC: Unable 
to receive
755c9c8e156ab7f1894417388d45ce7fb3216ebb: should remove me from vnodes 
since I failed to join.
newvnode_cb: status 2
lsd: fatal: unable to join
-------------------------------------

I appreciate your time and look forward to any suggestions you may have.

Deji.

fdabek at MIT.EDU wrote:

>Deji,
>
>    Does "keepthefaith" resolve to 192.168.1.101 on your network? If not
>you'll have to tell lsd to listen on a particular IP using the -l flag.
>
>
>--Frank
>
>----- Original Message ----- 
>From: "Deji Akinyemi" <ihnau at netscape.net>
>To: <chord at amsterdam.lcs.mit.edu>
>Sent: Tuesday, May 27, 2003 3:49 PM
>Subject: [chord] unablet to bootstrap chord
>
>
>  
>
>>Hi! I seem to be having problems bootstrapping chord. I am running the
>>2003-05-21 version
>>of chord, with sfs 0.7.2, under redhat 9.0 with kernel 2.4.20.
>>
>>Here is the execution dump. I followed the directions given in your
>>how-to, and I made
>>sure to disable the firewall on my machine just in case it may be
>>interefereing witht the network communications. Thanks for your time and
>>I look forward to hearing from you.
>>
>>Deji.
>>
>># lsd -j keepthefaith:50005 -p 50005
>>=== Configurator::dump
>>chord.lookup_mode "fingerlike"
>>chord.ncoords 3
>>chord.npred 1
>>chord.nsucc 16
>>chord.rpc_mode "stp"
>>chord.server_selection_mode 5
>>debruijn.logbase 2
>>dhash.dfrags 7
>>dhash.efrags 14
>>dhash.missing_outstanding_max 15
>>locationtable.maxcache 208
>>merkle.keyhash_timer 10
>>merkle.prt_timer 5
>>merkle.replica_timer 3
>>merkle.sync_timer 30
>>chord: running on 192.168.1.101:50005
>>lsd: CREATED RPC MANAGER
>>lsd: lsd: created new dhash
>> 1054064283:506233: creating new vnode:
>>755c9c8e156ab7f1894417388d45ce7fb3216ebb
>>lsd:  1054064283:507140 coords are: -920 -891 -806
>> 1054064283:508400 myID is 755c9c8e156ab7f1894417388d45ce7fb3216ebb
>>lsd: chord::handleProgram: 344447
>>lsd: lsd starting up at Tue May 27 15:38:03 2003
>>lsd:  running with options:
>>lsd:   IP/port: 192.168.1.101:50005
>>lsd:   vnodes: 1
>>lsd:   lookup_mode: 2
>>lsd:   ss_mode: 1
>>lsd:  1054064283:606272 Higher-level RPC Failure 2
>>755c9c8e156ab7f1894417388d45ce7fb3216ebb: join RPC failed: RPC: Unable
>>to receive
>>755c9c8e156ab7f1894417388d45ce7fb3216ebb: should remove me from vnodes
>>since I failed to join.
>>newvnode_cb: status 2
>>lsd: fatal: unable to join
>>
>>
>>
>>_______________________________________________
>>chord mailing list
>>chord at amsterdam.lcs.mit.edu
>>https://amsterdam.lcs.mit.edu/mailman/listinfo/chord
>>
>>    
>>