<@UBWUZESLB> can you screenshot your browser conso...
# kolideg
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 PMhi @groob here is the screenshot
R0n
12/11/2018, 2:48 PMR0n
12/11/2018, 4:27 PMany idea?
R0n
12/11/2018, 4:27 PM@zwass
g
groob
12/11/2018, 4:37 PM
it looks like you have some cert trust issues in there?
z
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 PMthe devops guy said we are not using a LB
R0n
12/11/2018, 4:41 PMI also seen this problem with certs, but i still dont know why its throwing the error
R0n
12/11/2018, 4:43 PM Copy code
This page isn’t working If the problem continues, contact the site owner.
HTTP ERROR 405<https://kolide/api/v1/kolide/results/306/fqy4fk2z/xhr_streaming?t=1544546549068>g
groob
12/11/2018, 4:44 PM
thats a CORS issue?
groob
12/11/2018, 4:45 PM
why would that happen with fleet, which serves its own files
groob
12/11/2018, 4:45 PM
something is really odd here
r
R0n
12/11/2018, 4:45 PMyes
R0n
12/11/2018, 4:45 PMi mean it should call itself
R0n
12/11/2018, 4:45 PMit was working just fine before
R0n
12/11/2018, 4:46 PMand the POST just returns
ERR_SPDY_PROTOCOL_ERROR 200R0n
12/11/2018, 4:46 PMwhat is odd is that the packs schedule are running just fine
R0n
12/11/2018, 5:03 PMif i try the ip i get
This site can’t be reachedR0n
12/11/2018, 5:03 PMim 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👍
R0n
12/11/2018, 5:53 PMim looking at the logs in one of the hosts. im seeing this msg.
Error sending status to logger: Request error: Bad file descriptorR0n
12/11/2018, 5:54 PMbut it looks like the host is able to post requests to kolide api
R0n
12/11/2018, 9:41 PM Copy code
"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"R0n
12/11/2018, 9:41 PMredis would be the problem?
g
groob
12/11/2018, 9:42 PM
yes, thats a redis connection issue
groob
12/11/2018, 9:42 PM
well
groob
12/11/2018, 9:42 PM
too many open files
groob
12/11/2018, 9:42 PM
do you need to set the ulimit higher?
r
R0n
12/11/2018, 10:01 PMwe went from 100 hosts to 800
R0n
12/11/2018, 10:01 PMdo i need to increase settings?
g
groob
12/11/2018, 10:02 PM
by default many servers have ulimit values that dont scale well
groob
12/11/2018, 10:03 PM
r
R0n
12/11/2018, 10:21 PMi'll look into that
R0n
12/11/2018, 10:21 PMthanks!
R0n
12/11/2018, 10:22 PMi would probably have to update to 2.0.1 right
R0n
12/12/2018, 2:53 PMthat fixed the problem
R0n
12/12/2018, 2:53 PMthanks!
2 Views