srch

23.12.2018 · I am trying to connect Postrgre with following setting: localhost:5432 Database: database_1 User: postgres pwd: SSL Mode: disable and getting following error: dial tcp 127.0.0.1:5432: connect: connection refused Can someone please help. Thanks

... Grafana with influxDB but each time i try i got this error: http: proxy error: dial tcp 127.0.0.1:8086: connect: connection refused

26.04.2017 · Hello, I am trying to setup Heapster v1.3.0 in a Vagrant-based Kubernetes cluster with Weave-net. There is a master node (bare-metal) running Ubuntu 16.04 with Kubernetes v1.6.1 and weave 1.9.4. This node runs several Ubuntu 16.04 Vagran...

01.10.2020 · What happened: After upgrading grafana from 7.1.5 to 7.2.0, some dashboards don't load completely anymore. But the strange thing is that it seems to stop sending out ajax calls to the backend (Prometheus) to get its data. What you expect...

ERRO[0061] InfluxDB: Couldn't write stats error="Post \"http://localhost:8086/ ... dial tcp 127.0.0.1:8086: connect: connection refused".

I try to deploy grafana/influxdb/heapster on my kubernetes 1.6.6 from this ... 12:44:09 http: proxy error: dial tcp 10.254.231.135:8086: i/o ...

19.11.2018 · Connection from 127.0.0.1:59518 closed these log was happened, when I tried to back it up. so never mind about these log. and the other log is showing like still opening the data files.

If you are having error messages in this section, please refer to the ... influx Connected to http://localhost:8086 version 1.7.7 InfluxDB ...

15.05.2020 · Can't add loki as source to grafana, using docker (Loki: Bad Gateway. 502). Windows #2081

Datasource server value 127.0.0.1:8086 is not valid in the container (localhost in the container != OS localhost - container lives in the ...

0 disables Grafana Live, -1 means unlimited connections. allowed_origins. Note: Available in Grafana v8.0.4 and later versions. The allowed_origins option is a comma-separated list of additional origins (Origin header of HTTP Upgrade request during WebSocket connection establishment) that will be accepted by Grafana Live.

11.02.2020 · Datasource server value 127.0.0.1:8086 is not valid in the container (localhost in the container != OS localhost - container lives in the different network namespace usually). Grafana container in your case is in monitoring network, so connect to influxdb:8086, instead of 127.0.0.1:8086.

I'm getting the following error in /var/log/openhab/events.log ... ConnectException: Failed to connect to localhost/127.0.0.1:8086.

I have created my Ubuntu server VM, installed Docker and ran the following commands to get the containers created, but for some reason, I cannot get Grafana to connect to InfluxDB. My settings are as follows: -Name:Grafana. -URL: https://localhost:8086. -Access: Server.

grafana_1 | 2019/01/07 20:29:39 http: proxy error: dial tcp 127.0.0.1:8086: connect: connection refused grafana_1 ...

Database locked, sleeping then retrying” logger=sqlstore error=“database is locked” retry=0” and then connection is refused. Also i have this ...

25.11.2019 · Depending on how you setup your python container it may be in --network host which allows it to use 127.0.0.1 . Normally you want the bridge mode because it allows you talk to the container by name. Additionally if you have two containers in host mode that both want to use port 80 one of them will fail.

grafana_1 | 2019/01/07 20:29:39 http: proxy error: dial tcp 127.0.0.1:8086: connect: connection refused grafana_1 ...

03.10.2017 · Bug report System info: [Include InfluxDB version, operating system name, and other relevant details] InfluxDB 1.3.5 on Ubuntu 16.04.3 LTS Steps to reproduce: sudo influxd run …

grafana proxy error: dial tcp 127.0.0.1:8086: connect: connection ... error connecting to 127.0.0.1:27017 :: caused by :: connection refused :ports are not ...