-
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
InfluxDb(0.6.2) crashes after a number of 'multiple time series in a single POST' updates #538
Comments
@Pavel---L can you please provide more information. may be a script that can reproduce the problem or the log file for example. |
Sure, [2014/05/13 21:31:42 FET] INFO local: Initializing write buffer with buffer size of 10000 goroutine 19 [running]: goroutine 1 [IO wait]: goroutine 3 [syscall]: goroutine 4 [chan receive]: goroutine 5 [select]: goroutine 6 [syscall]: goroutine 7 [chan receive]: goroutine 8 [sleep]: goroutine 9 [finalizer wait]: goroutine 11 [chan receive]: goroutine 12 [IO wait]: goroutine 25 [IO wait]: goroutine 14 [select]: goroutine 15 [select]: goroutine 16 [select]: goroutine 18 [IO wait]: goroutine 21 [IO wait]: goroutine 23 [IO wait]: goroutine 24 [IO wait]: goroutine 35 [runnable]: |
Also complete ngrep log of all messages that lead to crash. All messages were applied to fresh db interface: eth1 (192.168.40.0/255.255.255.0) T 192.168.40.178:65268 -> 192.168.40.184:8086 [A] T 192.168.40.178:65269 -> 192.168.40.184:8086 [A] T 192.168.40.178:65270 -> 192.168.40.184:8086 [A] T 192.168.40.178:65268 -> 192.168.40.184:8086 [A] T 192.168.40.178:65269 -> 192.168.40.184:8086 [A] T 192.168.40.178:65270 -> 192.168.40.184:8086 [A] T 192.168.40.178:65268 -> 192.168.40.184:8086 [AF] T 192.168.40.178:65269 -> 192.168.40.184:8086 [AF] T 192.168.40.178:65270 -> 192.168.40.184:8086 [AF] T 192.168.40.178:65290 -> 192.168.40.184:8086 [A] T 192.168.40.178:65290 -> 192.168.40.184:8086 [AP] T 192.168.40.184:8086 -> 192.168.40.178:65290 [AP] T 192.168.40.178:65290 -> 192.168.40.184:8086 [AF] T 192.168.40.178:65290 -> 192.168.40.184:8086 [A] T 192.168.40.178:65291 -> 192.168.40.184:8086 [A] T 192.168.40.178:65291 -> 192.168.40.184:8086 [AP] T 192.168.40.184:8086 -> 192.168.40.178:65291 [AP] T 192.168.40.178:65291 -> 192.168.40.184:8086 [AF] T 192.168.40.178:65291 -> 192.168.40.184:8086 [A] T 192.168.40.178:65292 -> 192.168.40.184:8086 [A] T 192.168.40.178:65292 -> 192.168.40.184:8086 [AP] T 192.168.40.184:8086 -> 192.168.40.178:65292 [AP] T 192.168.40.178:65292 -> 192.168.40.184:8086 [AF] T 192.168.40.178:65292 -> 192.168.40.184:8086 [A] T 192.168.40.178:65293 -> 192.168.40.184:8086 [A] T 192.168.40.178:65293 -> 192.168.40.184:8086 [AP] T 192.168.40.184:8086 -> 192.168.40.178:65293 [AP] T 192.168.40.178:65293 -> 192.168.40.184:8086 [AF] T 192.168.40.178:65293 -> 192.168.40.184:8086 [A] T 192.168.40.178:65294 -> 192.168.40.184:8086 [A] T 192.168.40.178:65294 -> 192.168.40.184:8086 [AP] T 192.168.40.184:8086 -> 192.168.40.178:65294 [AP] T 192.168.40.178:65294 -> 192.168.40.184:8086 [AF] T 192.168.40.178:65294 -> 192.168.40.184:8086 [A] T 192.168.40.178:65295 -> 192.168.40.184:8086 [A] T 192.168.40.178:65295 -> 192.168.40.184:8086 [AP] T 192.168.40.184:8086 -> 192.168.40.178:65295 [AP] T 192.168.40.178:65295 -> 192.168.40.184:8086 [AF] T 192.168.40.178:65295 -> 192.168.40.184:8086 [A] T 192.168.40.178:65297 -> 192.168.40.184:8086 [A] T 192.168.40.178:65297 -> 192.168.40.184:8086 [AP] T 192.168.40.178:65297 -> 192.168.40.184:8086 [AP] T 192.168.40.184:8086 -> 192.168.40.178:65297 [AP] T 192.168.40.178:65297 -> 192.168.40.184:8086 [AP] T 192.168.40.178:65297 -> 192.168.40.184:8086 [AP] T 192.168.40.184:8086 -> 192.168.40.178:65297 [AP] T 192.168.40.178:65297 -> 192.168.40.184:8086 [AP] T 192.168.40.178:65297 -> 192.168.40.184:8086 [AP] T 192.168.40.184:8086 -> 192.168.40.178:65297 [AP] T 192.168.40.178:65297 -> 192.168.40.184:8086 [AP] T 192.168.40.178:65297 -> 192.168.40.184:8086 [AP] T 192.168.40.178:65297 -> 192.168.40.184:8086 [A] T 192.168.40.178:65297 -> 192.168.40.184:8086 [AF] |
I'm a new to GitHub. Is there is a way to attach files instead of dumping the whole log in comment? |
The recommended way is to create a gist on https://gist.github.com/ and link to it in the comment. That said, I think we have the information that we need. I'll let you know if we need more info. |
I can provide you with complete curl commands if it helps |
let me try what i have first. |
I can reproduce the bug, thanks for reporting it. We'll have a fix asap. |
Thanks for fast answer. Looking forward for fix. |
After a number of 'multiple time series in a single POST' updates InfluxDb(0.6.2) crashes and can't be restarted without complete wipe out of /opt/influxdb/shared/data folder.
The text was updated successfully, but these errors were encountered: