Hello, I’m new to both Influxdb & RPI. i followed many tutorials to run influxdb on my RPI but i always ends up with this Error message :
pi@raspberrypi:~ $ sudo systemctl start influxdb
Job for influxdb.service failed because the control process exited with error code.
See "systemctl status influxdb.service" and "journalctl -xe" for details.
when i do the cmd " journalctl -xe " i get the following :
pi@raspberrypi:~ $ journalctl -xe
Aug 01 13:17:17 raspberrypi systemd[1]: Stopped InfluxDB is an open-source, distributed, time series database.
-- Subject: A stop job for unit influxdb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit influxdb.service has finished.
--
-- The job identifier is 1624 and the job result is done.
Aug 01 13:17:17 raspberrypi systemd[1]: influxdb.service: Start request repeated too quickly.
Aug 01 13:17:17 raspberrypi systemd[1]: influxdb.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit influxdb.service has entered the 'failed' state with result 'exit-code'.
Aug 01 13:17:17 raspberrypi systemd[1]: Failed to start InfluxDB is an open-source, distributed, time series database.
-- Subject: A start job for unit influxdb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit influxdb.service has finished with a failure.
--
-- The job identifier is 1624 and the job result is failed.
lines 2583-2605/2605 (END)
Aug 01 13:17:17 raspberrypi systemd[1]: Stopped InfluxDB is an open-source, distributed, time series database.
-- Subject: A stop job for unit influxdb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit influxdb.service has finished.
--
-- The job identifier is 1624 and the job result is done.
Aug 01 13:17:17 raspberrypi systemd[1]: influxdb.service: Start request repeated too quickly.
Aug 01 13:17:17 raspberrypi systemd[1]: influxdb.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit influxdb.service has entered the 'failed' state with result 'exit-code'.
Aug 01 13:17:17 raspberrypi systemd[1]: Failed to start InfluxDB is an open-source, distributed, time series database.
-- Subject: A start job for unit influxdb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit influxdb.service has finished with a failure.
--
-- The job identifier is 1624 and the job result is failed.
~
~
~
~
~
~
~
~
~
~
~
~
lines 2583-2605/2605 (END)
appreciate your kind help
@Mr_Influx if you’re trying to run v1.8.7, you’re probably running into this: Influxdb 1.8.7 will not start
yes, this popped up on my pi after the 1.8.7 update. I “fixed” it temporarily it seems when I chmod +x the startup script, but this morning, service keeps dying and I get
runtime: out of memory: cannot allocate 81920-byte block (1252196352 in use) fatal error: out of memory
i’ve already migrated off inmem use, so, that’s not it.
frustrating
Unless the log is captured differently on the Raspberry Pi, I think this is a different issue.
I’ve seen a similar issue where the service control command - systemctl start influxdb - attempted to start the influx service in rapid succession, failing each time, and then giving up. In my case, attempting to start are running influxdb seemed to be the problem. I would stop it, wait for the process to fully exit, and then start it.
If you wanted to pursue this on your own, see if there is a way to launch influxdb from a command line, i.e. trying remove systemd from the context, and look for other errors emitted that are not captured in the logs that displayed by journalctl. (Sorry, can’t be of much help to you there…)
i completely stopped the services, due to what you exactly stated. systemctl has restart on fail, so it’d want to keep starting influx. I killed the services all together and ran it manually, and was encountering the out of memory error, which is normally seen with inmem configured. I migrated to ts1 and off of inmem, several days ago and had not seen any issues. everything was re-indexed and operating as expected, until this 1.8.7 update. then there was the script permissions, which seemed to fix things, until today. then the out of mem error popped up again. lots of strangeness right now
