As mentioned, I think, I am currently on rc1. It did not start the new version
up, it’s still stopped (I stopped it and backed up weewx.sdb and my conf prior
to running the upgrade).
From: weewx-development@googlegroups.com
On Behalf Of Vince Skahan
Sent: Tuesday, January 9, 2024 5:24 PM
I haven’t tried to re-start weewx since it failed. Should I be good to do so?
Everything looks like it’s owned by the weewx user now.
From: rcsta...@gmail.com
Sent: Tuesday, January 9, 2024 11:01 AM
To: 'matthew wall' ; 'weewx-development'
Subject: RE: [weewx-development] Availability of
root@raspi-server-misc:/etc/systemd/system# cat /etc/default/weewx
WEEWX_PYTHON=python3
WEEWX_PYTHON_ARGS=
WEEWX_BINDIR=/usr/share/weewx
WEEWX_CFG=/etc/weewx/weewx.conf
root@raspi-server-misc:/etc/systemd/system# ls -la /var/lib/weewx
total 673176
drwxrwsr-x 2 weewx weewx 4096 Jan 9
Hey Tom,
Just tried to upgrade from rc1 to rc3-2, and get
Get:1 https://weewx.com/apt-test/python3 buster/main all weewx all 5.0.0rc3-2
[1,556 kB]
Fetched 1,556 kB in 0s (3,314 kB/s)
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 74780 files and
Yes. And yeah, pihole is running dnsmasq itself, and just adding entries for
known problems to 127.0.0.1.
And no, I’ve never seen pihole raise a “load too high” message or anything.
I’ve got it running on same raspberry pi my weewx runs on… chugs along every
day, all day, no issues. One of
Fwiw, I had the same response when my Meteobridge was talking to Pihole...
it just hit DNS like crazy. Thankfully it's just DNS, and that's what DNS
servers are meant to do. You can certainly install dnsmasq on whatever you
have weewx running on and let it handle that load, but as Greg mentioned,
Short of weewx including a dnscacher, which would only solve the issue for
weewx on a computer, not everything else, not sure what can be done. Maybe
include a note that users may want to install dnsmasq on their weewx box if
they use rapidfire? At least then the traffic is all local to the
Hey Tom,
That worked (on my MBP and Raspi, though the latter was substantially slower
(MBP total processing time was 475.95 seconds, raspi was a comical 7999.35))! I
was reading on sqlite3 locking processes for writing, and it seemed oddly
complex, but I’m sure there are reasons for it.
Hey Tom,
Got new weewx install on my MBP (just to speed things up), copied over
weewx.conf (making adjustments for venv install) and my db and can say
calc-missing hangs at a different spot on here. This time hanging at record
49000.
Oh a whim, I added –dry-run, and it processed all
Hey Tom,
Thanks. Below is what I tried… sadly I hit a few roadblocks.
I stopped weewx on the machine, and checked my weewx.conf, and changed the ET
value from “hardware” to “prefer_hardware”. I believe this was due to previous
issue, but I cannot find the thread… =(
Saved that change.
Swapping out default Seasons with the old version resulted in no change. I do
notice skin.conf still says 4.10.2. The previous Seasons skin I believe I had
modified because the station info defaults to saying “Vantage Pro2” (since
that’s the station type in weewx.conf), but I have a Vantage
Other piece I have is ephem installed.
Diffin’g the current Seasons vs the version I have, the biggest difference
seems to be in the Celestial.inc… Not sure if any of these would be causing
massive slowdowns though (output below). Also seeing a lot of unit differences
in skin.conf (things
Thanks Vince for confirming that. So not worried about that being the case
then, which is nice.
From: Vince Skahan
Sent: Wednesday, December 27, 2023 4:29 PM
To: rcsta...@gmail.com
Cc: weewx-development
Subject: Re: [weewx-development] Re: V5.0 release candidate available
I did tests
Chasing my issue, decided to remove some old extensions I wasn’t using.
Rtldavis, sdr, fileparse. Removed the blocks from the now uninstalled
extensions. During that process, the whole station block in weewx.conf seems to
have been removed (unclear if extension uninstall did this, or me on
Hey All,
Okay, stopped weewx, did the change in sources, and an apt upgrade. Declined to
replace weewx.conf, and then updated the existing one to have the weewx root
properly, and start weewx. Started right away. Grabbed the one archive record
that it missed during my process.
Files
Hey Tom,
Thanks! Should I assume I should stop the current weewx, backup the db, etc?
And yup, realize it’s a temp repo. =)
Thanks!
From: Tom Keffer
Sent: Tuesday, December 26, 2023 3:20 PM
To: rcsta...@gmail.com
Cc: weewx-development
Subject: Re: [weewx-development] V5.0 release
Hey All,
I’m going to give this a go, but want to confirm based on this:
https://weewx.com/docs/5.0/upgrade/
I’m just running on a raspi, and installed via apt, so I should just be able to
do as documented here and upgrade this way? I swear a few months back there
wasn’t going to be a
Awesome, thanks Paul! And please don’t consider anything as criticism. Just
testing. =)
Thanks for your work on this, it’s pretty cool! I’m curious what we’ll see when
Tom runs it with all his data. =P
From: weewx-development@googlegroups.com
On Behalf Of Paul Dunphy
Sent: Thursday,
18 matches
Mail list logo
