[weewx-user] Re: weewx 5.02 crashes (and restarts) on trying to access a docker file?

2024-02-14 Thread gjr80 
Correct. Cmon will try to scan all mounted file systems except for those in 
an ignore list. Problem is the ignore list is not user configurable via a 
config file, rather it is hard coded in cmon.py. You have a few options; 
(1) raise an issue against the weewx-cmon repo and ask for Matthew to make 
the ignore list user configurable, (2) drop cmon from your system or (3) 
manually change the ignore list in cmon.py to exclude your docker overlays. 
I'd suggest a combination of (3) and (1).

Have a look at line 266 in cmon.py 
, 
just add your docker overlay to the list. Not sure you can add one wildcard 
entry for all docker overlays but a bit of experimentation will get you 
there. 

Gary

And do raise an issue for when Matthew does get some time for cmon.  

On Thursday 15 February 2024 at 02:14:31 UTC+10 valken...@gmail.com wrote:

> Since upgrading to weewx 5.02 on ubuntue 22.04, deb instaal. I had some 
> issues becuase weewx does not run as root user anymore. Most of the were 
> easy to solve. However on this ubuntu also a docker instance is running for 
> another application. 
> My syslog now tells me this:
>
> INFO weewx.engine: Main loop exiting. Shutting engine down.
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: INFO weewx.engine: Shutting 
> down StdReport thread
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__: Caught 
> OSError: [Errno 13] Toegang geweigerd: 
> '/var/lib/docker/overlay2/f40006ded3b1ca4e49c40cb408c89374b8b4a067f4de13711cf4be188137d355/merged'
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
>  Traceback (most recent call last):
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>  File "/usr/share/weewx/weewx/engine.py", line 210, in run
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>  File "/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>callback(event)
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>  File "/usr/share/weewx/weewx/engine.py", line 660, in check_loop
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>raise BreakLoop
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
>  weewx.engine.BreakLoop
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:   
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
>  During handling of the above exception, another exception occurred:
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:   
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
>  Traceback (most recent call last):
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>  File "/usr/share/weewx/weewx/engine.py", line 676, in post_loop
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>self._catchup(self.engine.console.genArchiveRecords)
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>  File "/usr/share/weewx/weewx/engine.py", line 723, in _catchup
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>for record in generator(lastgood_ts):
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>  File "/usr/share/weewx/weewx/drivers/__init__.py", line 31, in 
> genArchiveRecords
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>raise NotImplementedError("Method 'genArchiveRecords' not implemented")
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
>  NotImplementedError: Method 'genArchiveRecords' not implemented
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:   
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
>  During handling of the above exception, another exception occurred:
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:   
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
>  Traceback (most recent call last):
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>  File "/usr/share/weewx/weewxd.py", line 166, in main
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>engine.run()
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>  File "/usr/share/weewx/weewx/engine.py", line 217, in run
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
>self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
> Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:

Re: [weewx-user] Re: Weewx upgrade questions

2024-02-14 Thread kufuu 
If you have any problems like I did with Bullseye and Bookworm they have a 
64bit version of Buster at 

https://downloads.raspberrypi.org/raspios_arm64/images/raspios_arm64-2021-05-28/

I had way to many problems with the weewx 4.10.2 and 5 with mqtt running 
them  on Bullseye and Bookworm so I went to Buster64 and weewx 4.10.2 on a 
new pi zero 2 w, runs really good just cant get my weewx.sdb moved over 
from the pi zero w,  Permission denied when I tried to copy it over.

On Tuesday, February 13, 2024 at 8:18:28 AM UTC-5 Tom Keffer wrote:

> The only thing I would add is that if you're using the original "wview" 
> schema, there is no reason to switch to the "wview-extended" schema unless 
> you need the extra types. For a VantagePro, the original schema works fine. 
>
> Conversion is a lot of work.
>
> -tk
>
> On Mon, Feb 12, 2024 at 2:02 PM kutz...@gmail.com  
> wrote:
>
>> Thanks Michael and Vince. My Vantage Vue is connected to the Pi ZeroW 
>> with a serial to usb cable. Both of your recommendatons are directionally 
>> similar. I'll go with Vince's step by step to reduce my chances of making 
>> an error.
>>
>> Vince, thanks for the suggestion of pre-seeding NOAA data. I've got about 
>> 7 years of data. I *am* running Belchertown on the PiZero. It runs 
>> pretty well (maybe because of the older version of Weewx), Weewx rsyncs the 
>> data to a Digital Ocean droplet running NGINX there to serve the pages (and 
>> also host mosquito). The website is https://wx.kutzenco.com. Thanks for 
>> the comprehensive sequence of steps to follow, I *am* aware that 
>> Belchertown keeps its own copy of NOAA data,
>>
>> Will give it a shot!
>>
>> Best,
>> Phil
>> On Monday, February 12, 2024 at 3:29:52 PM UTC-5 vince wrote:
>>
>>> oh - just to add.  I found that pre-seeding your NOAA files helps speed 
>>> up a new installation first boot.  Just copy things over from your zeroW to 
>>> the new box and weewx will update the current month+year files as needed.  
>>> The other thing is if you run Belchertown (unlikely on a slow zeroW) it 
>>> 'also' has NOAA files in its output, so copy those into place too.  You can 
>>> do this anytime really.  Stop weewx.  Copy the NOAA files into your web 
>>> output directory.  Start weewx up.  Helps a lot.  Lots of years of NOAA 
>>> files to generate takes quite a while on a pi3 or slower box.
>>>
>>> On Monday, February 12, 2024 at 12:26:40 PM UTC-8 vince wrote:
>>>
 I would personally recommend using the pi3b+ to set up a clean new v5 
 setup rather than worrying upgrade scenarios

- install the latest raspios 32bit on the 3b+
- install the latest weewx v5
- configure it to run the Simulator (initially) to get it running 
and stable running a simulated station
- install any extensions and skins you've added.  Probably set 
enable=false for anything that uploads to other systems (initially)
- maybe set up the RTC and get that working on the 3b+ if you have 
one to install there too
- in short - get a full setup working vs. the Simulator  and vs. a 
webserver (I use nginx) of your choosing

 If you're running the Vantage driver getting the 3b+ to work with v5 is 
 straightforward and you can keep using the zeroW attached to the Vue until 
 you get the new pi set up to your liking using the Simulator.

 Re: the db schema, you'll need to check your db for whether you're 
 using the old smaller wview schema or the newer wview_extended schema.  If 
 you need to convert it to the new schema do that offline on the 3b+.  Not 
 too hard to do but it might take a while depending on how many years of 
 data you have in your current db.  Instructions are at 
 https://www.weewx.com/docs/5.0/utilities/weectl-database/#reconfigure-a-database

 Once you're running the bigger schema in your zeroW actual db, you 
 would stop weewx on the 3b+, move the archive/weewx.sdb file and 
 public_html tree aside,  copy your actual db into the archive directory, 
 switch to the vantage driver, and start weewx up.   Assuming you have a 
 Davis logger weewx will backfill any needed records the logger captured 
 from the Vue. You can't really hurt anything if you mess the procedure up 
 a 
 time or two, but it's pretty straightforward.  You'll have the zeroW db 
 there just in case.

 You can check to see if you're already running the extended schema in 
 your db already by just counting the number of fields:
  echo "SELECT count() FROM PRAGMA_TABLE_INFO('archive');" | 
 sqlite3 weewx.sdb

 The extended schema will return a count of 114.   The original schema 
 had around 53 or so if I recall correctly.  If you're weewx 3.x you are 
 probably going to see 53 as your answer.

 -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user"

Re: [weewx-user] Re: Belchertown lightning graph

2024-02-14 Thread Dan Roman 
No, I have not.  The consensus was since it is only a warning, and
everything else still works, it wasn't worth trying to muck around and fix
the format in the belly of the beast.  So I just let it be.


On Wed, Feb 14, 2024 at 3:51 PM Joachim Puttkammer 
wrote:

> Except that:
> user.belchertown: Observation lightning_strike_count is using unit count
> that returns %d for StringFormat, rather than float point decimal format
> value - using 0 as rounding
> Is showing in the system log.
>
> Have you solved the problem?
> Mark Fraser schrieb am Dienstag, 20. Juni 2023 um 12:05:47 UTC+2:
>
>> I currently have this in graphs.conf to show lightning strikes over the
>> past 3 hours and it works:
>>
>> [[Lightning_chart]]
>> title = Lightning (Last 3 Hours)
>> time_length = 10800
>> aggregate_interval = 300
>> gapsize = 108000
>> type = column
>>
>> [[[lightning_strike_count]]]
>> name = Lightning Count
>> zIndex = 1
>> aggregate_type = sum
>>
>> Except that:
>> user.belchertown: Observation lightning_strike_count is using unit count
>> that returns %d for StringFormat, rather than float point decimal format
>> value - using 0 as rounding
>> Is showing in the system log.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/8S1zsvbW2v8/unsubscribe.
> To unsubscribe from this group and all its topics, 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/d0e589e4-e830-4a04-a184-84991840c69dn%40googlegroups.com
> 
> .
>


-- 
Dan Roman
gdann...@gmail.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/CANKdm-OHHCYb3Bxa5RPLWqNRgdy2eRmxZF5kb2qDVEJxOhZ4Rw%40mail.gmail.com.

[weewx-user] Re: Belchertown lightning graph

2024-02-14 Thread Joachim Puttkammer 
Except that:
user.belchertown: Observation lightning_strike_count is using unit count
that returns %d for StringFormat, rather than float point decimal format
value - using 0 as rounding
Is showing in the system log.

Have you solved the problem?
Mark Fraser schrieb am Dienstag, 20. Juni 2023 um 12:05:47 UTC+2:

> I currently have this in graphs.conf to show lightning strikes over the 
> past 3 hours and it works:
>
> [[Lightning_chart]]
> title = Lightning (Last 3 Hours)
> time_length = 10800
> aggregate_interval = 300
> gapsize = 108000
> type = column
>
> [[[lightning_strike_count]]]
> name = Lightning Count
> zIndex = 1
> aggregate_type = sum
>
> Except that:
> user.belchertown: Observation lightning_strike_count is using unit count 
> that returns %d for StringFormat, rather than float point decimal format 
> value - using 0 as rounding
> Is showing in the system log.
>

-- 
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/d0e589e4-e830-4a04-a184-84991840c69dn%40googlegroups.com.

[weewx-user] Interceptor (acurite) on weewx > v5.0.1 fix

2024-02-14 Thread Graham Knights 
For others coming here with issues after upgrading to 5.0.1 or greater, my 
interceptor -> acurite hub was no longer working due to weewx no longer 
being run as root and thus being denied permission to port 80. Here is my 
solution for getting the interceptor driver working with the fewest 
workarounds:

Ensure weewx is disabled:
> sudo systemctl stop weewx

Install authbind:
> sudo apt install authbind

Configure authbind to allow weewx:
> sudo touch /etc/authbind/byport/80
> sudo chown weewx /etc/authbind/byport/80
> sudo chmod 777 /etc/authbind/byport/80

Modifiy /etc/weewx/systemd/weewx.service as follows (changes in bold):
[Service]
ExecStart=*authbind --deep* weewxd /etc/weewx/weewx.conf

