If you continue to not do what we ask, we're eventually going to give up trying to help.
Find a time period where you're getting data, then it stops, then it restarts. Query your weewx database and get us the archive table records for that period (sorry, I don't recall mysqld syntax for that, I use sqlite3) Query your influxdb for the same time period and get us the data for that same time period Compare the timestamps on both. During your 'lost data' time period did both databases miss the data ? Do not use grafana. Use direct db queries for both databases please. On Wednesday, January 27, 2021 at 5:56:05 PM UTC-8 [email protected] wrote: > The dropouts have no pattern. I have a few days without any issues, and > then for 24hrs mysql starts choking. > At the beginning I didn't have the influx/grafana part. I've set it up for > testing purposes, to see if mqtt is pushing out data even if the mysql is > behaving. > Previously I tried setting up a vm/ct just for weewx, but I didn't manage > to get interceptor working on virtual interfaces. > > For now I've set the debug flag to 1, so as soon as I see any issue I'll > mark the time and start looking and posting the syslog. > > > On Thursday, January 28, 2021 at 2:41:43 PM UTC+13 vince wrote: > >> On Wednesday, January 27, 2021 at 4:33:25 PM UTC-8 [email protected] >> wrote: >> >>> As an extra info, weewx is failing to generate the html during these >>> periods, but interceptor and mqtt are able to function. >>> >> >> As Tom asked, we're going to need to see your syslogs with weewx debug=1 >> set in order to work this one. >> >> You have a lot of things running on that pi. Pat's skin is pretty >> heavyweight. Do you have other skins enabled too ? You have the box >> acting as an access point. You're running interceptor. You're running >> mysql. You're feeding influxdb in your remote vm. That's a lot of >> things expecting the pi network stack to work with multiple NICs and the >> processor to be able to keep up with. And it's a pi3 so it's 2.4 GHz which >> can be bouncy as well. That's a lot of things to have to be perfect. >> >> So we need to see some syslogs for the weewx stuff, but I'd suggest >> taking grafana out of the picture completely and just doing influxdb >> queries and weewx db queries for the same time periods so we can verify >> that there really is data missing in one db or the other. Find a one-hour >> period and just query each directly. >> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/7a155251-488a-4020-b911-840d8b90b4f6n%40googlegroups.com.
