From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v482) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Moroo Jun To: 9fans@cse.psu.edu Content-Transfer-Encoding: 7bit Message-Id: Subject: [9fans] rx problem on cpu/auth standalone machine Date: Sun, 12 Jan 2003 17:29:19 +0900 Topicbox-Message-UUID: 3fd06796-eacb-11e9-9e20-41e7f4b1d025 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.