InfluxDB 1.8.10 not starting anymore after 'stop influxdb.service'

InfluxDB 1
1

Sorry, but i am really frustrated to the influxdb. Influxdb might be fast but - in my opinion - very unstable :frowning:

A couple of weeks ago i have a installed a RasPI 3B+ (with Debian Bullseye) with Node-Red, mySQL, Mosquitto and Influxdb 1.8 completely fresh. The reason to the fresh install was a not starting influxdb!

After a reboot i cross my fingers when influxdb is running afterwards again.
Now the same again: After the last reboot, the service is not starting anymore - no i do that not very often. mySQL e.g. and all other stuff works fine.

What’s going on here? I would appreciate a support :slight_smile:

When i read the it gets a ECONNREFUSED - but why?
I have nothing changed?!

pi@raspberrypi:/ $ sudo systemctl start influxdb.service
Job for influxdb.service failed because a timeout was exceeded.
See “systemctl status influxdb.service” and “journalctl -xe” for details.

pi@raspberrypi:/ $ systemctl status influxdb.service
● 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 Tue 2022-11-01 17:47:29 CET; 1min 19s ago
Docs: InfluxDB OSS 2.6 Documentation
Cntrl PID: 12519 (influxd-systemd)
Tasks: 2 (limit: 1596)
CPU: 6.651s
CGroup: /system.slice/influxdb.service
├─12519 /bin/bash -e /usr/lib/influxdb/scripts/influxd-systemd-start.sh
└─12812 sleep 1

Nov 01 17:48:41 raspberrypi influxd-systemd-start.sh[12519]: InfluxDB API unavailable after 65 attempts…
Nov 01 17:48:41 raspberrypi influxd-systemd-start.sh[12519]: InfluxDB API unavailable after 66 attempts…
Nov 01 17:48:41 raspberrypi influxd-systemd-start.sh[12519]: InfluxDB API unavailable after 67 attempts…
Nov 01 17:48:41 raspberrypi influxd-systemd-start.sh[12519]: InfluxDB API unavailable after 68 attempts…
Nov 01 17:48:42 raspberrypi influxd-systemd-start.sh[12519]: InfluxDB API unavailable after 69 attempts…
Nov 01 17:48:44 raspberrypi influxd-systemd-start.sh[12519]: InfluxDB API unavailable after 70 attempts…
Nov 01 17:48:45 raspberrypi influxd-systemd-start.sh[12519]: InfluxDB API unavailable after 71 attempts…
Nov 01 17:48:46 raspberrypi influxd-systemd-start.sh[12519]: InfluxDB API unavailable after 72 attempts…
Nov 01 17:48:47 raspberrypi influxd-systemd-start.sh[12519]: InfluxDB API unavailable after 73 attempts…
Nov 01 17:48:48 raspberrypi influxd-systemd-start.sh[12519]: InfluxDB API unavailable after 74 attempts…

pi@raspberrypi:/ $ journalctl -xe
Nov 01 17:50:44 raspberrypi Node-RED[395]: port: 8086
Nov 01 17:50:44 raspberrypi Node-RED[395]: }
Nov 01 17:50:45 raspberrypi Node-RED[395]: WARN: Write to InfluxDB failed (attempt: 4). Error: connect ECONNREFUSED 127.0.0.1:8086
Nov 01 17:50:45 raspberrypi Node-RED[395]: at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) {
Nov 01 17:50:45 raspberrypi Node-RED[395]: errno: -111,
Nov 01 17:50:45 raspberrypi Node-RED[395]: code: ‘ECONNREFUSED’,
Nov 01 17:50:45 raspberrypi Node-RED[395]: syscall: ‘connect’,
Nov 01 17:50:45 raspberrypi Node-RED[395]: address: ‘127.0.0.1’,
Nov 01 17:50:45 raspberrypi Node-RED[395]: port: 8086
Nov 01 17:50:45 raspberrypi Node-RED[395]: }
Nov 01 17:50:45 raspberrypi influxd-systemd-start.sh[13178]: InfluxDB API unavailable after 15 attempts…
Nov 01 17:50:46 raspberrypi Node-RED[395]: WARN: Write to InfluxDB failed (attempt: 2). Error: connect ECONNREFUSED 127.0.0.1:8086
Nov 01 17:50:46 raspberrypi Node-RED[395]: at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) {
Nov 01 17:50:46 raspberrypi Node-RED[395]: errno: -111,
Nov 01 17:50:46 raspberrypi Node-RED[395]: code: ‘ECONNREFUSED’,
Nov 01 17:50:46 raspberrypi Node-RED[395]: syscall: ‘connect’,
Nov 01 17:50:46 raspberrypi Node-RED[395]: address: ‘127.0.0.1’,
Nov 01 17:50:46 raspberrypi Node-RED[395]: port: 8086
Nov 01 17:50:46 raspberrypi Node-RED[395]: }
Nov 01 17:50:46 raspberrypi influxd-systemd-start.sh[13178]: InfluxDB API unavailable after 16 attempts…
Nov 01 17:50:47 raspberrypi influxd-systemd-start.sh[13178]: InfluxDB API unavailable after 17 attempts…
Nov 01 17:50:48 raspberrypi influxd-systemd-start.sh[13178]: InfluxDB API unavailable after 18 attempts…
Nov 01 17:50:50 raspberrypi influxd-systemd-start.sh[13178]: InfluxDB API unavailable after 19 attempts…
Nov 01 17:50:51 raspberrypi influxd-systemd-start.sh[13178]: InfluxDB API unavailable after 20 attempts…

