(Illustration by Gaich Muramatsu)
Hi, Slowly, but surely I am building a functioning coda system. However I am still having a few problems. So far, I can successfully connect to the coda server from a client, and write date to a mounted volume. This works fine from the clients. However, when I try to access the directories from the SCM, I get a variety of different errors. I have a volume named "Storage" mounted on: /coda/pa-wb-001.public/storage I can read, write to the volume from every client I have tried so far. When I try to do a simple ls /coda/pa-wb-001.public on the scm machine, I seem to get a host of random errors. Sometimes, I get "Resource Temporarily Unavailable", other times I get "Connection Timed Out", and sometimes I even get "Permission Denied". This is very confusing. I was having similar problems with the clients, which I found was caused by my network setup on the server. The server has 2 nics, 1 nic on 192.168.10.16, the other on 10.1.1.1. I'm forcing coda to work on the 10.1.1.1 address. This seems to have fixed the client problem. I also changed the hosts file so pa-wb-001.public points to 10.1.1.1. The interesting part is the output of codacon when I try to do an "ls /coda/pa-wb-001.public": Codacon output: ------------------------------------------------------- ValidateAttrsPlusSHA pa-wb-001.public(501bdc88.7f000000.1.1) [0] ( 11:58:02 ) Fetch pa-wb-001.public [2] ( 11:58:02 ) ValidateAttrsPlusSHA pa-wb-001.public(501bdc88.7f000000.1.1) [0] ( 11:58:03 ) Fetch pa-wb-001.public [2] ( 11:58:03 ) ValidateAttrsPlusSHA pa-wb-001.public(501bdc88.7f000000.1.1) [0] ( 11:58:03 ) Fetch pa-wb-001.public [2] ( 11:58:03 ) ValidateAttrsPlusSHA pa-wb-001.public(501bdc88.7f000000.1.1) [0] ( 11:58:04 ) Fetch pa-wb-001.public [2] ( 11:58:04 ) ValidateAttrsPlusSHA pa-wb-001.public(501bdc88.7f000000.1.1) [0] ( 11:58:06 ) Fetch pa-wb-001.public [2] ( 11:58:06 ) bandwidth 192.168.10.16 976562 1088139 1228501 ( 11:58:07 ) ValidateAttrsPlusSHA pa-wb-001.public(501bdc88.7f000000.1.1) [0] ( 11:58:10 ) Fetch pa-wb-001.public [2] ( 11:58:10 ) bandwidth 192.168.10.16 1009081 1089324 1183431 ( 11:58:12 ) BeginStatusWalk [190] ( 11:58:47 ) [0, 0, 0, 0] [0] ( 11:58:47 ) NewConnectFS 192.168.10.16 ( 11:58:47 ) BackProbe 192.168.10.16 ( 11:58:47 ) bandwidth 192.168.10.16 931098 1146788 1492537 ( 11:58:47 ) ValidateAttrsPlusSHA pa-wb-001.public(501bdc88.7f000000.1.1) [0] ( 11:58:47 ) EndStatusWalk [190] ( 11:58:47 ) [0, 0, 0, 0] [0, 0, 0] [1, 0, 0.0] ( 11:58:47 ) BeginDataWalk [1] ( 11:58:47 ) EndDataWalk [1] ( 11:58:47 ) [1, 0, 0.0] [0, 0, 0, 0] ( 11:58:47 ) bandwidth 192.168.10.16 960614 1169590 1494768 ( 11:58:52 ) ------------------------------------------------------- Now, this looks ok to me, except for the part when it's trying to connect to 192.168.10.16. I don't know why its trying to connect to that address, since the server is on 10.1.1.1. If I ping pa-wb-001.public from itself, it does come up as 10.1.1.1. I'm very confused. Am I on the right track here, or totally off ? Any help would greatly appreciated. Thanks in advance, -RD _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.comReceived on 2004-09-20 12:04:54