Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loading error: HTTP 599: Timeout #7

Closed
lepiklepik opened this issue Nov 13, 2014 · 6 comments · Fixed by #60
Closed

Loading error: HTTP 599: Timeout #7

lepiklepik opened this issue Nov 13, 2014 · 6 comments · Fixed by #60

Comments

@lepiklepik
Copy link

Sometimes i get notification with the 'Loading error: HTTP 599: Timeout' and another one in one minute which tells that everything is ok now. Trying to find the reason of that. Without any success for now.

@klen
Copy link
Owner

klen commented Nov 14, 2014

It's mean that the beacon didn't load answer from Graphite or from a pinged site. Maybe I have to add timeout option to the package or an option for ignore such timeout errors.

@jrgifford
Copy link

@klen being able to ignore timeouts for graphite would be useful. As would being able to increase the tornado concurrent connections, which is related.

@sursma
Copy link

sursma commented Aug 10, 2015

@klen It would be great if I can supress these timeout errors. I keep getting
Loading error: HTTP 599: Timeout
then again back to normal
this complete fills my mailbox, cant find real alert
I tried setting
"loading_error": "normal"
still didnt help

@pzhuk
Copy link

pzhuk commented Oct 22, 2015

I am getting the same errors, and looking at nginx logs at graphite side - looks like request never had reached graphite. Only small amount of requests are failing from time to time. More looks like a beacon issue with requests expiring in async queue

@tpeng
Copy link
Contributor

tpeng commented Oct 22, 2015

@okyou
Copy link

okyou commented Apr 20, 2016

    'request_timeout': 1200.0,
    'connect_timeout': 1200.0,

still didnt help
lots of Loading error: HTTP 599: Timeout,cant return result when use historical

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants