I’ve had Influxdb running on my Raspberry Pi 3 for a couple of months successfully. I am attempting to run the Command Line Environment (CLI) by typing ‘influx’ but the command is not found. When I run ‘influxd’ I see "version 1.0.2"
which appears to be outdated and missing the CLI however when I go to update via apt-get, it says the newest package is installed.
Can someone explain how I upgrade to the newest version of influxdb for the RP3 without blowing out my existing database instance?
Can you paste the apt source you are using, usually it is in /etc/apt/sources.list.d/influxdb.list, and also the output of dpkg --print-architecture?
Thanks Daniel, I do not see an influxdb.list file in that directory.
Unwinding what I believe I had setup in the past, I think I followed these instructions: Raspberry Pi Data Logger with InfluxDB and Grafana | John Whittington's Blog
It appears I followed a one-time download install process for version 1.0.2 rather than an apt repo install. Now I need to figure out how to get upgraded without loosing past data.
Always good to have a backup, especially before upgrading, but nothing should be lost. To upgrade you can use the official apt repos listed in the installation instructions.
Hi…i am a new user here. As per my knowledge InfluxDB uses a host’s local time in UTC to assign timestamps to data and for coordination purposes. Use the Network Time Protocol to synchronize time between hosts; if hosts’ clocks aren’t synchronized with NTP, the timestamps on the data written to InfluxDB can be inaccurate.
Hi @NealXu,
You are indeed correct about the need to use a time-synchronization protocol to timestamp data if you want measurement accuracy, at least to a degree. You can, however, have your hosts leave OFF the timestamp in the line protocol from the host. This will then cause the InfluxDB host to timestamp data as it arrives. While this doesn’t necessarily solve the time problem, it at least gives you a single source of truth for timestamps: the InfluxDB server.
Time synchronization between small, embedded devices has been a problem since I first started doing IoT back in 2004. The smaller the device, the more ‘expensive’ time synchronization is, and the less practical it becomes.
Best regards,
dg
