NOT "custom logs". I turned on `debug=1` -- if that's customization, ok.
Paul Anderson nailed it. I knew nothing about systemd logging. Now I do. As a person with some significant background in computing (yet new to this environment), I suspect the following might be confusing to more than a few people new to weewx.. *Here is the extent of the documentation help for those who happen to have a system using systemd/journald:* "WeeWX logs many events to the system log. On Debian systems, this is /var/log/syslog, on SuSE, /var/log/messages. Your system may use yet another place. When troubleshooting the system, be sure to check it!" :-D On Wednesday, March 15, 2023 at 2:21:13 AM UTC-6 vince wrote: > [...vent mode on, I guess...] > We are seeing these kinds of threads all too often these days... > > A post essentially saying "*my standard logs from systemd are there, but > my old custom logs are gone - where are they?*" is an impossible ask. > > Given the original description saying something broke 23 days ago, it's > entirely possible any logs were logrotated to /dev/null by now. There's > no way to possibly guess what the original poster customized. For all we > know that log was in tmpfs and a reboot made them go poof. Impossible to > help with such a skeletal problem description. > > - No standard and requested twice 'how to report a problem' > information has been provided. > - No info on his customizations has been provided > - We seem to be expected to read minds. > > At some point if you decide to set up a custom setup, you have to be > willing+able to support that custom setup... > > No sympathy here. > > -- 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 on the web visit https://groups.google.com/d/msgid/weewx-user/5eff01a4-5e2e-4964-a1f0-98379a2a29d7n%40googlegroups.com.
