From: Moroo Jun <moroo@nifty.com>
To: 9fans@cse.psu.edu
Subject: [9fans] rx problem on cpu/auth standalone machine
Date: Sun, 12 Jan 2003 17:29:19 +0900 [thread overview]
Message-ID: <F268F48C-2607-11D7-9A52-0050E4504768@nifty.com> (raw)
My plan9 box(named tp560x) is a standalone cpu/auth server.
After updating Plan9, upas cron left error logs on /sys/log/cron as
follows.
tp560x Jan 12 10:01:15 upas: can't call tp560x: connection refused
So I cheked rx command logged in as upas.
tp560x# rx tp560x ls
rx: auth_proxy: auth_proxy rpc write: bootes: bad key
/sys/log/auth logged as follows.
tp560x Jan 12 02:31:07 tr-fail upas@bootes(192.168.1.32) -> upas@bootes
no speaks for
tp560x Jan 12 02:31:07 tr-ok upas@bootes(192.168.1.32) -> upas@bootes
At this time, /mnt/factotum/log says,
cpu% cat /mnt/factotum/log
13: no key matches proto=p9sk1 role=server dom?
13: failure no key matches proto=p9sk1 role=server dom?
12: failure upas can't use bootes's keys
12: failure bad key
I reset password and users likes as Plan9 Wiki page.
http://cm.bell-
labs.com/wiki/plan9/Configuring_a_standalone_CPU_server/index.html
But no luck.
Cron commands by bootes and rx commad from bootes works fine.
Where should I check?
Thank you.
next reply other threads:[~2003-01-12 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 8:29 Moroo Jun [this message]
2003-01-13 17:14 ` Russ Cox
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=F268F48C-2607-11D7-9A52-0050E4504768@nifty.com \
--to=moroo@nifty.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).