-
Notifications
You must be signed in to change notification settings - Fork 23.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CRASH] Redis 7.2.4 crashed by signal: 6, si_code: -6 #13203
Comments
it's strange that signal SIGTERM is send by the user. |
@sundb Looking at the time, the SIGTERM was logged 40mins prior to crash. At the log time, no user could have transmitted a shutdown directive to the container. Within the application, the permissible operations are setting, retrieving, and deleting. In the case of application failure, it may disconnect from the container, yet it does not initiate the shutdown process for the container. |
@doxg what operation system and version are you using? and how did you install Redis? |
i don't think it's SIGTERM sent by a user, it's a fortification assertion. involving LINDEX on a listpack. |
@sundb I apologize for late replies. It's Ubuntu 22.04. I installed redis container following tutorial on official website. |
@oranagra I apologize for late replies. I wasn't able to reproduce the issue, but I did stumble upon an intriguing case. Upon investigation, I discovered hardware issues with the current server and requested a replacement. Interestingly, this error hasn't occurred on other machines running different operating systems, such as Ubuntu 18 and Windows 10. |
interesting, what type of hardware was it and what was the HW error? |
Greetings,
I am currently utilizing the redis-server for the purpose of caching within my application. The workflow involves the reception of real-time data on a per-second basis, wherein I proceed to store these values in Redis utilizing a key:list format, with a limit of 100 elements per list. Subsequently, this data is transferred to a database. Upon completion of this transfer, all corresponding keys within Redis are removed. Then, the cycle repeats. The system have been running two days before the redis container exited with code (134).
Crash report
OS: Ubuntu 22.04
PS:
Additionally, upon inspecting the logs preceding the occurrence of a crash, I have observed the recurrence of the message:
where PID incrementally increases until reaching 288, subsequently resulting in a sigterm signal and what appears to be the automatic restart of the redis-server. For the moment of crash, the PID was 451.
To address the crash issue, I enabled overcommit and configured forced restart in case of crash. But i would like to know the root cause of these crashes for further investigation and resolution.
The text was updated successfully, but these errors were encountered: