-
Notifications
You must be signed in to change notification settings - Fork 52
Description
Traceback attached. I have a coredump (several, actually). We restarted it to flush its contents during other work, and it wouldn't stay running. I was able to connect to it when it didn't have offered work, and use the INFO command, but real offered work seems to kill it fairly quickly. Doesnt' seem like it's had an actual upgrade in a while. I'm probably missing something obvious I should add here, but it's been a long day; smack me with the clue-by-four.
2025-01-05T13:27:47Z [166/207] refreshing redis-7.2.5...
2025-01-05T13:28:20Z [194/207] refreshing php81-redis-5.3.7...
2025-01-17T13:27:09Z [166/207] refreshing redis-7.2.5...
2025-01-17T13:27:54Z [194/207] refreshing php81-redis-5.3.7...
2025-05-29T12:30:26Z [31/144] upgrading redis-8.0.1...
php81-redis-5.3.7
2025-05-30T12:27:12Z [54/63] upgrading php81-redis-6.2.0...
2025-06-10T12:13:57Z [86/123] upgrading redis-8.0.2...
2025-06-10T12:14:31Z [113/123] refreshing php81-redis-6.2.0...
2025-06-14T12:11:01Z [16/22] refreshing php81-redis-6.2.0...
2025-06-17T12:12:29Z [20/24] refreshing php81-redis-6.2.0...
2025-06-20T12:13:09Z [55/63] refreshing php81-redis-6.2.0...
2025-06-26T12:15:40Z [97/109] refreshing php81-redis-6.2.0...
versions:
redis-8.0.2
gcc13-libs-13.3.0
openssl-3.4.1
platform 20250417T003816Z