9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
* [9fans] runq says error
@ 2002-09-16  1:55 Moroo Jun
  0 siblings, 0 replies; 3+ messages in thread
From: Moroo Jun @ 2002-09-16  1:55 UTC (permalink / raw)
  To: 9fans

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?



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [9fans] runq says error
  2002-09-16 12:29 presotto
@ 2002-09-16 14:44 ` Moroo Jun
  0 siblings, 0 replies; 3+ messages in thread
From: Moroo Jun @ 2002-09-16 14:44 UTC (permalink / raw)
  To: 9fans

On 2002.09.16, at 21:29, presotto@plan9.bell-labs.com wrote:
> 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 updated by replica. After that cron looks fine.

cpu% md5sum /sys/src/cmd/ip/rexexec.c
5bd6a86976370003bc87f8dcc610d25d        /sys/src/cmd/ip/rexexec.c
cpu% ls -l /sys/src/cmd/ip/rexexec.c
--rw-rw-r-- M 54 sys sys 740 Jun 29 19:25 /sys/src/cmd/ip/rexexec.c
cpu% md5sum /bin/ip/rexexec
a341b933487e129063a7c698c6f09e6a        /bin/ip/rexexec
cpu% md5sum  /sys/src/cmd/auth/cron.c
51a567a06aac7bfe4d6e274585c74188        /sys/src/cmd/auth/cron.c
cpu% ls -l /sys/src/cmd/auth/cron.c
--rw-rw-r-- M 54 sys sys 11010 Jun 29 08:04 /sys/src/cmd/auth/cron.c
cpu% md5sum /bin/auth/cron
b175305f972563af91aea52a5c8c4169        /bin/auth/cron

Thank you.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [9fans] runq says error
@ 2002-09-16 12:29 presotto
  2002-09-16 14:44 ` Moroo Jun
  0 siblings, 1 reply; 3+ messages in thread
From: presotto @ 2002-09-16 12:29 UTC (permalink / raw)
  To: 9fans

[-- 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?

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-09-16 14:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-09-16  1:55 [9fans] runq says error Moroo Jun
2002-09-16 12:29 presotto
2002-09-16 14:44 ` Moroo Jun

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).