@theopolis Yes, osquery was already fully-configured before I updated to v2.2.1. That error and a few others came up only after the update. Is that particular error something to fret about or just ignore it?