Hi ,
Meanwhile i install on another Rasberry Pi 3 the complete buster raspbian
again and migrate again weewx on it.
Now rsyslogd is working fine but i compare the installation and found no
difference.
Very strange !
nevertheless thanks to all it's working
Am Sa., 23. Jan. 2021 um 09:48 Uhr
Hello,
as i sadly said there is no entry
pi@pi-weewx:/var/log $ ls -l syslog*
-rw-r- 1 root adm 0 Jän 23 00:00 syslog
-rw-r- 1 root adm 284251 Jän 22 19:44 syslog.1
-rw-r- 1 root adm 31249 Jän 20 16:15 syslog.2.gz
-rw-r- 1 root adm 109457 Jän 14 18:44 syslog.3.gz
pi@pi-wee
On Friday, January 22, 2021 at 11:52:32 PM UTC-8 nady...@gmail.com wrote:
> pi@pi-weewx:/var/log $ logger -p user.debug "This is a debug message"
>
> pi@pi-weewx:/var/log $ ls -l /var/log/syslog*
> -rw-r- 1 root adm 0 Jän 23 00:00 /var/log/syslog
> -rw-r- 1 root adm 284251 Jän 22 19:4
Hello,
thx for the hints but i guess it's a syslog issue but can anybody help me
to reinstall it with all default config files.
I checked also for some special characters in the /etc/rsyslogd.conf but I
didn't find any issues.
As i said after boot messages in the syslog entries no more mess
Logging came up a couple weeks ago.
On a pi there are two logfiles. You might find entries in /var/log/syslog
and/or in /var/log/messages depending on how you are configured.
Back then Tom suggested trying:
*logger -p user.debug "This is a debug message"*
On a pi running buster here that w
Everything seems to be configured correctly.
1. Try /var/log/messages
2. Try /var/log/user.log
3. If all else fails, you can use the systemd logger
journalctl --unit=weewx
Other than that, I'm out of ideas. Sorry.
-tk
On Fri, Jan 22, 2021 at 1:40 PM Manfred Nadymacek
wrote:
> pi@pi-weewx
pi@pi-weewx:/var/run $ sudo systemctl status rsyslog.service
● rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor
preset: enabled)
Active: active (running) since Fri 2021-01-22 19:43:44 CET; 2h 56min ago
Docs: man:rsyslogd(8)
Hello,
Only the boot process i guess
pi@pi-weewx:/var/run $ tail -n 50 /var/log/syslog
Jan 22 19:43:44 pi-weewx kernel: [9.793013] random: systemd:
uninitialized urandom read (16 bytes read)
Jan 22 19:43:44 pi-weewx kernel: [ 10.118843] random: crng init done
Jan 22 19:43:44 pi-weewx kernel:
1. What is in your log? For example,
tail -n 50 /var/log/syslog
2. Make sure rsyslog is running
ps aux | grep rsyslogd
On Fri, Jan 22, 2021 at 12:40 PM Manfred Nadymacek
wrote:
> I check the file /etc/rsyslogd
>
> and compare it with original:
> https://gist.github.com/anakuron/1b772fb743c45
I check the file /etc/rsyslogd
and compare it with original:
https://gist.github.com/anakuron/1b772fb743c45c9b685f9a156810be97
no difference found.
Some ideas why weewx don't log in syslog
thx
Manfred Nadymacek schrieb am Freitag, 22. Januar 2021 um 19:27:48 UTC+1:
> Hello,
> Nothing is logg
Hello,
Nothing is logged in /var/log/syslog also not the starting.
Here my /etc/rsyslog.conf
pi@pi-weewx:/var/run $ cat /etc/rsyslog.conf
# /etc/rsyslog.conf configuration file for rsyslog
#
# For more information install rsyslog-doc and see
# /usr/share/doc/rsyslog-doc/html/configuration/index.ht
1. Is anything at all being logged from weewx? Or, is the problem that
DEBUG messages are missing?
2. You may have an error in the configuration for your system logging. What
is in /etc/rsyslog.conf?
On Fri, Jan 22, 2021 at 10:08 AM Manfred Nadymacek
wrote:
>
> Hello,
> I installed on new Rasber
Hello,
I installed on new Rasberry lastest Rasbian buster release with the lastest
4.3 weewx version with python3 option.
All work fine but altough i do debug = 1 in weewx.conf i see nothing logged
in /var/log/syslog
I' not a Linux expert but under Sketch release it works fine.
# Set to 1 fo
13 matches
Mail list logo