Channels
android_tests
apple-silicon
arm-architecture
auditing-warroom
aws
carving
code-review
community-feeds
core
darkbytes
doorman
ebpf
eclecticiq-polylogyx-extension
extensions
file-carving
fim
fleet
fleet-dev
fleetosquery
foundation
fuzzing
general
golang
goquery
infrastructure
jobs
kolide
linen-dev
linux
macos
officehours
osctrl
plugins
process-auditing
querycon
queryhub
random
selfgroup
sql
tls
uptycs
vendor-feeds
website
windows
zeek
zentral
zercurity
Title
z
zwass
12/23/2020, 9:56 PMAre you seeing that same error message? Do you see the same value for
host_identifierMore details in https://github.com/fleetdm/fleet/issues/102. If you are seeing a perf issue please follow these instructions to get a debug archive that we can use to debug the perf: https://github.com/fleetdm/fleet/blob/master/docs/infrastructure/performance.md#generate-debug-archive-fleet-340
c
Chris Reisor
12/23/2020, 10:02 PMah, we're on 3.1.0 😞
z
zwass
12/23/2020, 10:03 PMWe've only seen this in association with the duplicate host identifier problem, so consider whether you could be running into that scenario. If you are able to modify the osqueryd flagfile, setting
host_identifier=instancec
Chris Reisor
12/23/2020, 10:05 PMOK thanks, I'll look into that
Do you know if MySQL should have
innodb_rollback_on_timeoutz
zwass
12/24/2020, 12:38 AMFleet's tx handling (https://github.com/fleetdm/fleet/blob/master/server/datastore/mysql/mysql.go#L63-L99) will rollback on any error encountered during the transaction, so I don't think that should make any difference. Please let us know if you observe any issues.