Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
2.5.5
-
None
Description
Enabled redis on maxscale for a client and after a few minutes it crashed with the following errors:
2020-12-08 21:20:29 error : [storage_redis] Expected status message 'OK' in the context of MULTI, but received 'QUEUED'.
2020-12-08 21:20:29 error : [storage_redis] Failed when reading response to MULTI: no error,
2020-12-08 21:20:29 error : [cache] Could not store new cache value, deleting a possibly existing old value.
2020-12-08 21:20:29 warning: [storage_redis] Unexpected redis return type (ARRAY) received.
2020-12-08 21:20:29 error : [cache] Could not delete cache item, the value may now be stale.
2020-12-08 21:20:29 warning: (183) [cache] (Read-Write-Service) Received data from the backend although filter is expecting nothing.
2020-12-08 21:20:29 warning: (187) [cache] (Read-Write-Service) Received data from the backend although filter is expecting nothing.
-
-
- Error in `/usr/bin/maxscale': double free or corruption (fasttop): 0x00007fbe800127d0 ***
- Error in `/usr/bin/maxscale': double free or corruption (fasttop): 0x00007fbe800127d0 ***
======= Backtrace: =========
======= Backtrace: =========
/lib64/libc.so.6(+0x81679)[0x7fbed60f5679]
/lib64/libc.so.6(+0x81679)[0x7fbed60f5679]
/usr/lib64/maxscale/libstorage_redis.so(redisBufferWrite+0x245)[0x7fbe905ed505]
/usr/lib64/maxscale/libstorage_redis.so(redisBufferWrite+0x245)[0x7fbe905ed505]
/usr/lib64/maxscale/libstorage_redis.so(redisGetReply+0x83)[0x7fbe905ed603]
/usr/lib64/maxscale/libstorage_redis.so(redisGetReply+0x83)[0x7fbe905ed603]
/usr/lib64/maxscale/libstorage_redis.so(redisvCommand+0x27)[0x7fbe905ed897]
/usr/lib64/maxscale/libstorage_redis.so(redisvCommand+0x27)[0x7fbe905ed897]
/usr/lib64/maxscale/libstorage_redis.so(+0x58cd)[0x7fbe905e38cd]
/usr/lib64/maxscale/libstorage_redis.so(+0x58cd)[0x7fbe905e38cd]
/usr/lib64/maxscale/libstorage_redis.so(+0xa32c)[0x7fbe905e832c]
/usr/lib64/maxscale/libstorage_redis.so(+0xa32c)[0x7fbe905e832c]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x182bab)[0x7fbed8dcebab]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x182bab)[0x7fbed8dcebab]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase10ThreadPool6Thread4mainEv+0x155)[0x7fbed8ced375]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase10ThreadPool6Thread4mainEv+0x155)[0x7fbed8ced375]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x2287ef)[0x7fbed8e747ef]
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x2287ef)[0x7fbed8e747ef]
/lib64/libpthread.so.0(+0x7e65)[0x7fbed7e66e65]
/lib64/libpthread.so.0(+0x7e65)[0x7fbed7e66e65]
/lib64/libc.so.6(clone+0x6d)[0x7fbed617288d]
======= Memory map: ========
/lib64/libc.so.6(clone+0x6d)[0x7fbed617288d]
======= Memory map: ========
00400000-00414000 r-xp 00000000 103:03 12591869 /usr/bin/maxscale
00613000-00614000 r--p 00013000 103:03 12591869 /usr/bin/maxscale
00614000-00615000 rw-p 00014000 103:03 12591869 /usr/bin/maxscale
00615000-00617000 rw-p 00000000 00:00 0
025e4000-02626000 rw-p 00000000 00:00 0 [heap]
-
Disabling redis again allows it to function normally. Log file and config will be attached.