Reload systemd manager config:
> sudo systemctl daemon-reload

Start weewx:
> sudo systemctl start weewx

Confirm no more errors:
> sudo tail -f /var/log/syslog

It took me forever to find the current weewx.service file as there are 
multiple copies scattered in several directories, and depending how you 
installed weewx the correct/currently used file may be in another directory 
so you may need to hunt and edit until the error stops.

Hopefully this helps others having similar issues!

-- 
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/87c1f9fe-4fd2-48e4-b6a5-2126e05dfe1dn%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

2024-02-14 Thread Ton Karsten 
Okay thanks.

Op wo 14 feb 2024 om 18:12 schreef vince :

> The weatherflow-udp driver works just fine on v5.
>
> On Wednesday, February 14, 2024 at 7:47:17 AM UTC-8 Ton Karsten wrote:
>
>> Thanks for sharing.
>> Which version are you using?
>> This: https://github.com/captain-coredump/weatherflow-udp
>> Or this one: https://github.com/rongrimes/weewx-tempest-pi
>>
>> Op woensdag 14 februari 2024 om 16:26:59 UTC+1 schreef Tom Hogland:
>>
>>> I'm currently using WeatherflowUDP with weewx 5.0.2 and it's working
>>> fine.
>>>
>>> On Wednesday, February 14, 2024 at 5:31:50 AM UTC-9 Ton Karsten wrote:
>>>
 I use the WeatherFlow Tempest for my weather station.
 I have equipped my weather station with the latest version of weewx.
 Is the WeatherFlowUDP driver suitable for weewx 5.x and has this been
 tested?
 I'm not sure if the installation will go without errors.
>>>
>>> --
> 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/50f83928-617b-447c-98a1-daff5f80964bn%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/CACngpza6bGxpWfbBVjhBPcd8UBsprq8CehG2GF3dauVQLpHvgw%40mail.gmail.com.

[weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

2024-02-14 Thread vince 
The weatherflow-udp driver works just fine on v5.

On Wednesday, February 14, 2024 at 7:47:17 AM UTC-8 Ton Karsten wrote:

> Thanks for sharing.
> Which version are you using?
> This: https://github.com/captain-coredump/weatherflow-udp
> Or this one: https://github.com/rongrimes/weewx-tempest-pi
>
> Op woensdag 14 februari 2024 om 16:26:59 UTC+1 schreef Tom Hogland:
>
>> I'm currently using WeatherflowUDP with weewx 5.0.2 and it's working fine.
>>
>> On Wednesday, February 14, 2024 at 5:31:50 AM UTC-9 Ton Karsten wrote:
>>
>>> I use the WeatherFlow Tempest for my weather station.
>>> I have equipped my weather station with the latest version of weewx.
>>> Is the WeatherFlowUDP driver suitable for weewx 5.x and has this been 
>>> tested?
>>> I'm not sure if the installation will go without errors.
>>
>>

-- 
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/50f83928-617b-447c-98a1-daff5f80964bn%40googlegroups.com.

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

2024-02-14 Thread walter Gross 
SOLVED


Hi Matthew

I have spent hours to solve this permission problems on version 5.  I had 
tested all with a new installation on a sep. SSD. After installing an 
Apache server and a dummy CMS I get the the same permission errors. Don't 
ask me why.
Anyway, I fetched the Version 4.10.2 with wget and installed the *.deb,  
gave the relevant permissions, uploaded the database to my "running system" 
and all works fine now. I am a bit anxious to get again problems on a 
system update, so I marked weewx on hold. Apologize for doing this. Thanks 
for your help

regards
Walter


matthew wall schrieb am Dienstag, 13. Februar 2024 um 15:44:05 UTC+1:

> On Tuesday, February 13, 2024 at 9:11:14 AM UTC-5 wagr...@gmail.com wrote:
>
>
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.imagegenerator: Unable to 
> save to file '/var/www/html/weewx/yearrx.png' [Errno 13] Keine 
> Berechtigung: '/var/www/html/weewx/yearrx.png':
> Feb 13 12:40:54 hp weewxd[4425]: INFO weewx.imagegenerator: Generated 0 
> images for report SeasonsReport in 3.97 seconds
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine: Caught 
> unrecoverable exception in generator 'weewx.reportengine.CopyGenerator'
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:  
>  [Errno 13] Keine Berechtigung: '/var/www/html/weewx'
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:  
>  Traceback (most recent call last):
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>  File "/usr/share/weewx/weewx/reportengine.py", line 220, in run
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>obj.start()
> Feb 13 12:40:54 hp weewxd[4425]: Traceback (most recent call last):
> Feb 13 12:40:54 hp weewxd[4425]:   File 
> "/usr/share/weewx/weewx/reportengine.py", line 220, in run
> Feb 13 12:40:54 hp weewxd[4425]: obj.start()
> Feb 13 12:40:54 hp weewxd[4425]:   File 
> "/usr/share/weewx/weewx/reportengine.py", line 409, in start
> Feb 13 12:40:54 hp weewxd[4425]: self.run()
> Feb 13 12:40:54 hp weewxd[4425]:   File 
> "/usr/share/weewx/weewx/reportengine.py", line 560, in run
> Feb 13 12:40:54 hp weewxd[4425]: ncopy += 
> weeutil.weeutil.deep_copy_path(path, html_dest_dir)
> Feb 13 12:40:54 hp weewxd[4425]:   File 
> "/usr/share/weewx/weeutil/weeutil.py", line 1807, in deep_copy_path
> Feb 13 12:40:54 hp weewxd[4425]: os.makedirs(d, exist_ok=True)
> Feb 13 12:40:54 hp weewxd[4425]:   File "/usr/lib/python3.9/os.py", line 
> 225, in makedirs
> Feb 13 12:40:54 hp weewxd[4425]: mkdir(name, mode)
> Feb 13 12:40:54 hp weewxd[4425]: PermissionError: [Errno 13] Keine 
> Berechtigung: '/var/www/html/weewx'
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>  File "/usr/share/weewx/weewx/reportengine.py", line 409, in start
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>self.run()
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>  File "/usr/share/weewx/weewx/reportengine.py", line 560, in run
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>ncopy += weeutil.weeutil.deep_copy_path(path, html_dest_dir)
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>  File "/usr/share/weewx/weeutil/weeutil.py", line 1807, in deep_copy_path
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>os.makedirs(d, exist_ok=True)
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>  File "/usr/lib/python3.9/os.py", line 225, in makedirs
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:    
>mkdir(name, mode)
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:  
>  PermissionError: [Errno 13] Keine Berechtigung: '/var/www/html/weewx'
> Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.reportengine:  
>  Generator terminated
>
>
> the process 'weewxd' does not have permission to create the directory 
> /var/www/html/weewx
>
> assuming that weewxd is configured to run as the user 'weewx', you can fix 
> it like this:
>
> sudo mkdir /var/www/html/weewx
> sudo chown weewx /var/www/html/weewx
> sudo chgrp weewx /var/www/html/weewx
>
>

-- 
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/935a14e3-e19f-4605-b3ad-8ee3ca2268c0n%40googlegroups.com.

[weewx-user] weewx 5.02 crashes (and restarts) on trying to access a docker file?

2024-02-14 Thread valken...@gmail.com 
Since upgrading to weewx 5.02 on ubuntue 22.04, deb instaal. I had some 
issues becuase weewx does not run as root user anymore. Most of the were 
easy to solve. However on this ubuntu also a docker instance is running for 
another application. 
My syslog now tells me this:

INFO weewx.engine: Main loop exiting. Shutting engine down.
Feb 14 16:55:15 kwsweerstation weewxd[9005]: INFO weewx.engine: Shutting 
down StdReport thread
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__: Caught 
OSError: [Errno 13] Toegang geweigerd: 
'/var/lib/docker/overlay2/f40006ded3b1ca4e49c40cb408c89374b8b4a067f4de13711cf4be188137d355/merged'
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
 Traceback (most recent call last):
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
 File "/usr/share/weewx/weewx/engine.py", line 210, in run
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
   self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
 File "/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
   callback(event)
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
 File "/usr/share/weewx/weewx/engine.py", line 660, in check_loop
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
   raise BreakLoop
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
 weewx.engine.BreakLoop
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:   
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
 During handling of the above exception, another exception occurred:
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:   
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
 Traceback (most recent call last):
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
 File "/usr/share/weewx/weewx/engine.py", line 676, in post_loop
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
   self._catchup(self.engine.console.genArchiveRecords)
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
 File "/usr/share/weewx/weewx/engine.py", line 723, in _catchup
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
   for record in generator(lastgood_ts):
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
 File "/usr/share/weewx/weewx/drivers/__init__.py", line 31, in 
genArchiveRecords
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
   raise NotImplementedError("Method 'genArchiveRecords' not implemented")
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
 NotImplementedError: Method 'genArchiveRecords' not implemented
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:   
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
 During handling of the above exception, another exception occurred:
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:   
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:  
 Traceback (most recent call last):
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
 File "/usr/share/weewx/weewxd.py", line 166, in main
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
   engine.run()
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
 File "/usr/share/weewx/weewx/engine.py", line 217, in run
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
   self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
 File "/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
   callback(event)
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
 File "/usr/share/weewx/weewx/engine.py", line 678, in post_loop
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
   self._software_catchup()
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
 File "/usr/share/weewx/weewx/engine.py", line 741, in _software_catchup
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
   self.engine.dispatchEvent(weewx.Event(weewx.NEW_ARCHIVE_RECORD,
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
 File "/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
   callback(event)
Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:    
 File

[weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

2024-02-14 Thread Ton Karsten 
Thanks for sharing.
Which version are you using?
This: https://github.com/captain-coredump/weatherflow-udp
Or this one: https://github.com/rongrimes/weewx-tempest-pi

Op woensdag 14 februari 2024 om 16:26:59 UTC+1 schreef Tom Hogland:

> I'm currently using WeatherflowUDP with weewx 5.0.2 and it's working fine.
>
> On Wednesday, February 14, 2024 at 5:31:50 AM UTC-9 Ton Karsten wrote:
>
>> I use the WeatherFlow Tempest for my weather station.
>> I have equipped my weather station with the latest version of weewx.
>> Is the WeatherFlowUDP driver suitable for weewx 5.x and has this been 
>> tested?
>> I'm not sure if the installation will go without errors.
>
>

-- 
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/bc564400-4f01-4f66-8c3b-27b8ada2ea33n%40googlegroups.com.

[weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

2024-02-14 Thread Tom Hogland 
I'm currently using WeatherflowUDP with weewx 5.0.2 and it's working fine.

On Wednesday, February 14, 2024 at 5:31:50 AM UTC-9 Ton Karsten wrote:

> I use the WeatherFlow Tempest for my weather station.
> I have equipped my weather station with the latest version of weewx.
> Is the WeatherFlowUDP driver suitable for weewx 5.x and has this been 
> tested?
> I'm not sure if the installation will go without errors.

-- 
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/364fcf06-f945-4694-9ee4-c4b89b4242efn%40googlegroups.com.

[weewx-user] WeatherFlowUDP driver for Tempest Weatherstations

2024-02-14 Thread Ton Karsten 
I use the WeatherFlow Tempest for my weather station.
I have equipped my weather station with the latest version of weewx.
Is the WeatherFlowUDP driver suitable for weewx 5.x and has this been 
tested?
I'm not sure if the installation will go without errors.

-- 
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/49c9fa07-2482-4841-9d5b-36b3d2d089c8n%40googlegroups.com.

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

2024-02-14 Thread Pierre-Yves 
Wahoo Gary ! You are a genius ;-) Thanks a lot

I would never have searched the bug here. it works perfectly now.

Thanks to all you guys too, who patiently answered my posts

Pierre-Yves

Le mercredi 14 février 2024 à 10:30:40 UTC+1, gjr80 a écrit :

> WeeWX is being run just fine, the error is in the [SDR] stanza in 
> weewx.conf. As is often the case the clue is in the log:
>
> Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown process 
> sudo 
> /usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k -R 
> 173 - R 172 -R 42 -M utc -F json
>
> Almost certainly the command to run rtl_433 at the cmd setting includes 
> sudo. Remove the sudo and it should be fine.
>
> Gary
>
>

-- 
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/e30461d2-1e1c-4354-98c6-93ed89e0c59bn%40googlegroups.com.

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

2024-02-14 Thread gjr80 
WeeWX is being run just fine, the error is in the [SDR] stanza in weewx.conf. 
As is often the case the clue is in the log:

Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown process sudo 
/usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k -R 
173 - R 172 -R 42 -M utc -F json

Almost certainly the command to run rtl_433 at the cmd setting includes 
sudo. Remove the sudo and it should be fine.

Gary

-- 
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/a74a0a3a-30f3-4cea-9b00-262ae4956121n%40googlegroups.com.

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

2024-02-14 Thread Pierre-Yves 
Just an idea...

Could the problem come from the fact I installed rtl-sdr and rtl_433 prior 
to install weewx 5.0.2 ?

PY

Le mercredi 14 février 2024 à 10:02:54 UTC+1, Pierre-Yves a écrit :

> hello Dominic,
>
> Thanks for feedback.
>
> Unfortunately, I don't see any "sudo" in the file 
> "/lib/systemd/system/weewx.service". See below:
>
> # systemd service configuration file for WeeWX
>
> [Unit]
> Description=WeeWX
> Documentation=https://weewx.com/docs
> Requires=time-sync.target
> After=time-sync.target
> Wants=network-online.target
> After=network-online.target
>
> [Service]
> ExecStart=weewxd /etc/weewx/weewx.conf
> StandardOutput=null
> StandardError=journal+console
> RuntimeDirectory=weewx
> RuntimeDirectoryMode=775
> User=weewx
> Group=weewx
>
> [Install]
> WantedBy=multi-user.target
>
> Pierre-Yves
>
> Le mercredi 14 février 2024 à 09:33:15 UTC+1, Dominic Reich a écrit :
>
>> Hello, i replied inline. 
>>
>> Pierre-Yves  wrote: 
>>
>> >Thanks Vince 
>> > 
>> >I found in rtl-sdr. rules a rule corresponding to my SDR stick : 
>> > 
>> >SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", 
>> ENV 
>> >{ID_SOFTWARE_RADIO}="1", MODE="0660", GROUP="plugdev" 
>> > 
>> >I added the weewx user to that group: "sudo usermod -aG plugdev weewx" 
>> > 
>> >I still can start weewx with the  "sudo weewd" command as before but I 
>> can't 
>> >run weewx in daemon mode. "sudo  systemctl start weewx" gives still the 
>> same 
>> >error : 
>> > 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Starting 
>> main 
>> >packet loop. 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: Nous espérons 
>> que 
>> >vous avez reçu de votre administrateur système local 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: les consignes 
>> >traditionnelles. Généralement, elles se concentrent sur ces trois 
>> éléments : 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #1) 
>> Respectez la 
>> >vie privée des autres. 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #2) 
>> Réfléchissez 
>> >avant d'utiliser le clavier. 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #3) De 
>> grands 
>> >pouvoirs confèrent de grandes responsabilités. 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: un 
>> terminal est 
>> >requis pour lire le mot de passe; utilisez soit l'option -S pour lire 
>> depuis 
>> >l'entrée standard ou configurez un outil askpass de demande de mot de 
>> passe 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: il est 
>> >nécessaire de saisir un mot de passe 
>>
>> I don't speak french, but it looks like you still have a sudo command 
>> somewhere in your unit file. 
>>
>> Would you please show us the contents of your running unit file 
>>
>> systemctl show -P FragmentPath weewx.service 
>>
>> will get you the path of that file. cat that file and paste it here or 
>> if you are confident remove the sudo statement in there somwhere at 
>> ExecStart...="sudo /usr.." 
>>
>> because you should not need sudo when you added weewx to the plugdev 
>> group. 
>>
>> That file contains usually also the information what user runs the 
>> daemon in the end. 
>>
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Main loop 
>> exiting. 
>> >Shutting engine down. 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown 
>> process sudo 
>> >/usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k 
>> -R 173 
>> >-R 172 -R 42 -M utc -F json 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stdout 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stderr 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread 
>> stdout-thread: 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown 
>> >stdout-thread 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call 
>> last): 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread 
>> stderr-thread: 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call 
>> last): 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/usr/lib/python3.9/ 
>> >threading.py", line 954, in _bootstrap_inner 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/usr/lib/python3.9/ 
>> >threading.py", line 954, in _bootstrap_inner 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: self.run() 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
>> "/etc/weewx/bin/user/sdr.py", 
>> >line 198, in run 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: self.run() 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
>> "/etc/weewx/bin/user/sdr.py", 
>> >line 198, in run 
>> >Feb 14 08:49:54 raspberrypi weewxd[5905]: for line in

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

2024-02-14 Thread Pierre-Yves 
hello Dominic,

Thanks for feedback.

Unfortunately, I don't see any "sudo" in the file 
"/lib/systemd/system/weewx.service". See below:

# systemd service configuration file for WeeWX

[Unit]
Description=WeeWX
Documentation=https://weewx.com/docs
Requires=time-sync.target
After=time-sync.target
Wants=network-online.target
After=network-online.target

[Service]
ExecStart=weewxd /etc/weewx/weewx.conf
StandardOutput=null
StandardError=journal+console
RuntimeDirectory=weewx
RuntimeDirectoryMode=775
User=weewx
Group=weewx

[Install]
WantedBy=multi-user.target

Pierre-Yves

Le mercredi 14 février 2024 à 09:33:15 UTC+1, Dominic Reich a écrit :

> Hello, i replied inline.
>
> Pierre-Yves  wrote:
>
> >Thanks Vince
> >
> >I found in rtl-sdr. rules a rule corresponding to my SDR stick :
> >
> >SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", ENV
> >{ID_SOFTWARE_RADIO}="1", MODE="0660", GROUP="plugdev"
> >
> >I added the weewx user to that group: "sudo usermod -aG plugdev weewx"
> >
> >I still can start weewx with the  "sudo weewd" command as before but I 
> can't
> >run weewx in daemon mode. "sudo  systemctl start weewx" gives still the 
> same
> >error :
> >
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Starting main
> >packet loop.
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: Nous espérons 
> que
> >vous avez reçu de votre administrateur système local
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: les consignes
> >traditionnelles. Généralement, elles se concentrent sur ces trois 
> éléments :
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #1) 
> Respectez la
> >vie privée des autres.
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #2) 
> Réfléchissez
> >avant d'utiliser le clavier.
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #3) De 
> grands
> >pouvoirs confèrent de grandes responsabilités.
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: un 
> terminal est
> >requis pour lire le mot de passe; utilisez soit l'option -S pour lire 
> depuis
> >l'entrée standard ou configurez un outil askpass de demande de mot de 
> passe
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: il est
> >nécessaire de saisir un mot de passe
>
> I don't speak french, but it looks like you still have a sudo command
> somewhere in your unit file.
>
> Would you please show us the contents of your running unit file
>
> systemctl show -P FragmentPath weewx.service
>
> will get you the path of that file. cat that file and paste it here or
> if you are confident remove the sudo statement in there somwhere at
> ExecStart...="sudo /usr.."
>
> because you should not need sudo when you added weewx to the plugdev
> group.
>
> That file contains usually also the information what user runs the
> daemon in the end.
>
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Main loop 
> exiting.
> >Shutting engine down.
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown process 
> sudo
> >/usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k 
> -R 173
> >-R 172 -R 42 -M utc -F json
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stdout
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stderr
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread 
> stdout-thread:
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown
> >stdout-thread
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call 
> last):
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread 
> stderr-thread:
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call 
> last):
> >Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/usr/lib/python3.9/
> >threading.py", line 954, in _bootstrap_inner
> >Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/usr/lib/python3.9/
> >threading.py", line 954, in _bootstrap_inner
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: self.run()
> >Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
> "/etc/weewx/bin/user/sdr.py",
> >line 198, in run
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: self.run()
> >Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
> "/etc/weewx/bin/user/sdr.py",
> >line 198, in run
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: for line in iter
> >(self._fd.readline, ''):
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ValueError: 
> PyMemoryView_FromBuffer
> >(): info->buf must not be NULL
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown
> >stderr-thread
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: for line in iter
> >(self._fd.readline, ''):
> >Feb 14 08:49:54 raspberrypi weewxd[5905]: ValueError: 
> PyMemoryView_FromBuffer
> >():

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

