From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] runq says error
Date: Mon, 16 Sep 2002 08:29:23 -0400 [thread overview]
Message-ID: <45201199e36a5b04f788c78e795f9ce2@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
cron is trying to call another system (or the same one) to run
runq. The authentication is failing. It looks like cron and rexexec
are out of date. Do you have a current version of
/sys/src/cmd/ip/rexexec.c and its corresponding binary installed?
Ditto with /sys/src/cmd/auth/cron.c? I know that I updated one
before the other and that for a while they where out of sync.
[-- Attachment #2: Type: message/rfc822, Size: 2100 bytes --]
From: Moroo Jun <moroo@nifty.com>
To: 9fans@cse.psu.edu
Subject: [9fans] runq says error
Date: Mon, 16 Sep 2002 10:55:47 +0900
Message-ID: <6B3E0BFE-C917-11D6-B8C7-0050E4504768@nifty.com>
I tried to install mail server on cpu/auth server(named myplan9).
Receiving mail and sending mail looks fine. But runq said error.
In /sys/log/cron:
myplan9 Sep 13 10:31:37 upas: called /bin/upas/runq -a /mail/queue
/mail/lib/remotemail on myplan9
myplan9 Sep 13 10:31:37 upas: can't authenticate for /bin/upas/runq -a
/mail/queue /mail/lib/remotemail on myplan9: auth_proxy rpc write:
\x01bootes: protocol phase error: read in state SNeedTicket
I set up upas password on myplan9. auth log:
myplan9 Sep 13 09:58:18 user upas installed for plan 9
myplan9 Sep 13 10:35:40 cr-ok upas@bootes(192.168.1.32)
Where should I check or correct?
next reply other threads:[~2002-09-16 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 12:29 presotto [this message]
2002-09-16 14:44 ` Moroo Jun
-- strict thread matches above, loose matches on Subject: below --
2002-09-16 1:55 Moroo Jun
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=45201199e36a5b04f788c78e795f9ce2@plan9.bell-labs.com \
--to=presotto@plan9.bell-labs.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).