Message: Aug 19 11:33:53 xili influxd-systemd-start.sh[610]: InfluxDB API at http://localhost:8086/ready unavailable after 1 attempts… The 2 things i’ve done: changed the name/value pair in /etc/influxdb/config.toml file: ‘http-bind-address = “:8086”’ to "http-bind-address = “MY_IP:8086"”, ""ht…

Please give more detail regarding “…since then, influxdb dose not work anymore.” Do you mean it does not start, is not available even on the machine itself, or simply cannot be accessed from elsewhere on the network? Please tell us how you are testing “does it work?” and give us details on what …

[image] ugvsffzawv: Aug 19 11:33:53 xili influxd-systemd-start.sh[610]: InfluxDB API at http://localhost:8086/ready unavailable after 1 attempts… Always message like that with the service status command: Aug 19 11:33:53 xili influxd-systemd-start.sh[610]: InfluxDB API at http://localhost:808…

…does not work anymore even after a complete cleanup procedure then reinstall via “apt install influxdb2 influxdb2-cli”: Linux xili 4.19.0-0.bpo.9-amd64 #1 SMP Debian 4.19.118-2+deb10u1~bpo9+1 (2020-06-09) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact d…

“even after a complete cleanup procedure” As described (shell script) here: [image] Influxdb daemon still runs after purge ALL influxdb things Correct uninstall procedure that cleans up all that s**t: #!/bin/bash set -e && set -x; systemctl daemon-reload; # JUST TO…

After ~1 minute, that “unavailable” erros occurs - then it repeats in and (endless?) loop: root@xili:~# service influxdb status ● influxdb.service - InfluxDB is an open-source, distributed, time series database Loaded: loaded (/lib/systemd/system/influxdb.service; enabled; vendor preset: enabled…

More “unavilable” entries after a few minutes: root@xili:~# service influxdb status ● influxdb.service - InfluxDB is an open-source, distributed, time series database Loaded: loaded (/lib/systemd/system/influxdb.service; enabled; vendor preset: enabled) Active: activating (start) since Fri 20…

Maybe it has sometinh to do with the iptables rules ive set…? iptables -A INPUT -p tcp -s xxx/24 --dport 8086 -j ACCEPT iptables -A INPUT -p tcp -s yyy/32 --dport 8086 -j ACCEPT iptables -A INPUT -p tcp --dport 8086 -j DROP

root@xili:~# iptables -S -P INPUT ACCEPT -P FORWARD ACCEPT -P OUTPUT ACCEPT -A INPUT -s xxx/24 -p tcp -m tcp --dport 8086 -j ACCEPT -A INPUT -s yyy/32 -p tcp -m tcp --dport 8086 -j ACCEPT -A INPUT -p tcp -m tcp --dport 8086 -j DROP root@xili:~#

SELF-CITE: "seems to be full of bugs … " One more to go!! :wink: → One problem (also a bug?) more: 403 Forbidden: User is inactive when create user - #5 by ugvsffzawv

InfluxDB 2.3 on Debian 9.x has suddenly given up

ugvsffzawv August 19, 2022, 10:44am 4

Seems to be FULL of BUGS, version 2.3 on Debian 9.x: Influxdb daemon still runs after purge ALL influxdb things

Influxdb daemon still runs after purge ALL influxdb things

Topic		Replies	Views
Run: open server: listen: listen tcp 127.0.0.1:8088: bind: address already in use Store influxdb , outputs	28	28927	February 21, 2023
Failed to connect to http://localhost:8086: Get http://localhost:8086/ping: dial tcp [::1]:8086: connect: connection refused	3	10478	October 5, 2020
My influxdb can't start influxdb	8	19287	August 19, 2020
"influx" connects to the wrong port Welcome & Getting Started influxdb	22	5659	December 7, 2019
Install issue with influxd on Ubuntu x64 InfluxDB 2 influxdb , installation	6	6750	August 22, 2024

InfluxDB 2.3 on Debian 9.x has suddenly given up

Related topics