Sure enough the rc.d script is rather broken. It has the path to UTIL_ROOT hardcoded to the user directory. A quick edit got around this.
I also edited the paths in /usr/local/etc/rc.d/weewx, but service weewx status is not supported. There is something else missing, as the daemon mode didn't update the database or web pages. Further experimentation showed that when I restarted manually the updates also fail. I moved the database file aside and restarted the daemon. As expected, a new database was created. I'm just concerned what will happen when I need to restart weewx the next time. On Sunday, March 8, 2026 at 1:17:40 PM UTC-5 Marius Schamschula wrote: > It looks like the database is not being updated. > > ls -l /tank/www/weewx/archive/ > > total 162211 > > -rw-rw-rw- 1 root wheel 197065728 Mar 8 03:00 weewx.sdb > > > I tried using the same .sdb file, as it has all the historical data, but > it failed to update with 5.3.1. > > > I have now move that out of the way, and am testing to see if new data is > use to update the web site: > > > That works! > > > However, I need to import data from the old database. I don't want to > loose eighteen year of data. > > On Sunday, March 8, 2026 at 12:54:14 PM UTC-5 Marius Schamschula wrote: > > Something broke my old installation of weewx 4.10.1. It stopped at 3:00 AM > with the change to CDT around here. > > As someone who spends a lot of time avoiding pip and venvs as a port > maintainer on MacPorts I have held back updating to 5.x. I don't like the > Python maintenance nightmare of having multiple (incompatible) versions of > packages installed under various paths. > > Despite the above, I tried installing 5.3.1 using pip and venv as a > regular user. > > The result: bad idea! > > Under FreeBSD the unprivileged user can't open the device (in this case > /dev/ttyU0) > > Root can open the device, but the paths for root are broken. > > Even after adding the path to /home/marius/.local/bin I get > > # weewxd > > Traceback (most recent call last): > > File "/home/marius/.local/bin/weewxd", line 5, in <module> > > from weewxd import main > > ModuleNotFoundError: No module named 'weewxd' > > I have no idea how to tell python 3.11 where that module lives. In the > olden days of 4.10.1, that wouldn't have been an issue. > > So I uninstalled the enduser venv, and installed it as root. > > I installed weewx-venv outside of the /root space, but sure enough > weewx-data appeared under /root. This is a security issue. So I moved it > under the same directory as weewx-venv and used --config to start weewxd. > So far so good. > > I see the live LOOP data come in on the console, the NOAA and html pages > are created. > > However, I'm back at square one: the time is also stuck at 3:00 AM CDT. > > Amy ideas? > > -- 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 visit https://groups.google.com/d/msgid/weewx-user/05aa7c65-4ee8-4ebd-b3f2-3a3c5aeb65e5n%40googlegroups.com.
