Thanks for your comment. No, it's not "harsh", logging IS all over the place, since it's in the designated weewx.log, syslog and also in the systemd journal under several different tags. I'm also aware of secondary instances' tagging scheme in the log. It's just that it's another source of misc. tagging, making it harder to organize and filter the log. Possibly it's caused by various modules using the old syslog module with assumptions about process names. I now constrained them using rsyslog filters, but it's more like inconsistent behavior or regression than anything else. What's not going to magically happen is all old module devs taking prior notice and fix all the old code to comply. At least the basic level of compatibility should have been kept, allowing the old debug flag work. There are also old modules that work very fine while being basically abandoned, but now have botched logging. And no, sadly not all of them are accessible nor willing to touch their legacy code.
On Thursday, May 21, 2020 at 2:24:00 AM UTC+2, gjr80 wrote: > > On Thursday, 21 May 2020 07:44:24 UTC+10, kobuki wrote: >> >> I've upgraded my 3.9.3 to 4.0.0 on a Debian 10. Unfortunately logging now >> is all over the place. >> > > Sounds a little harsh. > > Program name for rsyslog filters is either 'weewx' or 'weewxd' or on a >> second weewx instance, 'weewx-name'. >> > > I am running V4 under Debian 10 and see no 'weewxd' in the logs, but then > again I only run setup.py installs and not package installs. 'weewx-name' > for a second WeeWX instance is (and always has been) expected behaviour; if > you are logging to a single file different program names for each WeeWX > instance makes debugging far easier, also makes it far easier to log each > instance to separate files. > > But then it ignores 'debug = 0' in weewx.conf when a module uses >> syslog.syslog() calls instead of the new Python logger. Modules put out >> debug messages in the log. The old "central" debug setting used to take >> care of them. Can I set the syslog logging level somehow in config for all >> modules that still use the facility? >> > > I doubt whether there will be any magic button you can press in a config > file since V4 now uses the python logging module in lieu of the syslog > module and consequently the old syslog setup code was removed in V4. There > may well be some magic syslog incantation that someone will provide, but I > suspect you will be best served by contacting the 3rd party extension > authors and asking them to update their extension to work (properly) with > V4. > > Gary > -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/52241058-2ea2-457b-886b-2d1054f22f65%40googlegroups.com.
