Coda File System

Coda server trouble with multiple NIC's

From: UpFront Technology <upfronttechnology_at_columbus.rr.com>
Date: Sun, 1 Jun 2003 07:17:35 -0400
Hello,

	I am a small web developer intrigued by CODA's functionality.  I currently
host sites I design and like Brett Lymn (Nice article in Sys Admin, BTW), I
plan to try CODA to replicate to multiple web servers for fail over
purposes.

	I was able to set CODA up with almost no problem, however, I received an
error that has me puzzled.  My set-up is as follows:



				-----------
				CODA SERVER				------
				10.0.0.2 - 10.0.0.9		client
				-----------				10.0.0.5
					|	   |			-------															|	   | 				|															\	   | 				/
\	--------------------   /
WITCH																		---------------------

Venus looks to 10.0.0.2 for the server.




I receive the following errors when running    -venus -init &-

		Date: Sun 06/01/2003

08:02:07 /usr/coda/LOG size is 548342 bytes
08:02:07 /usr/coda/DATA size is 2193368 bytes
08:02:07 Initializing RVM data...
08:02:07 ...done
08:02:07 Loading RVM data
08:02:07 starting VDB scan
08:02:07        1 volume replicas
08:02:07        0 replicated volumes
08:02:07        0 CML entries allocated
08:02:07        0 CML entries on free-list
08:02:08 starting FSDB scan (833, 20000) (25, 75, 4)
08:02:08        0 cache files in table (0 blocks)
08:02:08        833 cache files on free-list
08:02:08 starting HDB scan
08:02:08        0 hdb entries in table
08:02:08        0 hdb entries on free-list
08:02:08 Initial LRDB allocation
08:02:08 Getting Root Volume information...
08:02:08 GetRootVolume: can't get root volume name!

After looking up "can't get root volume name!" in the discussion group
archives, I came across a similar messages regarding binding to the correct
IP.

"http://www.coda.cs.cmu.edu/maillists/codalist/codalist-2002/4771.html"
regarding Problems connecting to svm: RTP2_NOTCLIENT

 I took down 10.0.0.9 (eth1) and all works fine.  It seems to be a problem
with the server replying back on the wrong (multiple) interface.  The above
article finishes up by saying "Actually, the server is listening on all
interfaces. And indeed, after pointing the client to the internal interface
instead of the external, the mounting succeeded.

Thank you for your support"


I believe I have a similar problem, (although the interfaces are internal)
but unsure how to correct it.


Any thoughts...thanks
Received on 2003-06-01 07:27:38