-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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 cluster: tcp.Mux: handler not registered: 71 #5846
Comments
Hi @keksior, Can you provide more information, including steps to reproduce? How many nodes? How have you configured them? What version of Influx? |
Ubuntu 14.04.03, influx 0.10.1-1. 2 nodes: node0,node1. I configured them like this: node0: node1: on the node1 i also added into file /etc/default/influxdb this: |
@keksior you need to join to the meta node's HTTP service. Port So, when starting |
Now it added my node1 to meta_nodes, but not the data_nodes: data_nodes |
Can you provide the logs for both nodes please? |
node0: |
Can someone help me solving it out? |
I found that setting ":8086" in config make localhost in "show servers" data_nodes. When i changed it to ip address and cleared on node0 /var/lib/influxdb/meta/* it worked everything. Thanks for help. |
I still have a problem. I've got whole cluster running: data_nodes retention: But the data is not send to the secondary server. How can i debug this? |
Hi @keksior, Are you saying you're writing to |
I checked disk usage: node0: node1: |
Can you reproduce this from startup with a fresh cluster? If not can you provide the influx logs for a period where you know writes On Thursday, 3 March 2016, keksior notifications@github.com wrote:
Edd Robinson InfluxData.com http://influxdata.com/ Github http://www.github.com/e-dard / LinkedIn |
I have data coming in to my influx every few seconds. The logs for influx0: And the last logs from the node1: I have nothing more than tsm1 logs in my node1 log file. |
I cleared /var/lib/influxdb on both nodes and started from the start: node0: node1: The problem still exist. Any ideas? |
This is from an old version and we no longer support clustering in the open source version, but in case you're still trying to figure this out, you're probably using the wrong port somewhere in your configuration file. This error message happens when you try to make an HTTP (8086) request against the RPC port (8088). I can't remember which configuration option it was exactly, but that would be a good place to start with. I'm going to close this as it's an issue we're not going to fix (the clustering code is dramatically different from what 0.10 had), but I hope this helps a bit with trying to figure out your configuration issue. I'm sorry we were not able to get to responding to this issue in a more timely manner. |
I have a problem with setting up a influxdb cluster. I did everything from the manual and on the node0 i've got error in logs:
[tcp] 2016/02/26 09:55:00 tcp.Mux: handler not registered: 71
And on my joining node1:
[metaclient] 2016/02/26 09:57:59 failure getting snapshot from influx0.gem.lan:8088: Get http://influx0.gem.lan:8088?index=0: read tcp 10.33.44.158:8088: connection reset by peer
node0 (main) listenings:
tcp 0 0 10.33.44.158:8083 0.0.0.0:* LISTEN 10231/influxd
tcp 0 0 10.33.44.158:8088 0.0.0.0:* LISTEN 10231/influxd
tcp 0 0 10.33.44.158:8091 0.0.0.0:* LISTEN 10231/influxd
tcp6 0 0 :::8086 :::* LISTEN 10231/influxd
Tried to delete everything from /var/lib/influxdb/ on both servers, didn't worked.
My node1 /etc/default/influxdb:
INFLUXD_OPTS="-join 10.33.44.158:8088"
Please help me solving it out.
The text was updated successfully, but these errors were encountered: