-
Notifications
You must be signed in to change notification settings - Fork 490
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
Trouble Defining Multiple InfluxDB Servers #142
Comments
This looks correct to me. Are there any logs at all or does the process just hang when trying to connect? |
tail -f /var/log/kapacitor/kapacitor.log - no logs at all. |
@nhproject can you check /var/log/kapacitor/kapacitor.err ? If Kapacitor crashes before it can initialize its logs, the STDERR content gets put there. |
panic: reflect: slice index out of range goroutine 1 [running]: goroutine 17 [syscall, locked to thread]: goroutine 5 [syscall]: |
I've encountered this same issue when attempting to specify three 0.9.6.1 nodes in the config (not sure if it's 0.9-specific). |
I was looking into this an it turns out to be a bug in the config parser. Should be fixed with #155 |
thanks Nat! |
Fixed with #268 |
In the [influxdb] section in the configuration file, there's the "urls" variable. I tried to define over there three influxdb machines which I have in my cluster, like this:
urls = ["SERVER1_URL","SERVER2_URL","SERVER3_URL"].
After that, I restarted the Kapacitor in order to apply it - but nothing happened, it seemed like its stuck, and the log didn't showed the usual messages it always shows.
What can be the reason for that? Should I write the servers in a different way?
The text was updated successfully, but these errors were encountered: