Hello,
I’m not shure if I got your problem, I also have a Pi Zero W with InfluxDB and Grafana. When InfluxDB is starting, it reads many files in the database before providing service to Grafana or to the command influx in a shell. It may take many minutes before beeing ready. I can do a stop/start or both together with restart of the DB and then check my syslog with:
sudo systemctl restart influxdb
tail -f /var/log/syslog
There I see many lines from influxd-systemd-start.sh with …msg=“Opened shard”…, …msg=“Opened file”…, …InfluxDB API unavailable after 16 attempts… and finally InfluxDB started
You can also check afterwards the syslog, when InfluxDB is finally running.
Be patient! If there are many databases, influx has to read files of all of them, and there is a large _internal database, if you didn’t disable this self monitoring, see InfluxDB and Raspberry Pi Zero W
Happy new year!
