You said "*/var/log/weewx.log has been empty since the end of January.*" That file is not created in a vanilla default installation. That means you did something to choose to make that configuration happen. I suspect you might have followed this wiki page (link) <https://github.com/weewx/weewx/wiki/logging>. It is very likely you configured rsyslogd to put weewx logs someplace custom. It's also possible you didn't enable rsyslogd to run at boot so if your system rebooted it might not even be running.
You've provided zero information about your system. Nothing about its os or version. Nothing about its logging. Nothing about your weewx installation (version, package-or-setup etc.). In the absence of any real information, there is really not much we can do to help you out other than to point you to the docs of where to look for the usual places. I do not know what "nailed it" means. Re: logs - this is in the FAQ (link) <https://github.com/weewx/weewx/wiki/faq-where-are-my-logs>, in the User's Guide if you pick your os on (this section) <http://weewx.com/docs/usersguide.htm#Where_to_find_things>. Other User's Guide pointer is (here) <http://weewx.com/docs/usersguide.htm#Nothing_in_the_log_file> and there are a variety of other places logging is mentioned. Re: operating systems being confusing - that is not a weewx problem. Each os does things differently. You have to understand your os enough to know where to look and how logging work on your chosen os. On Monday, March 20, 2023 at 1:22:12 PM UTC-7 MrPete wrote: > 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/1a0ef102-9215-463b-9a7e-bdae7f2eaaf1n%40googlegroups.com.
