Hello everyone.
My current setup is as following:
Rpi5/4Gb + 256Gb M:2 SSD
McArthur hat
OP4
Data to OpenPlotter is fed from N2K network into SignalK. The entire setup is working fine. OpenCPN talks to SignalK, I can see all data etc
I also chose to use InfluxDB 2 + Grafana for historical statistics. I opted for an option to leverage InfluxDB2 plugin to send *all* data to InfluxDB2 from SignalK since I have lots of available storage.
The issue: The SignalK InfluxDB2 plugin frequently stops sending data to Influx. It works for a while and then it just stops. This typically happens when I stop and restart RPI but I think there are also other scenarios which causes data flow from SignalK to Influx to stop.
So far , the only recourse that I know of is to keep clicking on the "Submit" button from the Inflluxdb2 plug-in configuration but it does not last long and I often forget to so so.
Previous system (OP3+RPI4) did not have this issue.
Thanks in advance
Nick
I had a similar issue on a test machine and basically the "UUID" of the system changes after reboots, unless you add an MMSI to the system. once this is done, every reboot will result in the same ID
(2024-08-25, 04:54 AM)Techstyle Wrote: [ -> ]I had a similar issue on a test machine and basically the "UUID" of the system changes after reboots, unless you add an MMSI to the system. once this is done, every reboot will result in the same ID
Thanks Jason for your time taken to respond. I did enter the MMSI in SignalK configuration when I initially installed OP4 but I will pay attention to UUID as I did not think of that possibility. I will also enable plug-in log which hopefully will reveal something.
Everything else on the system works OK as far as I can tell. It is just InfluxDB2 plug-in which seems to be the issue.
Thanks again
Nick
What does the plugin status say on the dashboard? Anything interesting like error messages in Server Log?
(2024-08-25, 08:16 PM)tkurki Wrote: [ -> ]What does the plugin status say on the dashboard? Anything interesting like error messages in Server Log?
I have a similar problem. Rpi 5, Openplotter 4.
When I first boot the Rpi the signal k dashboard listening the plugins says for signalk-to-influxdb2 simply started, but no data is written to influxdata. When I restart signal k then
http://127.0.0.1:8086:... is listed and data is written to the database. It works also if I open the config dialog of the signalk-to-influxdb2 plugin and w/o changing anything press Submit.
Then it seems that the connection to the database stays as long as I don't reboot. BTW I put an MMSI in.
Thank's for the help on this very impressive system
Werner
I have a similar problem on a Rpi 5 running openplotter 4. After boot in the signal k dashboard it just says for signalk-to-influxdb2 "started" and no data is written to influxdb. When I restart signal k or go to the plugin configuration and press (w/o doing any changes) "submit", then the corresponding influxdb bucket is displayed and data is written. This works up to the next reboot. BTW I entered the MMSI, it does not save the problem.
Thank's for all the effort.
Werner
(2024-10-11, 10:42 AM)wernerweg Wrote: [ -> ]I have a similar problem on a Rpi 5 running openplotter 4. After boot in the signal k dashboard it just says for signalk-to-influxdb2 "started" and no data is written to influxdb. When I restart signal k or go to the plugin configuration and press (w/o doing any changes) "submit", then the corresponding influxdb bucket is displayed and data is written. This works up to the next reboot. BTW I entered the MMSI, it does not save the problem.
Thank's for all the effort.
Werner
Hi Werner
Thank you for confirming the issue on your end.
I did end up rebuilding my RPI5 + McArthur hat with fresh image and the issue returned. As you pointed out, data to InfluxDB2 will be written for as long as the system is up and running.
Regards
Hi I am also having the same problem with Rpi 5 running openplotter 4
and even though I followed Werner's instructions it still doesn't work
Version 1.9.2 of the plugin that I just published should fix this issue.