You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@KarnikJain this is very old version (IIRC the one that was latest on the day i joined the project).
besides that, for some reason the crash report is missing a stack trace part, so i don't really know where it crashed, and i can't check if that bug was fixed already or not.
what i do see is that CURRENT CLIENT INFO shows that we're probably running BGSAVE now (although i'm not sure if there was some bug in that version which makes this information a lie).
BGSAVE doesn't actually do much (before calling fork(), which means the chances for it to crash are low.
sadly i don't think anyone can help except suggest that you upgrade to a more recent version.
@oranagra Thank you for the response. Did we have such cases in past, where Redis-Server getting Zombie/defunct and redis-server.log showing Crash like I mentioned in my o/p? tried forum but no clear clue yet.
Crash Log:
++++++++
The text was updated successfully, but these errors were encountered: