subject:"\[weewx\-user\] weewx 4.x python3 Syslog problem"

Re: [weewx-user] weewx 4.x python3 Syslog problem

2021-01-23 Thread Manfred Nadymacek

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 schrieb Manfred Nadymacek <
nady2...@gmail.com>:

> 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-weewx:/var/log $ grep "debug message" /var/log/syslog*
> pi@pi-weewx:/var/log $ ls -l messages*
> -rw-r- 1 root adm 274810 Jän 22 19:44 messages
> -rw-r- 1 root adm 602120 Jän 20 16:15 messages.1
> pi@pi-weewx:/var/log $ grep "debug message" /var/log/messages
> pi@pi-weewx:/var/log $
>
>
> And the .gz is obviously a log file rotator.
>
> kr
>
> Am Sa., 23. Jan. 2021 um 09:20 Uhr schrieb vince :
>
>> 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:44 /var/log/syslog.1
>>> -rw-r- 1 root adm  31249 Jän 20 16:15 /var/log/syslog.2.gz
>>> -rw-r- 1 root adm 109457 Jän 14 18:44 /var/log/syslog.3.gz
>>>
>>
>> See if the logger message got into your logs.
>>
>> grep "debug message" /var/log/syslog.1
>>
>> And do a 'ls -l /var/log/messages*' as well, and grep for the same string
>> in any messages file that does not have a .gz extension.
>>
>>
>>
>> --
>> 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/8ef87c41-53c5-4d7c-9814-f9d0598c20b6n%40googlegroups.com
>> 
>> .
>>
>

-- 
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/CALNFVsgTBQFbA9pRO-Oe_i%2B3%2BgfhGiseJGKwB6us7yxKSwAJUQ%40mail.gmail.com.

Re: [weewx-user] weewx 4.x python3 Syslog problem

2021-01-23 Thread Manfred Nadymacek

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-weewx:/var/log $ grep "debug message" /var/log/syslog*
pi@pi-weewx:/var/log $ ls -l messages*
-rw-r- 1 root adm 274810 Jän 22 19:44 messages
-rw-r- 1 root adm 602120 Jän 20 16:15 messages.1
pi@pi-weewx:/var/log $ grep "debug message" /var/log/messages
pi@pi-weewx:/var/log $


And the .gz is obviously a log file rotator.

kr

Am Sa., 23. Jan. 2021 um 09:20 Uhr schrieb vince :

> 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:44 /var/log/syslog.1
>> -rw-r- 1 root adm  31249 Jän 20 16:15 /var/log/syslog.2.gz
>> -rw-r- 1 root adm 109457 Jän 14 18:44 /var/log/syslog.3.gz
>>
>
> See if the logger message got into your logs.
>
> grep "debug message" /var/log/syslog.1
>
> And do a 'ls -l /var/log/messages*' as well, and grep for the same string
> in any messages file that does not have a .gz extension.
>
>
>
> --
> 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/8ef87c41-53c5-4d7c-9814-f9d0598c20b6n%40googlegroups.com
> 
> .
>

-- 
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/CALNFVshBjFvNFKkv2K7msMhdDrE7i8GD5_rX-3m5fOg3ABZotA%40mail.gmail.com.

Re: [weewx-user] weewx 4.x python3 Syslog problem

2021-01-23 Thread vince

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:44 /var/log/syslog.1
> -rw-r- 1 root adm  31249 Jän 20 16:15 /var/log/syslog.2.gz
> -rw-r- 1 root adm 109457 Jän 14 18:44 /var/log/syslog.3.gz
>

See if the logger message got into your logs.

grep "debug message" /var/log/syslog.1

And do a 'ls -l /var/log/messages*' as well, and grep for the same string 
in any messages file that does not have a .gz extension.

 

-- 
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/8ef87c41-53c5-4d7c-9814-f9d0598c20b6n%40googlegroups.com.

Re: [weewx-user] weewx 4.x python3 Syslog problem

2021-01-22 Thread Manfred Nadymacek

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 messages come
up...  in General the syslog has entries but only from boot.

pi@pi-weewx:/var/log $ cat /boot/issue.txt
Raspberry Pi reference 2021-01-11
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen,
21090519d85bdaa1615d5d5057d37b09368ea5d2, stage5
pi@pi-weewx:/var/log $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/;
SUPPORT_URL="http://www.raspbian.org/RaspbianForums;
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs;

Can it have an issue with the install routines from weewx
I following this one!:

---

Prerequisites for Debian 10 (Buster), Raspbian 10, Ubuntu 18.04-19.10

sudo apt update

# Requiredsudo apt install python3-configobj
sudo apt install python3-pil
sudo apt install python3-serial
sudo apt install python3-usb
sudo apt install python3-pip

# This works for most installations...sudo apt install python3-cheetah
# ... if not, try this:sudo pip3 install Cheetah3

# Optional: for extended almanac informationsudo apt install python3-ephem

After installing the prerequisites, you can install WeeWX itself.

   1.

   Expand the source archive:

   tar xvfz weewx-X.Y.Z.tar.gz

   2.

   Change directory into the expanded archive:

   cd weewx-X.Y.Z

   3.

   To specify an install location different from the default /home/weewx,
   modify the parameter home in the setup.cfg file. Mac users will want to
   change it to /Users/Shared/weewx.
   4.

   Then build and install. Python 2 users: substitute python2 for python3.

   python3 ./setup.py build
   sudo python3 ./setup.py install


cd /home/weewx
sudo cp util/init.d/weewx.debian /etc/init.d/weewx
sudo chmod +x /etc/init.d/weewx
sudo update-rc.d weewx defaults 98
sudo /etc/init.d/weewx start

5. Status

Look in the system log for messages from WeeWX. For example, on Debian
systems:

sudo tail -f /var/log/syslog



Also the output from your hints only journalctl is working..

pi@pi-weewx:/var/log $ ls -l
insgesamt 2864
-rw-r--r--  1 root root   126 Jän 20 16:38 alternatives.log
drwxr-x---  2 root adm   4096 Jän 23 00:00 apache2
drwxr-xr-x  2 root root  4096 Jän 22 22:47 apt
-rw-r-  1 root adm  0 Jän 21 00:00 auth.log
-rw-r-  1 root adm  18427 Jän 14 16:12 auth.log.1
-rw---  1 root root167581 Jän 22 19:43 boot.log
-rw-r--r--  1 root root 0 Jän 11 14:32 bootstrap.log
-rw-rw  1 root utmp  3072 Jän 22 14:40 btmp
drwxr-xr-x  2 root root  4096 Jän 23 00:00 cups
-rw-r-  1 root adm  0 Jän 21 00:00 daemon.log
-rw-r-  1 root adm 203740 Jän 14 16:12 daemon.log.1
-rw-r-  1 root adm   9441 Jän 22 19:43 debug
-rw-r-  1 root adm  25663 Jän 20 16:15 debug.1
-rw-r--r--  1 root root 30990 Jän 22 22:48 dpkg.log
-rw-r--r--  1 root root 0 Jän 11 14:32 faillog
drwxr-xr-x  2 root root  4096 Feb  8  2019 firebird
-rw-r--r--  1 root root 0 Jän 11 14:32 fontconfig.log
drwxr-xr-x  3 root root  4096 Jän 11 13:59 hp
drwxr-sr-x+ 3 root systemd-journal   4096 Jän 14 16:12 journal
-rw-r-  1 root adm 284251 Jän 22 19:44 kern.log
-rw-r-  1 root adm 623296 Jän 20 16:15 kern.log.1
-rw-rw-r--  1 root utmp292292 Jän 23 08:21 lastlog
drwx--x--x  2 root root  4096 Jän 20 13:01 lightdm
-rw-r-  1 root adm 274810 Jän 22 19:44 messages
-rw-r-  1 root adm 602120 Jän 20 16:15 messages.1
drwx--  2 root root  4096 Jän 11 14:32 private
-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
-rw-r-  1 root adm  0 Jän 21 00:00 user.log
-rw-r-  1 root adm  13001 Jän 14 15:59 user.log.1
-rw---  1 root root 11019 Jän 22 19:43 vncserver-x11.log
-rw---  1 root root 11419 Jän 22 19:43 vncserver-x11.log.bak
-rw-rw-r--  1 root utmp114816 Jän 23 08:21 wtmp
-rw-r--r--  1 root root 11667 Jän 20 13:09 Xorg.0.log
-rw-r--r--  1 root root 11667 Jän 20 13:01 Xorg.0.log.old

pi@pi-weewx:/var/log $ journalctl --unit=weewx | more
-- Logs begin at Fri 2021-01-22 17:21:37 CET, end at Sat 2021-01-23
08:36:05 CET. --
Jän 22 17:51:57 pi-weewx systemd[1]:

Re: [weewx-user] weewx 4.x python3 Syslog problem

2021-01-22 Thread vince

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 would put the entry in /var/log/syslog but 
'not' into /var/log/messages.   Verified here on a buster pi.

You can check your os version by looking at /etc/os-release and 
/etc/debian_version and the vintage of the Raspbian os you started with is 
in /boot/issue.txt if you wanted to check that.


-- 
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/51e24e5e-f4b5-4899-8371-6f8586f78347n%40googlegroups.com.

Re: [weewx-user] weewx 4.x python3 Syslog problem

2021-01-22 Thread Tom Keffer

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:/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:

Re: [weewx-user] weewx 4.x python3 Syslog problem

2021-01-22 Thread Manfred Nadymacek

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]

Re: [weewx-user] weewx 4.x python3 Syslog problem

2021-01-22 Thread Manfred Nadymacek

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-3f98.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/3f98.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/3f98.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/3f98.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]

Re: [weewx-user] weewx 4.x python3 Syslog problem

2021-01-22 Thread Tom Keffer

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/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]:

Re: [weewx-user] weewx 4.x python3 Syslog problem

2021-01-22 Thread Manfred Nadymacek

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 :
>
>> 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

Re: [weewx-user] weewx 4.x python3 Syslog problem

2021-01-22 Thread Manfred Nadymacek

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 :

> 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 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

Re: [weewx-user] weewx 4.x python3 Syslog problem

2021-01-22 Thread Tom Keffer

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 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+unsubscr...@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
> 
> .
>

-- 
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/CAPq0zECAbGO%3DTBJLC5QsE5kps9-sDXJUp5KFE-oxEUgpi4A-uA%40mail.gmail.com.

[weewx-user] weewx 4.x python3 Syslog problem

2021-01-22 Thread Manfred Nadymacek


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+unsubscr...@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.

Re: [weewx-user] weewx 4.x python3 Syslog problem

Re: [weewx-user] weewx 4.x python3 Syslog problem

Re: [weewx-user] weewx 4.x python3 Syslog problem

Re: [weewx-user] weewx 4.x python3 Syslog problem

Re: [weewx-user] weewx 4.x python3 Syslog problem

Re: [weewx-user] weewx 4.x python3 Syslog problem

Re: [weewx-user] weewx 4.x python3 Syslog problem

Re: [weewx-user] weewx 4.x python3 Syslog problem

Re: [weewx-user] weewx 4.x python3 Syslog problem

Re: [weewx-user] weewx 4.x python3 Syslog problem

Re: [weewx-user] weewx 4.x python3 Syslog problem

Re: [weewx-user] weewx 4.x python3 Syslog problem

[weewx-user] weewx 4.x python3 Syslog problem

13 matches

Site Navigation

Mail list logo

Footer information