IETF Logo Mail Archive

Re: how to access jabber log now?

Benjamin Kaduk <kaduk@mit.edu> Fri, 16 August 2019 17:47 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C6121200F4 for <wgchairs@ietfa.amsl.com>; Fri, 16 Aug 2019 10:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Op3emN1npYMj for <wgchairs@ietfa.amsl.com>; Fri, 16 Aug 2019 10:47:39 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 670251200D5 for <wgchairs@ietf.org>; Fri, 16 Aug 2019 10:47:38 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x7GHlXXX006798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 16 Aug 2019 13:47:35 -0400
Date: Fri, 16 Aug 2019 12:47:32 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Kent Watsen <kent+ietf@watsen.net>
Cc: Working Group Chairs <wgchairs@ietf.org>, ietf@meetecho.com
Subject: Re: how to access jabber log now?
Message-ID: <20190816174732.GM88236@kduck.mit.edu>
References: <0100016c9b84f844-9dfabacb-362f-432e-ae3d-bfb305d0a469-000000@email.amazonses.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <0100016c9b84f844-9dfabacb-362f-432e-ae3d-bfb305d0a469-000000@email.amazonses.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/LM0qTSFoht_QsiTNt1wQnLY4gPA>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2019 17:47:41 -0000

On Fri, Aug 16, 2019 at 05:41:18PM +0000, Kent Watsen wrote:
> 
> I'm working on the minutes.
> 
> At one point in the audio (YouTube video), a Jabber question or comment was read into the mic, but the reader/speaker was facing their computer more so than the mic and therefore the audio recording didn't pickup the Jabber question/comment.  I suppose this is a case for taking a snapshot of the Jabber log at the end of the meeting but, given that wasn't done, what options exist now?
> 
> I tried http://www.meetecho.com/ietf105/netmod <http://www.meetecho.com/ietf105/netmod>, but the connection times out ("viger.conf.meetecho.com took too long to respond.").  Does MeetEcho have a retention policy?  Are the Jabber log retained there at all?

The jabber logs are retained on the IETF infrastructure; e.g.,
https://www.ietf.org/jabber/logs/dots/2019-07-24.html .  (I trust you can
map dates and WG names appropriately.)

-Ben

v2.23.0 | Report a Bug | By Email