From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Communication problem!!
Date: Tue, 10 Apr 2001 16:19:11 +0100 [thread overview]
Message-ID: <20010410151905.9C24919AFD@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
given a symbolic net!host!service string, cs(8) produces a set of possible
recipes to make the corresponding connection. the recipe is interpreted as:
open the name given by the first field, and
write the string given by the second field
to make a connection. each line gives a different possibility, which
applications via dial(2) try in sequence until one works (or the last one fails).
in your case, it means that ndb looks fine (as far as i can tell), and you
need to check that both cpu server and file server have correctly configured
interfaces.
on the cpu server, try
cat /net/ipselftab
cat /net/iproute
cat /net/ipifc/0/status
on the file server ...
it's harder. there isn't a command to print the configuration.
try
state
which gives ethernet status.
and
arp print
but it will also be helpful to know the file server configuration as given in config mode
to see how you've configured the interfaces.
[-- Attachment #2: Type: message/rfc822, Size: 5476 bytes --]
[-- Attachment #2.1.1: Type: TEXT/PLAIN, Size: 741 bytes --]
This is what the commands returned
il!odysseus!9fs:
/net/il/clone 192.168.1.3!17008
il!achilles!cpu:
/net/il/clone 192.168.1.1!17013
net!odysseus!9fs:
/net/il/clone 192.168.1.3!17008
/net/tcp/clone 192.168.1.3!564
??? whats this mean ??
On Tue, 10 Apr 2001 forsyth@vitanuova.com wrote:
> Date: Tue, 10 Apr 2001 15:46:57 +0100
> From: forsyth@vitanuova.com
> Reply-To: 9fans@cse.psu.edu
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] Communication problem!!
>
> to help debug this sort of thing, try using ndb/csquery to
> see its translations (if any):
>
> ndb/csquery
>
> then as input try the following
>
> il!$fs!9fs
>
> (note the $)
>
> il!odysseus!9fs
> il!achilles!cpu
> net!odysseus!9fs
>
>
[-- Attachment #2.1.2: Type: MESSAGE/RFC822, Size: 2243 bytes --]
Return-Path: <9fans-admin@cse.psu.edu>
Received: from punt-1.mail.demon.net by mailstore for forsyth@vitanuova.com
id 986912693:10:19759:3; Tue, 10 Apr 2001 14:24:53 GMT
Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-1.mail.demon.net
id aa1113457; 10 Apr 2001 14:24 GMT
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.8.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id BF0E519AF6; Tue, 10 Apr 2001 10:24:09 -0400 (EDT)
Received: from saturn.scs.ryerson.ca (unknown [141.117.150.10])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 269C619AF1
for <9fans@cse.psu.edu>; Tue, 10 Apr 2001 10:23:34 -0400 (EDT)
Received: from jupiter.scs.ryerson.ca ([141.117.150.31]:47027 "EHLO
jupiter.scs.ryerson.ca") by saturn.scs.ryerson.ca with ESMTP
id <S116885AbRDJOXO>; Tue, 10 Apr 2001 10:23:14 -0400
Received: from localhost (diafrate@localhost)
by jupiter.scs.ryerson.ca (8.9.3/8.9.3) with ESMTP id KAA22207
for <9fans@cse.psu.edu>; Tue, 10 Apr 2001 10:23:11 -0400 (EDT)
X-Authentication-Warning: jupiter.scs.ryerson.ca: diafrate owned process doing -bs
To: cse.psu.edu!9fans
Message-ID: <Pine.GSO.4.21.0104101020460.21497-100000@jupiter.scs.ryerson.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [9fans] Communication problem!!
Sender: cse.psu.edu!9fans-admin
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.1
Precedence: bulk
Reply-To: cse.psu.edu!9fans
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <http://lists.cse.psu.edu/archives/9fans/>
Date: Tue, 10 Apr 2001 10:23:11 -0400 (EDT)
Ok, we're having trouble with communication between the fileserver and cpu
server. IT says timeout cant establish a connection. Our ndb/local looks
like this:
database=
file=/lib/ndb/local
file=/lib/ndb/common
ipnet=plan9 ip=192.168.1.0 ipmask=255.255.255.0
fs=odysseus
auth=achilles
ip=192.168.1.1 sys=achilles ether=0020af4cc97b
proto=il
ip=192.168.1.3 sys=odysseus ether=0020af4cc981
proto=il
does this seem right or does it need to be changed. We are keeping
everyting local.
To: cse.psu.edu!9fans
Subject: [9fans] Communication problem!!
Date: Tue, 10 Apr 2001 10:23:11 -0400 (EDT)
Message-ID: <Pine.GSO.4.21.0104101020460.21497-100000@jupiter.scs.ryerson.ca>
Ok, we're having trouble with communication between the fileserver and cpu
server. IT says timeout cant establish a connection. Our ndb/local looks
like this:
database=
file=/lib/ndb/local
file=/lib/ndb/common
ipnet=plan9 ip=192.168.1.0 ipmask=255.255.255.0
fs=odysseus
auth=achilles
ip=192.168.1.1 sys=achilles ether=0020af4cc97b
proto=il
ip=192.168.1.3 sys=odysseus ether=0020af4cc981
proto=il
does this seem right or does it need to be changed. We are keeping
everyting local.
next reply other threads:[~2001-04-10 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 15:19 forsyth [this message]
2001-04-10 16:39 ` Dave Iafrate - CSCI/F1997
[not found] <20010410170519Z48579-10235+9@saturn.scs.ryerson.ca>
2001-04-10 17:10 ` Dave Iafrate - CSCI/F1997
-- strict thread matches above, loose matches on Subject: below --
2001-04-10 17:05 presotto
2001-04-10 14:48 forsyth
2001-04-10 15:18 ` Dave Iafrate - CSCI/F1997
2001-04-10 15:43 ` Martin Harriss
2001-04-10 15:46 ` Dave Iafrate - CSCI/F1997
2001-04-10 14:46 forsyth
2001-04-10 14:55 ` Dave Iafrate - CSCI/F1997
2001-04-10 14:23 Dave Iafrate - CSCI/F1997
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010410151905.9C24919AFD@mail.cse.psu.edu \
--to=forsyth@vitanuova.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).