From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] rimport error: tlsclient: auth_proxy: fauth_proxy start: too much activity
Date: Sat, 31 Mar 2018 05:15:24 +0200 [thread overview]
Message-ID: <9A3DADE4B19ABA96CAC21F6FBD19913D@felloff.net> (raw)
In-Reply-To: 55E7472CC2334EB2505A89AE2A0F5EE5@5ess.inri.net
too many auth procs spawned in factotum. it bounds the number of
processes to 16 and refuses to start another one. see:
/sys/src/cd/auth/factotum/fs.c:493:
static void
fsrpcio(Req *r)
{
Fsstate *fss;
Srv *srv;
fss = r->fid->aux;
srv = r->srv;
if(srv->sref.ref == 1 && srv->rref.ref > 16){
respond(r, "too much activity");
return;
}
srvrelease(srv);
qlock(fss);
if(r->ifcall.type == Tread)
rpcread(r);
else
rpcwrite(r);
qunlock(fss);
srvacquire(srv);
}
my guess is that factotum acts as a client and the auth server is
slow to respond? or theres a network issue?
factotum should eventually timeout the authserver communication.
--
cinap
next reply other threads:[~2018-03-31 3:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 3:15 cinap_lenrek [this message]
2018-03-31 3:31 ` Stanley Lieber
2018-03-31 3:55 cinap_lenrek
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=9A3DADE4B19ABA96CAC21F6FBD19913D@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/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).