https://github.com/osquery/osquery logo
#fleet
Title
# fleet
g

Guy E Matz

07/06/2021, 3:59 PM
Thank you!
Copy code
10.27.141.59:6379> info
# Server
redis_version:5.0.9
z

zwass

07/06/2021, 4:10 PM
Is this a standard Redis deployment? Or a managed one? What do you get for the rest of that
info
command?
If you are self managing Redis, can you share the contents of your
redis.conf
(with any password redacted)?
j

Jason

07/06/2021, 4:13 PM
it's GCP managed Redis I believe - right @Guy E Matz??
g

Guy E Matz

07/06/2021, 4:20 PM
Correct
z

zwass

07/06/2021, 4:27 PM
Ah, it seems GCP disables the
CLUSTER
command (https://cloud.google.com/memorystore/docs/redis/product-constraints#blocked_redis_commands) which means we see a different error than what we expect when we try that command with clustering not in use.
👀 2
j

Jason

07/06/2021, 4:34 PM
Should we file an issue? And what would you suggest the workaround be? Should we spin up a non-managed redis instance until this is resolved?
z

zwass

07/06/2021, 4:35 PM
Quickest solution would be spinning up a non-managed redis instance. We'll be able to push a fix for this in the next release.
Or reverting to Fleet 3.13.0
Or you can build binaries/Docker containers yourself after I merge the fix.
j

Jason

07/06/2021, 4:39 PM
got it. Very helpful - thanks!
g

Guy E Matz

07/06/2021, 5:54 PM
Thanks again. I migrated the DB when I upgraded to 4.0 . . . do I need to rebuild the DB after reverting to 3.13?
z

zwass

07/06/2021, 5:55 PM
Yes, restore from a backup or rebuild the DB.
g

Guy E Matz

07/06/2021, 7:31 PM
Thanks!
f

Flngen Flugen

11/19/2021, 2:12 PM
I'm having this issue on kubernetes with fleetdm v4 image. Is there a new docker image that fixed this issue?
z

zwass

11/20/2021, 12:59 AM
@Flngen Flugen Can you please open a new thread in #fleet with more information about the issue you are encountering?
6 Views