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 <nady2...@gmail.com> wrote: > 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) > https://www.rsyslog.com/doc/ > Main PID: 345 (rsyslogd) > Tasks: 4 (limit: 2063) > CGroup: /system.slice/rsyslog.service > └─345 /usr/sbin/rsyslogd -n -iNONE > > Jän 22 19:43:43 pi-weewx systemd[1]: Starting System Logging Service... > Jän 22 19:43:44 pi-weewx rsyslogd[345]: imuxsock: Acquired UNIX socket > '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0] > Jän 22 19:43:44 pi-weewx rsyslogd[345]: [origin software="rsyslogd" > swVersion="8.1901.0" x-pid="345" x-info="https://www.rsyslog.com";] start > Jän 22 19:43:44 pi-weewx systemd[1]: Started System Logging Service. > pi@pi-weewx:/var/run $ > > > > Am Fr., 22. Jan. 2021 um 22:39 Uhr schrieb Manfred Nadymacek < > nady2...@gmail.com>: > >> 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: [ 10.118857] random: 7 urandom >> warning(s) missed due to ratelimiting >> Jan 22 19:43:44 pi-weewx kernel: [ 10.119190] i2c /dev entries driver >> Jan 22 19:43:44 pi-weewx kernel: [ 11.634746] EXT4-fs (sda2): >> re-mounted. Opts: (null) >> Jan 22 19:43:44 pi-weewx kernel: [ 12.606884] mc: Linux media >> interface: v0.10 >> Jan 22 19:43:44 pi-weewx kernel: [ 12.659981] videodev: Linux video >> capture interface: v2.00 >> Jan 22 19:43:44 pi-weewx kernel: [ 12.673027] vc_sm_cma: module is from >> the staging directory, the quality is unknown, you have been warned. >> Jan 22 19:43:44 pi-weewx kernel: [ 12.675957] bcm2835_vc_sm_cma_probe: >> Videocore shared memory driver >> Jan 22 19:43:44 pi-weewx kernel: [ 12.675982] [vc_sm_connected_init]: >> start >> Jan 22 19:43:44 pi-weewx kernel: [ 12.684333] [vc_sm_connected_init]: >> installed successfully >> Jan 22 19:43:44 pi-weewx kernel: [ 12.702412] bcm2835_mmal_vchiq: >> module is from the staging directory, the quality is unknown, you have been >> warned. >> Jan 22 19:43:44 pi-weewx kernel: [ 12.702426] bcm2835_mmal_vchiq: >> module is from the staging directory, the quality is unknown, you have been >> warned. >> Jan 22 19:43:44 pi-weewx kernel: [ 12.717251] bcm2835_v4l2: module is >> from the staging directory, the quality is unknown, you have been warned. >> Jan 22 19:43:44 pi-weewx kernel: [ 12.732525] bcm2835_isp: module is >> from the staging directory, the quality is unknown, you have been warned. >> Jan 22 19:43:44 pi-weewx kernel: [ 12.748728] bcm2835_codec: module is >> from the staging directory, the quality is unknown, you have been warned. >> Jan 22 19:43:44 pi-weewx kernel: [ 12.754787] bcm2835-isp bcm2835-isp: >> Device node output[0] registered as /dev/video13 >> Jan 22 19:43:44 pi-weewx kernel: [ 12.755512] bcm2835-isp bcm2835-isp: >> Device node capture[0] registered as /dev/video14 >> Jan 22 19:43:44 pi-weewx kernel: [ 12.761745] bcm2835-isp bcm2835-isp: >> Device node capture[1] registered as /dev/video15 >> Jan 22 19:43:44 pi-weewx kernel: [ 12.765795] bcm2835-isp bcm2835-isp: >> Device node stats[2] registered as /dev/video16 >> Jan 22 19:43:44 pi-weewx kernel: [ 12.765844] bcm2835-isp bcm2835-isp: >> Register output node 0 with media controller >> Jan 22 19:43:44 pi-weewx kernel: [ 12.765882] bcm2835-isp bcm2835-isp: >> Register capture node 1 with media controller >> Jan 22 19:43:44 pi-weewx kernel: [ 12.765912] bcm2835-isp bcm2835-isp: >> Register capture node 2 with media controller >> Jan 22 19:43:44 pi-weewx kernel: [ 12.765950] bcm2835-isp bcm2835-isp: >> Register capture node 3 with media controller >> Jan 22 19:43:44 pi-weewx kernel: [ 12.766606] bcm2835-isp bcm2835-isp: >> Loaded V4L2 bcm2835-isp >> Jan 22 19:43:44 pi-weewx kernel: [ 12.768591] bcm2835-codec >> bcm2835-codec: Device registered as /dev/video10 >> Jan 22 19:43:44 pi-weewx kernel: [ 12.768651] bcm2835-codec >> bcm2835-codec: Loaded V4L2 decode >> Jan 22 19:43:44 pi-weewx kernel: [ 12.787790] snd_bcm2835: module is >> from the staging directory, the quality is unknown, you have been warned. >> Jan 22 19:43:44 pi-weewx kernel: [ 12.789439] bcm2835-codec >> bcm2835-codec: Device registered as /dev/video11 >> Jan 22 19:43:44 pi-weewx kernel: [ 12.789494] bcm2835-codec >> bcm2835-codec: Loaded V4L2 encode >> Jan 22 19:43:44 pi-weewx kernel: [ 12.794503] bcm2835_audio >> bcm2835_audio: card created with 4 channels >> Jan 22 19:43:44 pi-weewx kernel: [ 12.797944] bcm2835-codec >> bcm2835-codec: Device registered as /dev/video12 >> Jan 22 19:43:44 pi-weewx kernel: [ 12.798000] bcm2835-codec >> bcm2835-codec: Loaded V4L2 isp >> Jan 22 19:43:44 pi-weewx kernel: [ 12.861457] bcm2835_audio >> bcm2835_audio: card created with 4 channels >> Jan 22 19:43:44 pi-weewx kernel: [ 13.236648] usbcore: registered new >> interface driver uas >> Jan 22 19:43:44 pi-weewx kernel: [ 13.368702] sd 0:0:0:0: Attached scsi >> generic sg0 type 0 >> Jan 22 19:43:44 pi-weewx kernel: [ 13.895291] logitech-djreceiver >> 0003:046D:C52B.0003: hiddev96,hidraw0: USB HID v1.11 Device [Logitech USB >> Receiver] on usb-3f980000.usb-1.4/input2 >> Jan 22 19:43:44 pi-weewx kernel: [ 14.033543] input: Logitech Unifying >> Device. Wireless PID:4024 Keyboard as >> /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.2/0003:046D:C52B.0003/0003:046D:4024.0005/input/input5 >> Jan 22 19:43:44 pi-weewx kernel: [ 14.035203] input: Logitech Unifying >> Device. Wireless PID:4024 Mouse as >> /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.2/0003:046D:C52B.0003/0003:046D:4024.0005/input/input6 >> Jan 22 19:43:44 pi-weewx kernel: [ 14.036317] input: Logitech Unifying >> Device. Wireless PID:4024 Consumer Control as >> /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.2/0003:046D:C52B.0003/0003:046D:4024.0005/input/input7 >> Jan 22 19:43:44 pi-weewx kernel: [ 14.037377] hid-generic >> 0003:046D:4024.0005: input,hidraw1: USB HID v1.11 Keyboard [Logitech >> Unifying Device. Wireless PID:4024] on usb-3f980000.usb-1.4/input2:1 >> Jan 22 19:43:44 pi-weewx kernel: [ 14.769176] input: Logitech K400 as >> /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.2/0003:046D:C52B.0003/0003:046D:4024.0005/input/input11 >> Jan 22 19:43:44 pi-weewx kernel: [ 14.775774] logitech-hidpp-device >> 0003:046D:4024.0005: input,hidraw1: USB HID v1.11 Keyboard [Logitech K400] >> on usb-3f980000.usb-1.4/input2:1 >> Jan 22 19:43:44 pi-weewx kernel: [ 16.857731] 8021q: 802.1Q VLAN >> Support v1.8 >> Jan 22 19:43:44 pi-weewx kernel: [ 17.063954] cfg80211: Loading >> compiled-in X.509 certificates for regulatory database >> Jan 22 19:43:44 pi-weewx kernel: [ 17.206345] Adding 102396k swap on >> /var/swap. Priority:-2 extents:3 across:135164k FS >> Jan 22 19:43:44 pi-weewx kernel: [ 17.213391] cfg80211: Loaded X.509 >> cert 'sforshee: 00b28ddf47aef9cea7' >> Jan 22 19:43:45 pi-weewx kernel: [ 17.551558] smsc95xx 1-1.1:1.0 eth0: >> hardware isn't capable of remote wakeup >> Jan 22 19:43:46 pi-weewx kernel: [ 19.100835] smsc95xx 1-1.1:1.0 eth0: >> link up, 100Mbps, full-duplex, lpa 0xC1E1 >> Jan 22 19:44:08 pi-weewx kernel: [ 40.747005] warning: process >> `colord-sane' used the deprecated sysctl system call with 8.1.2. >> >> pi@pi-weewx:/var/run $ ps aux | grep rsyslogd >> root 345 0.0 0.2 25512 2736 ? Ssl 19:46 0:00 >> /usr/sbin/rsyslogd -n -iNONE >> pi 1771 0.0 0.0 7492 540 pts/0 S+ 22:38 0:00 grep >> --color=auto rsyslogd >> pi@pi-weewx:/var/run $ >> >> Thx >> >> >> >> >> >> Am Fr., 22. Jan. 2021 um 22:36 Uhr schrieb Tom Keffer <tkef...@gmail.com >> >: >> >>> 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 <nady2...@gmail.com> >>> wrote: >>> >>>> 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 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.html >>>>> >>>>> >>>>> ################# >>>>> #### MODULES #### >>>>> ################# >>>>> >>>>> module(load="imuxsock") # provides support for local system logging >>>>> module(load="imklog") # provides kernel logging support >>>>> #module(load="immark") # provides --MARK-- message capability >>>>> >>>>> # provides UDP syslog reception >>>>> #module(load="imudp") >>>>> #input(type="imudp" port="514") >>>>> >>>>> # provides TCP syslog reception >>>>> #module(load="imtcp") >>>>> #input(type="imtcp" port="514") >>>>> >>>>> >>>>> ########################### >>>>> #### GLOBAL DIRECTIVES #### >>>>> ########################### >>>>> >>>>> # >>>>> # Use traditional timestamp format. >>>>> # To enable high precision timestamps, comment out the following line. >>>>> # >>>>> $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat >>>>> >>>>> # >>>>> # Set the default permissions for all log files. >>>>> # >>>>> $FileOwner root >>>>> $FileGroup adm >>>>> $FileCreateMode 0640 >>>>> $DirCreateMode 0755 >>>>> $Umask 0022 >>>>> >>>>> # >>>>> # Where to place spool and state files >>>>> # >>>>> $WorkDirectory /var/spool/rsyslog >>>>> >>>>> # >>>>> # Include all config files in /etc/rsyslog.d/ >>>>> # >>>>> $IncludeConfig /etc/rsyslog.d/*.conf >>>>> >>>>> >>>>> ############### >>>>> #### RULES #### >>>>> ############### >>>>> >>>>> # >>>>> # First some standard log files. Log by facility. >>>>> # >>>>> auth,authpriv.* /var/log/auth.log >>>>> *.*;auth,authpriv.none -/var/log/syslog >>>>> #cron.* /var/log/cron.log >>>>> daemon.* -/var/log/daemon.log >>>>> kern.* -/var/log/kern.log >>>>> lpr.* -/var/log/lpr.log >>>>> mail.* -/var/log/mail.log >>>>> user.* -/var/log/user.log >>>>> >>>>> # >>>>> # Logging for the mail system. Split it up so that >>>>> # it is easy to write scripts to parse these files. >>>>> # >>>>> mail.info -/var/log/mail.info >>>>> mail.warn -/var/log/mail.warn >>>>> mail.err /var/log/mail.err >>>>> >>>>> # >>>>> # Some "catch-all" log files. >>>>> # >>>>> *.=debug;\ >>>>> auth,authpriv.none;\ >>>>> news.none;mail.none -/var/log/debug >>>>> *.=info;*.=notice;*.=warn;\ >>>>> auth,authpriv.none;\ >>>>> cron,daemon.none;\ >>>>> mail,news.none -/var/log/messages >>>>> >>>>> # >>>>> # Emergencies are sent to everybody logged in. >>>>> # >>>>> *.emerg :omusrmsg:* >>>>> >>>>> >>>>> >>>>> I see only something when i do: >>>>> /etc/init.d/weewx status >>>>> pi@pi-weewx:/home/weewx $ sudo /etc/init.d/weewx status >>>>> ● weewx.service - LSB: weewx weather system >>>>> Loaded: loaded (/etc/init.d/weewx; generated) >>>>> Active: active (running) since Fri 2021-01-22 17:51:58 CET; 1h >>>>> 35min ago >>>>> Docs: man:systemd-sysv-generator(8) >>>>> Process: 704 ExecStart=/etc/init.d/weewx start (code=exited, >>>>> status=0/SUCCESS) >>>>> Tasks: 5 (limit: 2063) >>>>> CGroup: /system.slice/weewx.service >>>>> └─719 /usr/bin/python3 /home/weewx/bin/weewxd --daemon >>>>> --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf >>>>> >>>>> Jän 22 19:26:24 pi-weewx weewxd[719]: weewx[719] DEBUG weewx.manager: >>>>> Daily summary version is 3.0 >>>>> Jän 22 19:26:24 pi-weewx weewxd[719]: weewx[719] INFO >>>>> weewx.cheetahgenerator: Generated 2 files for report SteelSeries in 0.17 >>>>> seconds >>>>> Jän 22 19:26:24 pi-weewx weewxd[719]: weewx[719] DEBUG weewx.manager: >>>>> Daily summary version is 3.0 >>>>> Jän 22 19:26:25 pi-weewx weewxd[719]: weewx[719] INFO >>>>> weewx.imagegenerator: Generated 11 images for report SteelSeries in 0.93 >>>>> seconds >>>>> Jän 22 19:26:25 pi-weewx weewxd[719]: weewx[719] DEBUG >>>>> weewx.reportengine: Running report 'StackedWindRose' >>>>> Jän 22 19:26:25 pi-weewx weewxd[719]: weewx[719] DEBUG >>>>> weewx.reportengine: Found configuration file >>>>> /home/weewx/skins/StackedWindRose/skin.conf for report 'StackedWindRose' >>>>> Jän 22 19:26:25 pi-weewx weewxd[719]: weewx[719] DEBUG weewx.manager: >>>>> Daily summary version is 3.0 >>>>> Jän 22 19:26:25 pi-weewx weewxd[719]: weewx[719] INFO >>>>> user.stackedwindrose: Generated 1 images for StackedWindRose in 0.20 >>>>> seconds >>>>> Jän 22 19:26:25 pi-weewx weewxd[719]: weewx[719] DEBUG >>>>> weewx.reportengine: Report 'FTP' not enabled. Skipping. >>>>> Jän 22 19:26:25 pi-weewx weewxd[719]: weewx[719] DEBUG >>>>> weewx.reportengine: Report 'RSYNC' not enabled. Skipping. >>>>> >>>>> >>>>> Thx >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Am Fr., 22. Jan. 2021 um 19:20 Uhr schrieb Tom Keffer < >>>>> tke...@gmail.com>: >>>>> >>>>>> 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 <nady...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> 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 for extra debug info, otherwise comment it out or set to >>>>>>> zero >>>>>>> debug = 1 >>>>>>> >>>>>>> # Root directory of the weewx data file hierarchy for this station >>>>>>> WEEWX_ROOT = /home/weewx >>>>>>> >>>>>>> # Whether to log successful operations >>>>>>> log_success = True >>>>>>> >>>>>>> # Whether to log unsuccessful operations >>>>>>> log_failure = True >>>>>>> >>>>>>> >>>>>>> Is there any general missing in Linux (python3 setting or something >>>>>>> else) that weewx will not log anything output in /var/log/syslog >>>>>>> >>>>>>> in the /var/log/syslog is only boot process logged??? >>>>>>> >>>>>>> Thx >>>>>>> >>>>>>> -- >>>>>>> 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+...@googlegroups.com. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/weewx-user/7861da3b-f346-43d3-81fc-4fcb11e7df5en%40googlegroups.com >>>>>>> <https://groups.google.com/d/msgid/weewx-user/7861da3b-f346-43d3-81fc-4fcb11e7df5en%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+...@googlegroups.com. >>>>>> >>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/weewx-user/CAPq0zECAbGO%3DTBJLC5QsE5kps9-sDXJUp5KFE-oxEUgpi4A-uA%40mail.gmail.com >>>>>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zECAbGO%3DTBJLC5QsE5kps9-sDXJUp5KFE-oxEUgpi4A-uA%40mail.gmail.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/3a8da31f-86e1-4759-9c2a-86e6a8307390n%40googlegroups.com >>>> <https://groups.google.com/d/msgid/weewx-user/3a8da31f-86e1-4759-9c2a-86e6a8307390n%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/CAPq0zEDBVi7UAxFf6XQO%3DMMS%3DTPUVELwXoL-i6ERWrx5-D-TdQ%40mail.gmail.com >>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEDBVi7UAxFf6XQO%3DMMS%3DTPUVELwXoL-i6ERWrx5-D-TdQ%40mail.gmail.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/CALNFVsjnQOM11L82NvCcTRU3LK%2Bb3t6q%2BW8HWm0xnyGhSCcaJQ%40mail.gmail.com > <https://groups.google.com/d/msgid/weewx-user/CALNFVsjnQOM11L82NvCcTRU3LK%2Bb3t6q%2BW8HWm0xnyGhSCcaJQ%40mail.gmail.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/CAPq0zEDpujefSY7Bd3CDF808-c4vhmTv0rBer8ddGhWFT05Prw%40mail.gmail.com.
