After running (and restarting) weewx with the new database file I tried replacing it with the old file: Back to 3:00 AM!
Moved back the new database file: it works again! On Sunday, March 8, 2026 at 1:58:04 PM UTC-5 Marius Schamschula wrote: > Indeed, the venv mess is not of weewx's making. > > I'm somewhat surprised at the permissions issue for the USB socket, as my > regular user is a member of wheel. > > I'll try setting up as regular user again. > On Sunday, March 8, 2026 at 1:36:57 PM UTC-5 Vince Skahan wrote: > >> You generally can't avoid venvs on a modern python on a current os. >> Nobody here did that. The python project forced that on everybody. >> >> Installing as root is generally a bad idea. One big improvement in weewx >> v5 is that it no longer needs to run as root nor even 'require' root other >> than to install system-level things. But to answer: >> >> - no module named 'weewxd' is due to you not activating your python >> venv. Always run 'source /some/path/here/bin/activate' to activate >> your >> venv before installing any modules with pip3 or running weewxd or weectl. >> >> >> - for a pip installation, weewxd will run as the user you used when >> you ran the pip command to install weewx itself. >> >> >> - if you installed weewx as a non-privileged user, you will usually >> need to add that user to whatever group has permissions to access the >> serial or usb devices. Typically adding them to group dialout helps. >> Alternately you can set up udev rules to do the right thing. There are >> wiki and faq pages with a variety of ways to do this and which groups can >> typically do what (varies os by os). >> >> >> - you shouldn't need to import data from an old db. The old db >> should work fine. >> >> >> - I have no idea what 'the time is also stuck at 3:00 AM' means. >> >> >> - I have no idea what '(the .sdb) failed to update with 5.3.1' means. >> Your system logs should show what happened if anything. My wild guess >> is >> your weewx.conf file is pointing someplace else. Set debug=1 in >> weewx.conf >> and restart it and check your logs. >> >> >> On Sunday, March 8, 2026 at 10:54:14 AM UTC-7 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/499a46da-2498-428b-848f-b4fa87056e03n%40googlegroups.com.
