root@xili:/# apt purge influxdb-client influxdb-dev influxdb influxdb2 influxdb2-cli
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen… Fertig
Paket »influxdb-client« ist nicht installiert, wird also auch nicht entfernt.
Paket »influxdb-dev« ist nicht installiert, wird also auch nicht entfernt.
Paket »influxdb« ist nicht installiert, wird also auch nicht entfernt.
Paket »influxdb2« ist nicht installiert, wird also auch nicht entfernt.
Paket »influxdb2-cli« ist nicht installiert, wird also auch nicht entfernt.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
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: active (running) since Thu 2022-08-18 17:20:03 CEST; 19min ago
Docs: InfluxDB OSS 2.6 Documentation
Process: 577 ExecStart=/usr/lib/influxdb/scripts/influxd-systemd-start.sh (code=exited, status=0/SUCCESS)
Main PID: 609 (influxd)
Tasks: 7 (limit: 9830)
CGroup: /system.slice/influxdb.service
└─609 /usr/bin/influxd
Aug 18 17:20:02 xili influxd-systemd-start.sh[577]: ts=2022-08-18T15:20:02.291275Z lvl=info msg=“Compaction settings” log_id=0cOOUS5G000 service=storage-engine service=store max_concur
Aug 18 17:20:02 xili influxd-systemd-start.sh[577]: ts=2022-08-18T15:20:02.291646Z lvl=info msg=“Open store (start)” log_id=0cOOUS5G000 service=storage-engine service=store op_name=tsd
Aug 18 17:20:02 xili influxd-systemd-start.sh[577]: ts=2022-08-18T15:20:02.292253Z lvl=info msg=“Open store (end)” log_id=0cOOUS5G000 service=storage-engine service=store op_name=tsdb_
Aug 18 17:20:02 xili influxd-systemd-start.sh[577]: ts=2022-08-18T15:20:02.301604Z lvl=info msg=“Starting retention policy enforcement service” log_id=0cOOUS5G000 service=retention che
Aug 18 17:20:02 xili influxd-systemd-start.sh[577]: ts=2022-08-18T15:20:02.302016Z lvl=info msg=“Starting precreation service” log_id=0cOOUS5G000 service=shard-precreation check_interv
Aug 18 17:20:02 xili influxd-systemd-start.sh[577]: ts=2022-08-18T15:20:02.321022Z lvl=info msg=“Starting query controller” log_id=0cOOUS5G000 service=storage-reads concurrency_quota=1
Aug 18 17:20:02 xili influxd-systemd-start.sh[577]: ts=2022-08-18T15:20:02.398361Z lvl=info msg=“Configuring InfluxQL statement executor (zeros indicate unlimited).” log_id=0cOOUS5G000
Aug 18 17:20:02 xili influxd-systemd-start.sh[577]: ts=2022-08-18T15:20:02.501589Z lvl=info msg=Listening log_id=0cOOUS5G000 service=tcp-listener transport=http addr=:8086 port=8086
Aug 18 17:20:02 xili influxd-systemd-start.sh[577]: ts=2022-08-18T15:20:02.502378Z lvl=info msg=Starting log_id=0cOOUS5G000 service=telemetry interval=8h
Aug 18 17:20:03 xili systemd[1]: Started InfluxDB is an open-source, distributed, time series database.
lines 1-20/20 (END)
???
Hi @ugvsffzawv,
Could you not run:
sudo systemctl disable influxdb
sudo systemctl stop influxdb
I tried to purge while running… was that the problem? Is the uninstaller unable to stop (and remove) the services?
Now i’ve deleted all manually then installed it again. Maybe there are some bugs on our old Debian 9 system with that…?
100% true - at least with v2.3 von Debian 9.x:
“find / | grep influxdb” AFTER “apt purge influxdb2 influxdb2-cli”:
More output of “find / | grep influxdb” - in the middle of the output is the grafana path (has nothing to do with influxdb itself - is just it’s client)
Correct uninstall procedure that cleans up all that s**t:
#!/bin/bash
set -e && set -x;
systemctl daemon-reload; # JUST TO BE SAFE... :-)
service influxdb stop ||:; # STOP SERVICE
apt purge influxdb2 influxdb2-cli; # REMOVE PACKAGES
rm -rf /var/cache/apt/archives && sleep 3 && apt purge --autoremove && sleep 3 && apt clean && sleep 3 && apt update # CLEANUP
unlink /etc/systemd/system/multi-user.target.wants/influxdb.service > /dev/null 2>&1 ||:;
#rm -rf /etc/apt/trusted.gpg.d/influxdb.gpg # DON'T DELETE THE APT CERTIFICATE FILE
rm -rf /etc/default/influxdb2;
rm -rf /etc/systemd/system/multi-user.target.wants/influxdb.service;
rm -rf /lib/systemd/system/influxdb.service;
rm -rf /etc/influxdb
#rm -rf /etc/influxdb/config.toml
rm -rf /var/lib/dpkg/info/influxdb2-cli.conffiles
rm -rf /var/lib/dpkg/info/influxdb2-cli.list
rm -rf /var/lib/dpkg/info/influxdb2-cli.md5sums
rm -rf /var/lib/influxdb
#rm -rf /var/lib/influxdb/influxd.bolt
#rm -rf /var/lib/influxdb/.cache
#rm -rf /var/lib/influxdb/.cache/snowflake
#rm -rf /var/lib/influxdb/.cache/snowflake/ocsp_response_cache.json
#rm -rf /var/lib/influxdb/engine
#rm -rf /var/lib/influxdb/engine/data
#rm -rf /var/lib/influxdb/engine/replicationq
#rm -rf /var/lib/influxdb/influxd.sqlite
rm -rf /var/log/influxdb
rm -rf /root/.influxdbv2
#rm -rf /root/.influxdbv2/influxd.bolt
#rm -rf /root/.influxdbv2/engine
#rm -rf /root/.influxdbv2/engine/data
#rm -rf /root/.influxdbv2/engine/replicationq
#rm -rf /root/.influxdbv2/influxd.sqlite
Also strange - one package in english, two packages in german… WT…?!?
Seems to be FULL of BUGS, version 2.3 on Debian 9.x:
One more: After a Hyper-V snapshop revert, then install it again, “service influxdb status” works while “service influxdb enable” NOT!! - but “systemctl enable influxdb” has not problems so it seems:
root@xili:~#
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: inactive (dead)
Docs: https://docs.influxdata.com/influxdb/
root@xili:~# service influxdb enable
influxdb: unrecognized service
root@xili:~#
root@xili:~#
root@xili:~#
root@xili:~# systemctl enable influuxdb
Failed to enable unit: File influuxdb.service: No such file or directory
root@xili:~# systemctl enable influxdb
root@xili:~# systemctl enable influxdb
root@xili:~# systemctl start influxdb
root@xili:~#
root@xili:~#
root@xili:~# systemctl stataus influxdb
Unknown operation stataus.
root@xili:~# systemctl statas influxdb
Unknown operation statas.
root@xili:~# systemctl status influxdb
● influxdb.service - InfluxDB is an open-source, distributed, time series database
Loaded: loaded (/lib/systemd/system/influxdb.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2022-08-19 13:20:41 CEST; 11s ago
Docs: https://docs.influxdata.com/influxdb/
Process: 46005 ExecStart=/usr/lib/influxdb/scripts/influxd-systemd-start.sh (code=exited, status=0
Main PID: 46006 (influxd)
Tasks: 7 (limit: 9830)
CGroup: /system.slice/influxdb.service
└─46006 /usr/bin/influxd
Aug 19 13:20:41 xili influxd-systemd-start.sh[46005]: ts=2022-08-19T11:20:41.823596Z lvl=info msg="C
Aug 19 13:20:41 xili influxd-systemd-start.sh[46005]: ts=2022-08-19T11:20:41.824013Z lvl=info msg="O
Aug 19 13:20:41 xili influxd-systemd-start.sh[46005]: ts=2022-08-19T11:20:41.824493Z lvl=info msg="O
Aug 19 13:20:41 xili influxd-systemd-start.sh[46005]: ts=2022-08-19T11:20:41.824889Z lvl=info msg="S
Aug 19 13:20:41 xili influxd-systemd-start.sh[46005]: ts=2022-08-19T11:20:41.825413Z lvl=info msg="S
Aug 19 13:20:41 xili influxd-systemd-start.sh[46005]: ts=2022-08-19T11:20:41.826809Z lvl=info msg="S
Aug 19 13:20:41 xili influxd-systemd-start.sh[46005]: ts=2022-08-19T11:20:41.829625Z lvl=info msg="C
Aug 19 13:20:41 xili influxd-systemd-start.sh[46005]: ts=2022-08-19T11:20:41.841640Z lvl=info msg=Li
Aug 19 13:20:41 xili influxd-systemd-start.sh[46005]: ts=2022-08-19T11:20:41.842130Z lvl=info msg=St
Aug 19 13:20:41 xili systemd[1]: Started InfluxDB is an open-source, distributed, time series databa
root@xili:~#
root@xili:~#
root@xili:~#
root@xili:~#
root@xili:~#
root@xili:~# ^C
root@xili:~# ^C
root@xili:~#
Now i will apply the firewall rules again - maybe it will break it?
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
apt install iptables-persistant
YES, GOT IT!! That was the fu***ng problem!!! What kind of shit!! I think i need to vomit soon!!
But iptables -A INPUT -p tcp -s 127.0.0.1/32 --dport 8086 -j ACCEPT does also not help… i’m confused. Really.
No anwser?? Hello…?
??? → (Body is too short (minimum is 20 characters)…)