Still lost what you're getting at, nor if you solved your own problem
somehow (and how, for the next guy).
Bottom line is you have to understand your os and how it logs. You also
have to completely describe your setup so we can try to help. That's why
we always ask.
Most common os will log to /var/log/syslog or /var/log/messages or both.
Sometimes you need to add a syslog daemon package to the core os (rsyslog
or syslog-ng or others) and enable 'that' to make logging to those files
happen, especially if you are systemd based like modern debian/ubuntu.
Your mention of weewx.log tells me you have added a syslog package
configured to put things now. No os does that by default. I'm guessing
you have rsyslog installed. You can check with "dpkg -l | grep syslog"
On a systemd-based os (modern debian(ish) and redhat(ish)) you should learn
journalctl as well. The systemd borg has been increasingly consuming
everything everywhere. We don't control that.
What I asked multiple times for was a basic description of your setup.
A good problem description would have included:
- you're running ubuntu 22.04 LTS
- you're running weewx 4.10.2 in a proxmox vm
- (you STILL have not said if you installed weewx via apt from a
package, or if you ran setup.py to install that way)
- you have rsyslog installed and configured to log weewx to
/var/log/weewx.log
- that log is empty for at least 3 weeks now
- but system status weewx is showing some recent logs
- why is my weewx.log empty ?
If you'd provided that as a description of your setup, my assessment would
have been that you'd added rsyslog log ago and manually started it, and
that the problem was likely that you didn't enable it to start on boot.
You should see output similar to this example from a pi.
pi@pi4:~ $ systemctl status rsyslog
● rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor
preset: enabled)
Active: active (running) since Mon 2022-09-12 18:58:43 PDT; 6 months
10 days ago
TriggeredBy: ● syslog.socket
Docs: man:rsyslogd(8)
man:rsyslog.conf(5)
https://www.rsyslog.com/doc/
Main PID: 421 (rsyslogd)
Tasks: 4 (limit: 4915)
CPU: 5min 41.717s
CGroup: /system.slice/rsyslog.service
└─421 /usr/sbin/rsyslogd -n -iNONE
Warning: journal has been rotated since unit was started, output may be
incomplete.
If your system shows empty yet enabled+running, then I'd guess your
logrotate setup nuked the file but kept the filehandle open, rather than
doing a proper log rotation. It happens.
--
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/ffa8b96e-4976-4509-900a-8a5b6c88ae8bn%40googlegroups.com.
