From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Bob Proulx Newsgroups: gmane.emacs.help Subject: Re: Mail posting in newsgroups in Gnus Date: Sun, 15 May 2016 16:25:17 -0600 Message-ID: <20160515160711053121293@bob.proulx.com> References: <87mvntj7wy.fsf@gnus.org> <83shxl6k3q.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1463351146 14315 80.91.229.3 (15 May 2016 22:25:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 15 May 2016 22:25:46 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon May 16 00:25:40 2016 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1b24Td-00022G-7y for geh-help-gnu-emacs@m.gmane.org; Mon, 16 May 2016 00:25:33 +0200 Original-Received: from localhost ([::1]:41620 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b24Tc-0006kQ-FJ for geh-help-gnu-emacs@m.gmane.org; Sun, 15 May 2016 18:25:32 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45289) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b24TT-0006iL-40 for help-gnu-emacs@gnu.org; Sun, 15 May 2016 18:25:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b24TO-0005zk-RW for help-gnu-emacs@gnu.org; Sun, 15 May 2016 18:25:21 -0400 Original-Received: from havoc.proulx.com ([96.88.95.61]:39758) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b24TO-0005zg-LO for help-gnu-emacs@gnu.org; Sun, 15 May 2016 18:25:18 -0400 Original-Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTP id F0912CA9 for ; Sun, 15 May 2016 16:25:17 -0600 (MDT) Original-Received: from hysteria.proulx.com (hysteria.proulx.com [192.168.230.119]) by joseki.proulx.com (Postfix) with ESMTP id 7AA0F21846 for ; Sun, 15 May 2016 16:25:17 -0600 (MDT) Original-Received: by hysteria.proulx.com (Postfix, from userid 1000) id 49D532DC49; Sun, 15 May 2016 16:25:17 -0600 (MDT) Mail-Followup-To: help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <83shxl6k3q.fsf@gnu.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 96.88.95.61 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:109965 Archived-At: Eli Zaretskii wrote: > Lars Magne Ingebrigtsen wrote: > > The gnu.org SMTP servers have been timing out on incoming mail for some > > people the last couple of days, whether you're posting through Gmane or > > not. But some seem to make it through, for some reason... > > > > Or perhaps it's just email from Norway? I wonder whether this one make > > it through... > > gnu.org machines have connectivity problems lately. I hope they will > be resolved soon. Since Friday the 6th there was a large move with various assorted related and unrelated changes. Which has made it difficult to tell what broke what. I am deep in the middle of *.savannah and can give the most information about it. The *.savannah.gnu.org machines moved to a different host server in the same data center. But their file systems got repackaged and the copy process had problems. 1) All of the system uids were mapped to the host used to do the copy. All of those had to be renamed back to their proper uids. Fixed that. 2) All of the ACLs were lost. This prevented the web team from being able to access files. Fixed that. 3) Swap was lost. Causing OOM activity. Fixed that. 4) Additionally a very new kernel from the host system was booted instead of the system one. That caused a subset of networking problems. The managed switch was reporting a continuous high rate of dropped packets. Reverting back to the system kernel fixed the switch's reports of dropped packets. 5) This happened late on a Friday without notice meaning that we had to scramble around over the weekend to find and fix the problems. 6) Long term there has been persistent problems with stuck connections to git, cvs, bzr, hg daemons. Since git is by far most popular we mostly hear about git problems but it happens with the others too. The stuck daemons stack up consuming slots until all of the xinetd slots are filled and it hits the limit at 100 processes running. At that point no new connections can be made. This has been made worse by the Friday network move. Something is now tickly this problem agressively. We are manually monitoring this and mitigating it by killing stale processes. We hope this to be fixed as soon as we can migrate onto the new operating sytsem VMs promised to us any day now for the last two years. On the same day the entire Boston FSF network was changed to a different network routing of which I know little. I don't have much visibility into this change. traceroute shows a different route now. This changed for every system. People are reporting many problems across all of the system. There are reports of differences seen between IPv4 and IPv6. Except for the stuck process problem I think the Savannah systems are running within nominal limits. It is "normal". For Savannah anyway. (Not to say things don't need fixing. But we are waiting in the pipeline for a new VM that we can migrate onto.) However all of the random network problems people are reporting include fencepost, eggs (mail relay), lists.gnu.org (mailing list), www.gnu.org, and many others. Those don't have anything in common except for the networking and all are suffering. If you are suffering problems I encourage a trouble report being made. Please include details. Say where from and where to. Say whether it was IPv4 or IPv6. Time the problem occurred. Then if later it works update and say that. Because one of the problems is that this seems worse from Europe than from the US. I in Colorado have a hard time triggering any problems. But I have been able to on occassion. But people in Europe have been most of the problem reports. Most of them have been using IPv6. And that is all I know. Bob