I just skip all that and use: journalctl -xe -u weewx
On Wed, Aug 16, 2023 at 1:37 PM messyp...@gmail.com <messypota...@gmail.com> wrote: > https://github.com/weewx/weewx/wiki/logging > Followed the instr above and while it's probably the best so far, my > current server, Linux OPI5B 5.10.110-rockchip-rk3588 #1.0.2 SMP Thu Apr 13 > 16:55:55 CST 2023 aarch64 aarch64 aarch64 GNU/Linux, running ubuntu jammy > server (22.04), is up to date and I've been reading that the system > maintainers have changed the security on logrotate and even following the > instructions logrotate complained and wouldn't rotate until I set tighter > security on /var/log. Currently the default user has to sudo to view > syslog, and I changed that by adding myself to the adm group. But there are > other problems that needed tightening up. > So when someone says something like "logs are a problem with the operating > system and are outside weewx" (something like that), they're right. PITA. > Thanks. > Here are the links I read up on this about: > > https://stackoverflow.com/questions/52743279/uwsgi-log-rotation-gets-error-parent-directory-has-insecure-permissions > https://github.com/rodjek/puppet-logrotate/issues/50 > > https://stackoverflow.com/questions/55915275/error-ignoring-etc-logrotate-conf-because-it-is-writable-by-group-or-others > (I think my problems were solved, at least on this install, by issuing > "sudo chmod 755 -R /var/log") > > On Wednesday, August 16, 2023 at 7:00:20 PM UTC+2 messyp...@gmail.com > wrote: > >> "sudo systemctl restart rsyslogd" ... there is no process rsyslogd. >> There is a rsyslog. restarted that, but not working. I really don't want to >> have to take a short course on darned system logging for my new ubuntu >> 22.04 running on a orangepi5b. Oh well. >> Thanks for trying to help. >> >> On Friday, July 7, 2023 at 3:46:07 AM UTC+2 vince wrote: >> >>> Impossible to know what you did from your skeletal description, but this >>> worked for me on debian12 using the beta of v5 pip. >>> >>> - wget >>> >>> https://raw.githubusercontent.com/weewx/weewx/master/util/rsyslog.d/weewx.conf >>> -O /tmp/weewx-rsyslogd.conf >>> - sudo cp /tmp/weewx-rsyslogd.conf /etc/rsyslog.d/weewx.conf >>> - sudo systemctl restart rsyslogd >>> - sudo systemctl restart weewx >>> >>> Be careful in the first step to wget the file and output to something >>> 'other' than weewx.conf to protect yourself from accidentally overwriting >>> your actual weewx config file. As long as the file in /etc/rsyslog.d ends >>> in .conf it will work. >>> >>> >>> >>> -- > 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/b325f86f-f6b3-4ee7-8d7e-8035c921c674n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/b325f86f-f6b3-4ee7-8d7e-8035c921c674n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CA%2Bz%2BvD6TwaAOWK49ZKr%2Be-E%3DzQit4RjOCdH1r6BhM%2BHJDN8BZA%40mail.gmail.com.
