*item 3. How about logging? Version 5 will log to a dedicated weewx file, generally /var/log/weewx/weewx.log. Is that what you're seeing?*
Debian package install under a fresh Debian 12 OS will only log to Systemd's journald. Due to fact that logrotate and rsyslog are no longer installed by default. apt install weewx creates: /etc/logrotate.d/weewx /etc/rsyslog.d/weewx.conf /var/log/weewx Very similar behavior with a pip install under Debian 12 if user runs setup-daemon.systemd But these are all ineffectual as /var/log/weewx/weewx.log will never be created as there is no rsyslog or logrotate running. Logging is only done to Systemd's journald and can be viewed with something like sudo journalctl -f -u weewx Big fear I have is the number 1 support issue of WeeWX V5 is going to become "/var/log/weewx/weewx.log is missing". Maybe a caveat is needed that WeeWx V5 will try to create a dedicated log file, but may not under some OS. Currently under the WeeWx Debian set up Verify section there is this check the log file: tail -50 /var/log/weewx/weewx.log Rather than be helpful this will trigger confusion when the command fails because .var/log/weewx/weewx.log does not exist. BTW just to add to the confusion folks with a fresh Debian 12 install will have the logging issue, while folks that upgraded from a previous version of Debian will not. Oh bother. Paul On Thursday, December 14, 2023 at 5:52:51 PM UTC-5 Tom Keffer wrote: > Hopefully, we are getting very close to a final release for V5.0! > > *Warning!* > But, until then, this is still very much a beta release. You could break > your installation, and it might take skills to recover. If you're using pip > in a virtual environment, the risk is low of breaking other things, but you > will have to shut down your production instance temporarily. For a package > installer, try it in a VM, or on another computer, first. > > *Pip* > > For pip installs, please delete your old virtual environment, then install > from scratch by following the new pip install instructions > <https://weewx.com/docs/5.0/quickstarts/pip/#install-in-a-virtual-environment>. > > While upgrading should work, we are particularly interested in the > experience of a new install, including setting up a daemon and udev files. > Make sure to follow the new instructions that use a daemon setup script. > > > *Debian* > > For Debian package installs, modify /etc/apt/sources.list as follows: > > *echo "deb [arch=all] https://weewx.com/apt-test/python3 > <https://weewx.com/apt-test/python3> buster main" | sudo tee > /etc/apt/sources.list.d/weewx.list* > > Note the "apt-test". This tells apt to look there for the beta release, > instead of the normal repository. You may want to change it back when > you're done. > > > *Red Hat* > > For Red Hat package installs, put this in /etc/yum.repos.d/weewx.repo > > *[weewx] > name=weewx > baseurl=http://weewx.com/yum-test/weewx/el9 > <http://weewx.com/yum-test/weewx/el9> > enabled=1* > > Note the "yum-test". This tells yum to look there for the beta release, > instead of the normal repository. Again, you may want to change things back > when you're done. > > > *What we're looking for* > > 1. We are interested in your upgrade experience. Did the installers get > your configuration file right? Skins? Is the daemon configured correctly? > > 2. With this release, we have included udev rules to set the correct > permissions for devices. Did it work? If not, did unplugging then > replugging the device work? > > 3. How about logging? Version 5 will log to a dedicated weewx file, > generally /var/log/weewx/weewx.log. Is that what you're seeing? > > > *Thanks!* > > -Tom & Matt > > -- 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 weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/48b1ee34-c014-446a-a769-f4f008642f8bn%40googlegroups.com.