2

After I ran out of time and didn’t feel like losing any more live data, I restored an image backup to the SD card and re-imported the rest of the data into mySQL after launch. Now the system is running again and i have at least the mySQL-DB is my reference DB again.

Therefore bypassed the problem with the sledgehammer method. Too bad Influx is highly unreliable here - at least for me. Sorry for this hard opinion.
When the service runs - but only then - Influx runs very well. But it’s not reliable.

Am I betting on the wrong platform here with a Raspi 3B with 2GB SDRAM?
I have read that Influx needs quite a lot of RAM at startup and therefore takes a long time to boot.

Must there be at least four GB?

By the way: It is not only the restart that causes a problem when starting Influx. The same thing happens when I import a lot of data via script.
Too bad, because Influx is already great in terms of functionality and speed.

3

Udate: Even after a ‘systemctl stop influxdb.service’ the DB does not start anymore

On my well working system I wanted to activate Flux. Therefore in the config activated.
After the necessary stop service I started the service again: Again influxdb does not start anymore!

So the issue is not the reboot. This service has - in my opinion - a real problem with the startup.
Or i have the wrong system with a Raspi 3B. I don’t know.

After waiting around 20 Minutes :frowning:
pi@raspberrypi:/etc/influxdb $ systemctl status influxdb.service
● 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 Wed 2022-11-02 09:27:23 CET; 459ms ago
Docs: InfluxDB OSS 2.6 Documentation
Cntrl PID: 31343 (influxd-systemd)
Tasks: 22 (limit: 1596)
CPU: 450ms
CGroup: /system.slice/influxdb.service
├─31343 /bin/bash -e /usr/lib/influxdb/scripts/influxd-systemd-start.sh
├─31344 /usr/bin/influxd -config /etc/influxdb/influxdb.conf
├─31345 /bin/bash -e /usr/lib/influxdb/scripts/influxd-systemd-start.sh
├─31346 influxd config
├─31347 grep -A5 [http]
├─31348 grep ^ bind-address
├─31349 cut -d -f5
└─31350 tr -d "

Nov 02 09:27:23 raspberrypi systemd[1]: Starting InfluxDB is an open-source, distributed, time series database…
Nov 02 09:27:24 raspberrypi influxd-systemd-start.sh[31344]: ts=2022-11-02T08:27:24.019022Z lvl=info msg=“InfluxDB starting” log_id=0dus4axW000 version=1.8.10 branch=1.8 commit=688e697c51fd
Nov 02 09:27:24 raspberrypi influxd-systemd-start.sh[31344]: ts=2022-11-02T08:27:24.021044Z lvl=info msg=“Go runtime” log_id=0dus4axW000 version=go1.13.8 maxprocs=4

4

Since a V2.5 unfortunately does not run on the Raspi 3B, I used the sledgehammer method: Complete uninstallation of Influx.
Then activated Flux before the first start.
Now it runs again.

Let’s see how long. Probably until the first reboot :frowning: