Notice! - If a Redis module was involved, please open an issue in the module's repo instead! - If you're using docker on Apple M1, please make sure the image you're using was compiled for ARM!
Crash report
Paste the complete crash log between the quotes below. Please include a few lines from the log preceding the crash report to provide some context.
=== REDIS BUG REPORT START: Cut & paste starting from here ===
4186020:M 06 Sep 2024 05:37:42.052 # Redis 7.0.3 crashed by signal: 11, si_code: 1
4186020:M 06 Sep 2024 05:37:42.052 # Accessing address: 0x138a20
4186020:M 06 Sep 2024 05:37:42.052 # Crashed running the instruction at: 0x138a20
1226725:C 06 Sep 2024 05:37:42.528 * Supervised by systemd. Please make sure you set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
1226725:C 06 Sep 2024 05:37:42.528 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1226725:C 06 Sep 2024 05:37:42.528 # Redis version=7.0.3, bits=64, commit=00000000, modified=0, pid=1226725, just started
1226725:C 06 Sep 2024 05:37:42.528 # Configuration loaded
1226725:M 06 Sep 2024 05:37:42.537 * Increased maximum number of open files to 25032 (it was originally set to 1024).
1226725:M 06 Sep 2024 05:37:42.537 * monotonic clock: POSIX clock_gettime
1226725:M 06 Sep 2024 05:37:42.538 * Node configuration loaded, I'm f6fee237b4fa79a0d430c154dc0785c41def8b88
1226725:M 06 Sep 2024 05:37:42.538 * Running mode=cluster, port=26379.
1226725:M 06 Sep 2024 05:37:42.538 # Server initialized
1226725:M 06 Sep 2024 05:37:42.540 * <search> redis version observed by redisearch : 7.0.3
1226725:M 06 Sep 2024 05:37:42.540 * <search> Redis version found by RedisSearch : 7.0.3 - oss
1226725:M 06 Sep 2024 05:37:42.540 * <search> RediSearch version 2.6.12 (Git=HEAD-11b44a2d)
1226725:M 06 Sep 2024 05:37:42.540 * <search> Low level api version 1 initialized successfully
1226725:M 06 Sep 2024 05:37:42.552 * <search> Initialized thread pool!
1226725:M 06 Sep 2024 05:37:42.540 * <search> concurrent writes: OFF, gc: ON, prefix min length: 2, prefix max expansions: 200, query timeout (ms): 500, timeout policy: return, cursor read size: 1000, cursor max idle (ms): 300000, max doctable size: 1000000, max number of search results: 1000000, search pool size: 20, index pool size: 8,
1226725:M 06 Sep 2024 05:37:42.552 * <search> Initialized thread pool!
1226725:M 06 Sep 2024 05:37:42.552 * <search> Enabled role change notification
1226725:M 06 Sep 2024 05:37:42.552 * <search> Cluster configuration: 0 partitions, type: 0, coordinator timeout: 0ms
1226725:M 06 Sep 2024 05:37:42.563 * <search> Register write commands
1226725:M 06 Sep 2024 05:37:42.563 * Module 'search' loaded from /usr/local/bin/redis-modules-RediSearchv2.6.12_Ubuntuv22.so
1226725:M 06 Sep 2024 05:37:42.564 * <ReJSON> version: 20407 git sha: a4412b3 branch: HEAD
1226725:M 06 Sep 2024 05:37:42.564 * <ReJSON> Exported RedisJSON_V1 API
1226725:M 06 Sep 2024 05:37:42.564 * <ReJSON> Exported RedisJSON_V2 API
1226725:M 06 Sep 2024 05:37:42.564 * <ReJSON> Exported RedisJSON_V3 API
1226725:M 06 Sep 2024 05:37:42.564 * <ReJSON> Enabled diskless replication
1226725:M 06 Sep 2024 05:37:42.564 * <ReJSON> Created new data type 'ReJSON-RL'
1226725:M 06 Sep 2024 05:37:42.564 * Module 'ReJSON' loaded from /usr/local/bin/redis-modules-RedisJSONv2.4.7_Ubuntuv22.so
1226725:M 06 Sep 2024 05:37:42.564 * <search> Acquired RedisJSON_V3 API
1226725:M 06 Sep 2024 05:37:42.564 * <search> Loading event starts
1226725:M 06 Sep 2024 05:37:42.564 * Loading RDB produced by version 7.0.3
1226725:M 06 Sep 2024 05:37:42.564 * RDB age 1555905 seconds
1226725:M 06 Sep 2024 05:37:42.564 * RDB memory usage when created 8.01 Mb
1226725:M 06 Sep 2024 05:37:42.579 * Done loading RDB, keys loaded: 2259, keys expired: 0.
Additional information
- OS distribution and version
PRETTY_NAME="Ubuntu 22.04.3 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)"
- Steps to reproduce (if any) a. Using Redis 7.0.3 b. Add Search and JSON modules c. Edit RDB config 'config set save 1800 1'
Comment From: sundb
@muvelus do you have the fully crash report?
Comment From: muvelus
@sundb Is there a command I can run to get the complete crash report? If required, I can attach more logs. Please do let me know. Thank you!
Comment From: sundb
@muvelus normally the crash log is what you sent, but it is missing most of the crash information, can you find keyword crashed by signal from other log files?