Re: [106attendees] Etherpad Issues - SOLVED
"Aaron Falk" <aaron.falk@gmail.com> Mon, 18 November 2019 02:16 UTC
Return-Path: <aaron.falk@gmail.com>
X-Original-To: 106attendees@ietfa.amsl.com
Delivered-To: 106attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D382120048 for <106attendees@ietfa.amsl.com>; Sun, 17 Nov 2019 18:16:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.754
X-Spam-Level:
X-Spam-Status: No, score=-0.754 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, NUMERIC_HTTP_ADDR=1.242, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bcjmcc2Yfgcw for <106attendees@ietfa.amsl.com>; Sun, 17 Nov 2019 18:16:34 -0800 (PST)
Received: from mail-pl1-x641.google.com (mail-pl1-x641.google.com [IPv6:2607:f8b0:4864:20::641]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFD8B12083E for <106attendees@ietf.org>; Sun, 17 Nov 2019 18:16:33 -0800 (PST)
Received: by mail-pl1-x641.google.com with SMTP id s10so8826644plp.2 for <106attendees@ietf.org>; Sun, 17 Nov 2019 18:16:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:embedded-html; bh=KUeTBncrsQCu8SH/NywenLMqIThgDfPnnuwMINS6p+s=; b=JjuCHprEy4WxiJ0Om0UD91VAZmYVkJ9Vfln7gKOHUt/AwGIb9JxpXpHqsmrdwbLBjY bLWRAJxKzWQ/bYqcnCo8XoWHeasgrmt+RB0SmvtlFZ7YHxwnzVsBdoDT9WH4OO1PTjRc gkBY1As1gtMHpskeVIkwy5E2ObW3MsSmasqmWQU8pLa4yvevgX14R8UW/C/RbsYEg7Qy LEbA7FMEE+HtTUxk9rg0zLbZcjdBYHsDF/3cndmmR0nXM0JB1hIy1ybUFX95O8IQt/+L cwUYh9UQgoHQFnz+qqwG19ShyRTUCDFD3ckV29Af+Ffn2mbEgSYr2RSCKGjf83vOr+MD A6Fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding:embedded-html; bh=KUeTBncrsQCu8SH/NywenLMqIThgDfPnnuwMINS6p+s=; b=W0cnqChWxJUW335PpZU+S2/LQs/U+wBBT4dBBx+QHR0mylXDO54/ZdThfldz2AwQ+u mGVsGrU0yIF8u1WShYOLIz0EHhwE7WjIVZ2toJuzzHG5UCIJjxBRmoqPjt6Al9ItOyZk ws34VxI9ytIc+HWtt1ffcklumWB2SWdyOPCyesnkx0ARaOqG6pQKuX1tF684H+TmgmVx /k8GRQEHteVDMqWMa/CR8izEDoAb0MV9k4TDcLiP6DWSkPperr1axTkX/5QRq4GXXFI2 w4pUOXe+WefNI0Cz3Ed7KT8uZNJS5vpxqFErL5yJzH5bwbfXioOdLiC5xIsdTYJG1FB3 Y8iA==
X-Gm-Message-State: APjAAAVV+llBHpkCKS09D/jnkxqSFl1bdAtMlHTXWq0cND8WkkNbf3SZ 77PIFs7PVOXI2RW/r69C8fg=
X-Google-Smtp-Source: APXvYqzYnB724beO5oOqLGjJtx4RrWR3tgEgyxvmDtfQ/AvMPho1LhbMwNohFOvs2jjLnH2V9tHcww==
X-Received: by 2002:a17:902:d891:: with SMTP id b17mr27238649plz.256.1574043393246; Sun, 17 Nov 2019 18:16:33 -0800 (PST)
Received: from [172.19.217.89] ([2001:67c:370:128:a9d3:73e9:5a0f:be2c]) by smtp.gmail.com with ESMTPSA id b5sm19610282pfp.149.2019.11.17.18.16.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 17 Nov 2019 18:16:32 -0800 (PST)
From: Aaron Falk <aaron.falk@gmail.com>
To: Robert Sparks <rjsparks@nostrum.com>
Cc: Glen <glen@amsl.com>, Henrik Levkowetz <henrik@levkowetz.com>, 106 attendees <106attendees@ietf.org>
Date: Mon, 18 Nov 2019 10:16:26 +0800
X-Mailer: MailMate (1.13r5655)
Message-ID: <2FCD2E1F-6DF6-4823-9F04-8D92DB4179D3@gmail.com>
In-Reply-To: <3bf96b20-a02a-e32a-0b42-ced987c7a7c7@nostrum.com>
References: <CABL0ig4Tk8dpzFK+gyYrtuZ5Rk4cVXStoB1YNRkVMyX9xcOC5A@mail.gmail.com> <3bf96b20-a02a-e32a-0b42-ced987c7a7c7@nostrum.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_E9D5BB04-1986-4905-90D4-287B8507EA1D_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"HTML":[496, 5979], "plain":[165, 3720], "uuid":"0098DD0A-53B3-4C35-A2EF-1D7ADA7F21D6"}]
Archived-At: <https://mailarchive.ietf.org/arch/msg/106attendees/jK1zO6701F6HbISXUsj3-0aYjZI>
Subject: Re: [106attendees] Etherpad Issues - SOLVED
X-BeenThere: 106attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list of all 106 attendees for official communication <106attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/106attendees>, <mailto:106attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/106attendees/>
List-Post: <mailto:106attendees@ietf.org>
List-Help: <mailto:106attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/106attendees>, <mailto:106attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2019 02:16:36 -0000
Thanks, Robert. Cc’ing 106attendees to head off other NOC tickets as Etherpad is working as expected. --aaron On 18 Nov 2019, at 10:10, Robert Sparks wrote: > Hi Aaron - > > Here is a little detail on why the etherpads are showing an IP address > as a workaround for the moment. > > RjS > > > > -------- Forwarded Message -------- > Subject: Etherpad Issues - SOLVED > Date: Sat, 16 Nov 2019 20:03:38 -0800 > From: Glen <glen@amsl.com> > To: Lou Berger <lberger@labn.net>, Russ Housley > <housley@vigilsec.com>, Henrik Levkowetz <henrik@levkowetz.com>, > Robert Sparks <rjsparks@nostrum.com>, Tero Kivinen <kivinen@iki.fi> > > > > Lou/Tero - > > Very short version: It's working now. Quit your browser COMPLETELY > and retry. > > All - > > Lou and Tero have both reported problems with Etherpad, in which users > on Etherpad were getting constant "reconnecting" messages, and the > system was not recording their text or changes. I confirmed that the > same thing was happening for me from here in California. > > I initially thought that the system had been set up incorrectly - the > configuration was not in accordance with the instructions online - but > even trying other documented configurations did not solve this > problem, and Alexa informed me that this worked at previous meetings. > > I've spent several hours on this, and the problem appears to be in > Apache. Etherpad is set up as a Proxy destination from Apache, which > means Apache stores and forwards data from the web to Etherpad. Over > the course of the last number of months, we've added lots of other > proxying to Apache, for Wagtail and for other sites and systems, and I > can only speculate that we've changed something in Apache that has > broken this. > > And the biggest clue: If you access Etherpad directly, without going > through Apache, it works great. Fast, responsive, no problems. The > problem exists only when we proxy through Apache. > > I've tried downloading and building the latest version of Etherpad - > alas, it too works great on its on - and horribly when proxied through > Apache. > > Moreover, Googling around for this problem seems to result in lots of > statements like "Apache is horrible at proxying, you should use > [Nginx|Litehttp|some other web server] - anything but Apache!" > followed by a complete lack of solution to this issue. I get that > this was working before; on the other hand, it seems that *many* users > globally are experiencing the same issue with Apache proxying, and > given the changes we've made recently, I would want to poke there > next. > > I'm confident that I could fix this if I had the luxury of scheduled > downtime; but the problem is I can't "work on" Apache without throwing > everything offline. Every time I try to apply a change to Apache, > there is a 60-90 second interruption as it reloads or restarts, and > this causes problems not only for the attendees generally, but > especially for the registration desk. I've already interrupted them > four times, and that's all they can take. > > So, I consulted briefly with Henrik, who agreed with my approach, > which is that I've now exposed Etherpad via IP address and port number > (a nonstandard port, just to prevent scan attacks) to the world > directly... and I've put in a redirect, so that, for example, when I > go to: > > https://etherpad.ietf.org/p/Glen > > I get redirected to: > > http://4.31.198.44:9009/p/Glen > > And can then use Etherpad seamlessly. > > Lou - I'm sorry I don't have a more elegant solution here, but this > solves the problem, and should get you and everyone online. In the > near future we have a major server/OS upgrade coming, and I'm hopeful > that we can make this elegant again after that. > > For now, this should get you both - and everyone else - online and > working again. > > Thanks for your patience as we got this sorted out. > > Glen
- Re: [106attendees] Etherpad Issues - SOLVED Aaron Falk