2024-02-14 Thread Dominic Reich 

Hello, i replied inline.

Pierre-Yves  wrote:


Thanks Vince

I found in rtl-sdr. rules a rule corresponding to my SDR stick :

SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", ENV
{ID_SOFTWARE_RADIO}="1", MODE="0660", GROUP="plugdev"

I added the weewx user to that group: "sudo usermod -aG plugdev weewx"

I still can start weewx with the  "sudo weewd" command as before but I can't
run weewx in daemon mode. "sudo  systemctl start weewx" gives still the same
error :

Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Starting main
packet loop.
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: Nous espérons que
vous avez reçu de votre administrateur système local
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: les consignes
traditionnelles. Généralement, elles se concentrent sur ces trois éléments :
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:     #1) Respectez la
vie privée des autres.
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:     #2) Réfléchissez
avant d'utiliser le clavier.
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:     #3) De grands
pouvoirs confèrent de grandes responsabilités.
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr:
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: un terminal est
requis pour lire le mot de passe; utilisez soit l'option -S pour lire depuis
l'entrée standard ou configurez un outil askpass de demande de mot de passe
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: il est
nécessaire de saisir un mot de passe


I don't speak french, but it looks like you still have a sudo command
somewhere in your unit file.

Would you please show us the contents of your running unit file

systemctl show -P FragmentPath weewx.service

will get you the path of that file. cat that file and paste it here or
if you are confident remove the sudo statement in there somwhere at
ExecStart...="sudo /usr.."

because you should not need sudo when you added weewx to the plugdev
group.

That file contains usually also the information what user runs the
daemon in the end.


Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Main loop exiting.
Shutting engine down.
Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown process sudo
/usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k -R 173
-R 172 -R 42 -M utc -F json
Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stdout
Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stderr
Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread stdout-thread:
Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown
stdout-thread
Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call last):
Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread stderr-thread:
Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call last):
Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/usr/lib/python3.9/
threading.py", line 954, in _bootstrap_inner
Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/usr/lib/python3.9/
threading.py", line 954, in _bootstrap_inner
Feb 14 08:49:54 raspberrypi weewxd[5905]:     self.run()
Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/etc/weewx/bin/user/sdr.py",
line 198, in run
Feb 14 08:49:54 raspberrypi weewxd[5905]:     self.run()
Feb 14 08:49:54 raspberrypi weewxd[5905]:   File "/etc/weewx/bin/user/sdr.py",
line 198, in run
Feb 14 08:49:54 raspberrypi weewxd[5905]:     for line in iter
(self._fd.readline, ''):
Feb 14 08:49:54 raspberrypi weewxd[5905]: ValueError: PyMemoryView_FromBuffer
(): info->buf must not be NULL
Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown
stderr-thread
Feb 14 08:49:54 raspberrypi weewxd[5905]:     for line in iter
(self._fd.readline, ''):
Feb 14 08:49:54 raspberrypi weewxd[5905]: ValueError: PyMemoryView_FromBuffer
(): info->buf must not be NULL
Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown complete
Feb 14 08:49:54 raspberrypi weewxd[5905]: CRITICAL __main__: Caught
WeeWxIOError: rtl_433 process is not running
Feb 14 08:49:54 raspberrypi weewxd[5905]: CRITICAL __main__:       Waiting
60.0 seconds then retrying...
Feb 14 08:50:03 raspberrypi weewxd[5905]: INFO __main__: Received signal TERM
(15).
Feb 14 08:50:03 raspberrypi systemd[1]: Stopping WeeWX...
Feb 14 08:50:03 raspberrypi weewxd[5905]: Traceback (most recent call last):
Feb 14 08:50:03 raspberrypi weewxd[5905]:   File "/usr/share/weewx/weewxd.py",
line 166, in main
Feb 14 08:50:03 raspberrypi weewxd[5905]:     engine.run()
Feb 14 08:50:03 raspberrypi weewxd[5905]:   File "/usr/share/weewx/weewx/
engine.py", line 204, in run
Feb 14 08:50:03 raspberrypi weewxd[5905]:     for packet in
self.console.genLoopPackets():
Feb 14 08:50:03 raspberrypi weewxd[5905]:  

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

