Osquery uses basic SQL commands to leverage a relational data-model to describe a device.

osquery

Thank you!
```10.27.141.59:6379&gt; info
# Server
redis_version:5.0.9```

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)?

it's GCP managed Redis I believe - right <@U0277JVQNSF>??

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.

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?

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 you can build binaries/Docker containers yourself after I merge the fix.

<https://github.com/fleetdm/fleet/pull/1312>

Thanks again.  I migrated  the DB when I upgraded to 4.0 . . .  do I need to rebuild the DB after reverting to 3.13?

Yes, restore from a backup or rebuild the DB.

I'm having this issue on kubernetes with fleetdm v4 image. Is there a new docker image that fixed this issue?

<@UK6UD29KK> Can you please open a new thread in <#C01DXJL16D8|fleet> with more information about the issue you are encountering?