Influxdb not running since update to dietpi 9.8.0

Troubleshooting
1

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | 9.8.0
  • Distro version | bookworm 0
  • Kernel version | Linux DietPiRysolar 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
  • Architecture | arm64
  • SBC model | RPi Zero 2 W (aarch64)
  • Power supply used | 5V 1A RAVpower
  • SD card used | SanDisk ultra

Additional Information (if applicable)

  • Software title | influxdb
  • Was the software title installed freshly or updated/migrated? updated
  • Can this issue be replicated on a fresh installation of DietPi?

Steps to reproduce

update dietpi to 9.8.0, influxdb.servivce fails to start

Expected behaviour

influxdb service should start smoothly

Actual behavior

systemctl start influxdb gives:
Job for influxdb.service failed because the control process exited with error code.

systemctl status influxdb gives:
ExecStart=/usr/share/influxdb/scripts/influxd-systemd-start.sh (code=exited, status=1/FAILURE)-

However, executing as root /usr/share/influxdb/scripts/influxd-systemd-start.sh works as expected!

Extra details

In some log I think I saw something like /usr/share/bin/pkttyagent file not found. But not sure where

2

Pls share following log

journalctl -u influxdb
3

Sure:

> journalctl -r -n 200 -u influxdb 
Dec 04 08:39:04 DietPiRysolar systemd[1]: Failed to start influxdb.service - InfluxDB is an open-source, distributed, time series database.
Dec 04 08:39:04 DietPiRysolar systemd[1]: influxdb.service: Failed with result 'exit-code'.
Dec 04 08:39:04 DietPiRysolar systemd[1]: influxdb.service: Start request repeated too quickly.
Dec 04 08:39:04 DietPiRysolar systemd[1]: influxdb.service: Consumed 1.140s CPU time.
Dec 04 08:39:04 DietPiRysolar systemd[1]: Stopped influxdb.service - InfluxDB is an open-source, distributed, time series database.
Dec 04 08:39:04 DietPiRysolar systemd[1]: influxdb.service: Scheduled restart job, restart counter is at 5.
Dec 04 08:39:03 DietPiRysolar systemd[1]: influxdb.service: Consumed 1.140s CPU time.
Dec 04 08:39:03 DietPiRysolar systemd[1]: Failed to start influxdb.service - InfluxDB is an open-source, distributed, time series database.
Dec 04 08:39:03 DietPiRysolar systemd[1]: influxdb.service: Failed with result 'exit-code'.
Dec 04 08:39:03 DietPiRysolar systemd[1]: influxdb.service: Control process exited, code=exited, status=1/FAILURE
Dec 04 08:39:03 DietPiRysolar influxd-systemd-start.sh[1858916]: yes: standard output: Broken pipe
Dec 04 08:39:03 DietPiRysolar influxd-systemd-start.sh[1858917]: buildtsi: mkdir /var/lib/influxdb/data/_internal/_series: permission denied
Dec 04 08:39:02 DietPiRysolar systemd[1]: Starting influxdb.service - InfluxDB is an open-source, distributed, time series database...
Dec 04 08:39:02 DietPiRysolar systemd[1]: influxdb.service: Consumed 1.110s CPU time.
Dec 04 08:39:02 DietPiRysolar systemd[1]: Stopped influxdb.service - InfluxDB is an open-source, distributed, time series database.
Dec 04 08:39:02 DietPiRysolar systemd[1]: influxdb.service: Scheduled restart job, restart counter is at 4.
Dec 04 08:39:02 DietPiRysolar systemd[1]: influxdb.service: Consumed 1.110s CPU time.

The service seems to be started under influxdb, so I tried to change permissions for /var/lib/influxdb like so:

> chgrp -R influxdb influxdb
> chmod -R g+w influxdb

But that didnt change the error message.

4

probably you would need to check the whole chain

Can you check following

ls -la /var/lib

Usually folder influxdb should be linked to /mnt/dietpi_userdata/influxdb. And within /mnt/dietpi_userdata/influxdb all files and folder should belong to user & group influxdb

AAAHhh and now I remember Influxdb not working after update - #6 by Joulinar

Thats why a forum search could help sometimes

5

yep, that was it! thanks, despite some minor hiccup ensuring that all influxdb processes were stopped, and pid file removed. But now it starts smoothly again.
Thanks for the quick help!

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.