9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: yan cui <ccuiyyan@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [GSOC] auth server: connection refused
Date: Fri, 23 May 2014 00:42:52 -0400	[thread overview]
Message-ID: <CAAVq3rm05D5BOJc7DLRadz5CF9djS6u4b=m7ZZoo9qrbY49Jqg@mail.gmail.com> (raw)
In-Reply-To: <CAAVq3rmrUnDE1zS5mrs5+F--V9Z+XfzsZVdm1Qe5Wds59751ww@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]

Finally got the reason, I execute a command exec rio at the end of
/cfg/$sysname/cpurc, which turns out the reason of blocking drawterm,
although do not know the detailed reason. Sorry for the noise.


2014-05-22 23:24 GMT-04:00 yan cui <ccuiyyan@gmail.com>:

> Hi all,
>
>    I encountered an error when connecting drawterm with cpu/auth server.
> Basically, I use
> drawterm -c super -a super -u bootes
> but it turns out an error,
> cpu: can't dial: super: Connection refused
> goodbye
>
> on the plan9 cpu/auth server, I type auth/debug, it outputs
> p9sk1 key: proto=p9sk1 user=bootes dom=cuiy.net !hex? !password?
>       dialing auth server net!super!ticket
>       cannot dial auth server: connection refused
>       csquery authdom=cuiy.net auth=super
>
> I also type cpu -h super on the auth/cpu server, the error is the same
> with drawterm:
> cpu: can't dail: super: connection refused
>
> I set up the auth/cpu server according to plan9 wiki,
> http://plan9.bell-labs.com/wiki/plan9/configuring_a_standalone_cpu_server/
>
> Followings are my /lib/ndb/local config.
> Any suggestions or comments are welcome!
>
> #
> #  files comprising the database, use as many as you like, see ndb(6)
> #
> database=
>     file=/lib/ndb/local
>     file=/lib/ndb/common
> #    file=/lib/ndb/auth
>
> auth=sources.cs.bell-labs.com authdom=outside.plan9.bell-labs.com
>
> ipnet=cuiy ip=192.168.122.0 ipmask=255.255.255.0
>     auth=super
>     cpu=super
>     fs=super
>     ntp=128.59.22.30
>     dns=192.168.122.1
>     ipgw=192.168.122.1
>     authdom=cuiy.net
>     dnsdom=cuiy.net
>
> ip=192.168.122.71 sys=super dom=cuiy.net
>
> #
> #  because the public demands the name localsource
> #
> ip=127.0.0.1 sys=localhost dom=localhost
>
> --
> Think big; Dream impossible; Make it happen.
>



--
Think big; Dream impossible; Make it happen.

[-- Attachment #2: Type: text/html, Size: 3670 bytes --]

  reply	other threads:[~2014-05-23  4:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23  3:24 yan cui
2014-05-23  4:42 ` yan cui [this message]
2014-05-23  7:17   ` Charles Forsyth
2014-05-23 18:25     ` yan cui
2014-05-23 18:29       ` erik quanstrom
2014-05-23 19:44         ` Steve Simon
2014-05-23 19:49           ` erik quanstrom
2014-05-23  3:26 yan cui

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='CAAVq3rm05D5BOJc7DLRadz5CF9djS6u4b=m7ZZoo9qrbY49Jqg@mail.gmail.com' \
    --to=ccuiyyan@gmail.com \
    --cc=9fans@9fans.net \
    /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).