-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[0.9.4.2] After a few days running all HTTP requests start to throw 500 errors #4884
Comments
@prawnsalad Thanks for opening. Does a service restart resolve the problem? Is there anything else of note going on in the database (or server in general) when the issue occurs? @corylanou Could this be the deadlock issue you've been working on? |
@rossmcdonald Yes, a service restart gets things working again. Nothing else stands out to mention.. the CPU and memory usage were low. I'm using UDP input sources for writes, under 100 points /second. Had a grafana dashboard open querying every 5s. Ubuntu 14.04.3 LTS. |
Duplicate of #4870? |
@beckettsean Sounds like it could be - though that issue doesn't mention any errors similar to the ones I mention here. |
@beckettsean we are having the same symptom on InfluxDB v0.9.4.2 (git: 0.9.4 da1b59e) Soon we got this symptom errors 500, we need to restart influxdb for have be able to restore service (soon action 'reading WAL files to flush to index' are done which is slow currently) |
@prawnsalad Did you have to do anything to get the stack trace (like explicitly kill the process, etc), or did it just appear in the logs during runtime? |
They had just appeared in the log file at runtime. There was many others similar to the 3 I pasted too that went on for several hours. |
Find new logs following several 500 error creating panic during this nights (dunno if it's linked to the same issue but symptom are same, having huge of 500 errors before crash) :
|
Believed fixed by #4913, which is available in the just-released version @JulienChampseix that's a different panic and doesn't look like the deadlock issue. Can you open a new issue with that stack trace? |
thanks @beckettsean i did here #4655 (but before to go on 0.9.5.X, i would be sure it's fixed on the 0.9.5.1 also) |
@JulienChampseix we've reverted to building with Go 1.4 for the time being, so any Go 1.5 bugs like #4655 should not be relevant for 0.9.5.1. |
Version: 0.9.4.2
Error log: (many more similar)
The text was updated successfully, but these errors were encountered: