From nobody Mon Sep 15 12:33:18 2025 X-Original-To: freebsd-pkg@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4cQPb952t8z67JMV for ; Mon, 15 Sep 2025 12:33:41 +0000 (UTC) (envelope-from sblachmann@gmail.com) Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4cQPb94XfFz49YF for ; Mon, 15 Sep 2025 12:33:41 +0000 (UTC) (envelope-from sblachmann@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-b0428b537e5so561450166b.3 for ; Mon, 15 Sep 2025 05:33:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1757939610; x=1758544410; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=IhilvcoN2oMYzQjNg6oJ7z+S+EeeBmFw9tk+r7ML0Ss=; b=KO+iJqjYpWclF1Wsr4gErRw26KaoxEYkIGReva4MW5pNBf5d/e3NmoaW0sljA97r0S 8fGxecgo7+os43lg7rK39vqI18cRSSYloAb18rXr9JcLKq0QEkigi7XDiDlC+1pJueFU OEJljXZSbAge8Cy2xjWzTSLctBh/dsDgaWacy83SFnsSUTuzNcVV3OhmtyzBWXZk+lam mq/vJdtd86O0Hi2P1GKrptLtb/6MXi7Gn1IEoc/asE3mAF90EPZ2Cx4ss3HAd2fwRQii MR45/c8kN5pVPIA18dravC+ffOxXj0J9oG6AxhCNXplL+4ZS6cGVb+YC7tGJ9qU7+8sX iojw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1757939610; x=1758544410; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=IhilvcoN2oMYzQjNg6oJ7z+S+EeeBmFw9tk+r7ML0Ss=; b=nRgsZhDbuA0MJvB9GERkyxHT8oIdRJysZ4RARgOM1tTYvviYgf6M4DsLMPG5KElbQZ BYuPC8OdM1NGF7vPnz+i7o/GDgX1XxKhPB8maONWCI/QdFe+rR9O735ZSQ/180q5UgJU r9fNFKSJ7x+9CLKhVQ+GiY5DFMlS5cSWpz1k6RX7GbF9bUhpX+F3UbOkqKefb1rDlgnJ SZYCPqqUmxhtkq2DQxHKBGMJpz8XKXw/wIOaZx5f3L/TjMQ+882hh3GCR69F2aICAr2O //KC+2HY53AF80fptRXhN1WOIFfBIAYiMtL4l7jScri9mHZzfyzb6pfTDFMGcw6Fi8Cl GAyA== X-Forwarded-Encrypted: i=1; AJvYcCVFqudITnL5qON2vp+oPZUZXdF5vScQ7+NItlwF/CuHmmFsgfw74BKGKiBxfoe/+gog1vNUfFpu7YeG8w==@freebsd.org X-Gm-Message-State: AOJu0YzwULOUTS3ixxukdmA3WlZLxaaiMZPTdeuNe56jHbSSnoY1mZu7 51IpsAii9adJRJlI30dfnZEluYxxCPLyoJTqlZGGkB5v7GEvd/NsnRc85BAAboDD88TT7gCO0so b4ABTwGMNL/hNBExAkvLSDpGn5+WsnYE= X-Gm-Gg: ASbGncvYVCh+jxBHnPhd7dRj8d+xLnxoi4DbeFzAP1aA/Cq39D+HHodI/mXVdhyYcd8 NQCLiOIjgGmBCMbDl7eE+zNEEJM/As9EqrIMQTDWW5JygSJCfn3c9U3glgFqhruUSmqlgtbEhNn CjqWVPXB8evixiIUL35Pq0vaqGaPHAxv4voYz48GgywWsDC+d6DE+fOMVxHdmwTRWdXDAVvihuK 8nyzw== X-Google-Smtp-Source: AGHT+IEa0XBucpeQYCIqh7/0mw0E6FWctqmTeWYYZVw2TYKiH0Flp0Ugz6VtDngZY+1cpsyJmJ79HuBtQpSHe0nLFIM= X-Received: by 2002:a17:907:3e29:b0:b04:1a1c:cb5f with SMTP id a640c23a62f3a-b07c381fe3emr1368718066b.33.1757939610267; Mon, 15 Sep 2025 05:33:30 -0700 (PDT) List-Id: Binary package management and package tools discussion List-Archive: https://lists.freebsd.org/archives/freebsd-pkg List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkg@FreeBSD.org MIME-Version: 1.0 References: <7AB42872-8CF9-4730-BDDA-0BE0B6507FE9.ref@yahoo.com> <7AB42872-8CF9-4730-BDDA-0BE0B6507FE9@yahoo.com> In-Reply-To: <7AB42872-8CF9-4730-BDDA-0BE0B6507FE9@yahoo.com> From: Stefan Blachmann Date: Mon, 15 Sep 2025 14:33:18 +0200 X-Gm-Features: AS18NWD49bPDtTbrvTsNNNiACL017oDmr4TdchPMTWHVVOPqqXq4RCQJtuJPko8 Message-ID: Subject: Re: I've got a pkg 2.3.1 "pkg-static autoremove" that has grown to have over 1 GiByte of RAM resident after more than 77 minutes of cpu time To: Mark Millard Cc: FreeBSD-pkgbase@freebsd.org, FreeBSD-pkg@freebsd.org, Baptiste Daroussin Content-Type: multipart/alternative; boundary="00000000000001b665063ed63686" X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4cQPb94XfFz49YF --00000000000001b665063ed63686 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Unfortunately, I have to confirm your observation, but on 14.3-RELEASE-p2 on amd64. As pkg's curl fetcher seems buggy beyond repair, the only way to finish the installation of a planned FreeBSD small server farm seems to use pkg's stdio/file methods. To save the project and avoid migration to Linux only because of this long-standing pkg bug "pkg: An error occurred while fetching package: No error", which tends to appear unpredictably and is a real FreeBSD showstopper because when it appears first, from then on it appears always, I just set up a poudriere server with 20 cores at 3GHz and 256GB RAM. to make the repos available via NFS. Poudriere ran fine for a few minutes until it stopped for a loooong time. Maybe 20 minutes the machine's drives were quiet. No SSH output. Then I looked at the console, and top showed 5 or 6 pkg-static processes, each with between 99.97 and 100.x CPU load. Unfortunately, suddenly the machine awakened again from this pkg-static freeze, so I could not get a full ps listing with more information, or even a truss output. On Sun, Sep 14, 2025 at 6:39=E2=80=AFPM Mark Millard wr= ote: > [Some prior testing was also seeing such for pkg, not just pkg-static .] > > The context here is a armv7 chroot on an aarch64 system, > in case that turns out to matter. > > # pkg-static -v > 2.3.1 > > > For reference: > > load: 1.44 cmd: pkg-static 57217 [running] 4856.83r 4619.81u 2.24s 99% > 1056180k > > ..PID JID USERNAME PRI NICE SIZE RES STATE C TIME > CPU COMMAND > 57217 0 root 141 0 1096Mi 1038Mi CPU3 3 78:07 > 100.00% pkg-static autoremove > > The boot system: > > # uname -apKU > FreeBSD aarch64-main-pbase 16.0-CURRENT FreeBSD 16.0-CURRENT > main-n280292-3c60ea77649d GENERIC-NODEBUG arm64 aarch64 1600000 1600000 > > Inside the chroot: > > # uname -apKU > FreeBSD aarch64-main-pbase 16.0-CURRENT FreeBSD 16.0-CURRENT > main-n280292-3c60ea77649d GENERIC-NODEBUG arm armv7 1600000 1600000 > > # truss -p 57217 > freebsd32_mmap(0x0,20480,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_AL= IGNED(12),-1,0x0) > =3D 926179328 (0x37346000) > freebsd32_mmap(0x0,20480,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_AL= IGNED(12),-1,0x0) > =3D 926199808 (0x3734b000) > freebsd32_mmap(0x0,4096,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_ALI= GNED(12),-1,0x0) > =3D 926220288 (0x37350000) > freebsd32_mmap(0x0,12288,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_AL= IGNED(12),-1,0x0) > =3D 926224384 (0x37351000) > freebsd32_mmap(0x0,4096,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_ALI= GNED(12),-1,0x0) > =3D 926236672 (0x37354000) > freebsd32_mmap(0x0,4096,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_ALI= GNED(12),-1,0x0) > =3D 926240768 (0x37355000) > freebsd32_mmap(0x0,20480,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_AL= IGNED(12),-1,0x0) > =3D 926244864 (0x37356000) > freebsd32_mmap(0x0,20480,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_AL= IGNED(12),-1,0x0) > =3D 926265344 (0x3735b000) > freebsd32_mmap(0x0,12288,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_AL= IGNED(12),-1,0x0) > =3D 926285824 (0x37360000) > freebsd32_mmap(0x0,20480,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_AL= IGNED(12),-1,0x0) > =3D 926298112 (0x37363000) > freebsd32_mmap(0x0,12288,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_AL= IGNED(12),-1,0x0) > =3D 926318592 (0x37368000) > freebsd32_mmap(0x0,28672,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_AL= IGNED(12),-1,0x0) > =3D 926330880 (0x3736b000) > freebsd32_mmap(0x0,20480,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_AL= IGNED(12),-1,0x0) > =3D 926359552 (0x37372000) > freebsd32_mmap(0x0,4096,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON|MAP_ALI= GNED(12),-1,0x0) > =3D 926380032 (0x37377000) > . . . > > No other activity reported by truss, other than freebsd32_mmap use, > at least for what i looked at. > > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > > --00000000000001b665063ed63686 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Unfortunately, I have to confirm your observation, bu= t on 14.3-RELEASE-p2 on amd64.

As pkg's curl fetcher seems buggy beyond repair,=C2=A0the only way to fin= ish=20 the installation of a planned FreeBSD small=C2=A0 server farm seems to use= =20 pkg's stdio/file methods.
To save the project and= =20 avoid migration to Linux only because of this long-standing pkg bug=C2=A0= =20 "pkg: An error occurred while fetching package: No error", which = tends=20 to appear unpredictably and is a real FreeBSD showstopper because when=20 it appears first, from then on it appears always, I just set up a=20 poudriere server with 20 cores at 3GHz and 256GB RAM. to make the repos=20 available via NFS.

Poudriere ran fine for a few mi= nutes until it stopped for a loooong time.
Maybe 20 minutes the m= achine's drives were quiet. No SSH output.
Then I looked at t= he console, and top showed 5 or 6 pkg-static processes, each=C2=A0with=C2= =A0between 99.97 and 100.x CPU load.
Unfortunately, suddenly the machine awakened again from this pkg-static freeze, so I=20 could not get a full ps listing with more information, or even a truss=20 output.


On Sun, Sep 14, 2025 at 6:39=E2=80= =AFPM Mark Millard <marklmi@yahoo.c= om> wrote:
yahoo.com


--00000000000001b665063ed63686--