[weewx-user] New install weewx 4.5.1 on fresh Ubuntu focal 20.04 LTS cannot start???

[Manfred Nadymacek]

Hello,
I test several hours to install on new ubuntu server for weewx.

I install it via DEB or via setup.py script. compete new installed.
No any errors during install. Then i start to have the orginal weewx.conf 
only start changing the Station Type to Simulator and a section to 
[Simulator]

First i install it on LXC in Proxmox 20.04 focal.Then i test it to run on 
VM Ubuntu Server image but same situation?

I run weewx many years from to 3.x to 4.x and also updated on python3 on my 
RPI but now i would want to migrate all to Proxmox LXC Container but since 
hours i have no glue why it cannot start.

Can anybody help me please!

Thx Manfred

But: After start is see following issue in syslog Container Install:

Jan 14 13:29:13 Weewx systemd[1]: Starting LSB: weewx weather system...
Jan 14 13:29:13 Weewx weewx[462]:  * Starting weewx weather system weewx
Jan 14 13:29:13 Weewx weewx[473] INFO __main__: Initializing weewx version 
4.5.1
Jan 14 13:29:13 Weewx weewx[473] INFO __main__: Using Python 3.8.10 
(default, Nov 26 2021, 20:14:08) #012[GCC 9.3.0]
Jan 14 13:29:13 Weewx weewx[473] INFO __main__: Platform 
Linux-5.13.19-2-pve-x86_64-with-glibc2.29
Jan 14 13:29:13 Weewx weewx[473] INFO __main__: Locale is 'de_AT.UTF-8'
Jan 14 13:29:13 Weewx weewx[473] INFO __main__: PID file is 
/var/run/weewx.pid
Jan 14 13:29:13 Weewx weewx[462]:...done.
Jan 14 13:29:13 Weewx systemd[1]: Started LSB: weewx weather system.
Jan 14 13:29:13 Weewx weewx[478] INFO __main__: Using configuration file 
/home/weewx/weewx.conf
Jan 14 13:29:13 Weewx weewx[478] INFO __main__: Debug is 1
Jan 14 13:29:13 Weewx weewx[478] DEBUG __main__: Initializing engine
Jan 14 13:29:13 Weewx weewx[478] CRITICAL __main__: Caught unrecoverable 
exception:
Jan 14 13:29:13 Weewx weewx[478] CRITICAL __main__:   'driver'
Jan 14 13:29:13 Weewx weewx[478] CRITICAL __main__:   Traceback 
(most recent call last):
Jan 14 13:29:13 Weewx weewx[478] CRITICAL __main__: File 
"/home/weewx/bin/weewxd", line 151, in main
Jan 14 13:29:13 Weewx weewx[478] CRITICAL __main__:   engine = 
weewx.engine.StdEngine(config_dict)
Jan 14 13:29:13 Weewx weewx[478] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 81, in __init__
Jan 14 13:29:13 Weewx weewx[478] CRITICAL __main__:  
 self.setupStation(config_dict)
Jan 14 13:29:13 Weewx weewx[478] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 103, in setupStation
Jan 14 13:29:13 Weewx weewx[478] CRITICAL __main__:   driver = 
config_dict[station_type]['driver']
Jan 14 13:29:13 Weewx weewx[478] CRITICAL __main__: File 
"/usr/lib/python3/dist-packages/configobj.py", line 554, in __getitem__
Jan 14 13:29:13 Weewx weewx[478] CRITICAL __main__:   val = 
dict.__getitem__(self, key)
Jan 14 13:29:13 Weewx weewx[478] CRITICAL __main__:   KeyError: 
'driver'
Jan 14 13:29:13 Weewx weewx[478] CRITICAL __main__:   Exiting.

And in VM Install with Ubuntu ISO same issue

Jan 14 14:32:18 weewx-ubuntu systemd[1]: Starting LSB: weewx weather 
system...
Jan 14 14:32:18 weewx-ubuntu weewx[9110]:  * Starting weewx weather system 
weewx
Jan 14 14:32:18 weewx-ubuntu weewx[9121] INFO __main__: Initializing weewx 
version 4.5.1
Jan 14 14:32:18 weewx-ubuntu weewx[9121] INFO __main__: Using Python 3.8.10 
(default, Nov 26 2021, 20:14:08) #012[GCC 9.3.0]
Jan 14 14:32:18 weewx-ubuntu weewx[9121] INFO __main__: Platform 
Linux-5.4.0-94-generic-x86_64-with-glibc2.29
Jan 14 14:32:18 weewx-ubuntu weewx[9121] INFO __main__: Locale is 
'en_US.UTF-8'
Jan 14 14:32:18 weewx-ubuntu weewx[9121] INFO __main__: PID file is 
/var/run/weewx.pid
Jan 14 14:32:18 weewx-ubuntu weewx[9125] INFO __main__: Using configuration 
file /home/weewx/weewx.conf
Jan 14 14:32:18 weewx-ubuntu weewx[9125] INFO __main__: Debug is 0
Jan 14 14:32:18 weewx-ubuntu weewx[9125] CRITICAL __main__: Caught 
unrecoverable exception:
Jan 14 14:32:18 weewx-ubuntu weewx[9110]:...done.
Jan 14 14:32:18 weewx-ubuntu systemd[1]: Started LSB: weewx weather system.
Jan 14 14:32:18 weewx-ubuntu weewx[9125] CRITICAL __main__:  
 'driver'
Jan 14 14:32:18 weewx-ubuntu weewx[9125] CRITICAL __main__:  
 Traceback (most recent call last):
Jan 14 14:32:18 weewx-ubuntu weewx[9125] CRITICAL __main__:    
 File "/home/weewx/bin/weewxd", line 151, in main
Jan 14 14:32:18 weewx-ubuntu weewx[9125] CRITICAL __main__:  
 engine = weewx.engine.StdEngine(config_dict)
Jan 14 14:32:18 weewx-ubuntu weewx[9125] CRITICAL __main__:    
 File "/home/weewx/bin/weewx/engine.py", line 81, in __init__
Jan 14 14:32:18 weewx-ubuntu weewx[9125] CRITICAL __main__:  
 self.setupStation(config_dict)
Jan 14 14:32:18 weewx-ubuntu weewx[9125] CRITICAL __main__:    
 File "/home/weewx/bin/weewx/engine.py", line 103, in setupStation
Jan 14 14:32:18 weewx-ubuntu weewx[9125] CRITICAL __main__:  
 driver = confi

[weewx-user] Re: NGINX Reverse Proxy / SSL cannot display the SteelGauges skin

[Manfred Nadymacek]

Thx i found the problem in the Source of the Steel Gauges skin. Because 
there was a problem with one Javacripts which is opened with http and not 
https:

br


sbar...@gmail.com schrieb am Donnerstag, 11. Februar 2021 um 13:53:43 UTC+1:

> I am not familiar with nginx reverseproxy, but with apache reverse proxy, 
> you can have a https website facing the web and a http internal server. 
> The reverse proxy module will take care of fixing the urls and protocol on 
> the fly.
>
> I imagine that nginx does the same. Is it possible that your html page 
> template has hardlinked url, instead of relative to the source?
> I you look in the console from the browser what error do you get ?
>
> On Thursday, February 11, 2021 at 10:33:04 AM UTC+1 nady...@gmail.com 
> wrote:
>
>>
>> Hello,
>> I run a weewx installation with Season (default skin) and the steel 
>> gauges skin /ss.
>> All is working well in local environment. But when i want to have SSL 
>> from outside to my internal website.
>> Therefore i install in a docker station nginx reverse proxy with 
>> letsencrypt and want to forward this to SSL.
>> Means nginx can switch external traffic to my local weewx station which 
>> run with local apache2 server.
>>
>> All is working but when i want enable SSL then only the skin /ss cannot 
>> display the gaues only the header and bottom botton is visible. I have no 
>> idea why.
>> I guess this is a issue regaring SSL and javascript or some other issues 
>> in /ss skin. but i have no knowledge about Javascript.
>>
>> When i reconfigure the nginx reverseproxy to use only http not https then 
>> all including the /ss skin is working
>>
>> I asked already the develover of the SS skin but he mentioned there is an 
>> other problem.
>>
>> Can anybody help me to find out why the /ss skin cannot display on a ssl 
>> access?
>>
>> thx
>> Manfred
>>
>

