You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See comments above for where to toggle nixpkgs, architecture, kernel;
changing foundationdb version is outside the scope of this simple
reproduction but suffice it to say I've tested that also.
Resulting coredump can be seen with:
coredumpctl list | grep fdbserver | tail -n 1 | awk '{ print $5 }'| xargs coredumpctl info
Using cluster file `/etc/foundationdb/fdb.cluster'.
Configuration:
Redundancy mode - single
Storage engine - ssd-2
Coordinators - 1
Usable Regions - 1
Cluster:
FoundationDB processes - 1
Zones - 1
Machines - 1
Memory availability - 7.5 GB per process on machine with least available
Fault Tolerance - 0 machines
Server time - 06/13/24 10:14:01
Data:
Replication health - (Re)initializing automatic data distribution
Moving data - unknown (initializing)
Sum of key-value sizes - unknown
Disk space used - 210 MB
Operating space:
Storage server - 3.1 GB free on most full server
Log server - 3.1 GB free on most full server
Workload:
Read rate - 16 Hz
Write rate - 0 Hz
Transactions started - 4 Hz
Transactions committed - 0 Hz
Conflict rate - 0 Hz
Backup and DR:
Running backups - 0
Running DRs - 0
Client time: 06/13/24 10:14:01
The issue appears to be the glibc version change 2.38-77 -> glibc-2.39-52,
which is both a direct dependency of foundationdb and an indirect dependency
via boost-1.78.0, it was not obvious how to test this further.
It looks to me like the implementation of ClusterConnectionString was replaced in newer versions
so not encountering this would probably be a benefit of updating the version, so that may be an option.
(But I am not able to participate in that process.)
Describe the bug
foundationdb
dumps core in the following system configurations:Steps To Reproduce
Set up a single machine test cluster using a minimal flake:
See comments above for where to toggle nixpkgs, architecture, kernel;
changing foundationdb version is outside the scope of this simple
reproduction but suffice it to say I've tested that also.
Resulting coredump can be seen with:
Example:
Expected behavior
A running single-node foundationdb cluster, check with
sudo fdbcli --exec status
:Broken System
Working System
Additional context
Looking at the dependency tree with:
nix-tree .#nixosConfigurations.test-system.config.services.foundationdb.package
The issue appears to be the glibc version change
2.38-77
->glibc-2.39-52
,which is both a direct dependency of foundationdb and an indirect dependency
via
boost-1.78.0
, it was not obvious how to test this further.I am happy to collect additional data as needed.
Notify maintainers
foundationdb maintainers:
@thoughtpolice @lostnet
glibc maintainers:
@eelco @Ma27 @ConnorBaker
Metadata
Broken System
"x86_64-linux"
Linux 6.6.32, NixOS, 24.05 (Uakari), 24.05.20240613.bbc6229
no
yes
nix-env (Nix) 2.18.2
not found
Working System
"x86_64-linux"
Linux 6.6.33, NixOS, 23.11 (Tapir), 23.11.20240612.5c2ec3a
yes
yes
nix-env (Nix) 2.18.1
/nix/var/nix/profiles/per-user/root/channels/nixos
The text was updated successfully, but these errors were encountered: