date:20241015

Re: [weewx-user] Updated linux and weewx, nwo won't run. Help, please.

2024-10-15 Thread 'loonsailor' via weewx-user

re the version of weewx, I did "sudo apt update; sudo apt upgrade; sudo apt 
install weewx" and I get the response that 5.0.1 is the current version.  I 
looked in /etc/apt/sources.d, and the file weewx.list contains only one 
commented out line:

# deb [arch=all] http://weewx.com/apt/python3 buster main # disabled on 
upgrade to jammy

I'm now on Linux 24.04.1 LTS, which is, I think, jammy.  Should I have a 
different repository list?

Re the port problem, I've changed the wifilogger port to  (instead of 
2), and set debug to 1 and port  in weewx.conf.  Still no joy.  
Here's the log with debug.

2024-10-14T18:25:40.108787-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Initializing weewxd version 5.0.1
2024-10-14T18:25:40.110003-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Command line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
2024-10-14T18:25:40.121078-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Using Python 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0]
2024-10-14T18:25:40.121308-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Located at /usr/bin/python3
2024-10-14T18:25:40.122800-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Platform Linux-5.15.0-122-generic-x86_64-with-glibc2.39
2024-10-14T18:25:40.123611-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Locale: 'en_US.UTF-8'
2024-10-14T18:25:40.124478-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Entry path: /usr/share/weewx/weewxd.py
2024-10-14T18:25:40.125329-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: WEEWX_ROOT: /etc/weewx
2024-10-14T18:25:40.126199-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Configuration file: /etc/weewx/weewx.conf
2024-10-14T18:25:40.127036-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: User module: /etc/weewx/bin/user
2024-10-14T18:25:40.127989-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Debug: 1
2024-10-14T18:25:40.128951-07:00 ubu-mini-weather weewxd[941]: DEBUG 
__main__: Initializing engine
2024-10-14T18:25:40.136337-07:00 ubu-mini-weather weewxd[941]: INFO 
weewx.engine: Loading station type Vantage (weewx.drivers.vantage)
2024-10-14T18:25:40.291519-07:00 ubu-mini-weather weewxd[941]: DEBUG 
weewx.drivers.vantage: Driver version is 3.6.2
2024-10-14T18:25:40.300207-07:00 ubu-mini-weather weewxd[941]: DEBUG 
weewx.drivers.vantage: Option loop_request=2
2024-10-14T18:25:40.301295-07:00 ubu-mini-weather weewxd[941]: ERROR 
weewx.drivers.vantage: Socket error while opening port  to ethernet 
host 192.168.198.91.
2024-10-14T18:25:40.302074-07:00 ubu-mini-weather weewxd[941]: ERROR 
weewx.engine: Import of driver failed: [Errno 101] Network is unreachable 
()
2024-10-14T18:25:40.309610-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   Traceback (most recent call last):
2024-10-14T18:25:40.310587-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine: File "/usr/share/weewx/weewx/drivers/vantage.py", 
line 354, in openPort
2024-10-14T18:25:40.311404-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   self.socket.connect((self.host, self.port))
2024-10-14T18:25:40.312183-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   OSError: [Errno 101] Network is unreachable
2024-10-14T18:25:40.312794-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   
2024-10-14T18:25:40.313291-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   During handling of the above exception, another 
exception occurred:
2024-10-14T18:25:40.313738-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   
2024-10-14T18:25:40.314173-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   Traceback (most recent call last):
2024-10-14T18:25:40.314724-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine: File "/usr/share/weewx/weewx/engine.py", line 
115, in setupStation
2024-10-14T18:25:40.316118-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   self.console = loader_function(config_dict, 
self)

I tried to telnet to the new port, and get the following:
$ telnet 192.168.198.91 
Trying 192.168.198.91...
telnet: Unable to connect to remote host: Connection refused

This worked fine before updating OS and weewx, so I'm mystified.

BTW, I'm using my old conf file, which still says it's version 4.8.  
Doesn't seem like that should be thr problem, but...
On Monday, October 14, 2024 at 4:58:52 PM UTC-7 Tom Keffer wrote:

On Monday, October 14, 2024 at 6:38:35 PM UTC-7 vince wrote:

>
> To check which user weewx is running as, try  "ps aux | grep weewx | grep 
> -v grep" and look at the output. It should say something like:
> weewx 4977 7.8 0.7 117336 30056 ? Ssl 18:28 0:00 python3 
> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>
> Your numbers in the middle of your output will vary but the first column 
> should say 'weewx' and the command starting with 'python3' above should 
> look the same

Re: [weewx-user] Updated linux and weewx, nwo won't run. Help, please.

2024-10-15 Thread 'loonsailor' via weewx-user

I've confirmed that the computer can reach the station by doing so from the 
browser.  WifiLogger has an html interface, and I can see it and interact 
with it from the same computer that's running weewx.

It's been some years since I moved to weewx and configured this, and I 
don't remember why socket 2 is used.  Does anybody know, or is that 
something that I chose arbitrarily?  I used to access a vantage through a 
ethernet-serial converter, and maybe it was the socket used in that?

On Monday, October 14, 2024 at 4:13:46 PM UTC-7 Tom Keffer wrote:

> (In passing, it's a good idea to set debug=1 when you're trying to obtain 
> a log.)
>
> I would guess that the upgrade of Ubuntu somehow changed a firewall or 
> iptables setting, or something similar, rendering the address 
> 192.168.198.91 unreachable from whatever computer WeeWX is running on. To 
> double check this, you could try using telnet to see if you at least have 
> connectivity.
>
> Without connectivity, WeeWX won't get far.
>
> -tk
>
> On Mon, Oct 14, 2024 at 4:06 PM 'loonsailor' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> I've been running weewx 4.8.0 under unbuntu linux 20.04 (I think).  I 
>> upgraded today to ubunbtu 24.04.1 LTS, and the process also moved me to 
>> weewx 5.0.1.  Now it won't run.  First question is, why does "sudo apt 
>> update; sudo apt install weewx" not get me to 5.1?  But the much more 
>> important question is, why won't it run at all?  Here is the syslog.  Note 
>> that the socket that it's trying to open is to the WifiLogger2 board in my 
>> Vantage Pro 2.  Any ideas?
>>
>> Oct 14 14:32:29 ubu-mini-weather systemd[1]: Stopped Discard unused 
>> blocks once a week.
>> Oct 14 14:33:18 ubu-mini-weather systemd[1]: Started Discard unused 
>> blocks once a week.
>> Oct 14 14:33:19 ubu-mini-weather weewxd[833]: INFO __main__: Initializing 
>> weewxd version 5.0.1
>> Oct 14 14:33:19 ubu-mini-weather weewxd[833]: INFO __main__: Command 
>> line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Using Python 
>> 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0]
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Located at 
>> /usr/bin/python3
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Platform 
>> Linux-5.15.0-122-generic-x86_64-with-glibc2.35
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Locale: 
>> 'en_US.UTF-8'
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Entry path: 
>> /usr/share/weewx/weewxd.py
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: WEEWX_ROOT: 
>> /etc/weewx
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: 
>> Configuration file: /etc/weewx/weewx.conf
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: User module: 
>> /etc/weewx/bin/user
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Debug: 0
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: ERROR 
>> weewx.drivers.vantage: Socket error while opening port 2 to ethernet 
>> host 192.168.198.91.
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: ERROR weewx.engine: Import 
>> of driver failed: [Errno 101] Network is unreachable (> 'weewx.WeeWxIOError'>)
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   Traceback (most recent call last):
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 354, in 
>> openPort
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   self.socket.connect((self.host, self.port))
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   OSError: [Errno 101] Network is unreachable
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   During handling of the above exception, another exception occurred:
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   Traceback (most recent call last):
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   self.console = loader_function(config_dict, self)
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   return VantageService(engine, config_dict)
>> Oct 14 14:33:20

Re: [weewx-user] Updated linux and weewx, nwo won't run. Help, please.

2024-10-15 Thread 'loonsailor' via weewx-user

I've confirmed that the computer can reach the station by opening it from a 
browser.  The Wifilogger has an html interface, and when I enter its IP 
address into the browser's bar, I can see and interact with the station.

I'd been some years since I moved to weewx and configured this.  I don't 
remember why socket 2 is there in the config file.  Is there a 
historical reason for it?  
On Monday, October 14, 2024 at 4:13:46 PM UTC-7 Tom Keffer wrote:

> (In passing, it's a good idea to set debug=1 when you're trying to obtain 
> a log.)
>
> I would guess that the upgrade of Ubuntu somehow changed a firewall or 
> iptables setting, or something similar, rendering the address 
> 192.168.198.91 unreachable from whatever computer WeeWX is running on. To 
> double check this, you could try using telnet to see if you at least have 
> connectivity.
>
> Without connectivity, WeeWX won't get far.
>
> -tk
>
> On Mon, Oct 14, 2024 at 4:06 PM 'loonsailor' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> I've been running weewx 4.8.0 under unbuntu linux 20.04 (I think).  I 
>> upgraded today to ubunbtu 24.04.1 LTS, and the process also moved me to 
>> weewx 5.0.1.  Now it won't run.  First question is, why does "sudo apt 
>> update; sudo apt install weewx" not get me to 5.1?  But the much more 
>> important question is, why won't it run at all?  Here is the syslog.  Note 
>> that the socket that it's trying to open is to the WifiLogger2 board in my 
>> Vantage Pro 2.  Any ideas?
>>
>> Oct 14 14:32:29 ubu-mini-weather systemd[1]: Stopped Discard unused 
>> blocks once a week.
>> Oct 14 14:33:18 ubu-mini-weather systemd[1]: Started Discard unused 
>> blocks once a week.
>> Oct 14 14:33:19 ubu-mini-weather weewxd[833]: INFO __main__: Initializing 
>> weewxd version 5.0.1
>> Oct 14 14:33:19 ubu-mini-weather weewxd[833]: INFO __main__: Command 
>> line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Using Python 
>> 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0]
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Located at 
>> /usr/bin/python3
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Platform 
>> Linux-5.15.0-122-generic-x86_64-with-glibc2.35
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Locale: 
>> 'en_US.UTF-8'
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Entry path: 
>> /usr/share/weewx/weewxd.py
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: WEEWX_ROOT: 
>> /etc/weewx
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: 
>> Configuration file: /etc/weewx/weewx.conf
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: User module: 
>> /etc/weewx/bin/user
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Debug: 0
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: ERROR 
>> weewx.drivers.vantage: Socket error while opening port 2 to ethernet 
>> host 192.168.198.91.
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: ERROR weewx.engine: Import 
>> of driver failed: [Errno 101] Network is unreachable (> 'weewx.WeeWxIOError'>)
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   Traceback (most recent call last):
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 354, in 
>> openPort
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   self.socket.connect((self.host, self.port))
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   OSError: [Errno 101] Network is unreachable
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   During handling of the above exception, another exception occurred:
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   Traceback (most recent call last):
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   self.console = loader_function(config_dict, self)
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   return VantageService(engine, config_dict)
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/dri

Re: [weewx-user] Updated linux and weewx, nwo won't run. Help, please.

2024-10-15 Thread 'loonsailor' via weewx-user

I've confirmed that the computer can reach the station, at least from a 
browser.  Entering the IP address into the browser's address bar does get 
me to the station.  I can tell because the wifilogger has a simple html 
interface that I can see and interact with just fine.

On Monday, October 14, 2024 at 4:13:46 PM UTC-7 Tom Keffer wrote:

> (In passing, it's a good idea to set debug=1 when you're trying to obtain 
> a log.)
>
> I would guess that the upgrade of Ubuntu somehow changed a firewall or 
> iptables setting, or something similar, rendering the address 
> 192.168.198.91 unreachable from whatever computer WeeWX is running on. To 
> double check this, you could try using telnet to see if you at least have 
> connectivity.
>
> Without connectivity, WeeWX won't get far.
>
> -tk
>
> On Mon, Oct 14, 2024 at 4:06 PM 'loonsailor' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> I've been running weewx 4.8.0 under unbuntu linux 20.04 (I think).  I 
>> upgraded today to ubunbtu 24.04.1 LTS, and the process also moved me to 
>> weewx 5.0.1.  Now it won't run.  First question is, why does "sudo apt 
>> update; sudo apt install weewx" not get me to 5.1?  But the much more 
>> important question is, why won't it run at all?  Here is the syslog.  Note 
>> that the socket that it's trying to open is to the WifiLogger2 board in my 
>> Vantage Pro 2.  Any ideas?
>>
>> Oct 14 14:32:29 ubu-mini-weather systemd[1]: Stopped Discard unused 
>> blocks once a week.
>> Oct 14 14:33:18 ubu-mini-weather systemd[1]: Started Discard unused 
>> blocks once a week.
>> Oct 14 14:33:19 ubu-mini-weather weewxd[833]: INFO __main__: Initializing 
>> weewxd version 5.0.1
>> Oct 14 14:33:19 ubu-mini-weather weewxd[833]: INFO __main__: Command 
>> line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Using Python 
>> 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0]
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Located at 
>> /usr/bin/python3
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Platform 
>> Linux-5.15.0-122-generic-x86_64-with-glibc2.35
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Locale: 
>> 'en_US.UTF-8'
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Entry path: 
>> /usr/share/weewx/weewxd.py
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: WEEWX_ROOT: 
>> /etc/weewx
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: 
>> Configuration file: /etc/weewx/weewx.conf
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: User module: 
>> /etc/weewx/bin/user
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO __main__: Debug: 0
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: ERROR 
>> weewx.drivers.vantage: Socket error while opening port 2 to ethernet 
>> host 192.168.198.91.
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: ERROR weewx.engine: Import 
>> of driver failed: [Errno 101] Network is unreachable (> 'weewx.WeeWxIOError'>)
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   Traceback (most recent call last):
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 354, in 
>> openPort
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   self.socket.connect((self.host, self.port))
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   OSError: [Errno 101] Network is unreachable
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   During handling of the above exception, another exception occurred:
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   Traceback (most recent call last):
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   self.console = loader_function(config_dict, self)
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>>   return VantageService(engine, config_dict)
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in 
>> __init__
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL weewx.engine:

Re: [weewx-user] Updated linux and weewx, nwo won't run. Help, please.

2024-10-15 Thread 'loonsailor' via weewx-user

re the version of weewx, I did "sudo apt update; sudo apt upgrade; sudo apt 
install weewx" and I get the response that 5.0.1 is the current version.  I 
looked in /etc/apt/sources.d, and the file weewx.list contains only one 
commented out line:

# deb [arch=all] http://weewx.com/apt/python3 buster main # disabled on 
upgrade to jammy

I'm now on Linux 24.04.1 LTS, which is, I think, jammy.  Should I have a 
different repository list?

Re the port problem, I've changed the wifilogger port to  (instead of 
2), and set debug to 1 and port  in weewx.conf.  Still no joy.  
Here's the log with debug.

2024-10-14T18:25:40.108787-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Initializing weewxd version 5.0.1
2024-10-14T18:25:40.110003-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Command line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
2024-10-14T18:25:40.121078-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Using Python 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0]
2024-10-14T18:25:40.121308-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Located at /usr/bin/python3
2024-10-14T18:25:40.122800-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Platform Linux-5.15.0-122-generic-x86_64-with-glibc2.39
2024-10-14T18:25:40.123611-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Locale: 'en_US.UTF-8'
2024-10-14T18:25:40.124478-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Entry path: /usr/share/weewx/weewxd.py
2024-10-14T18:25:40.125329-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: WEEWX_ROOT: /etc/weewx
2024-10-14T18:25:40.126199-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Configuration file: /etc/weewx/weewx.conf
2024-10-14T18:25:40.127036-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: User module: /etc/weewx/bin/user
2024-10-14T18:25:40.127989-07:00 ubu-mini-weather weewxd[941]: INFO 
__main__: Debug: 1
2024-10-14T18:25:40.128951-07:00 ubu-mini-weather weewxd[941]: DEBUG 
__main__: Initializing engine
2024-10-14T18:25:40.136337-07:00 ubu-mini-weather weewxd[941]: INFO 
weewx.engine: Loading station type Vantage (weewx.drivers.vantage)
2024-10-14T18:25:40.291519-07:00 ubu-mini-weather weewxd[941]: DEBUG 
weewx.drivers.vantage: Driver version is 3.6.2
2024-10-14T18:25:40.300207-07:00 ubu-mini-weather weewxd[941]: DEBUG 
weewx.drivers.vantage: Option loop_request=2
2024-10-14T18:25:40.301295-07:00 ubu-mini-weather weewxd[941]: ERROR 
weewx.drivers.vantage: Socket error while opening port  to ethernet 
host 192.168.198.91.
2024-10-14T18:25:40.302074-07:00 ubu-mini-weather weewxd[941]: ERROR 
weewx.engine: Import of driver failed: [Errno 101] Network is unreachable 
()
2024-10-14T18:25:40.309610-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   Traceback (most recent call last):
2024-10-14T18:25:40.310587-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine: File "/usr/share/weewx/weewx/drivers/vantage.py", 
line 354, in openPort
2024-10-14T18:25:40.311404-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   self.socket.connect((self.host, self.port))
2024-10-14T18:25:40.312183-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   OSError: [Errno 101] Network is unreachable
2024-10-14T18:25:40.312794-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   
2024-10-14T18:25:40.313291-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   During handling of the above exception, another 
exception occurred:
2024-10-14T18:25:40.313738-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   
2024-10-14T18:25:40.314173-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   Traceback (most recent call last):
2024-10-14T18:25:40.314724-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine: File "/usr/share/weewx/weewx/engine.py", line 
115, in setupStation
2024-10-14T18:25:40.316118-07:00 ubu-mini-weather weewxd[941]: CRITICAL 
weewx.engine:   self.console = loader_function(config_dict, 
self)

I tried to telnet to the new port, and get the following:
$ telnet 192.168.198.91:
Server lookup failure:  192.168.198.91::telnet, Name or service not 
known

I think that is a message from the logger, but I'm not certain.

BTW, I'm using my old conf file, which still says it's version 4.8.  
Doesn't seem like that should be thr problem, but...
On Monday, October 14, 2024 at 4:58:52 PM UTC-7 Tom Keffer wrote:

> Being able to browse to the logger doesn't really prove much. Port 80 is a 
> very common port to leave open. Port 2, not so common.
>
> Try telnet to port 2 as the same user that's running weewxd. I don't 
> know what user that is (debug=1 would tell you), but if you upgraded to 
> v5.0.1, it's likely to be user 'weewx'.
>
> Which makes me realize we didn't address your other problem: not upgrading 
> to v5.1.0. I have not seen that before. Can you try apt update and upgrade 
>

Re: [weewx-user] Updated linux and weewx, nwo won't run. Help, please.

2024-10-15 Thread matthew wall

On Tuesday, October 15, 2024 at 8:01:47 AM UTC-4 loonsailor wrote:

re the version of weewx, I did "sudo apt update; sudo apt upgrade; sudo apt 
install weewx" and I get the response that 5.0.1 is the current version.  I 
looked in /etc/apt/sources.d, and the file weewx.list contains only one 
commented out line:

# deb [arch=all] http://weewx.com/apt/python3 buster main # disabled on 
upgrade to jammy

I'm now on Linux 24.04.1 LTS, which is, I think, jammy.  Should I have a 
different repository list?


please uncomment that line, then do 'sudo apt update'.  at that point you 
should see 5.1.0 as the latest available weewx.  something like 'apt-cache 
show weewx' i think?

there is only one weewx repository for python3 on debian systems.  the 
'buster' indicates the oldest compatible debian release; that repository 
will work with buster and anything later.


 

-- 
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/2f985185-311b-4048-a262-514404972515n%40googlegroups.com.

[weewx-user] Re: Updated linux and weewx, nwo won't run. Help, please.

2024-10-15 Thread matthew wall



On Monday, October 14, 2024 at 7:06:24 PM UTC-4 loonsailor wrote:

Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL __main__: Unable to 
load driver: [Errno 101] Network is unreachable
Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL __main__:  
 Exiting...


this smells like weewx starting before the networking has started.  can you 
'sudo systemctl start weewx' once the system is up and running?
 

Oct 14 14:33:20 ubu-mini-weather systemd[1]: weewx.service: Main process 
exited, code=exited, status=4/NOPERMISSION
Oct 14 14:33:20 ubu-mini-weather systemd[1]: weewx.service: Failed with 
result 'exit-code'.


but this indicates something more insidious, such as a firewall, or 
selinux/apparmor, or some kind of systemd jail.  can you get more 
information from systemd about why it is reporting NOPERMISSION for your 
weewxd process?

-- 
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/b952b770-1651-4820-82bd-2c1727396083n%40googlegroups.com.

[weewx-user] Re: paho-mqtt 1.6.1 Still Required for WeeWX 5.x?

2024-10-15 Thread tarob...@gmail.com

Is it confirmed that paho-mqtt (latest is version 5.0) works with 
weewx-mqtt extension? Having a hard time on installing paho-mqtt version 
1.6.1 on Bookworm given the externally managed environment error.

On Tuesday, October 1, 2024 at 10:51:20 PM UTC-4 gary@gmail.com wrote:

> Yeah, I read the stackoverflow thread and it doesn't suggest that the 
> issue was fixed. The breaking changes are still there, just a workaround 
> for developers. Or so it seems. Perhaps the extension in question is a 
> limited circumstance.
> I'll give it a try and report back. I'm doing a favor install for a friend 
> who requires SDR and a BMP for pressure. For this install, I'll just stay 
> with 1.6.1
>
> *Update 2024-05*
>
> Version 2.1 
>  has now 
> been released. This now defaults to CallbackAPIVersion.VERSION1 which 
> will, in limited circumstances, mean old code still runs. This will not 
> help if you pass positional parameters to client (e.g. 
> mqtt.Client("thisIsMyClientID")) and specifying a callback version is 
> recommended to avoid future confusion (because this has an impact on the 
> parameters passed to callbacks
> On Tuesday, October 1, 2024 at 10:05:46 PM UTC-4 vince wrote:
>
>> weewx itself does not require paho-mqtt at all, although some extensions 
>> of course do require that library.
>>
>> A quick search says there were breaking changes in paho-mqtt 2.0.0 which 
>> came out in January but these were reportedly fixed in the default config 
>> in 2.1.0 according to a followup in 
>> https://stackoverflow.com/questions/77984857/paho-mqtt-unsupported-callback-api-version-error
>>  
>> if you want to do the reading.
>>
>> You can certainly pin your setup to 1.6.1 if you want to do so and if 
>> you're running a pip installation.   Looks like 1.6.1 is the current 
>> version for raspi os if you use their dpkg.
>>
>> You'd have to find whatever 'issue' you are thinking of for folks to 
>> answer yes/no on whatever question you can't remember.  Or give it a try 
>> and let us all know !
>>
>> On Tuesday, October 1, 2024 at 6:23:47 PM UTC-7 gary@gmail.com wrote:
>>
>>> There was an issue with paho-mqtt that needed version 1.6.1 installed as 
>>> a workaround.
>>> I've lost track of the issue and would like to know if this workaround 
>>> is still needed.
>>> Thanks
>>>
>>

-- 
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/dfe099d9-5659-4323-a472-7e9618f9fb99n%40googlegroups.com.

[weewx-user] Error pasar de FTP a SFTP

2024-10-15 Thread pachu fernandez

Hola
Mi proveedor de hosting (Ionos) ha dejado de funcionar con ftp y mi página 
web no funciona desde hace unos días www.meteolamadrid.es 
Al instalar Sftp https://github.com/matthewwall/weewx-sftp me da error y no 
consigo que funcione...

root@raspberrypi:~# sudo pip install pysftp
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting pysftp
  Using cached 
https://www.piwheels.org/simple/pysftp/pysftp-0.2.9-py3-none-any.whl
Collecting paramiko>=1.17 (from pysftp)
  Using cached 
https://files.pythonhosted.org/packages/1f/66/14b2c030fcce69cba482d205c2d1462ca5c77303a263260dcb1192801c85/paramiko-3.5.0-py3-none-any.whl
Collecting cryptography>=3.3 (from paramiko>=1.17->pysftp)
  Using cached 
https://www.piwheels.org/simple/cryptography/cryptography-43.0.1-cp37-abi3-linux_armv7l.whl
Collecting bcrypt>=3.2 (from paramiko>=1.17->pysftp)
  Using cached 
https://files.pythonhosted.org/packages/e4/7e/d95e7d96d4828e965891af92e43b52a4cd3395dc1c1ef4ee62748d0471d0/bcrypt-4.2.0.tar.gz
Exception:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", 
line 143, in main
status = self.run(options, args)
  File "/usr/lib/python3/dist-packages/pip/_internal/commands/install.py", 
line 338, in run
resolver.resolve(requirement_set)
  File "/usr/lib/python3/dist-packages/pip/_internal/resolve.py", line 102, 
in resolve
self._resolve_one(requirement_set, req)
  File "/usr/lib/python3/dist-packages/pip/_internal/resolve.py", line 256, 
in _resolve_one
abstract_dist = self._get_abstract_dist_for(req_to_install)
  File "/usr/lib/python3/dist-packages/pip/_internal/resolve.py", line 209, 
in _get_abstract_dist_for
self.require_hashes
  File 
"/usr/lib/python3/dist-packages/pip/_internal/operations/prepare.py", line 
298, in prepare_linked_requirement
abstract_dist.prep_for_dist(finder, self.build_isolation)
  File 
"/usr/lib/python3/dist-packages/pip/_internal/operations/prepare.py", line 
100, in prep_for_dist
self.req.load_pyproject_toml()
  File "/usr/lib/python3/dist-packages/pip/_internal/req/req_install.py", 
line 428, in load_pyproject_toml
str(self)
  File "/usr/lib/python3/dist-packages/pip/_internal/pyproject.py", line 
43, in load_pyproject_toml
pp_toml = pytoml.load(f)
  File 
"/usr/share/python-wheels/pytoml-0.1.2-py2.py3-none-any.whl/pytoml/parser.py", 
line 303, in load
filename=fin.name)
  File 
"/usr/share/python-wheels/pytoml-0.1.2-py2.py3-none-any.whl/pytoml/parser.py", 
line 370, in loads
toks.expect('=', 'expected_equals')
  File 
"/usr/share/python-wheels/pytoml-0.1.2-py2.py3-none-any.whl/pytoml/parser.py", 
line 250, in expect
self.error(error_text)
  File 
"/usr/share/python-wheels/pytoml-0.1.2-py2.py3-none-any.whl/pytoml/parser.py", 
line 253, in error
raise TomlError(message, self.pos[0][0], self.pos[0][1], self._filename)
pytoml.core.TomlError: /tmp/pip-install-idvpps1r/bcrypt/pyproject.toml(61, 
5): expected_equals
root@raspberrypi:~#

-- 
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/457078e9-35a0-4740-9577-ffd900ee7b32n%40googlegroups.com.

[weewx-user] Re: Updated linux and weewx, nwo won't run. Help, please.

2024-10-15 Thread 'loonsailor' via weewx-user

Thanks, Matthew, I think you're right.  I started weewx using systemctl and 
it works.  So, probably a startup ordering problem.  I won't be able to 
work on that until this afternoon (PDT) to confirm.

As for the version issue, I hadn't noticed that I was getting this error.  
Should I override somehow, or is it an issue with the repository?

Err:1 https://weewx.com/apt/python3 buster InRelease
  The following signatures couldn't be verified because the public key is 
not available: NO_PUBKEY E788768B9CB16E10
Reading package lists... Done
W: GPG error: https://weewx.com/apt/python3 buster InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY E788768B9CB16E10
E: The repository 'https://weewx.com/apt/python3 buster InRelease' is not 
signed.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.

On Tuesday, October 15, 2024 at 5:48:30 AM UTC-7 matthew wall wrote:

> On Monday, October 14, 2024 at 7:06:24 PM UTC-4 loonsailor wrote:
>
> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL __main__: Unable to 
> load driver: [Errno 101] Network is unreachable
> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL __main__:  
>  Exiting...
>
>
> this smells like weewx starting before the networking has started.  can 
> you 'sudo systemctl start weewx' once the system is up and running?
>  
>
> Oct 14 14:33:20 ubu-mini-weather systemd[1]: weewx.service: Main process 
> exited, code=exited, status=4/NOPERMISSION
> Oct 14 14:33:20 ubu-mini-weather systemd[1]: weewx.service: Failed with 
> result 'exit-code'.
>
>
> but this indicates something more insidious, such as a firewall, or 
> selinux/apparmor, or some kind of systemd jail.  can you get more 
> information from systemd about why it is reporting NOPERMISSION for your 
> weewxd process?
>
>

-- 
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/a17cc2c9-6b6f-4184-810e-38e974e91227n%40googlegroups.com.

[weewx-user] Error al instalar SFTP

2024-10-15 Thread pachu fernandez

 Hola
Mi proveedor de hosting (Ionos) ha dejado de funcionar con ftp y mi página 
web no funciona desde hace unos días www.meteolamadrid.es 
Al instalar Sftp https://github.com/matthewwall/weewx-sftp me da error y no 
consigo que funcione...

root@raspberrypi:~# sudo pip install pysftp
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting pysftp
  Using cached 
https://www.piwheels.org/simple/pysftp/pysftp-0.2.9-py3-none-any.whl
Collecting paramiko>=1.17 (from pysftp)
  Using cached 
https://files.pythonhosted.org/packages/1f/66/14b2c030fcce69cba482d205c2d1462ca5c77303a263260dcb1192801c85/paramiko-3.5.0-py3-none-any.whl
Collecting cryptography>=3.3 (from paramiko>=1.17->pysftp)
  Using cached 
https://www.piwheels.org/simple/cryptography/cryptography-43.0.1-cp37-abi3-linux_armv7l.whl
Collecting bcrypt>=3.2 (from paramiko>=1.17->pysftp)
  Using cached 
https://files.pythonhosted.org/packages/e4/7e/d95e7d96d4828e965891af92e43b52a4cd3395dc1c1ef4ee62748d0471d0/bcrypt-4.2.0.tar.gz
Exception:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", 
line 143, in main
status = self.run(options, args)
  File "/usr/lib/python3/dist-packages/pip/_internal/commands/install.py", 
line 338, in run
resolver.resolve(requirement_set)
  File "/usr/lib/python3/dist-packages/pip/_internal/resolve.py", line 102, 
in resolve
self._resolve_one(requirement_set, req)
  File "/usr/lib/python3/dist-packages/pip/_internal/resolve.py", line 256, 
in _resolve_one
abstract_dist = self._get_abstract_dist_for(req_to_install)
  File "/usr/lib/python3/dist-packages/pip/_internal/resolve.py", line 209, 
in _get_abstract_dist_for
self.require_hashes
  File 
"/usr/lib/python3/dist-packages/pip/_internal/operations/prepare.py", line 
298, in prepare_linked_requirement
abstract_dist.prep_for_dist(finder, self.build_isolation)
  File 
"/usr/lib/python3/dist-packages/pip/_internal/operations/prepare.py", line 
100, in prep_for_dist
self.req.load_pyproject_toml()
  File "/usr/lib/python3/dist-packages/pip/_internal/req/req_install.py", 
line 428, in load_pyproject_toml
str(self)
  File "/usr/lib/python3/dist-packages/pip/_internal/pyproject.py", line 
43, in load_pyproject_toml
pp_toml = pytoml.load(f)
  File 
"/usr/share/python-wheels/pytoml-0.1.2-py2.py3-none-any.whl/pytoml/parser.py", 
line 303, in load
filename=fin.name)
  File 
"/usr/share/python-wheels/pytoml-0.1.2-py2.py3-none-any.whl/pytoml/parser.py", 
line 370, in loads
toks.expect('=', 'expected_equals')
  File 
"/usr/share/python-wheels/pytoml-0.1.2-py2.py3-none-any.whl/pytoml/parser.py", 
line 250, in expect
self.error(error_text)
  File 
"/usr/share/python-wheels/pytoml-0.1.2-py2.py3-none-any.whl/pytoml/parser.py", 
line 253, in error
raise TomlError(message, self.pos[0][0], self.pos[0][1], self._filename)
pytoml.core.TomlError: /tmp/pip-install-idvpps1r/bcrypt/pyproject.toml(61, 
5): expected_equals
root@raspberrypi:~#

root@raspberrypi:~# sudo tail -f /var/log/weewx.log
Oct 15 12:07:55 raspberrypi weewx[1008] INFO user.sftp: sftpgenerator: 
upload not possible: No module named pysftp
Oct 15 12:10:14 raspberrypi weewx[1008] INFO weewx.manager: Added record 
2024-10-15 12:10:00 CEST (1728987000) to database 'weewx.sdb'
Oct 15 12:10:14 raspberrypi weewx[1008] INFO weewx.manager: Added record 
2024-10-15 12:10:00 CEST (1728987000) to daily summary in 'weewx.sdb'
Oct 15 12:10:19 raspberrypi weewx[1008] INFO weewx.cheetahgenerator: 
Generated 10 files for report SeasonsReport in 3.79 seconds
Oct 15 12:10:47 raspberrypi weewx[1008] INFO weewx.imagegenerator: 
Generated 12 images for report SeasonsReport in 28.27 seconds
Oct 15 12:10:47 raspberrypi weewx[1008] INFO weewx.reportengine: Copied 17 
files to /var/www/html/weewx
Oct 15 12:10:51 raspberrypi weewx[1008] INFO weewx.cheetahgenerator: 
Generated 14 files for report StandardReport in 4.27 seconds
Oct 15 12:10:53 raspberrypi weewx[1008] INFO weewx.imagegenerator: 
Generated 12 images for report StandardReport in 1.65 seconds
Oct 15 12:10:53 raspberrypi weewx[1008] INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx
Oct 15 12:10:53 raspberrypi weewx[1008] INFO user.sftp: sftpgenerator: 
upload not possible: No module named pysftp

-- 
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/3dfdcfdb-d6ed-44d2-9c3c-5860d20cf7fbn%40googlegroups.com.

Re: [weewx-user] Re: '[Errno 101] Network is unreachable' with MQTT.Subscribe

2024-10-15 Thread bell...@gmail.com

Stefan, 
Here are a couple of more things you could try.
First, try subscribing via mosquitto_sub to via the host name and the IPV4 
and IPV6 addresses.
mosquitto_sub  -v -t '#' -h wxvm.bz3gfkrlqtrsc3sv.myfritz.net
mosquitto_sub  -v -t '#' -h 77.21.85.171
mosquitto_sub  -v -t '#' -h 2a02:8108:9340:757c:efa5:3c2b:a158:b1d9

You could also try to run the attached  (python3 connect.py). If I have 
read the paho mqtt and socket code correctly, this should simulate what it 
does to establish a connection.
rich
On Tuesday 15 October 2024 at 05:11:52 UTC-4 Stefan Gliessmann wrote:

> Hello Rich et al.,
>
> I was a bit busy exploring Spain and, so, did not do a lot of trouble 
> shooting on this issue ...
>
> Well - I still have the same issue:
>
> [image: Screenshot 2024-10-15 at 11.05.50.png]
>
> When I run the little socket info py, I get this:
>
> [image: Screenshot 2024-10-15 at 11.05.13.png]
>
> which looks good to me ... I am continued to be puzzled ...
>
> Please throw more stuff at me to see if anything might stick and we have 
> an inlay to the problem ...
>
> Cheers,
> Stefan
>
> On Wednesday, October 9, 2024 at 1:28:55 AM UTC+2 bell...@gmail.com wrote:
>
>> Well, the fact that MBP is behind the router and connect via websockets 
>> (Belchertown) and MQTT (MQTT Explorer) could connect to your broker, makes 
>> it seem like it is something with the PI or pahoo mqtt.
>> While not exact, this seems similar 
>> https://github.com/eclipse/paho.mqtt.python/issues/154
>> I''d try running mosquitto_sub from the PI and MBP and see if it works on 
>> both.
>> You could also try running the attached on both. From my understanding, 
>> it is used to get the IP to create the socket. I'm wondering if on the PI 
>> it is not returning a 'good' IP.
>> I'm definitely not a network guy and I'm wading deep into pahoo mqtt and 
>> the the python socket module. So, yes, I am throwing stuff against the wall 
>> to see what will stick...
>> rich
>>
>> On Tuesday 8 October 2024 at 16:45:36 UTC-4 Stefan Gliessmann wrote:
>>
>>> So your RV Router can publish to your MQTT broker? Is this some type of 
>>> built in functionality of the router?
>>>   - Yes, it is. The RV Router has a ton of features including GPS and 
>>> MQTT. For GPS I was able to configure "Modbus TCP Devices" (menu point of 
>>> the RV Router) to publish lat & long per MQTT under topic GPS.
>>> This is the router that the PI is behind that cannot publish or 
>>> subscribe?
>>>   - Yes, the weewx PI is behind the RV Router (Teltonika RUTX11 is the 
>>> brand and model)
>>> Are you running MQTT Explorer on the PI. If so, it appears that can 
>>> subscribe, correct?
>>>   - Ah, no! The MQTT Explorer runs on my MBP. My MBP is also "behind" 
>>> the RV Router and can connect to the home MQTT broker!
>>> The browser is also runing on the PI, correct?
>>>   - Hmm, no ... You mean the web browser showing "Connected. Waiting for 
>>> data ..."? No, that is again on my MBP connected to a web host in the 
>>> cloud. There is - at least for me - no way to have a web server on the PI 
>>> behind the RV Router which does not get a static IP over 4G ... The PI ftps 
>>> to the remote (cloud) web server (the provider is strato.de - I use the 
>>> same for my "home" WeeWX).
>>>
>>> Next - probably tomorrow - I will try to VPN my RV Router to my home 
>>> router via WireGuard ... Maybe that will solve it temporarily (while I am 
>>> on holiday)!
>>>
>>> On Tuesday, October 8, 2024 at 9:58:11 PM UTC+2 bell...@gmail.com wrote:
>>>
 A few of questions/clarifications
 So you RV Router can publish to your MQTT broker? Is this some type of 
 built in functionality of the router?
 This is the router that the PI is behind that cannot publish or 
 subscribe?
 Are you running MQTT Explorer on the PI. If so, it appears that can 
 subscribe, correct?
 The browser is also runing on the PI, correct?
 Things are pointing to something in paho mqtt client, used by both 
 MQTTSubscribe WeeWX-MQTT… Unfortunately I still don’t have any good ideas 
 yet. I was really hoping that the IP address would work…

 Note, 1.6.1 is not the latest version. The version installed by apt is 
 behind. The version is up to 2.1.0 
 BUT, I would be very hesitant to upgrade to that. 2.0 introduced many 
 breaking changes and many python clients broke. In theory 2.1.0 ‘fixes’ 
 this, but since I have updated all my MQTT clients to work with 2.x and 
 1.6, I cannot verify that.
 AND, I do not see anything in the release notes that leads me to think 
 this would be fixed.
 rich

 On Tuesday 8 October 2024 at 15:37:06 UTC-4 Stefan Gliessmann wrote:

> Continuing to find some more details/hints/breadcrumbs ...
> For MQTT.Subscribe I used the IP of the broker which gets resolved via 
> ping. Still not reachable.
> Then I set MQTT.Subcribe enable = false to see if the other client can 
> connect to the same bro

[weewx-user] Re: paho-mqtt 1.6.1 Still Required for WeeWX 5.x?

2024-10-15 Thread tarob...@gmail.com

Disregard. I ran apt-cache policy python3-paho-mqtt which showed version 
1.6.1-1 as the latest for rpi on Bookworm.

On Tuesday, October 15, 2024 at 9:20:00 AM UTC-4 tarob...@gmail.com wrote:

> Is it confirmed that paho-mqtt (latest is version 5.0) works with 
> weewx-mqtt extension? Having a hard time on installing paho-mqtt version 
> 1.6.1 on Bookworm given the externally managed environment error.
>
> On Tuesday, October 1, 2024 at 10:51:20 PM UTC-4 gary@gmail.com wrote:
>
>> Yeah, I read the stackoverflow thread and it doesn't suggest that the 
>> issue was fixed. The breaking changes are still there, just a workaround 
>> for developers. Or so it seems. Perhaps the extension in question is a 
>> limited circumstance.
>> I'll give it a try and report back. I'm doing a favor install for a 
>> friend who requires SDR and a BMP for pressure. For this install, I'll just 
>> stay with 1.6.1
>>
>> *Update 2024-05*
>>
>> Version 2.1 
>>  has 
>> now been released. This now defaults to CallbackAPIVersion.VERSION1 which 
>> will, in limited circumstances, mean old code still runs. This will not 
>> help if you pass positional parameters to client (e.g. 
>> mqtt.Client("thisIsMyClientID")) and specifying a callback version is 
>> recommended to avoid future confusion (because this has an impact on the 
>> parameters passed to callbacks
>> On Tuesday, October 1, 2024 at 10:05:46 PM UTC-4 vince wrote:
>>
>>> weewx itself does not require paho-mqtt at all, although some extensions 
>>> of course do require that library.
>>>
>>> A quick search says there were breaking changes in paho-mqtt 2.0.0 which 
>>> came out in January but these were reportedly fixed in the default config 
>>> in 2.1.0 according to a followup in 
>>> https://stackoverflow.com/questions/77984857/paho-mqtt-unsupported-callback-api-version-error
>>>  
>>> if you want to do the reading.
>>>
>>> You can certainly pin your setup to 1.6.1 if you want to do so and if 
>>> you're running a pip installation.   Looks like 1.6.1 is the current 
>>> version for raspi os if you use their dpkg.
>>>
>>> You'd have to find whatever 'issue' you are thinking of for folks to 
>>> answer yes/no on whatever question you can't remember.  Or give it a try 
>>> and let us all know !
>>>
>>> On Tuesday, October 1, 2024 at 6:23:47 PM UTC-7 gary@gmail.com 
>>> wrote:
>>>
 There was an issue with paho-mqtt that needed version 1.6.1 installed 
 as a workaround.
 I've lost track of the issue and would like to know if this workaround 
 is still needed.
 Thanks

>>>

-- 
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/edb46f19-0be7-40db-9671-dcf853841cadn%40googlegroups.com.

[weewx-user] Re: Updated linux and weewx, nwo won't run. Help, please.

2024-10-15 Thread 'loonsailor' via weewx-user

Not sure how I missed the configure part, but I guess I did.  Ran that, and 
now I'm on 5.1.  And, miraculously, 5.1 works just fine.  Not sure why I 
had the driver problem with 5.0.1, but all's well that ends well.

One last question.  What's best practice with weewx.conf?  I kept my old 
(4.8) config file and it works.  I see a file called 
weewx.conf-4.8.0-5.1.0.  Is that a merged config file?  Should I just use 
that, or stick with my old config, or merge by hand?

Thanks for all the help!

On Tuesday, October 15, 2024 at 1:25:24 PM UTC-7 vince wrote:

> Run the 'configure apt' section at the beginning of 
> https://www.weewx.com/docs/5.1/quickstarts/debian/ please.  On a clean 
> ubuntu 24.04.1LTS system the quickstart instructions worked perfectly and I 
> got 5.1.0 
>
> On Tuesday, October 15, 2024 at 7:36:28 AM UTC-7 loonsailor wrote:
>
>> Thanks, Matthew, I think you're right.  I started weewx using systemctl 
>> and it works.  So, probably a startup ordering problem.  I won't be able to 
>> work on that until this afternoon (PDT) to confirm.
>>
>> As for the version issue, I hadn't noticed that I was getting this 
>> error.  Should I override somehow, or is it an issue with the repository?
>>
>> Err:1 https://weewx.com/apt/python3 buster InRelease
>>   The following signatures couldn't be verified because the public key is 
>> not available: NO_PUBKEY E788768B9CB16E10
>> Reading package lists... Done
>> W: GPG error: https://weewx.com/apt/python3 buster InRelease: The 
>> following signatures couldn't be verified because the public key is not 
>> available: NO_PUBKEY E788768B9CB16E10
>> E: The repository 'https://weewx.com/apt/python3 buster InRelease' is 
>> not signed.
>> N: Updating from such a repository can't be done securely, and is 
>> therefore disabled by default.
>> N: See apt-secure(8) manpage for repository creation and user 
>> configuration details.
>>
>> On Tuesday, October 15, 2024 at 5:48:30 AM UTC-7 matthew wall wrote:
>>
>>> On Monday, October 14, 2024 at 7:06:24 PM UTC-4 loonsailor wrote:
>>>
>>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL __main__: Unable 
>>> to load driver: [Errno 101] Network is unreachable
>>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL __main__: 
>>>   Exiting...
>>>
>>>
>>> this smells like weewx starting before the networking has started.  can 
>>> you 'sudo systemctl start weewx' once the system is up and running?
>>>  
>>>
>>> Oct 14 14:33:20 ubu-mini-weather systemd[1]: weewx.service: Main process 
>>> exited, code=exited, status=4/NOPERMISSION
>>> Oct 14 14:33:20 ubu-mini-weather systemd[1]: weewx.service: Failed with 
>>> result 'exit-code'.
>>>
>>>
>>> but this indicates something more insidious, such as a firewall, or 
>>> selinux/apparmor, or some kind of systemd jail.  can you get more 
>>> information from systemd about why it is reporting NOPERMISSION for your 
>>> weewxd process?
>>>
>>>

-- 
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/666aafe4-6b86-40ea-8397-2f718adc1940n%40googlegroups.com.

[weewx-user] Re: Updated linux and weewx, nwo won't run. Help, please.

2024-10-15 Thread 'loonsailor' via weewx-user

Not sure how I missed the configure part, but I guess I did.  Ran that, and 
now I'm on 5.1.  And, miraculously, 5.1 works just fine, and I see why.  
Weewx is now started by a systemd service, which specifies that it requires 
the network before startup.  5.0.1 was started with the old rc5.d system, 
and it made no such specification, so it started too early.  It was, 
indeed, a bug in 5.0.1 that has now been fixed.

One last question.  What's best practice with weewx.conf?  I kept my old 
(4.8) config file and it works.  I see a file called 
weewx.conf-4.8.0-5.1.0.  Is that a merged config file?  Should I just use 
that, or stick with my old config, or merge by hand?

Thanks for all the help!


On Tuesday, October 15, 2024 at 1:25:24 PM UTC-7 vince wrote:

> Run the 'configure apt' section at the beginning of 
> https://www.weewx.com/docs/5.1/quickstarts/debian/ please.  On a clean 
> ubuntu 24.04.1LTS system the quickstart instructions worked perfectly and I 
> got 5.1.0 
>
> On Tuesday, October 15, 2024 at 7:36:28 AM UTC-7 loonsailor wrote:
>
>> Thanks, Matthew, I think you're right.  I started weewx using systemctl 
>> and it works.  So, probably a startup ordering problem.  I won't be able to 
>> work on that until this afternoon (PDT) to confirm.
>>
>> As for the version issue, I hadn't noticed that I was getting this 
>> error.  Should I override somehow, or is it an issue with the repository?
>>
>> Err:1 https://weewx.com/apt/python3 buster InRelease
>>   The following signatures couldn't be verified because the public key is 
>> not available: NO_PUBKEY E788768B9CB16E10
>> Reading package lists... Done
>> W: GPG error: https://weewx.com/apt/python3 buster InRelease: The 
>> following signatures couldn't be verified because the public key is not 
>> available: NO_PUBKEY E788768B9CB16E10
>> E: The repository 'https://weewx.com/apt/python3 buster InRelease' is 
>> not signed.
>> N: Updating from such a repository can't be done securely, and is 
>> therefore disabled by default.
>> N: See apt-secure(8) manpage for repository creation and user 
>> configuration details.
>>
>> On Tuesday, October 15, 2024 at 5:48:30 AM UTC-7 matthew wall wrote:
>>
>>> On Monday, October 14, 2024 at 7:06:24 PM UTC-4 loonsailor wrote:
>>>
>>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL __main__: Unable 
>>> to load driver: [Errno 101] Network is unreachable
>>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL __main__: 
>>>   Exiting...
>>>
>>>
>>> this smells like weewx starting before the networking has started.  can 
>>> you 'sudo systemctl start weewx' once the system is up and running?
>>>  
>>>
>>> Oct 14 14:33:20 ubu-mini-weather systemd[1]: weewx.service: Main process 
>>> exited, code=exited, status=4/NOPERMISSION
>>> Oct 14 14:33:20 ubu-mini-weather systemd[1]: weewx.service: Failed with 
>>> result 'exit-code'.
>>>
>>>
>>> but this indicates something more insidious, such as a firewall, or 
>>> selinux/apparmor, or some kind of systemd jail.  can you get more 
>>> information from systemd about why it is reporting NOPERMISSION for your 
>>> weewxd process?
>>>
>>>

-- 
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/1d2cba85-63a3-4103-9e98-119b931361adn%40googlegroups.com.

[weewx-user] Re: Updated linux and weewx, nwo won't run. Help, please.

2024-10-15 Thread vince

Run the 'configure apt' section at the beginning 
of https://www.weewx.com/docs/5.1/quickstarts/debian/ please.  On a clean 
ubuntu 24.04.1LTS system the quickstart instructions worked perfectly and I 
got 5.1.0 

On Tuesday, October 15, 2024 at 7:36:28 AM UTC-7 loonsailor wrote:

> Thanks, Matthew, I think you're right.  I started weewx using systemctl 
> and it works.  So, probably a startup ordering problem.  I won't be able to 
> work on that until this afternoon (PDT) to confirm.
>
> As for the version issue, I hadn't noticed that I was getting this error.  
> Should I override somehow, or is it an issue with the repository?
>
> Err:1 https://weewx.com/apt/python3 buster InRelease
>   The following signatures couldn't be verified because the public key is 
> not available: NO_PUBKEY E788768B9CB16E10
> Reading package lists... Done
> W: GPG error: https://weewx.com/apt/python3 buster InRelease: The 
> following signatures couldn't be verified because the public key is not 
> available: NO_PUBKEY E788768B9CB16E10
> E: The repository 'https://weewx.com/apt/python3 buster InRelease' is not 
> signed.
> N: Updating from such a repository can't be done securely, and is 
> therefore disabled by default.
> N: See apt-secure(8) manpage for repository creation and user 
> configuration details.
>
> On Tuesday, October 15, 2024 at 5:48:30 AM UTC-7 matthew wall wrote:
>
>> On Monday, October 14, 2024 at 7:06:24 PM UTC-4 loonsailor wrote:
>>
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL __main__: Unable 
>> to load driver: [Errno 101] Network is unreachable
>> Oct 14 14:33:20 ubu-mini-weather weewxd[833]: CRITICAL __main__:  
>>  Exiting...
>>
>>
>> this smells like weewx starting before the networking has started.  can 
>> you 'sudo systemctl start weewx' once the system is up and running?
>>  
>>
>> Oct 14 14:33:20 ubu-mini-weather systemd[1]: weewx.service: Main process 
>> exited, code=exited, status=4/NOPERMISSION
>> Oct 14 14:33:20 ubu-mini-weather systemd[1]: weewx.service: Failed with 
>> result 'exit-code'.
>>
>>
>> but this indicates something more insidious, such as a firewall, or 
>> selinux/apparmor, or some kind of systemd jail.  can you get more 
>> information from systemd about why it is reporting NOPERMISSION for your 
>> weewxd process?
>>
>>

-- 
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/c822fb09-2584-4bd7-8cc3-870e16d69c7an%40googlegroups.com.

Re: [weewx-user] Updated linux and weewx, nwo won't run. Help, please.

Re: [weewx-user] Updated linux and weewx, nwo won't run. Help, please.

Re: [weewx-user] Updated linux and weewx, nwo won't run. Help, please.

Re: [weewx-user] Updated linux and weewx, nwo won't run. Help, please.

Re: [weewx-user] Updated linux and weewx, nwo won't run. Help, please.

Re: [weewx-user] Updated linux and weewx, nwo won't run. Help, please.

[weewx-user] Re: Updated linux and weewx, nwo won't run. Help, please.

[weewx-user] Re: paho-mqtt 1.6.1 Still Required for WeeWX 5.x?

[weewx-user] Error pasar de FTP a SFTP

[weewx-user] Re: Updated linux and weewx, nwo won't run. Help, please.

[weewx-user] Error al instalar SFTP

Re: [weewx-user] Re: '[Errno 101] Network is unreachable' with MQTT.Subscribe

[weewx-user] Re: paho-mqtt 1.6.1 Still Required for WeeWX 5.x?

[weewx-user] Re: Updated linux and weewx, nwo won't run. Help, please.

[weewx-user] Re: Updated linux and weewx, nwo won't run. Help, please.

[weewx-user] Re: Updated linux and weewx, nwo won't run. Help, please.

16 matches

Site Navigation

Mail list logo

Footer information