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

osquery

I'm getting a bunch of 422 errors when trying to view device details. Using 4.57.1, the fix in 4.57.2 seems unrelated. Where can I look to troubleshoot this? Yesterday we updated from 4.54.1 to 4.57.1 and moved from a hosted Redis instance to on-VM Redis instance yesterday, if that's relevant.

hey <@UN9SVU8JW> - can you tell me a bit about your infrastructure? which mysql version and redis versions are you running?

you're right that this wouldn't be related to the 4.57.2 bug fixes (those were for software/app management)

This is the error that's repeating in the logs:
```fleet[2234]: level=error ts=2024-10-04T19:06:43.665546323Z component=http user=smaddock@&lt;redacted&gt; method=GET uri="/api/latest/fleet/hosts/1212/activities/upcoming?page=0&amp;per_page=8" took=5.28477ms err="count upcoming activities: Error 1267 (HY000): Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_0900_ai_ci,IMPLICIT) for operation '='"```

I feel like I run into collation errors every other time we update :disappointed:

I'm sorry you keep running into this! Did you take Fleet down before the uprade?

I'm going to have a support team member jump in and take a look (he's working on an issue with a customer right now, but stand by)

Our upgrades are always: stop fleet, install the new version, run `fleet prepare db`, restart fleet

<@U045LRCCF7U> should I just open a GitHub issue?

Hey <@UN9SVU8JW>, I can help out. Just catching up on the thread. Did you start getting those errors immediately after upgrading to 4.57.1 from 4.54.1?

As of 4.55.0, the minimum supported version of MySQL is 8.0.36. Would you be able to update?

I just applied the latest patch our host offers, but it's still on 8.0.30 :disappointed:

Wow, your documentation has changed completely

Is there a specific doc you're looking for?

Found it. FYI DigitalOcean is listed in your reference architecture but that's what I'm using and they're only 8.0.30 <https://fleetdm.com/docs/deploy/reference-architectures#digital-ocean>

I guess for now I'll spin up another DigitalOcean VM and run our own copy of MySQL off of that.

With requirements as tight as Fleet has, and since y'all are not using semantic versioning (breaking change in a dot-release), I'd suggest adding some checks to the server boot sequence that looks for the required version and errors out if it doesn't meet the minimum.

Thanks for the feedback. I'll write up a feature request to do those versioning checks to avoid issues related to that

And probably to update your documentation to remove DigitalOcean from your reference architecture