AlmaLinux 9.5
Nginx, indico 3.3.2
IN log/celery.log
2025-05-29 20:20:38,503 WARNING celery.redirected Message: 'consumer: Cannot connect to %s: %s.\n%s\n'
Arguments: ('redis://127.0.0.1:6379/0', ResponseError('MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.'), 'Trying again in 30.00 seconds... (15/100)')
/var/log/redis/redis.log
# Errorstats
errorstat_ERR:count=3958
errorstat_MISCONF:count=7863
errorstat_NOSCRIPT:count=3
Fast memory test PASSED, however your memory can still be broken. Please run a memory test for several hours if possible.
------ DUMPING CODE AROUND EIP ------
Symbol: rdbSaveStringObject (base: 0x559025966ba0)
Module: /usr/bin/redis-server 127.0.0.1:6379 (base 0x5590258df000)
$ xxd -r -p /tmp/dump.hex /tmp/dump.bin
$ objdump --adjust-vma=0x559025966ba0 -D -b binary -m i386:x86-64 /tmp/dump.bin
------
3747187:M 29 May 2025 20:20:43.633 # dump of function (hexdump of 157 bytes):
f30f1efa0fb60689c283e2f080fa10747fa8700f8580000000488b76080fb656ff89d083e0073c040f87c6ccfbff488d0d234316000fb6c0486304814801c83effe0660f1f4400008b56f7e960feffff488b56efe957feffff0f1f8000000000c0ea030fb6d2e945feffff0f1f4400000fb656fde937feffff0f1f80000000000fb756fbe927feffff0f1f8000000000488b7608e96774ffff5041b8ee
=== REDIS BUG REPORT END. Make sure to include from START to END. ===
Please report the crash by opening an issue on github:
http://github.com/redis/redis/issues
If a Redis module was involved, please open in the module's repo instead.
Suspect RAM error? Use redis-server --test-memory to verify it.
Some other issues could be detected by redis-server --check-system
3695497:C 29 May 2025 20:20:44.112 * Supervised by systemd. Please make sure you set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
3695497:C 29 May 2025 20:20:44.112 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3695497:C 29 May 2025 20:20:44.112 # Redis version=6.2.17, bits=64, commit=00000000, modified=0, pid=3695497, just started
3695497:C 29 May 2025 20:20:44.112 # Configuration loaded
3695497:M 29 May 2025 20:20:44.113 * monotonic clock: POSIX clock_gettime
3695497:M 29 May 2025 20:20:44.114 * Running mode=standalone, port=6379.
3695497:M 29 May 2025 20:20:44.114 # Server initialized
3695497:M 29 May 2025 20:20:44.114 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
I’m having trouble with redis and celery not being able to proceed. It seems to be related to redis’s dump file or memory. Is there a solution?