Hello everyone, I'm now further, if I remove the part from weewx.conf, it works
data_services = user.weatherservices.DWDservice [email protected] schrieb am Mittwoch, 24. Juli 2024 um 01:38:43 UTC+2: > Probably enough chefs in the kitchen already…. But I can’t help myself. > > Did this work at one time and now doesn’t? If so, can you remember what > you changed? > > If it never ‘worked’ or you can’t remember what you changed, I’d step back > and ‘disable’ all non core WeeWX extensions. A quick scan of the > weewx.conf, this is Belchertown skin, weatherservices.DWDservice, and > GTS.GTSService. If it works, add them back one at a time. Or perhaps you > don’t need them for the import… I don’t understand exactly how the > scheduled import interacts or replaces a standard WeeWX install. But if you > are ‘just’ importing data, running the reports after import only to have > them run at the archive interval might be redundant… > > -rich > > On Tuesday 23 July 2024 at 19:12:00 UTC-4 vince wrote: > >> Agree, but it eliminates some possibilities. They also have a secondary >> db which might be where the issue is. Quick thing to try to pin down the >> cause... >> >> On Tuesday, July 23, 2024 at 3:53:00 PM UTC-7 gjr80 wrote: >> >>> True, but I suspect Belchertown is not playing a significant role here, >>> the log extract shows Belchertown completes in less than 10 seconds. My >>> understanding tis that the v5 Belchertown issue is characterised by >>> excessively long Belchertown report generation times. >>> >>> Gary >>> >>> On Wednesday 24 July 2024 at 07:01:47 UTC+10 vince wrote: >>> >>>> One thing to check is that while weewx.conf might say it's using the >>>> wview_extended schema, that is only positively true if the db was created >>>> at weewx v4 or later. Suggest the original poster check their actual db >>>> files to see what the database is actually using. You should probably >>>> check all the databases you have. >>>> >>>> On Tuesday, July 23, 2024 at 1:38:08 PM UTC-7 gjr80 wrote: >>>> >>>>> 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 [email protected] 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/82c28e26-1971-4b69-a6b6-7743fff8f268n%40googlegroups.com.