2024-02-14 Thread Pierre-Yves 
To complete the post above, I tested the command : "sudo systemctl restart 
udev weewx"

ps aux|grep weewxd issues now:

pi@raspberrypi:~ $ ps aux|grep weewxd
weewx11862  7.0  0.9  46012 18772 ?Ss   09:26   0:00 python3 
/usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
pi   11883  0.0  0.0   7460   572 pts/3S+   09:26   0:00 grep 
--color=auto weewxd

But weewx still fails to start with the same error...

Le mercredi 14 février 2024 à 09:13:48 UTC+1, Pierre-Yves a écrit :

> Thanks Vince
>
> I found in rtl-sdr. rules a rule corresponding to my SDR stick : 
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="*0bda*", ATTRS{idProduct}=="*2838*", 
> ENV{ID_SOFTWARE_RADIO}="1", MODE="0660", GROUP="*plugdev*"
>
> I added the weewx user to that group: "sudo usermod -aG plugdev weewx"
>
> I still can start weewx with the  "sudo weewd" command as before but I 
> can't run weewx in daemon mode. "sudo  systemctl start weewx" gives still 
> the same error :
>
> Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Starting main 
> packet loop.
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: Nous espérons 
> que vous avez reçu de votre administrateur système local
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: les consignes 
> traditionnelles. Généralement, elles se concentrent sur ces trois éléments :
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #1) 
> Respectez la vie privée des autres.
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #2) 
> Réfléchissez avant d'utiliser le clavier.
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #3) De 
> grands pouvoirs confèrent de grandes responsabilités.
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: un 
> terminal est requis pour lire le mot de passe; utilisez soit l'option -S 
> pour lire depuis l'entrée standard ou configurez un outil askpass de 
> demande de mot de passe
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: il est 
> nécessaire de saisir un mot de passe
> Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Main loop 
> exiting. Shutting engine down.
> Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown process 
> sudo /usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 
> 1024k -R 173 -R 172 -R 42 -M utc -F json
> Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stdout
> Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stderr
> Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread 
> stdout-thread:
> Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown 
> stdout-thread
> Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call 
> last):
> Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread 
> stderr-thread:
> Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call 
> last):
> Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
> "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
> Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
> "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
> Feb 14 08:49:54 raspberrypi weewxd[5905]: self.run()
> Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
> "/etc/weewx/bin/user/sdr.py", line 198, in run
> Feb 14 08:49:54 raspberrypi weewxd[5905]: self.run()
> Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
> "/etc/weewx/bin/user/sdr.py", line 198, in run
> Feb 14 08:49:54 raspberrypi weewxd[5905]: for line in 
> iter(self._fd.readline, ''):
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ValueError: 
> PyMemoryView_FromBuffer(): info->buf must not be NULL
> Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown 
> stderr-thread
> Feb 14 08:49:54 raspberrypi weewxd[5905]: for line in 
> iter(self._fd.readline, ''):
> Feb 14 08:49:54 raspberrypi weewxd[5905]: ValueError: 
> PyMemoryView_FromBuffer(): info->buf must not be NULL
> Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown complete
> Feb 14 08:49:54 raspberrypi weewxd[5905]: CRITICAL __main__: *Caught 
> WeeWxIOError: rtl_433 process is not running*
> Feb 14 08:49:54 raspberrypi weewxd[5905]: CRITICAL __main__:  
>  Waiting 60.0 seconds then retrying...
> Feb 14 08:50:03 raspberrypi weewxd[5905]: INFO __main__: Received signal 
> TERM (15).
> Feb 14 08:50:03 raspberrypi systemd[1]: Stopping WeeWX...
> Feb 14 08:50:03 raspberrypi weewxd[5905]: Traceback (most recent call 
> last):
> Feb 14 08:50:03 raspberrypi weewxd[5905]:   File 
> "/usr/share/weewx/weewxd.py", line 166, in main
> Feb 14 08:50:03 raspberrypi weewxd[5905]: engine.run()
> Feb 14 08:50:03 raspberrypi weewxd[5905]:   File 
> "/usr/share/weewx/weewx/engine.py", line 204, in run
> Feb 14 08:50:03 raspberrypi