-- 
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/e0f0702f-12ad-4a06-801e-377838770d68n%40googlegroups.com.

[weewx-user] NGINX Reverse Proxy / SSL cannot display the SteelGauges skin

[Manfred Nadymacek]

Hello,
I run a weewx installation with Season (default skin) and the steel gauges 
skin /ss.
All is working well in local environment. But when i want to have SSL from 
outside to my internal website.
Therefore i install in a docker station nginx reverse proxy with 
letsencrypt and want to forward this to SSL.
Means nginx can switch external traffic to my local weewx station which run 
with local apache2 server.

All is working but when i want enable SSL then only the skin /ss cannot 
display the gaues only the header and bottom botton is visible. I have no 
idea why.
I guess this is a issue regaring SSL and javascript or some other issues in 
/ss skin. but i have no knowledge about Javascript.

When i reconfigure the nginx reverseproxy to use only http not https then 
all including the /ss skin is working

I asked already the develover of the SS skin but he mentioned there is an 
other problem.

Can anybody help me to find out why the /ss skin cannot display on a ssl 
access?

thx
Manfred

-- 
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/7107f888-d3ee-45cb-9cc8-643168fa3916n%40googlegroups.com.

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

[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
>> <https://groups.google.com/d/msgid/weewx-user/8ef87c41-53c5-4d7c-9814-f9d0598c20b6n%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/CALNFVsgTBQFbA9pRO-Oe_i%2B3%2BgfhGiseJGKwB6us7yxKSwAJUQ%40mail.gmail.com.

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

[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

[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]: Star

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

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

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

[Manfred Nadymacek]

] hid-generic
0003:046D:4024.0005: input,hidraw1: USB HID v1.11 Keyboard [Logitech
Unifying Device. Wireless PID:4024] on usb-3f98.usb-1.4/input2:1
Jan 22 19:43:44 pi-weewx kernel: [   14.769176] input: Logitech K400 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/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-3f98.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
pi1771  0.0  0.0   7492   540 pts/0S+   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 :

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

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

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

Re: [weewx-user] Question regarding new 4.x schema

[Manfred Nadymacek]

thx good to know for next time migration.


Am Fr., 22. Jan. 2021 um 19:28 Uhr schrieb Tom Keffer :

> If you leave it alone, either will work just fine.
>
> On Fri, Jan 22, 2021 at 10:23 AM Manfred Nadymacek 
> wrote:
>
>> i was confused because this !
>> Default in 4.3 :
>> [DataBindings]
>>
>> [[wx_binding]]
>> # The database must match one of the sections in [Databases].
>> # This is likely to be the only option you would want to change.
>> database = archive_sqlite
>> # The name of the table within the database
>> table_name = archive
>> # The manager handles aggregation of data for historical summaries
>> manager = weewx.*manager.DaySummaryManager*
>> # The schema defines the structure of the database.
>> # It is *only* used when the database is created.
>> schema = schemas.*wview_extended*.schema
>>
>> and on my old instance 3.9.x:
>> [DataBindings]
>>
>> [[wx_binding]]
>> # The database must match one of the sections in [Databases].
>> # This is likely to be the only option you would want to change.
>> database = archive_sqlite
>> # The name of the table within the database
>> table_name = archive
>> # The manager handles aggregation of data for historical summaries
>> manager = weewx.*wxmanager.WXDaySummaryManager*
>> # The schema defines the structure of the database.
>> # It is *only* used when the database is created.
>> schema = schemas.*wview*.schema
>>
>>
>> My fear as i said is that only copy cannot work with it... It't not
>> written in the docs...
>>
>> br
>>
>> Am Fr., 22. Jan. 2021 um 19:06 Uhr schrieb Tom Keffer > >:
>>
>>> Well done, but, as I said, there is no reason to migrate to the new
>>> schema unless you intend to take advantage of the new database types.
>>>
>>> On Fri, Jan 22, 2021 at 9:58 AM Manfred Nadymacek 
>>> wrote:
>>>
>>>> Thx for answering, I did following after long search
>>>> Copy from old instance to the new installed 4.3.x version.
>>>> Then wee_database weewx.conf --reconfigure
>>>> replace _new db to orig name
>>>> Restart and rebuilt daily summary take ~1 houre for 50 records
>>>> now it's migrated to new schema so for future features releases.
>>>>
>>>> br
>>>>
>>>> tke...@gmail.com schrieb am Freitag, 22. Januar 2021 um 14:56:14 UTC+1:
>>>>
>>>>> The schema is used only when you create a new database. WIth old
>>>>> databases, the schema is read directly from the database. So, you can just
>>>>> copy your old database to the new installation. WeeWX will continue to 
>>>>> work.
>>>>>
>>>>> If you want to *change* schemas, that's something different, but
>>>>> there is no reason to do so unless you want to take advantage of the new
>>>>> types.
>>>>>
>>>>> -tk
>>>>>
>>>>> On Fri, Jan 22, 2021 at 1:33 AM Manfred Nadymacek 
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>> My problem is following:
>>>>>> I run since 4,5 years my weewx station hosted on a raspberry pi.
>>>>>> I start 2016 with a prober version and update it to latest 3.9
>>>>>> version.
>>>>>>
>>>>>> Now  I reinstall a new raspberry Pi with lastest raspian version and
>>>>>> weewx 4.3 and do also all new configuration and add new skins aso...
>>>>>>
>>>>>> BUT: I found out that the old version has following Databinding:
>>>>>> [DataBindings]
>>>>>>
>>>>>> [[wx_binding]]
>>>>>> # The database must match one of the sections in [Databases].
>>>>>> # This is likely to be the only option you would want to
>>>>>> change.
>>>>>> database = archive_sqlite
>>>>>> # The name of the table within the database
>>>>>> table_name = archive
>>>>>> # The manager handles aggregation of data for historical
>>>>>> summaries
>>>>>> manager = weewx.wxmanager.WXDaySummaryManager
>>>>>> # The schema defines the structure

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

[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
&g

Re: [weewx-user] Question regarding new 4.x schema

[Manfred Nadymacek]

i was confused because this !
Default in 4.3 :
[DataBindings]

[[wx_binding]]
# The database must match one of the sections in [Databases].
# This is likely to be the only option you would want to change.
database = archive_sqlite
# The name of the table within the database
table_name = archive
# The manager handles aggregation of data for historical summaries
manager = weewx.*manager.DaySummaryManager*
# The schema defines the structure of the database.
# It is *only* used when the database is created.
schema = schemas.*wview_extended*.schema

and on my old instance 3.9.x:
[DataBindings]

[[wx_binding]]
# The database must match one of the sections in [Databases].
# This is likely to be the only option you would want to change.
database = archive_sqlite
# The name of the table within the database
table_name = archive
# The manager handles aggregation of data for historical summaries
manager = weewx.*wxmanager.WXDaySummaryManager*
# The schema defines the structure of the database.
# It is *only* used when the database is created.
schema = schemas.*wview*.schema


My fear as i said is that only copy cannot work with it... It't not written
in the docs...

br

Am Fr., 22. Jan. 2021 um 19:06 Uhr schrieb Tom Keffer :

> Well done, but, as I said, there is no reason to migrate to the new schema
> unless you intend to take advantage of the new database types.
>
> On Fri, Jan 22, 2021 at 9:58 AM Manfred Nadymacek 
> wrote:
>
>> Thx for answering, I did following after long search
>> Copy from old instance to the new installed 4.3.x version.
>> Then wee_database weewx.conf --reconfigure
>> replace _new db to orig name
>> Restart and rebuilt daily summary take ~1 houre for 50 records
>> now it's migrated to new schema so for future features releases.
>>
>> br
>>
>> tke...@gmail.com schrieb am Freitag, 22. Januar 2021 um 14:56:14 UTC+1:
>>
>>> The schema is used only when you create a new database. WIth old
>>> databases, the schema is read directly from the database. So, you can just
>>> copy your old database to the new installation. WeeWX will continue to work.
>>>
>>> If you want to *change* schemas, that's something different, but there
>>> is no reason to do so unless you want to take advantage of the new types.
>>>
>>> -tk
>>>
>>> On Fri, Jan 22, 2021 at 1:33 AM Manfred Nadymacek 
>>> wrote:
>>>
>>>> Hi all,
>>>> My problem is following:
>>>> I run since 4,5 years my weewx station hosted on a raspberry pi.
>>>> I start 2016 with a prober version and update it to latest 3.9 version.
>>>>
>>>> Now  I reinstall a new raspberry Pi with lastest raspian version and
>>>> weewx 4.3 and do also all new configuration and add new skins aso...
>>>>
>>>> BUT: I found out that the old version has following Databinding:
>>>> [DataBindings]
>>>>
>>>> [[wx_binding]]
>>>> # The database must match one of the sections in [Databases].
>>>> # This is likely to be the only option you would want to change.
>>>> database = archive_sqlite
>>>> # The name of the table within the database
>>>> table_name = archive
>>>> # The manager handles aggregation of data for historical
>>>> summaries
>>>> manager = weewx.wxmanager.WXDaySummaryManager
>>>> # The schema defines the structure of the database.
>>>> # It is *only* used when the database is created.
>>>> schema = schemas.wview.schema
>>>>
>>>>
>>>> And in the new config has already the new extrended schema:
>>>> [DataBindings]
>>>>
>>>> [[wx_binding]]
>>>> # The database must match one of the sections in [Databases].
>>>> # This is likely to be the only option you would want to change.
>>>> database = archive_sqlite
>>>> # The name of the table within the database
>>>> table_name = archive
>>>> # The manager handles aggregation of data for historical
>>>> summaries
>>>> manager = weewx.manager.DaySummaryManager
>>>> # The schema defines the structure of the database.
>>>> # It is *only* used when the database is created.
>>>> schema = schemas.wview_extended.schema
&g

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

[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] Question regarding new 4.x schema

[Manfred Nadymacek]

Thx for answering, I did following after long search
Copy from old instance to the new installed 4.3.x version.
Then wee_database weewx.conf --reconfigure
replace _new db to orig name
Restart and rebuilt daily summary take ~1 houre for 50 records 
now it's migrated to new schema so for future features releases.

br

tke...@gmail.com schrieb am Freitag, 22. Januar 2021 um 14:56:14 UTC+1:

> The schema is used only when you create a new database. WIth old 
> databases, the schema is read directly from the database. So, you can just 
> copy your old database to the new installation. WeeWX will continue to work.
>
> If you want to *change* schemas, that's something different, but there is 
> no reason to do so unless you want to take advantage of the new types.
>
> -tk
>
> On Fri, Jan 22, 2021 at 1:33 AM Manfred Nadymacek  
> wrote:
>
>> Hi all,
>> My problem is following:
>> I run since 4,5 years my weewx station hosted on a raspberry pi.
>> I start 2016 with a prober version and update it to latest 3.9 version.
>>
>> Now  I reinstall a new raspberry Pi with lastest raspian version and 
>> weewx 4.3 and do also all new configuration and add new skins aso... 
>>
>> BUT: I found out that the old version has following Databinding:
>> [DataBindings]
>>
>> [[wx_binding]]
>> # The database must match one of the sections in [Databases].
>> # This is likely to be the only option you would want to change.
>> database = archive_sqlite
>> # The name of the table within the database
>> table_name = archive
>> # The manager handles aggregation of data for historical summaries
>> manager = weewx.wxmanager.WXDaySummaryManager
>> # The schema defines the structure of the database.
>> # It is *only* used when the database is created.
>> schema = schemas.wview.schema
>>
>>
>> And in the new config has already the new extrended schema:
>> [DataBindings]
>>
>> [[wx_binding]]
>> # The database must match one of the sections in [Databases].
>> # This is likely to be the only option you would want to change.
>> database = archive_sqlite
>> # The name of the table within the database
>> table_name = archive
>> # The manager handles aggregation of data for historical summaries
>> manager = weewx.manager.DaySummaryManager
>> # The schema defines the structure of the database.
>> # It is *only* used when the database is created.
>> schema = schemas.wview_extended.schema
>>
>> My idea would be i will shutdown the old weewx instance and copy the old 
>> database to the correct folder in the new installed weewx version. 
>> BUT i guess that will not work and my fear is the old data are lost or 
>> not visible.
>>
>> CAN anybody help me to migrate the old sqlite database to the new 4.x 
>> schema standard without lost my history data??
>>
>> Thx very much!
>> Manfred
>>
>>
>>
>> -- 
>> 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/8d31bb56-0b2c-4e77-956b-57decefd4cf3n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/8d31bb56-0b2c-4e77-956b-57decefd4cf3n%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/4943a2fd-cdb7-4f43-9d17-a466d743b7adn%40googlegroups.com.

[weewx-user] Question regarding new 4.x schema

[Manfred Nadymacek]

Hi all,
My problem is following:
I run since 4,5 years my weewx station hosted on a raspberry pi.
I start 2016 with a prober version and update it to latest 3.9 version.

Now  I reinstall a new raspberry Pi with lastest raspian version and weewx 
4.3 and do also all new configuration and add new skins aso... 

BUT: I found out that the old version has following Databinding:
[DataBindings]

[[wx_binding]]
# The database must match one of the sections in [Databases].
# This is likely to be the only option you would want to change.
database = archive_sqlite
# The name of the table within the database
table_name = archive
# The manager handles aggregation of data for historical summaries
manager = weewx.wxmanager.WXDaySummaryManager
# The schema defines the structure of the database.
# It is *only* used when the database is created.
schema = schemas.wview.schema


And in the new config has already the new extrended schema:
[DataBindings]

[[wx_binding]]
# The database must match one of the sections in [Databases].
# This is likely to be the only option you would want to change.
database = archive_sqlite
# The name of the table within the database
table_name = archive
# The manager handles aggregation of data for historical summaries
manager = weewx.manager.DaySummaryManager
# The schema defines the structure of the database.
# It is *only* used when the database is created.
schema = schemas.wview_extended.schema

My idea would be i will shutdown the old weewx instance and copy the old 
database to the correct folder in the new installed weewx version. 
BUT i guess that will not work and my fear is the old data are lost or not 
visible.

CAN anybody help me to migrate the old sqlite database to the new 4.x 
schema standard without lost my history data??

Thx very much!
Manfred



-- 
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/8d31bb56-0b2c-4e77-956b-57decefd4cf3n%40googlegroups.com.

[weewx-user] weewx 4.x version with sofaskin

[Manfred Nadymacek]

Did anybody do already an update to version 4.x with python 3.x  and active 
sofaskin ?
I asked because i'm running actual on 3.9.2. version with python 2.7and 
after update i got several errors and for example almanche cannot update 
aso...

Is sofaskin python 3 compatible?

thx
Manfred

-- 
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/88c87d35-edda-434b-b3ce-301bd08eabcfo%40googlegroups.com.