wennan.he
09/16/2022, 3:49 AMMichal Nicpon
09/16/2022, 3:24 PMwennan.he
09/16/2022, 5:19 PMKathy Satterlee
09/16/2022, 5:37 PMapi/vu/fleet/hosts/identifier/<key from the error>
https://fleetdm.com/docs/using-fleet/rest-api#get-host-by-identifier
Hope that helps!wennan.he
09/16/2022, 8:19 PMKathy Satterlee
09/16/2022, 8:35 PM<your fleet address>/api/v1/fleet/hosts/identifier/<node key>
Or, using MySQL to query the Fleet db:
SELECT id, hostname FROM hosts WHERE node_key=<node key>
wennan.he
09/16/2022, 8:39 PMMichal Nicpon
09/19/2022, 5:20 PMshow engine innodb status;
show processlist;
wennan.he
09/19/2022, 8:42 PMMichal Nicpon
09/21/2022, 4:27 PMSep 16 19:41:51 n107-019-021 fleet[2438691]: 2022/09/16 19:41:51 http: Accept error: accept tcp [::]:8080: accept4: too many open files; retrying in 5ms
Which suggests that maybe your fleet instance is trying to handle too many requests. Can you give me some information about your architecture?
• How many fleet instances are you running? How much memory and cpu do they have?
• How many hosts are enrolled with fleet?wennan.he
09/21/2022, 4:33 PMMichal Nicpon
09/21/2022, 4:35 PMHmm, do you notice any particular patterns for when you start seeing these errors?For example, do they happen every hour or do you see these errors consistently?
wennan.he
09/21/2022, 4:35 PMMichal Nicpon
09/21/2022, 6:38 PMtoo many open files
This can be caused by having the ulimit for user running fleet being set too low.
See https://fleetdm.com/docs/deploying/faq#what-do-i-do-about-too-many-open-files-errorsLimitNOFILE=8192
Kathy Satterlee
09/21/2022, 6:42 PMwennan.he
09/21/2022, 6:46 PM