-
Notifications
You must be signed in to change notification settings - Fork 58
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
Failed to connect to InfluxDB #10
Comments
The Influxdb service is running as a ClusterIP service type, this is why you will not see any Nodeport that will be assigned to it, the loopback IP 127.0.0.1 is not referring to your system, this is referring to the influxdb POD.. Can you provide the output of the following command?
|
Hi, MacBook:jmeter-operator $ kubectl -n tqa get all NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE NAME READY UP-TO-DATE AVAILABLE AGE NAME DESIRED CURRENT READY AGE kubectl -n tqa describe svc tqa-loadtest-influxdb |
Looks Ok to me.. Can you please check the Influxdb logs also.. From your explanation both grafana and jmeter can't establish a connection with the Influxdb, can you try to use the service IP address of influxdb directly in the Grafana and the test script? Change http://tqa-loadtest-influxdb:8086/write?db=jmeter (in cloudssky.jmx) to http://10.107.35.203:8086/write?db=jmeter Also in the influxdb datasource in GRAFANA use the Inlfuxdb IP address 10.107.35.203 instead of tqa-loadtest-influxdb |
Hi, jmeter-operator $ ./start_test.sh Created the tree successfully using cloudssky.jmx Configuring remote engine: 172.17.0.2 Configuring remote engine: 172.17.0.4 Starting remote engines Starting the test @ Fri Jun 07 19:06:05 UTC 2019 (1559934365966) |
First of all, it looks like your kube-dns/coredns is not functioning properly, this should not be, I suggested that action as a way of troubleshooting why you are having issues with the inlfuxdb, I strongly suggest you fix this! DNS is a critical aspect of your kubernetes infrastructure.. The test plan (cloudssky.jmx) is where you configure all the necessary test parameters, please check the jmeter documentation for more information on this. To stop an ongoing test, you can try the suggestion in issue #7 |
Hi, |
HI,
I followed the steps and looks like my cluster and pods are running. ./initialize_cluster.sh also worked as expected and i see the correct output as posted on your github. I tried to run the test via ./start_test.sh and that seemed to work fine but looks my grafana data source (jmterdb) is showing up but failing to connect.
I tried the same in my local jmeter and it says Failed to connect to influx db. Please find the log from jmeter below. I did google stuff and i cant connect to InfluxDB via cluster ip and its shows no node port for infuxdb service when i run minikube service list. Any ideas how to troubleshoot this?
Endpoint: http://tqa-loadtest-influxdb:8086/write?db=jmeter
InfluxdConfig file: bind-address = "127.0.0.1:8088" (this is also not reachable via browser)
Log:
ava.util.concurrent.ExecutionException: java.net.UnknownHostException: tqa-loadtest-influxdb
at org.apache.http.concurrent.BasicFuture.getResult(BasicFuture.java:71) ~[httpcore-4.4.11.jar:4.4.11]
at org.apache.http.concurrent.BasicFuture.get(BasicFuture.java:95) ~[httpcore-4.4.11.jar:4.4.11]
at org.apache.http.impl.nio.client.FutureWrapper.get(FutureWrapper.java:75) ~[httpasyncclient-4.1.4.jar:4.1.4]
at org.apache.jmeter.visualizers.backend.influxdb.HttpMetricsSender.destroy(HttpMetricsSender.java:235) [ApacheJMeter_components.jar:5.1.1 r1855137]
at org.apache.jmeter.visualizers.backend.influxdb.InfluxdbBackendListenerClient.teardownTest(InfluxdbBackendListenerClient.java:413) [ApacheJMeter_components.jar:5.1.1 r1855137]
at org.apache.jmeter.visualizers.backend.BackendListener.testEnded(BackendListener.java:387) [ApacheJMeter_components.jar:5.1.1 r1855137]
at org.apache.jmeter.visualizers.backend.BackendListener.testEnded(BackendListener.java:395) [ApacheJMeter_components.jar:5.1.1 r1855137]
at org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfEnd(StandardJMeterEngine.java:218) [ApacheJMeter_core.jar:5.1.1 r1855137]
at org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:492) [ApacheJMeter_core.jar:5.1.1 r18551
The text was updated successfully, but these errors were encountered: