Pages 240- 241
Raspberry Pi System ui displays
everything looks good with data for 2 -3 minutes, then every one of the system monitor windows gets the following error:
error @3:37-3:38: record is missing label linux_host error @2:19-2:20: record is missing label timeRangeStart error @2:43-2:44: record is missing label timeRangeStop error @1:14-1:15: record is missing label bucket
all of the messages are identical as far as I can tell, and I stopped and started influx – exactly the same thing happens – good data for 2-3 minutes and then EXACTLY the same errors.
Did I miss a step? or is this because my system is slightly different somehow?
What are the steps to debug/troubleshoot? for the noobie?
Hi.
But do you get the data on influxDB? Or it just stops sending the data when you get those errors?
Regadrs,
Sara
The data is all there for about 2 min, then the errors pop up on all the items being monitored.
How do I remove the template? I went back to the influx page for the
Monitor Raspberry Pi
and noticed there was a box in the top right to click for cloud or oss and other stuff, I am wondering if I got the wrong download. I would like to just re-load it all and start over but do not want to complicate the problem by loading a second template that might confuse the issue.
Thanks
I think you can just go to the Telegraf tab in InfluxDB and Delete the template there.
Then, run the command to install the Raspberry Pi Template again (page 236)
Well Sara, I am still at a loss. I deleted everything I could find about the pi monitor using the trash can symbol on each item. then re-loaded the template and got a new token.
I did exactly the same thing when I started to monitor, with EXACTLY the same error.
Do you think there is a problem with this template and running the latest CLI and telegraph? It looks like the template was last updated 2 years ago if I read the github data correctly.
I will continue researching, let me know if you have ideas
Below are my latest cmd sequences – notice the last line:
pi@raspberrypi:~ $ influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/raspberry-pi/raspberry-pi-system.yml
2022/12/02 13:06:32 WARN: Passing URLs via -f/–file is deprecated, please use -u/–template-url instead
L
stuff left out
pi@raspberrypi:~ $ export INFLUX_HOST=http://192.168.1.233:8086
export INFLUX_HOST=http://192.168.1.233:8086
pi@raspberrypi:~ $ export INFLUX_TOKEN=2xMS9YNzRQcsZmZRPrCG0kefwgYXxy0_1R-t4PXBuJET18Iktln8kqPlsS6ifzStfepq5V-TW-RmaNMU6FeMWw==
pi@raspberrypi:~ $ export INFLUX_ORG=”2911 Tree Top”
pi@raspberrypi:~ $ telegraf –config http://192.168.1.233:8086/api/v2/telegrafs/0a61009b21f4a000
2022-12-02T18:25:49Z I! Starting Telegraf 1.24.4
2022-12-02T18:25:49Z I! Available plugins: 221 inputs, 9 aggregators, 26 processors, 20 parsers, 57 outputs
2022-12-02T18:25:49Z I! Loaded inputs: cpu disk diskio exec mem net processes swap system temp
2022-12-02T18:25:49Z I! Loaded aggregators:
2022-12-02T18:25:49Z I! Loaded processors:
2022-12-02T18:25:49Z I! Loaded outputs: influxdb_v2
2022-12-02T18:25:49Z I! Tags enabled: host=raspberrypi
2022-12-02T18:25:49Z I! [agent] Config: Interval:10s, Quiet:false, Hostname:”raspberrypi”, Flush Interval:10s
^C2022-12-02T18:41:54Z I! [agent] Hang on, flushing any cached metrics before shutdown
2022-12-02T18:41:54Z I! [agent] Stopping running outputs
Sara,
This problem has been frustrating, but this item is not critical to the course so I am going to skip the Raspberry Pi System Dashboard template for now and continue with the next part – 6.4 – MQTT + Node-RED + InfluxDB.
But I might be back to this problem later if I can not solve it myself. I will post anything I discover later.
Hi again.
I’ve just installed everything from the start this morning accordingly to the eBook instructions and telegraf monitoring is been running fine for me. So, it’s not a problem with the instructions….
I’m not sure if there is some issue with your system that causes that error….
That unit is not essential to follow the rest of the eBook, but it’s a nice feature to have. So, it would be great if you get it working
Meanwhile, if you find something more about this issue, just let me know.
Regards,
Sara
Sara,
Rereading through my posts I did not mention that I did an update and upgrade on the pi, node-red and when I got the influx I got the newest version of it and the CLI also. Maybe something isn’t working quite right after doing that. I have not had any Pi or node-red problems that I know of.
As I said I will skip the Pi Monitor for now, but we might have to re-visit the problem after I finish other parts of the course.
Thanks
Dave