Re: [codesprints] Problems updating from IETF 116

Jim Fenton <fenton@bluepopcorn.net> Fri, 21 July 2023 21:00 UTC

Return-Path: <fenton@bluepopcorn.net>
X-Original-To: codesprints@ietfa.amsl.com
Delivered-To: codesprints@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27696C13AE25 for <codesprints@ietfa.amsl.com>; Fri, 21 Jul 2023 14:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mu8jWlD_LKuP for <codesprints@ietfa.amsl.com>; Fri, 21 Jul 2023 14:00:31 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB7A3C13AE36 for <codesprints@ietf.org>; Fri, 21 Jul 2023 14:00:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=CcAue0tdI1dbRRx6qMsmbBvsds0VkYuE3p5AOUOCgGo=; b=p93UJeAMDH5SCSBfYn0ViMOxw7 7fU3uZ9MBSRqeIkqwP2Z8lODegAmdWkKdvbRI+jr1q2Q+YgkPMQEbACjouE4zfPAUav/RE73mL2fG jx26g9oJAUxzOYtw1Lgx/UWfWDKzS5ZOaa9mWn0QEcISip/N7RemWh3Fj9eCVrKcemfg=;
Received: from [2601:647:6880:ac1:85a3:135:b1bf:8a3c] (helo=[10.10.20.192]) by v2.bluepopcorn.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <fenton@bluepopcorn.net>) id 1qMxEW-0004mG-S5; Fri, 21 Jul 2023 14:00:21 -0700
From: Jim Fenton <fenton@bluepopcorn.net>
To: Kesara Rathnayake <kesara@staff.ietf.org>
Cc: Lars Eggert <lars@eggert.org>, codesprints@ietf.org
Date: Fri, 21 Jul 2023 14:00:21 -0700
X-Mailer: MailMate (1.14r5852)
Message-ID: <1AF7F1C2-6617-46F7-86DF-0019A136EBE5@bluepopcorn.net>
In-Reply-To: <8B384813-03A8-4207-A7B8-A2D8D0091C84@staff.ietf.org>
References: <BF526F2E-6FB2-4B0D-9541-415BD5484979@eggert.org> <8B384813-03A8-4207-A7B8-A2D8D0091C84@staff.ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_DA4A1F7A-A503-4DD4-8D3F-89579D61DCB0_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"plain":[622, 732], "uuid":"4BFB4977-5222-4511-86B1-3EE9B5DC7FE4"}]
Archived-At: <https://mailarchive.ietf.org/arch/msg/codesprints/NXkBqIUtU5_w3s6AMDWqo4Ma-QM>
Subject: Re: [codesprints] Problems updating from IETF 116
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codesprints>, <mailto:codesprints-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/codesprints/>
List-Post: <mailto:codesprints@ietf.org>
List-Help: <mailto:codesprints-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codesprints>, <mailto:codesprints-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2023 21:00:35 -0000

Thanks for both suggestions. Increasing the storage in the Docker 
settings did the trick, although I might try prune as well.

Now getting a different error trying to connect to the database:

```
psycopg2.OperationalError: connection to server at "db" (172.20.0.2), 
port 5432 failed: Connection refused
	Is the server running on that host and accepting TCP/IP connections?
```

I notice that what’s running in data tracker is called ‘db-1’. Is 
that perhaps the problem, or is there a setting somewhere to set the IP 
address of the database, that I missed?

-Jim

On 21 Jul 2023, at 13:53, Kesara Rathnayake wrote:

> Running docker prune to clean up the system might help too.
> See https://docs.docker.com/engine/reference/commandline/system_prune/
>   —Kesara
>
> Sent from my ☎️
>
>> On 22/07/2023, at 06:16, Lars Eggert <lars@eggert.org> wrote:
>>
>> On Jul 21, 2023, at 11:14, Lars Eggert <lars@eggert.org> wrote:
>>> What platform do you run docker on? At least on the Mac, docker runs 
>>> in a Linux VM, and you may need to give that VM more space (through 
>>> the docker settings.)
>>
>> See the part highlighted in blue:
>>
>> <Screenshot 2023-07-21 at 11.15.12.png>
>>
>>
>> Lars
>> _______________________________________________
>> codesprints mailing list
>> codesprints@ietf.org
>> https://www.ietf.org/mailman/listinfo/codesprints