icingadb-redis-server: libgcc_s.so.1 must be installed for pthread_cancel to work / Out Of Memory allocating

[tectumopticum]

Describe the bug

Out of the sudden the icingadb-redis.service stopped working.
output of journalctl -u icingadb-redis.service:

icingadb-redis-server[1524]: libgcc_s.so.1 must be installed for pthread_cancel to work
icingadb-redis-server[1524]: libgcc_s.so.1 must be installed for pthread_cancel to work
systemd[1]: icingadb-redis.service: Main process exited, code=dumped, status=6/ABRT
systemd[1]: icingadb-redis.service: Failed with result 'core-dump'.

After restarting everything looks fine again.

Excerpt from redis.log:
[...]

1524:M 09 Dec 2024 05:08:34.380 # Out Of Memory allocating 16400 bytes!


=== REDIS BUG REPORT START: Cut & paste starting from here ===
1524:M 09 Dec 2024 05:08:34.380 # ------------------------------------------------
1524:M 09 Dec 2024 05:08:34.380 # !!! Software Failure. Press left mouse button to continue
1524:M 09 Dec 2024 05:08:34.380 # Guru Meditation: Redis aborting for OUT OF MEMORY. Allocating 16400 bytes! #server.c:6844

------ STACK TRACE ------

Backtrace:

------ INFO OUTPUT ------
# Server
redis_version:7.2.6
redis_git_sha1:00000000
redis_git_dirty:0
redis_build_id:420fd3a3a5cb1475
redis_mode:standalone
os:Linux 5.14.21-150500.55.80-default x86_64
arch_bits:64
monotonic_clock:POSIX clock_gettime
multiplexing_api:epoll
atomicvar_api:c11-builtin
gcc_version:7.5.0
process_id:1524
process_supervised:systemd
run_id:9e7bf872495db0e5ff1ca1506d45c2e077ebe19c
tcp_port:6380
server_time_usec:1733717314378878
uptime_in_seconds:2223013
uptime_in_days:25
hz:10
configured_hz:10
lru_clock:5664066
executable:/usr/bin/icingadb-redis-server
config_file:/usr/share/icingadb-redis/icingadb-redis-systemd.conf
io_threads_active:0
listener0:name=tcp,bind=10.1.51.130,port=6380

# Clients
connected_clients:29
cluster_connections:0
maxclients:10000
client_recent_max_input_buffer:229472
client_recent_max_output_buffer:0
blocked_clients:7
tracking_clients:0
clients_in_timeout_table:7
total_blocking_keys:7
total_blocking_keys_on_nokey:0

# Memory
used_memory:813027680
used_memory_human:775.36M
used_memory_rss:839344128
used_memory_rss_human:800.46M
used_memory_peak:818097856
used_memory_peak_human:780.20M
used_memory_peak_perc:99.38%
used_memory_overhead:1320242
used_memory_startup:866048
used_memory_dataset:811707438
used_memory_dataset_perc:99.94%
allocator_allocated:811751136
allocator_active:812941312
allocator_resident:835772416
total_system_memory:33652883456
total_system_memory_human:31.34G
used_memory_lua:31744
used_memory_vm_eval:31744
used_memory_lua_human:31.00K
used_memory_scripts_eval:0
number_of_cached_scripts:0
number_of_functions:0
number_of_libraries:0
used_memory_vm_functions:32768
[...]

To Reproduce

unknown yet

Expected behavior

redis-service shouldn't stop working

Your Environment

Include as many relevant details about the environment you experienced the problem in

• Icinga DB version: 1.1.3
• Icinga 2 version: 2.14.3
• Operating System and version: SLES 15 SP5

[oxzi]

Thanks for creating this issue. Unfortunately, we don't have a dedicated icingadb-redis issue tracker and as this is not directly Icinga DB, I have moved it here.

Based on the output and on the fact that a restarted solved it, may it be possible that this happened during or after a system upgrade where your libraries were replaced with newer versions?