I am getting random segfaults like:
[19111916.107655] redis-server[19251]: segfault at 396d960 ip 00007ff73aca56e4 sp 00007ffff8740e60 error 4 in libc-2.17.so[7ff73ac5d000+1b8000]
(using dmesg | grep segfault | tail -10 )
What do I need to provide for further debugging?
Comment From: trevor211
Can you give the redis log and coredump backtrace?
Comment From: kkmuffme
Redis Log: Nothing in this specific minute (18:11) In the vicinity I see:
23344:C 06 Apr 2020 18:09:04.721 * DB saved on disk
23344:C 06 Apr 2020 18:09:04.748 * RDB: 79 MB of memory used by copy-on-write
27436:S 06 Apr 2020 18:09:04.822 * Background saving terminated with success
27436:S 06 Apr 2020 18:12:37.812 # Connection with replica 127.0.0.1:<unknown-replica-port> lost.
27436:S 06 Apr 2020 18:12:55.204 * Replica 127.0.0.1:<unknown-replica-port> asks for synchronization
27436:S 06 Apr 2020 18:12:55.204 * Unable to partial resync with replica 127.0.0.1:<unknown-replica-port> for lack of backlog (Replica request was: 360655798469).
27436:S 06 Apr 2020 18:12:55.204 * Starting BGSAVE for SYNC with target: disk
27436:S 06 Apr 2020 18:12:55.233 * Background saving started by pid 30981
30981:C 06 Apr 2020 18:13:31.331 * DB saved on disk
30981:C 06 Apr 2020 18:13:31.360 * RDB: 83 MB of memory used by copy-on-write
27436:S 06 Apr 2020 18:13:31.476 * Background saving terminated with success
27436:S 06 Apr 2020 18:13:58.377 * Synchronization with replica 127.0.0.1:<unknown-replica-port> succeeded
Coredump not available, since it's the first time I had this error
Comment From: trevor211
As far as I know, redis would log backtrace when segfault happens.