Re: [weewx-user] unable to save to file '/var/www/html/weewx/...

2024-02-14 Thread Pierre-Yves 
Thanks Vince

I found in rtl-sdr. rules a rule corresponding to my SDR stick : 

SUBSYSTEMS=="usb", ATTRS{idVendor}=="*0bda*", ATTRS{idProduct}=="*2838*", 
ENV{ID_SOFTWARE_RADIO}="1", MODE="0660", GROUP="*plugdev*"

I added the weewx user to that group: "sudo usermod -aG plugdev weewx"

I still can start weewx with the  "sudo weewd" command as before but I 
can't run weewx in daemon mode. "sudo  systemctl start weewx" gives still 
the same error :

Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Starting main 
packet loop.
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: Nous espérons que 
vous avez reçu de votre administrateur système local
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: les consignes 
traditionnelles. Généralement, elles se concentrent sur ces trois éléments :
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #1) Respectez 
la vie privée des autres.
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #2) 
Réfléchissez avant d'utiliser le clavier.
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: #3) De grands 
pouvoirs confèrent de grandes responsabilités.
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: 
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: un terminal 
est requis pour lire le mot de passe; utilisez soit l'option -S pour lire 
depuis l'entrée standard ou configurez un outil askpass de demande de mot 
de passe
Feb 14 08:49:54 raspberrypi weewxd[5905]: ERROR user.sdr: sudo: il est 
nécessaire de saisir un mot de passe
Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO weewx.engine: Main loop 
exiting. Shutting engine down.
Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown process 
sudo /usr/local/bin/rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 
1024k -R 173 -R 172 -R 42 -M utc -F json
Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stdout
Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: close stderr
Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread stdout-thread:
Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown 
stdout-thread
Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call last):
Feb 14 08:49:54 raspberrypi weewxd[5905]: Exception in thread stderr-thread:
Feb 14 08:49:54 raspberrypi weewxd[5905]: Traceback (most recent call last):
Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
"/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
"/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
Feb 14 08:49:54 raspberrypi weewxd[5905]: self.run()
Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
"/etc/weewx/bin/user/sdr.py", line 198, in run
Feb 14 08:49:54 raspberrypi weewxd[5905]: self.run()
Feb 14 08:49:54 raspberrypi weewxd[5905]:   File 
"/etc/weewx/bin/user/sdr.py", line 198, in run
Feb 14 08:49:54 raspberrypi weewxd[5905]: for line in 
iter(self._fd.readline, ''):
Feb 14 08:49:54 raspberrypi weewxd[5905]: ValueError: 
PyMemoryView_FromBuffer(): info->buf must not be NULL
Feb 14 08:49:54 raspberrypi weewxd[5905]: DEBUG user.sdr: shutdown 
stderr-thread
Feb 14 08:49:54 raspberrypi weewxd[5905]: for line in 
iter(self._fd.readline, ''):
Feb 14 08:49:54 raspberrypi weewxd[5905]: ValueError: 
PyMemoryView_FromBuffer(): info->buf must not be NULL
Feb 14 08:49:54 raspberrypi weewxd[5905]: INFO user.sdr: shutdown complete
Feb 14 08:49:54 raspberrypi weewxd[5905]: CRITICAL __main__: *Caught 
WeeWxIOError: rtl_433 process is not running*
Feb 14 08:49:54 raspberrypi weewxd[5905]: CRITICAL __main__:  
 Waiting 60.0 seconds then retrying...
Feb 14 08:50:03 raspberrypi weewxd[5905]: INFO __main__: Received signal 
TERM (15).
Feb 14 08:50:03 raspberrypi systemd[1]: Stopping WeeWX...
Feb 14 08:50:03 raspberrypi weewxd[5905]: Traceback (most recent call last):
Feb 14 08:50:03 raspberrypi weewxd[5905]:   File 
"/usr/share/weewx/weewxd.py", line 166, in main
Feb 14 08:50:03 raspberrypi weewxd[5905]: engine.run()
Feb 14 08:50:03 raspberrypi weewxd[5905]:   File 
"/usr/share/weewx/weewx/engine.py", line 204, in run
Feb 14 08:50:03 raspberrypi weewxd[5905]: for packet in 
self.console.genLoopPackets():
Feb 14 08:50:03 raspberrypi weewxd[5905]:   File 
"/etc/weewx/bin/user/sdr.py", line 3316, in genLoopPackets
Feb 14 08:50:03 raspberrypi weewxd[5905]: raise 
weewx.WeeWxIOError("rtl_433 process is not running")
Feb 14 08:50:03 raspberrypi weewxd[5905]: weewx.WeeWxIOError: rtl_433 
process is not running
Feb 14 08:50:03 raspberrypi weewxd[5905]: During handling of the above 
exception, another exception occurred:
Feb 14 08:50:03 raspberrypi weewxd[5905]: Traceback (most recent call last):
Feb 14 08:50:03 raspberrypi weewxd[5905]:   File 
"/usr/share/weewx/weewxd.py", line 265, in 
Feb 14 08:50:03