I tried an upgrade from a 4.10.2 simulator system just to see what happened. It looked OK, so I tried on my main system.
- Debian 12, using the apt package upgrade. - I have two hardware units - Oregon WMR300 and EcoWitt 1000 (v0.6.0b2), both with custom databases and the gw1000 has remapped names. - I have been running as non-root, but *not user or group named "weewx"* - I have been running the systems via systemd-multi (for just on 12 months). I accept many of my problems relate to my non-standard systems and so are of my own making, but here goes... *User name:* I had WEEWX_USER defined in /etc/default/weewx to be "weather" because that user is also attached to other software unrelated to weewx. I was slightly surprised that the installer did not check, but that's not a big deal, bacause I doubt there are many in my situation. I modified my operation to use user 'weewx', who becomes a member of group 'weather'. The installation process changed ownership of files under /etc/weewx, but did not touch anything under HTML_ROOT, so reports failed from then on. My only suggestion here is it would be good if you mention in the upgrade notes that the ownership change will happen unconditionally and that if people do have weewx running under a non-root user of any other name then convert first. *Udev rules*: The upgrade notes state that the example udev rules allow for group ownership. My installation did not get any rules with owner or group changes in them. The example rules just give read-write permission to the world. The sample rules under /etc/weewx/udev are mainly dated 2018 for individual devices, a vantage rule is dated Nov 2021 and an all-in-one "weewx.rules" dated Jan 2021. None of them sets owner or group. On my test system, the sample udev rules are all dated Feb 2023, which I guess is from v4.10.2 *Reports not completing:* Both systems report via customised Seasons skins, and they *appear *to be giving reasonable updates to the reports. The WMR300 merges data from both databases and has a separate issue that I will report in detail later. The gw100 seems to give updated reports, including sensible plots and current conditions every 2 minutes. They sample at 1 minute intervals and every 2 minutes *both *systems independently report: *INFO weewx.engine: Launch of report thread aborted: existing report thread still running* *Both instances are each consuming 60 to 100% cpu permanently.* When I stop (allow it to die) and restart, there is not much cpu activity for the first minute, so I would guess it is tied into thje report generation. I'll have a go with the default skin... -- You received this message because you are subscribed to the Google Groups "weewx-development" 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-development/017d033f-9758-4e79-9d5a-e3c4a1f6c7bfn%40googlegroups.com.
