From: plan9fans@ntlworld.nospam.com
To: 9fans@cse.psu.edu
Subject: [9fans] auth_proxy: write fd: file does not exist
Date: Mon, 29 Mar 2004 23:02:53 +0100 [thread overview]
Message-ID: <f1d0367d8c239b5063004f3b4cb3a884@snellwilcox.com> (raw)
Hi
I am trying to get a single machine to
serve CPU/fossil/venti/auth.
Venti and fossil are happy.
keyfs seems OK - If I boot my terminal standalone
auth/debug to the server is happy with both my
username and bootes.
The secstore seems to work - put and get are OK and
when I network boot a terminal off the server I can
see a GET of 'factotum'.
The secstore contents is correct, I use the same
list of keys cat'ed int /mnt/factotum/ctl on my
standalone terminals.
All the below give the correct results, though
auth/debug checks them implicitly I beleive.
ndb/ipquery ip xx.xx.xx.xx auth
ndb/ipquery ip xx.xx.xx.xx fs
ndb/ipquery ip xx.xx.xx.xx cpu
ndb/ipquery authdom mydom.com auth
BUT
When I try to boot from the server (pulling only
9load from the terminals hard drive), the kernel loads
(even bootp is OK), I enter my username and secstore
password and get:
Version...
Authentication failed (auth_proxy write fd: file does not exist), trying anyways.
[panic and stackdump]
Other very suspicious symptom is that cpu from a
standalone terminal to the server also fails (even though
auth/debug is happy).
cpu -h felix
cpu: can't authenticate: felix: auth_proxy rpc write: cpu: srvauth:: auth server protocol botch
Pointers?
-Steve
next reply other threads:[~2004-03-29 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 22:02 plan9fans [this message]
2004-03-29 23:38 ` Geoff Collyer
2004-03-30 9:29 ` Xning Lee
2004-03-30 10:30 plan9fans
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=f1d0367d8c239b5063004f3b4cb3a884@snellwilcox.com \
--to=plan9fans@ntlworld.nospam.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).