Date: Thu, 6 Nov 2014 13:47:45 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: =?ISO-8859-15?Q?Juan_Ram=F3n_Molina_Menor?= <listjm@club-internet.fr> Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Status of svnlite(1) in make.conf(5) Message-ID: <alpine.BSF.2.11.1411061344260.10314@wonkity.com> In-Reply-To: <545B8BCB.9040106@club-internet.fr> References: <545B5707.20300@club-internet.fr> <alpine.BSF.2.11.1411060738080.10645@wonkity.com> <545B8BCB.9040106@club-internet.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 6 Nov 2014, Juan Ramón Molina Menor wrote: >>> Can I help somehow? It?s not only the man page which needs a fix, but >>> maybe also /Makefile.inc1: >>> https://svnweb.freebsd.org/base/head/Makefile.inc1?revision=273755&view=markup#l122 >>> >> >> A PR with patch to fix all the files would be the best. A list of the >> files to change and changes to be made is probably just as difficult to >> create, but would also work. > > For the man page, I?ll try to find time to follow the "FreeBSD Documentation > Project Primer for New Contributors", even if it seems quite daunting. Much of the FDP Primer does not apply to man pages. I or others can help with the markup (contact me off-list if you like), it's the actual content that's important. > For the make infrastructure, I?m quite sure I won?t be able to fulfil the > task, but I?ll try too. Pointing out what is wrong with the current implementation is good enough. From owner-freebsd-stable@FreeBSD.ORG Fri Nov 7 08:57:04 2014 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7DE5E4B7 for <stable@freebsd.org>; Fri, 7 Nov 2014 08:57:04 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 40A4BF26 for <stable@freebsd.org>; Fri, 7 Nov 2014 08:57:03 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <ronald-lists@klop.ws>) id 1Xmf6E-0000re-7V; Fri, 07 Nov 2014 09:40:59 +0100 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: stable@freebsd.org, "Pete French" <petefrench@ingresso.co.uk> Subject: Re: Advice on an odd networking problem References: <E1Xm5Ex-0008RQ-Jm@dilbert.ingresso.co.uk> Date: Fri, 07 Nov 2014 09:40:52 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" <ronald-lists@klop.ws> Message-ID: <op.xox42e0dkndu52@ronaldradial.radialsg.local> In-Reply-To: <E1Xm5Ex-0008RQ-Jm@dilbert.ingresso.co.uk> User-Agent: Opera Mail/12.17 (Win32) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.3.1 X-Scan-Signature: 12f61b0c8dc8dcc8c992b8e1fde77987 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>; List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 07 Nov 2014 08:57:04 -0000 On Wed, 05 Nov 2014 19:23:31 +0100, Pete French <petefrench@ingresso.co.uk> wrote: > I have some ouzzling behaviour here - looks very much like > I am running out of network resources of some kind, but I cant find > out what, so am wondering if anyone has any ideas. > > All machines are running FreeBSD 9.2-STABLE r265427 - which is from > the start of May (probbaly around heartbleed time!) > > We have 5 machines running webservers - apache24 serving cgi scripts, > plyus nginx being used to drive uwsgi with some django/python based > code. These are load balanced by pound on a machine which faces > the internet. This all works as expected, except that if I modify > the cgi-scripts running inside Apache so they make some https > calls to the nginx server on 127.0.0.1 then what we see is that > pound then stops being able to connect to Apache for a proportion > of its calls - its returns 503's. > > The effect on the calls which fail are as if the webserver is > not listening anymore. But this only applies to a fraction of > the calls - most get through. If I disable the cuntionality > which makes the intrenal call to 127.0.0.1 then the problem > goes away. > > It looks to me like I am runing out of some network resource somwhow, > but the load is very very low, and I cant see any obvious parameters > hitting their limits. Nothing is looged out of the ordinary on > the webservers, the only symptoom is the load balancer not being > able to connect. > > Does anyone have any ideas where to look for a solution ? It is > puzzling the hell out of me! > > -pete. Do the https calls to nginx succeed? I can imagine that the https certificate is not valid on 127.0.0.1 and fetch/curl/wget asks for confirmation or something like that. Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.11.1411061344260.10314>