Not sure how I missed the configure part, but I guess I did. Ran that, and now I'm on 5.1. And, miraculously, 5.1 works just fine, and I see why. Weewx is now started by a systemd service, which specifies that it requires the network before startup. 5.0.1 was started with the old rc5.d system, and it made no such specification, so it started too early. It was, indeed, a bug in 5.0.1 that has now been fixed.
One last question. What's best practice with weewx.conf? I kept my old (4.8) config file and it works. I see a file called weewx.conf-4.8.0-5.1.0. Is that a merged config file? Should I just use that, or stick with my old config, or merge by hand? Thanks for all the help! On Tuesday, October 15, 2024 at 1:25:24 PM UTC-7 vince wrote: > Run the 'configure apt' section at the beginning of > https://www.weewx.com/docs/5.1/quickstarts/debian/ please. On a clean > ubuntu 24.04.1LTS system the quickstart instructions worked perfectly and I > got 5.1.0 > > On Tuesday, October 15, 2024 at 7:36:28 AM UTC-7 loonsailor wrote: > >> Thanks, Matthew, I think you're right. I started weewx using systemctl >> and it works. So, probably a startup ordering problem. I won't be able to >> work on that until this afternoon (PDT) to confirm. >> >> As for the version issue, I hadn't noticed that I was getting this >> error. Should I override somehow, or is it an issue with the repository? >> >> Err:1 https://weewx.com/apt/python3 buster InRelease >> The following signatures couldn't be verified because the public key is >> not available: NO_PUBKEY E788768B9CB16E10 >> Reading package lists... Done >> W: GPG error: https://weewx.com/apt/python3 buster InRelease: The >> following signatures couldn't be verified because the public key is not >> available: NO_PUBKEY E788768B9CB16E10 >> E: The repository 'https://weewx.com/apt/python3 buster InRelease' is >> not signed. >> N: Updating from such a repository can't be done securely, and is >> therefore disabled by default. >> N: See apt-secure(8) manpage for repository creation and user >> configuration details. >> >> On Tuesday, October 15, 2024 at 5:48:30 AM UTC-7 matthew wall wrote: >> >>> On Monday, October 14, 2024 at 7:06:24 PM UTC-4 loonsailor wrote: >>> >>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL __main__: Unable >>> to load driver: [Errno 101] Network is unreachable >>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL __main__: >>> **** Exiting... >>> >>> >>> this smells like weewx starting before the networking has started. can >>> you 'sudo systemctl start weewx' once the system is up and running? >>> >>> >>> Oct 14 14:33:20 ubu-mini-weather systemd[1]: weewx.service: Main process >>> exited, code=exited, status=4/NOPERMISSION >>> Oct 14 14:33:20 ubu-mini-weather systemd[1]: weewx.service: Failed with >>> result 'exit-code'. >>> >>> >>> but this indicates something more insidious, such as a firewall, or >>> selinux/apparmor, or some kind of systemd jail. can you get more >>> information from systemd about why it is reporting NOPERMISSION for your >>> weewxd process? >>> >>> -- 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/1d2cba85-63a3-4103-9e98-119b931361adn%40googlegroups.com.
