9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] rimport error: tlsclient: auth_proxy: fauth_proxy start: too much activity
Date: Fri, 30 Mar 2018 23:31:02 -0400	[thread overview]
Message-ID: <4E866EE6-3A97-49AC-ACE4-1AC352A635DB@stanleylieber.com> (raw)
In-Reply-To: <9A3DADE4B19ABA96CAC21F6FBD19913D@felloff.net>

On Mar 30, 2018, at 11:15 PM, cinap_lenrek@felloff.net wrote:
> 
> 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.

The error shows up in my logging for my backup scripts, which runs a new rimport each time the script is run (several times per hour). It’s definitely plausible that there could be 16 or more firing off at more or less the same time, all backed by the same factotum acting as a client.

However, the backup script runs on the auth server, shared by all the machines involved.

sl




  reply	other threads:[~2018-03-31  3:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-31  3:15 cinap_lenrek
2018-03-31  3:31 ` Stanley Lieber [this message]
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=4E866EE6-3A97-49AC-ACE4-1AC352A635DB@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --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).