It's possible the so called 'Belchertown v5 issue' is involved but a few things suggest it is not, or if it is it's effect is insignificant:
- weewx.conf indicates the user is using the wview_extended schema - the Belchertown issue raises it's head when a report is run and missing derived obs are calculated on the fly, in this case weectl import is calculating those missing derived obs before reports are run - the Belchertown report generation is completed within 10 seconds - the 'Ctl-C response' shows weectl import was caught executing code that was not Belchertown code (Belchertown does not use locks or threading) Gary On Tuesday 23 July 2024 at 22:15:06 UTC+10 kk44...@gmail.com wrote: > Sebastian E schrieb am Dienstag, 23. Juli 2024 um 13:41:03 UTC+2: > > Here is a longer excerpt from journalctl > > > What I get from that log is, that weectl starts report generation after > importing data. And I see, the Belchertown skin is involved. So there is a > possibility that this problem is involved: v5 performance troubleshooting > <https://github.com/weewx/weewx/wiki/v5-performance-troubleshooting>. > > -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/7d1a603f-b7ed-48a3-aca0-0c6836ae270en%40googlegroups.com.
