Title
#kolide
g

groob

12/10/2018, 11:03 PM
@R0n can you screenshot your browser console when you repro this issue?
r

R0n

12/11/2018, 2:47 PM
hi @groob here is the screenshot
2:48 PM
4:27 PM
any idea?
4:27 PM
@zwass
g

groob

12/11/2018, 4:37 PM
it looks like you have some cert trust issues in there?
zwass

zwass

12/11/2018, 4:40 PM
I have only ever seen errors like this when Fleet is running behind an LB. are you certain you are connecting directly to it? Can you try connecting to the IP of the Fleet server?
r

R0n

12/11/2018, 4:41 PM
the devops guy said we are not using a LB
4:41 PM
I also seen this problem with certs, but i still dont know why its throwing the error
4:43 PM
This page isn’t working If the problem continues, contact the site owner.
HTTP ERROR 405
when i hit
<https://kolide/api/v1/kolide/results/306/fqy4fk2z/xhr_streaming?t=1544546549068>
g

groob

12/11/2018, 4:44 PM
thats a CORS issue?
4:45 PM
why would that happen with fleet, which serves its own files
4:45 PM
something is really odd here
r

R0n

12/11/2018, 4:45 PM
yes
4:45 PM
i mean it should call itself
4:45 PM
it was working just fine before
4:46 PM
and the POST just returns
ERR_SPDY_PROTOCOL_ERROR 200
4:46 PM
what is odd is that the packs schedule are running just fine
5:03 PM
if i try the ip i get
This site can’t be reached
5:03 PM
im not sure how kolide is setup in GCP
g

groob

12/11/2018, 5:06 PM
IMO you should either point these questions at your sysadmin or ask them to join here and we can troubleshoot. There’s something clearly wrong with your server setup or with how you’re connecting to it, but we can’t really tell what without more information.
r

R0n

12/11/2018, 5:09 PM
👍
5:53 PM
im looking at the logs in one of the hosts. im seeing this msg.
Error sending status to logger: Request error: Bad file descriptor
any idea what that is
5:54 PM
but it looks like the host is able to post requests to kolide api
9:41 PM
"error": "failed to ingest result: writing results: PUBLISH failed to channel results_3751: dial tcp: lookup -<http://redis.qa.com|redis.qa.com> on x.x.x.x:53: dial udp x.x.x.x:53: socket: too many open files"
tahts the error after the host gets the query
9:41 PM
redis would be the problem?
g

groob

12/11/2018, 9:42 PM
yes, thats a redis connection issue
9:42 PM
well
9:42 PM
too many open files
9:42 PM
do you need to set the ulimit higher?
r

R0n

12/11/2018, 10:01 PM
we went from 100 hosts to 800
10:01 PM
do i need to increase settings?
g

groob

12/11/2018, 10:02 PM
by default many servers have ulimit values that dont scale well
r

R0n

12/11/2018, 10:21 PM
i'll look into that
10:21 PM
thanks!
10:22 PM
i would probably have to update to 2.0.1 right
2:53 PM
that fixed the problem
2:53 PM
thanks!