From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from duke.felloff.net ([216.126.196.34]) by ewsd; Fri Mar 30 23:15:31 EDT 2018
Message-ID: <9A3DADE4B19ABA96CAC21F6FBD19913D@felloff.net>
Date: Sat, 31 Mar 2018 05:15:24 +0200
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] rimport error: tlsclient: auth_proxy: fauth_proxy start: too much activity
In-Reply-To: 55E7472CC2334EB2505A89AE2A0F5EE5@5ess.inri.net
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: structured transactional template strategy event 

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