pkg-1.21.0: after upgrade 1.20.9_1 -> 1.21.0: pkg core dumps on specific ports

[Rainer Hurling]

Hello,
after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 on CURRENT and
www/apache24
databases/redis
pkg core dumps while performing installation. apache24 and redis are ports I realized this
misbehaviour on ALL 14-STABLE and CURRENT boxes (both OS variants latest builds, i.e. FreeBSD
15.0-CURRENT #32 main-n269135-da2b732288c7: Fri Apr 5 20:30:39 CEST 2024 amd64).
After some updates on a poudriere builder (CURRENT base host, 14.0-RELENG jail with poudriere)
building packages for 14.0-RELENG, I observed the same behaviour when updating packages on
target hosts where pkg is first updated, on those hosts, nextcloud-server and icinga2 host
utilizing also databases/redis and www/apache24, pkg fails the same way.
I do not dare to update our poudriere hosts since the problem seems to pop up when pkg 1.21.0
is installed, no matter whether I use poudriere built ports (from our own builder hosts) or
recent source tree with portmaster/make build process.
Looks like a serious bug to me and not a site/user specific problem. Hopefully others do
realize the same ...
Thanks in advance,
oh

Hmm, I just tried to reproduce that. Both ports mentioned,
databases/redis and www/apache24, can be built and installed with
Portmaster. The box is a 15.0-CURRENT with pkg-1.21.0.

Maybe 'pkg check -Bn' or 'portmaster --check-depends --check-port-dbdir'
show some inconsistencies?

Best wishes,
Rainer



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[FreeBSD User]

Am Sat, 6 Apr 2024 09:05:00 +0200

Hello,
after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 on CURRENT and
www/apache24
databases/redis
pkg core dumps while performing installation. apache24 and redis are ports I realized this
misbehaviour on ALL 14-STABLE and CURRENT boxes (both OS variants latest builds, i.e. FreeBSD
15.0-CURRENT #32 main-n269135-da2b732288c7: Fri Apr 5 20:30:39 CEST 2024 amd64).
After some updates on a poudriere builder (CURRENT base host, 14.0-RELENG jail with
poudriere) building packages for 14.0-RELENG, I observed the same behaviour when updating
packages on target hosts where pkg is first updated, on those hosts, nextcloud-server and
icinga2 host utilizing also databases/redis and www/apache24, pkg fails the same way.
I do not dare to update our poudriere hosts since the problem seems to pop up when pkg 1.21.0
is installed, no matter whether I use poudriere built ports (from our own builder hosts) or
recent source tree with portmaster/make build process.
Looks like a serious bug to me and not a site/user specific problem. Hopefully others do
realize the same ...
Thanks in advance,
oh

Hello,

after following a recommnedation checking dependencies on ports via pkg check -Bn, recompiling
pkg via "portmaster -df ports-mgmt/pkg" along with all ports found by the check command as
well a sqlite (precaustion), still the pkg-static binary drops core dumps on some ports.

Phenomenon: When updating existing ports, like

www/apache24
databases/redis
net/openldap26-server
misc/e2fsprogs-libuuid

building the port runs smootly, but pkg-static dies on deleting attempt of the
old/to-be-reinstalled port. The problem arises by using portmaster as well as performing "make
install/make deinstall" in the specific target port.

Last port I hit is misc/e2fsprogs-libuuid.

My skills debugging core dumps are rather limited, our boxes do have debugging disabled. Since
the problem spreads across several hosts running CURRENT (same IcyBridge CPU generation, but
one host most recent CURRENT with LLVM18, the other one running a CURRENT compiled 4 days ago
and as of last week the problem arose also on 14-STABLE on a box in the lab when performing
the tansition from pkg 1.20.9_1 -> 1.21.0), I'd exclude a hardware/memory issue.

Using (a freshly recompiled) gdb 14 from ports gives not much:

[...]
***@thor:/usr/ports # gdb /usr/local/sbin/pkg-static
/packages/portmaster-backup/pkg-static.core
GNU gdb (GDB) 14.1 [GDB v14.1 for FreeBSD]
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-portbld-freebsd15.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/sbin/pkg-static...
(No debugging symbols found in /usr/local/sbin/pkg-static)
[New LWP 101269]
Core was generated by `/usr/local/sbin/pkg-static delete -yf e2fsprogs-libuuid-1.47.0'.
Program terminated with signal SIGSEGV, Segmentation fault.
Address not mapped to object.
#0 0x0000000000b3de2b in strlen_baseline ()



Kind regards,
oh

[FreeBSD User]

Am Tue, 9 Apr 2024 17:10:52 +0200

Hello,
after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 on CURRENT
www/apache24
databases/redis
pkg core dumps while performing installation. apache24 and redis are ports I realized
this misbehaviour on ALL 14-STABLE and CURRENT boxes (both OS variants latest builds,
i.e. FreeBSD 15.0-CURRENT #32 main-n269135-da2b732288c7: Fri Apr 5 20:30:39 CEST 2024
amd64).
After some updates on a poudriere builder (CURRENT base host, 14.0-RELENG jail with
poudriere) building packages for 14.0-RELENG, I observed the same behaviour when
updating packages on target hosts where pkg is first updated, on those hosts,
nextcloud-server and icinga2 host utilizing also databases/redis and www/apache24, pkg
fails the same way.
I do not dare to update our poudriere hosts since the problem seems to pop up when pkg
1.21.0 is installed, no matter whether I use poudriere built ports (from our own builder
hosts) or recent source tree with portmaster/make build process.
Looks like a serious bug to me and not a site/user specific problem. Hopefully others do
realize the same ...
Thanks in advance,
oh

Hmm, I just tried to reproduce that. Both ports mentioned, databases/redis
and www/apache24, can be built and installed with Portmaster. The box is a
15.0-CURRENT with pkg-1.21.0.
Maybe 'pkg check -Bn' or 'portmaster --check-depends --check-port-dbdir'
show some inconsistencies?
Best wishes,
Rainer

using portmaster or not are strictly unlikely to be helpful here.
The right way to test if to report running with pkg -dddd and also to recommand
testing with default options in pkg.conf.
Best regards,
Bapt

This is correct and certainly better. I was not aware of this.
Fortunately, my less optimal suggestions helped O. Hartmann in this case
to find the missing and outdated dependencies.
In any case, many thanks for this helpfull advice.
Regards,
Rainer

Hello,

@Babptist : it should be pkg -d, shouldn't it? Or do I miss again something here?

With today's update to pkg 1.21.1 the problem has vanished.

@R. Hurling: Thanks for the tip using the checks. I missed that and somehow it revealed some
problems here I hopefully have fixed so far.

Kind regads and thanks,

oh

[Baptiste Daroussin]

Post by FreeBSD User
Am Tue, 9 Apr 2024 17:10:52 +0200

Hello,
after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0 on CURRENT
www/apache24
databases/redis
pkg core dumps while performing installation. apache24 and redis are ports I realized
this misbehaviour on ALL 14-STABLE and CURRENT boxes (both OS variants latest builds,
i.e. FreeBSD 15.0-CURRENT #32 main-n269135-da2b732288c7: Fri Apr 5 20:30:39 CEST 2024
amd64).
After some updates on a poudriere builder (CURRENT base host, 14.0-RELENG jail with
poudriere) building packages for 14.0-RELENG, I observed the same behaviour when
updating packages on target hosts where pkg is first updated, on those hosts,
nextcloud-server and icinga2 host utilizing also databases/redis and www/apache24, pkg
fails the same way.
I do not dare to update our poudriere hosts since the problem seems to pop up when pkg
1.21.0 is installed, no matter whether I use poudriere built ports (from our own builder
hosts) or recent source tree with portmaster/make build process.
Looks like a serious bug to me and not a site/user specific problem. Hopefully others do
realize the same ...
Thanks in advance,
oh

Hmm, I just tried to reproduce that. Both ports mentioned, databases/redis
and www/apache24, can be built and installed with Portmaster. The box is a
15.0-CURRENT with pkg-1.21.0.
Maybe 'pkg check -Bn' or 'portmaster --check-depends --check-port-dbdir'
show some inconsistencies?
Best wishes,
Rainer

using portmaster or not are strictly unlikely to be helpful here.
The right way to test if to report running with pkg -dddd and also to recommand
testing with default options in pkg.conf.
Best regards,
Bapt

This is correct and certainly better. I was not aware of this.
Fortunately, my less optimal suggestions helped O. Hartmann in this case
to find the missing and outdated dependencies.
In any case, many thanks for this helpfull advice.
Regards,
Rainer

Hello,
@Babptist : it should be pkg -d, shouldn't it? Or do I miss again something here?

Each d will provide a more verbose level of debug

Bapt



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de