You are not logged in.
I had a problem with ISC Kea 2.2.0-7 where segfault was occurring:
Jul 25 13:20:31 mybox kernel: kea-lfc[5164]: segfault at 7efe20000020 ip 00007efe322aa170 sp 00007efe31624db0 error 6 likely on CPU 3 (core 12, socket 0)
Jul 25 13:20:31 mybox kernel: Code: ee 48 89 df e8 b1 f3 06 00 85 c0 0f 85 41 01 00 00 48 8b 05 4a 71 14 00 48 83 e8 01 48 39 e8 0f 82 b5 00 00 00 66 0f 6f 0c 24 <4c> 89 6b 20 0f 11 4b 10 90 48 83 c4 18 48 89 d8 5b 5d 41 5c 41 5d
ISC Kea support recommended me to upgrade to stable 2.4.0. I created my own installation package via makepkg and installed it. Everything works fine, but I still get a warning when using pacman / yay: kea: local (2.4.0-0) is newer than extra (2.2.0-7)
Is there any way to get rid of this warning?
this doesn't help (/etc/pacman.conf)
IgnorePkg = kea
BTW: Where and who can I ask to package the new official Kea 2.4.0 package for Arch?
Thank you
Last edited by vecino (2023-08-04 14:34:51)
Offline
Try sudo pacman -Syuu: uu means you downgrade newer packages to official versions.
Offline
Clearly the OP wouldn't want to downgrade as the current repo version has the problem they fixed by upgrading.
But what's wrong with the warning? It's correctly informing you that the repos have not (yet) caught up with your installed package. They will eventually and that will go away on it's own.
Where and who can I ask to package the new official Kea 2.4.0 package for Arch?
If there isn't one already you can report this as a bug on the bug-tracker and note that there is an upstream fix available in the newer version.
Last edited by Trilby (2023-07-30 17:12:25)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
You're probably right... I don't like warnings, but I think I see the point in this case. It kind of annoys me every time I run pacman -Syu.
Okay, I'll report it through the bug-tracker.
Thanks
Offline
I have requested a new official Kea 2.4.x package - https://bugs.archlinux.org/task/79260 .
Offline
Please can someone help me get "backtrace with debug symbols"?
I tried it like this:
❯ gdb /usr/bin/kea-dhcp4
GNU gdb (GDB) 13.2
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-pc-linux-gnu".
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/bin/kea-dhcp4...
This GDB supports auto-downloading debuginfo from the following URLs:
<https://debuginfod.archlinux.org>
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Downloading separate debug info for /usr/bin/kea-dhcp4
(No debugging symbols found in /usr/bin/kea-dhcp4)
(gdb) set logging enabled
Copying output to gdb.txt.
Copying debug output to gdb.txt.
(gdb) bt full
No stack.
(gdb)
Offline
If you install the debug package are debug symbols then found?
pacman -U https://geo.mirror.pkgbuild.com/extra-debug/os/x86_64/kea-debug-2.2.0-7-x86_64.pkg.tar.zst
Offline
I would need the newer kea 2.4.0-1 - https://archlinux.org/packages/extra-te … 86_64/kea/ ... so it's only in extra-testing for now. Is that a problem?
I haven't found 2.4.0-1 here yet: https://geo.mirror.pkgbuild.com/extra-debug/os/x86_64/
Offline
I haven't found 2.4.0-1 here yet: https://geo.mirror.pkgbuild.com/extra-debug/os/x86_64/
That could be the reason the debug symbols are not being obtained using debuginfod. You may have to build your own package with debug symbols. Or I could do it for you. It would also appear to be a packaging bug that the debug package is missing.
Offline
I am able to build my own package + modify PKGBUILD. Could you advise me what parameters I can use to add the debug symbols? Thanks a lot
Offline
Either use pkgctl from devtools which will automatically build with debug enabled
$ pkgctl repo clone --protocol=https kea
$ cd kea
$ pkgctl build
Or add an options line as shown in the diff below
diff --git a/PKGBUILD b/PKGBUILD
index 7fca2fa..7d699e5 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -44,6 +44,7 @@ optdepends=('mariadb: lease information database'
# Checks are disabled for now
# We can ignore mysql/pgsql, but admin tests use custom scripts that break everything
checkdepends=('gtest' 'procps-ng') # procps-ng needed for 'pgrep'
+options=(debug !strip)
source=(
"https://ftp.isc.org/isc/${pkgbase}/${_upstreamver}/${pkgbase}-${_upstreamver}.tar.gz"{,.asc}
'tmpfiles-kea.conf'
Last edited by loqs (2023-08-01 17:49:15)
Offline
[vecino@archlinux kea]$ makepkg -s
/home/vecino/kea/PKGBUILD: line 34: syntax error near unexpected token `debug'
/home/vecino/kea/PKGBUILD: line 34: `+options=(debug !strip)'
==> ERROR: Failed to source /home/vecino/kea/PKGBUILD
Offline
The + in the diff means line inserted. If you are manually editing the file just remove the +.
Offline
I stupidly copied it and didn't realize the + didn't belong there.
Thank you so much - the package is already being created.
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
Yes, definitely - I'm counting on it. I'm just waiting to see if I can make the required. If so - I will mark the thread as solved.
Offline
I would need the newer kea 2.4.0-1 - https://archlinux.org/packages/extra-te … 86_64/kea/ ... so it's only in extra-testing for now. Is that a problem?
I haven't found 2.4.0-1 here yet: https://geo.mirror.pkgbuild.com/extra-debug/os/x86_64/
I just noticed you were looking in extra-debug not extra-testing-debug. kea has been updated 2.4.0-2 but the debug package for 2.4.0-1 is currently still there as well.
Offline
Oh - thanks for the tip. I have it installed:
❯ pacman -Q | grep kea
kea 2.4.0-2
kea-debug 2.4.0-2
But I'm not getting any results yet:
❯ gdb /usr/bin/kea-dhcp4
GNU gdb (GDB) 13.2
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-pc-linux-gnu".
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/bin/kea-dhcp4...
Reading symbols from /usr/lib/debug/usr/bin/kea-dhcp4.debug...
(gdb) set logging enabled
Copying output to gdb.txt.
Copying debug output to gdb.txt.
(gdb) bt full
No stack.
(gdb)
Offline
If you can produce the issue using kea 2.4 you want Getting_traces#Getting_the_trace.
As mentioned in the closed bug report are there any core dumps listed in
coredumpctl list
For the old kea 2.2 which could be examined?
Offline
I am currently experiencing the same problem (segfault) in Kea 2.4.
❯ coredumpctl list
No coredumps found.
Offline
Please post the full system journal from a boot where kea-dhcp4.service fails. Were you able to reproduce the issue under gdb?
Offline
inb4: you forgot to "run" the process, but also the segfault occurred in (the sub-process?) "kea-lfc" binary what means you probably will have to "set follow-fork-mode child"
"Probably", because if kea-dhcp4 forks multiple times, you'll just follow the first child down the rabbit hole.
So post the journal no matter what.
Offline
Sorry I'm not a very advanced linux user. I didn't get any results with the debugging. I tried it according to the wiki, but failed.
Thanks for your time
Offline
All three kea-lfc segmentation faults in the journal you posted happen immediately after the root user logs out. How is kea-lfc started? Have you changed anything that would prevent core dumps from being generated?
Offline
Kea is started automatically via systemd.
❯ systemctl status kea-dhcp4.service
● kea-dhcp4.service - ISC Kea IPv4 DHCP daemon
Loaded: loaded (/etc/systemd/system/kea-dhcp4.service; enabled; preset: disabled)
Drop-In: /etc/systemd/system/kea-dhcp4.service.d
└─spam.conf
Active: active (running) since Tue 2023-08-01 22:54:28 CEST; 19h ago
Docs: man:kea-dhcp4(8)
Main PID: 26282 (kea-dhcp4)
Tasks: 9 (limit: 2324)
Memory: 4.8M
CPU: 11.904s
CGroup: /system.slice/kea-dhcp4.service
└─26282 /usr/bin/kea-dhcp4 -c /etc/kea/kea-dhcp4.conf
Offline