Re: [weewx-user] Re: Upgrade to 5.0.x does not start
The third time I tried the Apt configuration, it found weewx. The installation worked so far except for the dpkg: Warnung: Altes Verzeichnis. Unfortunately, weewx did not react after that and a reboot did not work anymore. Now I have to restore the backup and try again. What went wrong? pi@Wetter-Raspi4:~ $ sudo apt install -y wget gnupg wget -qO - https://weewx.com/keys.html | \ sudo gpg --dearmor --output /etc/apt/trusted.gpg.d/weewx.gpg Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig gnupg ist schon die neueste Version (2.2.27-2+deb11u2). wget ist schon die neueste Version (1.21-1+deb11u1). 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. Datei '/etc/apt/trusted.gpg.d/weewx.gpg' existiert bereits. Überschreiben (j/N)? j pi@Wetter-Raspi4:~ $ echo "deb [arch=all] https://weewx.com/apt/python3 buster main" | \ sudo tee /etc/apt/sources.list.d/weewx.list deb [arch=all] https://weewx.com/apt/python3 buster main pi@Wetter-Raspi4:~ $ sudo apt update OK:1 http://deb.debian.org/debian bullseye InRelease Holen:2 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB] OK:3 http://security.debian.org/debian-security bullseye-security InRelease Holen:4 http://archive.raspberrypi.org/debian bullseye InRelease [23.6 kB] Holen:5 https://weewx.com/apt/python3 buster InRelease [4’252 B] Holen:6 http://archive.raspberrypi.org/debian bullseye/main armhf Packages [313 kB] Holen:7 http://archive.raspberrypi.org/debian bullseye/main arm64 Packages [307 kB] Holen:8 https://weewx.com/apt/python3 buster/main all Packages [4’988 B] Es wurden 697 kB in 2 s geholt (315 kB/s). Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Aktualisierung für 1 Paket verfügbar. Führen Sie »apt list --upgradable« aus, um es anzuzeigen. pi@Wetter-Raspi4:~ $ sudo apt install weewx Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Vorgeschlagene Pakete: sqlite ftp httpd Die folgenden Pakete werden aktualisiert (Upgrade): weewx 1 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. Es müssen 1’556 kB an Archiven heruntergeladen werden. Nach dieser Operation werden 428 kB Plattenplatz freigegeben. Holen:1 https://weewx.com/apt/python3 buster/main all weewx all 5.0.2-1 [1’556 kB] Es wurden 1’556 kB in 13 s geholt (121 kB/s). Changelogs werden gelesen... Fertig Vorkonfiguration der Pakete ... (Lese Datenbank ... 99087 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../archives/weewx_5.0.2-1_all.deb ... Entpacken von weewx (5.0.2-1) über (4.10.2-1) ... dpkg: Warnung: Altes Verzeichnis »/usr/share/weewx/user« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/udev/rules.d« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Standard/smartphone/icons« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Standard/smartphone« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Standard/lang« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Standard/backgrounds« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Standard/RSS« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Standard/NOAA« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Standard« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Smartphone/lang« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Smartphone/icons« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Smartphone« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Seasons/lang« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Seasons/font« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Seasons/NOAA« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Seasons« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Rsync«
[weewx-user] Weewx Upgrade to 5.0.1 successful but.... sensor values
Hi folks, Like others, I ran into a few issues upgrading to 5.0.1, which I've mostly sorted, and it's up and running now as before - except - using my rtl_433 (matt wall) integration is leading to interesting sensor values. My temperatures are wrong/seemingly random and I have no idea why. Everything seems to be in order - but it's been a LONG time since I've run into issues that I almost forget how to address this. SDR mapping is maintained in my weewx conf. file, my skin is active/working - weewx is not presenting any errors, just the values in the sensors are seemingly made up (+20 degrees above actual temp yesterday, now situated about 9 degrees below the actual outdoor temperature. The sensors are updating, the values are fluctuating - but the values are just wrong. I did not add any conversions/changes to the weewx conf file, this happened spontaneously post-update. Help! -- 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/02379f3d-e066-49dc-aded-d64f90f71a17n%40googlegroups.com.
[weewx-user] Re: Weewx Upgrade to 5.0.1 successful but.... sensor values
Details: Acurite 5-in-1 sensor, RTL_433 to MQTT (matt wall) + Weewx. Weewx conf sensors: [SDR] # This section is for the software-defined radio driver. # The driver to use driver = user.sdr path = /usr/local/bin log_unknown_sensors = True log_unmapped_sensors = True [[sensor_map]] extraTemp1 = temperature.1720.AcuriteTowerPacketV2# basement extraHumid1 = humidity.1720.AcuriteTowerPacketV2 outTemp = temperature.041D.Acurite5n1PacketV2 outHumidity = humidity.041D.Acurite5n1PacketV2 rain_total = rain_total.041D.Acurite5n1PacketV2 windDir = wind_dir.041D.Acurite5n1PacketV2 windSpeed = wind_speed.041D.Acurite5n1PacketV2 inHumidity = humidity.009B.AcuriteLightningPacket#upstairs Humidity inTemp = temperature.009B.AcuriteLightningPacket#upstairs Temperature strikes_total = strikes_total.009B.AcuriteLightningPacket#Total Lightning Strike Count lightning_distance = distance.009B.AcuriteLightningPacket#Storm Distance KM Example: outTemp=32 (in the RTL data) - I have it converted to Celsius, but the problem is *it's not 32F outside, it's actually 15.8F,* which is registered on my other non-connected temperature sensors, so the RTL reading is 15 degrees off where it should be reading post 5.0.1 upgrade. No idea how to start picking this apart to find the root cause in V5. Thanks! On Tuesday, February 13, 2024 at 8:34:53 AM UTC-4 Kingsclear Studios wrote: > Hi folks, > > Like others, I ran into a few issues upgrading to 5.0.1, which I've mostly > sorted, and it's up and running now as before - except - using my rtl_433 > (matt wall) integration is leading to interesting sensor values. My > temperatures are wrong/seemingly random and I have no idea why. Everything > seems to be in order - but it's been a LONG time since I've run into issues > that I almost forget how to address this. > > SDR mapping is maintained in my weewx conf. file, my skin is > active/working - weewx is not presenting any errors, just the values in the > sensors are seemingly made up (+20 degrees above actual temp yesterday, now > situated about 9 degrees below the actual outdoor temperature. > > The sensors are updating, the values are fluctuating - but the values are > just wrong. > > I did not add any conversions/changes to the weewx conf file, this > happened spontaneously post-update. > > Help! > -- 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/e6ae2456-6a9c-40af-b804-518aacdd053en%40googlegroups.com.
Re: [weewx-user] Re: Weewx upgrade questions
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" 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/04fdf7c2-1958-4862-9e8d-85f4219e821cn%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
htt
Re: [weewx-user] Re: Upgrade to 5.0.x does not start
On Tuesday, February 13, 2024 at 4:13:27 AM UTC-5 geni08...@gmail.com wrote: The third time I tried the Apt configuration, it found weewx. The installation worked so far except for the dpkg: Warnung: Altes Verzeichnis. Unfortunately, weewx did not react after that and a reboot did not work anymore. Now I have to restore the backup and try again. What went wrong? it looks like nothing is wrong with the upgrade. if weewx is not running, we must see the log messages from weewx. these will be in the system log (different from the installer log). this should give some hint about what is happening: sudo systermctl status weewx this wiki article has more information about logging: https://github.com/weewx/weewx/wiki/view-logs#journalctl -- 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/05790545-0f6e-4234-aac8-f3fd004ba077n%40googlegroups.com.
[weewx-user] Re: Weewx Upgrade to 5.0.1 successful but.... sensor values
On Tuesday, February 13, 2024 at 7:42:35 AM UTC-5 Kingsclear Studios wrote: No idea how to start picking this apart to find the root cause in V5. i would be surprised if something in v5 is the root cause, but who knows? did you update rtl-sdr? did you update rtl_433? did you update weewx-sdr? did you update weewx-mqtt? to find the root cause, take one piece at a time. start by running rtl_433 directly. look a the values there and see if they match what you see on the hardware/reality. then run weewx-sdr directly. see what the values look like there. then run weewxd directly, and check the values in the LOOP output. finally, run weewxd directly and look at the values coming out of mqtt. m -- 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/1635fc86-a5ef-4cef-b7cf-1b08207cc63cn%40googlegroups.com.
[weewx-user] Re: Weewx Upgrade to 5.0.1 successful but.... sensor values
re: did you update rtl-sdr? did you update rtl_433? did you update weewx-sdr? did you update weewx-mqtt? Do you have suggestions on how to execute that properly - can do the research if needed, just curious if there's a quick way to accomplish that properly without impacting V5 On Tuesday, February 13, 2024 at 9:40:11 AM UTC-4 matthew wall wrote: > On Tuesday, February 13, 2024 at 7:42:35 AM UTC-5 Kingsclear Studios wrote: > > No idea how to start picking this apart to find the root cause in V5. > > > i would be surprised if something in v5 is the root cause, but who knows? > > did you update rtl-sdr? > did you update rtl_433? > did you update weewx-sdr? > did you update weewx-mqtt? > > to find the root cause, take one piece at a time. > > start by running rtl_433 directly. look a the values there and see if > they match what you see on the hardware/reality. > > then run weewx-sdr directly. see what the values look like there. > > then run weewxd directly, and check the values in the LOOP output. > > finally, run weewxd directly and look at the values coming out of mqtt. > > m > -- 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/ba3a1ea5-93df-4a58-8a3a-736b1910529fn%40googlegroups.com.
[weewx-user] Re: Install error
Matthew, It worked! Thank you so much, and thanks to Werner as well. Follow-up question: I am looking into getting one of those Misol stations that have RS-485 connections. I prefer hardwired solutions instead of wifi. Would you recommend that, or should I look for something else? My ideal solution would be a POE station, but I wasn't able to find any that are affordable. A Czech company apparently has one - but I haven't seen any reviews. Please advise. On Sunday, February 11, 2024 at 12:10:42 PM UTC-8 matthew wall wrote: > On Sunday, February 11, 2024 at 1:32:19 PM UTC-5 dusan.ta...@gmail.com > wrote: > > usage: weectl.py -v|--version >weectl.py -h|--help >weectl.py database --help >weectl.py debug --help >weectl.py device --help >weectl.py extension --help >weectl.py import --help >weectl.py report --help >weectl.py station --help > weectl.py: error: unrecognized arguments: meters,foot > dpkg: error processing package weewx (--configure): > installed weewx package post-installation script subprocess returned > error exit > status 2 > Errors were encountered while processing: > weewx > > > it looks like you have a bogus value for the units in your station > altitude. apparently you entered 'meters,foot' instead of just 'meter' or > 'foot'. this is in the debconf database. > > you can verify this by looking at the values in /var/cache/debconf > > you can purge the values for weewx by doing this: > > echo PURGE | sudo debconf-communicate weewx > > then do 'apt install weewx' again, and be sure to enter the correct units > for altitude. > > m > -- 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/b2c0e461-338c-47bf-a02c-2b1c4aa0ab30n%40googlegroups.com.
[weewx-user] Re: Weewx Upgrade to 5.0.1 successful but.... sensor values
On Tuesday, February 13, 2024 at 8:41:31 AM UTC-5 Kingsclear Studios wrote: re: did you update rtl-sdr? did you update rtl_433? did you update weewx-sdr? did you update weewx-mqtt? Do you have suggestions on how to execute that properly - can do the research if needed, just curious if there's a quick way to accomplish that properly without impacting V5 you should not have to update any of these items. i ask only to help figure out why values/behavior are different now than before. -- 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/a9db660e-3740-4fc6-88b1-81ea180091b0n%40googlegroups.com.
Re: [weewx-user] unable to save to file '/var/www/html/weewx/...
Hi Matthew As said I made e new installation (Raspi4, bullseye) now version 5.0.2-1 according installation guide. Weewx installs: Entpacken von weewx (5.0.2-1) ... weewx (5.0.2-1) wird eingerichtet ... Using weewx:weewx as user:group Creating /etc/default/weewx Using configuration file /etc/weewx/weewx.conf Processing configuration file /etc/weewx/weewx.conf Setting record_generation to software. Saving configuration file /etc/weewx/weewx.conf Adding system group weewx...done Adding system user weewx...done Adding user wag to group weewx Installing systemd units Installing udev rules Creating skins directory /etc/weewx/skins Creating user extension directory /etc/weewx/bin/user Configuring database directory /var/lib/weewx Configuring reporting directory /var/www/html/weewx Setting permissions weewx:weewx on /etc/weewx Enabling startup using systemd Created symlink /etc/systemd/system/multi-user.target.wants/weewx.service → /lib/systemd/system/weewx.service. Starting weewxd using systemd Next step: weewx takes stored records from the weatherstation and write to database. That worked. After this the same result: 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 Next step: Gave permission acc. wiki, and restarted with "sudo systemctl start weewx". No effect --- next step: ps aux|grep weewxd: weewx 4425 10.3 0.8 61488 33168 ?Ssl 12:30 2:22 python3 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf wag 5411 0.0 0.0 7372 556 pts/0S+ 12:53 0:00 grep --color=auto weewxd content as per your request content of /etc/default/weewx: WEEWX_PYTHON=python3 WEEWX_BINDIR=/usr/share/weew -
Re: [weewx-user] unable to save to file '/var/www/html/weewx/...
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/6b55fae4-553c-453d-b03b-c5dcbd3f7ecbn%40googlegroups.com.
Re: [weewx-user] Re: Weewx Upgrade to 5.0.1 successful but.... sensor values
I did not update those. Just a standard update to weewx v5___"Sent from my mobile device"On Feb 13, 2024, at 9:54 AM, matthew wall wrote:On Tuesday, February 13, 2024 at 8:41:31 AM UTC-5 Kingsclear Studios wrote:re: did you update rtl-sdr?did you update rtl_433?did you update weewx-sdr?did you update weewx-mqtt? Do you have suggestions on how to execute that properly - can do the research if needed, just curious if there's a quick way to accomplish that properly without impacting V5you should not have to update any of these items. i ask only to help figure out why values/behavior are different now than before. -- 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/wPXgRxzC31U/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/a9db660e-3740-4fc6-88b1-81ea180091b0n%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/7A649E99-91BB-4FED-8DC6-CC1E72AD82E3%40gmail.com.
Re: [weewx-user] unable to save to file '/var/www/html/weewx/...
Hello, I experience very similar behavior to that described above. Recently, I failed to upgrade my Weewx 4.10 to Weewx 5.0.x. I reverted "temporarily" to 4.10 and decided to make a fresh install on a spare set Pi4 + SDR stick. I installed RTL_433 and sdr-rtl following the https://github.com/weewx/weewx/wiki/sdr-rpi-recipe tutorial. I then installed weewx 5.0.3 and the sdr driver I finally replaced the weewx.conf by the one coming from my 4.10 setup. I tried several commands : - rtl_433 -> ok - rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k -R 173 -R 172 -R 42 -M utc -F json -> ok - sudo PYTHONPATH=/usr/share/weewx python3 /etc/weewx/bin/user/sdr.py --cmd="rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k -R 173 -R 172 -R 42 -M utc -F json" -> ok But "weewxd" fails : problem of permission error (see "weewxd log") And "sudo systemctl start weewx" fails too (see "sudo systemctl start weewx log") Finally I tried "sudo weewd" that works and writes data to /var/www/html/weewx ... ps aux|grep weewxd gives : pi@raspberrypi:~ $ ps aux|grep weewxd pi 31049 0.0 0.0 7460 548 pts/1S+ 19:23 0:00 grep --color=auto weewxd It seems that weewx user doesn't exist ! ls -la /var/www/html/weewx gives : pi@raspberrypi:~ $ ls -la /var/www/html/weewx total 824 drwxrwsrwx 4 weewx weewx 4096 13 févr. 19:20 . drwxr-xr-x 3 root root 4096 13 févr. 14:57 .. -rw-r--r-- 1 root weewx 5628 13 févr. 19:20 celestial.html -rw-r--r-- 1 weewx weewx 10018 13 févr. 19:20 daybarometer.png -rw-r--r-- 1 weewx weewx 7875 13 févr. 19:20 dayET.png -rw-r--r-- 1 weewx weewx 8068 13 févr. 19:20 dayhumext.png -rw-r--r-- 1 weewx weewx 7226 13 févr. 19:20 dayhumin.png -rw-r--r-- 1 weewx weewx 8086 13 févr. 19:20 dayhum.png -rw-r--r-- 1 weewx weewx 6884 13 févr. 09:21 daylightning.png -rw-r--r-- 1 weewx weewx 8608 13 févr. 19:20 dayradiation.png -rw-r--r-- 1 weewx weewx 7004 13 févr. 19:20 dayrain.png -rw-r--r-- 1 weewx weewx 6490 13 févr. 19:20 dayrx.png -rw-r--r-- 1 weewx weewx 9330 13 févr. 19:20 daytempdew.png -rw-r--r-- 1 weewx weewx 8071 13 févr. 19:20 daytempext.png -rw-r--r-- 1 weewx weewx 8923 13 févr. 19:20 daytempfeel.png -rw-r--r-- 1 weewx weewx 8125 13 févr. 19:20 daytempin.png -rw-r--r-- 1 weewx weewx 6225 13 févr. 19:20 dayUV.png -rw-r--r-- 1 weewx weewx 11508 13 févr. 19:20 dayvolt.png -rw-r--r-- 1 weewx weewx 8087 13 févr. 19:20 daywinddir.png -rw-r--r-- 1 weewx weewx 9878 13 févr. 19:20 daywind.png -rw-r--r-- 1 weewx weewx 8503 13 févr. 19:20 daywindvec.png -rw-r--r-- 1 weewx weewx 1150 13 févr. 19:20 favicon.ico drwxr-sr-x 2 weewx weewx 4096 13 févr. 09:21 font -rw-r--r-- 1 root weewx 31797 13 févr. 19:20 index.html -rw-r--r-- 1 weewx weewx 7702 13 févr. 18:00 monthbarometer.png -rw-r--r-- 1 weewx weewx 8532 13 févr. 18:00 monthET.png -rw-r--r-- 1 weewx weewx 8006 13 févr. 18:00 monthhumext.png -rw-r--r-- 1 weewx weewx 7446 13 févr. 18:00 monthhumin.png -rw-r--r-- 1 weewx weewx 7328 13 févr. 18:00 monthhum.png -rw-r--r-- 1 weewx weewx 7383 13 févr. 09:21 monthlightning.png -rw-r--r-- 1 weewx weewx 8135 13 févr. 18:00 monthradiation.png -rw-r--r-- 1 weewx weewx 7181 13 févr. 18:00 monthrain.png -rw-r--r-- 1 weewx weewx 6503 13 févr. 18:00 monthrx.png -rw-r--r-- 1 weewx weewx 7870 13 févr. 18:00 monthtempdew.png -rw-r--r-- 1 weewx weewx 7357 13 févr. 18:00 monthtempext.png -rw-r--r-- 1 weewx weewx 9012 13 févr. 18:00 monthtempfeel.png -rw-r--r-- 1 weewx weewx 7911 13 févr. 18:00 monthtempin.png -rw-r--r-- 1 weewx weewx 6574 13 févr. 18:00 monthUV.png -rw-r--r-- 1 weewx weewx 11055 13 févr. 18:00 monthvolt.png -rw-r--r-- 1 weewx weewx 6080 13 févr. 18:00 monthwinddir.png -rw-r--r-- 1 weewx weewx 7732 13 févr. 18:00 monthwind.png -rw-r--r-- 1 weewx weewx 6752 13 févr. 18:00 monthwindvec.png drwxr-sr-x 2 weewx weewx 12288 13 févr. 19:20 NOAA -rw-r--r-- 1 root weewx 11717 13 févr. 19:20 rss.xml -rw-r--r-- 1 weewx weewx 5406 13 févr. 19:20 seasons.css -rw-r--r-- 1 weewx weewx 6404 13 févr. 19:20 seasons.js -rw-r--r-- 1 root weewx 23189 13 févr. 19:20 statistics.html -rw-r--r-- 1 root weewx 1461 13 févr. 19:20 tabular.html -rw-r--r-- 1 root weewx 5460 13 févr. 19:20 telemetry.html -rw-r--r-- 1 weewx weewx 8165 13 févr. 19:20 weekbarometer.png -rw-r--r-- 1 weewx weewx 8273 13 févr. 19:20 weekET.png -rw-r--r-- 1 weewx weewx 7852 13 févr. 19:20 weekhumext.png -rw-r--r-- 1 weewx weewx 7285 13 févr. 19:20 weekhumin.png -rw-r--r-- 1 weewx weewx 7532 13 févr. 19:20 weekhum.png -rw-r--r-- 1 weewx weewx 7056 13 févr. 09:21 weeklightning.png -rw-r--r-- 1 weewx weewx 7758 13 févr. 19:20 weekradiation.png -rw-r--r-- 1 weewx weewx 7419 13 févr. 19:20 weekrain.png -rw-r--r-- 1 weewx weewx 6577 13 févr. 19:20 weekrx.png -rw-r--r-- 1 weewx weewx 8905 13 févr. 19:20 weektempdew.png -rw-r--r-- 1 weewx weewx 7887 13 févr. 19:20 weektempext.png -rw-r--r-- 1 weewx weewx 8105 13 févr. 19:20 weektempfeel.png -rw-r--r-- 1 weewx weewx 7566 13
Re: [weewx-user] unable to save to file '/var/www/html/weewx/...
Contents of several files to complete the previous post: /etc/default/weewx : WEEWX_PYTHON=python3 WEEWX_BINDIR=/usr/share/weewx /etc/systemd/system/weewx.service : no file named weewx.service /etc/init.d/weewx no file named weewx PYB Le mardi 13 février 2024 à 20:31:29 UTC+1, Pierre-Yves a écrit : > Hello, > > I experience very similar behavior to that described above. > > Recently, I failed to upgrade my Weewx 4.10 to Weewx 5.0.x. > I reverted "temporarily" to 4.10 and decided to make a fresh install on a > spare set Pi4 + SDR stick. > > I installed RTL_433 and sdr-rtl following the > https://github.com/weewx/weewx/wiki/sdr-rpi-recipe tutorial. I then > installed weewx 5.0.3 and the sdr driver > > I finally replaced the weewx.conf by the one coming from my 4.10 setup. > > I tried several commands : > > - rtl_433 -> ok > > - rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k -R 173 -R 172 > -R 42 -M utc -F json -> ok > > - sudo PYTHONPATH=/usr/share/weewx python3 /etc/weewx/bin/user/sdr.py > --cmd="rtl_433 -f 868.3M -f 433.92M -H 90 -Y autolevel -s 1024k -R 173 -R > 172 -R 42 -M utc -F json" -> ok > > But "weewxd" fails : problem of permission error (see "weewxd log") > > > And "sudo systemctl start weewx" fails too (see "sudo systemctl start > weewx log") > > Finally I tried "sudo weewd" that works and writes data to > /var/www/html/weewx ... > > ps aux|grep weewxd gives : > > pi@raspberrypi:~ $ ps aux|grep weewxd > pi 31049 0.0 0.0 7460 548 pts/1S+ 19:23 0:00 grep > --color=auto weewxd > > It seems that weewx user doesn't exist ! > > ls -la /var/www/html/weewx gives : > > pi@raspberrypi:~ $ ls -la /var/www/html/weewx > total 824 > drwxrwsrwx 4 weewx weewx 4096 13 févr. 19:20 . > drwxr-xr-x 3 root root 4096 13 févr. 14:57 .. > -rw-r--r-- 1 root weewx 5628 13 févr. 19:20 celestial.html > -rw-r--r-- 1 weewx weewx 10018 13 févr. 19:20 daybarometer.png > -rw-r--r-- 1 weewx weewx 7875 13 févr. 19:20 dayET.png > -rw-r--r-- 1 weewx weewx 8068 13 févr. 19:20 dayhumext.png > -rw-r--r-- 1 weewx weewx 7226 13 févr. 19:20 dayhumin.png > -rw-r--r-- 1 weewx weewx 8086 13 févr. 19:20 dayhum.png > -rw-r--r-- 1 weewx weewx 6884 13 févr. 09:21 daylightning.png > -rw-r--r-- 1 weewx weewx 8608 13 févr. 19:20 dayradiation.png > -rw-r--r-- 1 weewx weewx 7004 13 févr. 19:20 dayrain.png > -rw-r--r-- 1 weewx weewx 6490 13 févr. 19:20 dayrx.png > -rw-r--r-- 1 weewx weewx 9330 13 févr. 19:20 daytempdew.png > -rw-r--r-- 1 weewx weewx 8071 13 févr. 19:20 daytempext.png > -rw-r--r-- 1 weewx weewx 8923 13 févr. 19:20 daytempfeel.png > -rw-r--r-- 1 weewx weewx 8125 13 févr. 19:20 daytempin.png > -rw-r--r-- 1 weewx weewx 6225 13 févr. 19:20 dayUV.png > -rw-r--r-- 1 weewx weewx 11508 13 févr. 19:20 dayvolt.png > -rw-r--r-- 1 weewx weewx 8087 13 févr. 19:20 daywinddir.png > -rw-r--r-- 1 weewx weewx 9878 13 févr. 19:20 daywind.png > -rw-r--r-- 1 weewx weewx 8503 13 févr. 19:20 daywindvec.png > -rw-r--r-- 1 weewx weewx 1150 13 févr. 19:20 favicon.ico > drwxr-sr-x 2 weewx weewx 4096 13 févr. 09:21 font > -rw-r--r-- 1 root weewx 31797 13 févr. 19:20 index.html > -rw-r--r-- 1 weewx weewx 7702 13 févr. 18:00 monthbarometer.png > -rw-r--r-- 1 weewx weewx 8532 13 févr. 18:00 monthET.png > -rw-r--r-- 1 weewx weewx 8006 13 févr. 18:00 monthhumext.png > -rw-r--r-- 1 weewx weewx 7446 13 févr. 18:00 monthhumin.png > -rw-r--r-- 1 weewx weewx 7328 13 févr. 18:00 monthhum.png > -rw-r--r-- 1 weewx weewx 7383 13 févr. 09:21 monthlightning.png > -rw-r--r-- 1 weewx weewx 8135 13 févr. 18:00 monthradiation.png > -rw-r--r-- 1 weewx weewx 7181 13 févr. 18:00 monthrain.png > -rw-r--r-- 1 weewx weewx 6503 13 févr. 18:00 monthrx.png > -rw-r--r-- 1 weewx weewx 7870 13 févr. 18:00 monthtempdew.png > -rw-r--r-- 1 weewx weewx 7357 13 févr. 18:00 monthtempext.png > -rw-r--r-- 1 weewx weewx 9012 13 févr. 18:00 monthtempfeel.png > -rw-r--r-- 1 weewx weewx 7911 13 févr. 18:00 monthtempin.png > -rw-r--r-- 1 weewx weewx 6574 13 févr. 18:00 monthUV.png > -rw-r--r-- 1 weewx weewx 11055 13 févr. 18:00 monthvolt.png > -rw-r--r-- 1 weewx weewx 6080 13 févr. 18:00 monthwinddir.png > -rw-r--r-- 1 weewx weewx 7732 13 févr. 18:00 monthwind.png > -rw-r--r-- 1 weewx weewx 6752 13 févr. 18:00 monthwindvec.png > drwxr-sr-x 2 weewx weewx 12288 13 févr. 19:20 NOAA > -rw-r--r-- 1 root weewx 11717 13 févr. 19:20 rss.xml > -rw-r--r-- 1 weewx weewx 5406 13 févr. 19:20 seasons.css > -rw-r--r-- 1 weewx weewx 6404 13 févr. 19:20 seasons.js > -rw-r--r-- 1 root weewx 23189 13 févr. 19:20 statistics.html > -rw-r--r-- 1 root weewx 1461 13 févr. 19:20 tabular.html > -rw-r--r-- 1 root weewx 5460 13 févr. 19:20 telemetry.html > -rw-r--r-- 1 weewx weewx 8165 13 févr. 19:20 weekbarometer.png > -rw-r--r-- 1 weewx weewx 8273 13 févr. 19:20 weekET.png > -rw-r--r-- 1 weewx weewx 7852 13 févr. 19:20 weekhumext.png > -rw-r--r-- 1 weewx weewx 7285 13 févr. 19:20 weekhumin.png > -rw-r--r-- 1 weewx weewx
Re: [weewx-user] unable to save to file '/var/www/html/weewx/...
I suggest you try to get weewx and your webserver working using the Simulator driver first before trying to get the RTL/SDR configuration working. -- 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/9ac38536-c9b9-4963-acab-3d5ed815493bn%40googlegroups.com.
Re: [weewx-user] unable to save to file '/var/www/html/weewx/...
Thanks Vince for feedback. Weewx and webserver are perfectly working in simulator mode with "sudo systemctl start weewx" command Feb 13 21:28:23 raspberrypi systemd[1]: Started WeeWX. Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Initializing weewxd version 5.0.2 Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Command line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Using Python 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110] Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Located at /usr/bin/python3 Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Platform Linux-6.1.21-v8+-aarch64-with-glibc2.31 Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Locale: 'fr_FR.UTF-8' Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Entry path: /usr/share/weewx/weewxd.py Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: WEEWX_ROOT: /etc/weewx Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Configuration file: /etc/weewx/weewx.conf Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: User module: /etc/weewx/bin/user Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Debug: 1 Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG __main__: Initializing engine Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.engine: Loading station type Simulator (weewx.drivers.simulator) Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading service weewx.engine.StdTimeSynch Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished loading service weewx.engine.StdTimeSynch Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: No services in service group data_services Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading service weewx.engine.StdConvert Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.engine: StdConvert target unit is 0x1 Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished loading service weewx.engine.StdConvert Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading service weewx.engine.StdCalibrate Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished loading service weewx.engine.StdCalibrate Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading service weewx.engine.StdQC Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished loading service weewx.engine.StdQC Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading service weewx.wxservices.StdWXCalculate Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.wxservices: StdWXCalculate will use data binding wx_binding Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.manager: Daily summary version is 4.0 Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished loading service weewx.wxservices.StdWXCalculate Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading service weewx.wxxtypes.StdWXXTypes Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished loading service weewx.wxxtypes.StdWXXTypes Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading service weewx.wxxtypes.StdPressureCooker Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished loading service weewx.wxxtypes.StdPressureCooker Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading service weewx.wxxtypes.StdRainRater Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished loading service weewx.wxxtypes.StdRainRater Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading service weewx.wxxtypes.StdDelta Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished loading service weewx.wxxtypes.StdDelta Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading service weewx.engine.StdArchive Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.engine: Archive will use data binding wx_binding Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.engine: Record generation will be attempted in 'hardware' Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.engine: Using archive interval of 300 seconds (specified in weewx configuration) Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Use LOOP data in hi/low calculations: 1 Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished loading service weewx.engine.StdArchive Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading service weewx.restx.StdStationRegistry Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO weewx.restx: StationRegistry: Registration not requested. Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Finished loading service weewx.restx.StdStationRegistry Feb 13 21:28:23 raspberrypi weewxd[17482]: DEBUG weewx.engine: Loading service weewx.restx.StdWunderground Feb 13 21:28:23
Re: [weewx-user] unable to save to file '/var/www/html/weewx/...
On Tuesday, February 13, 2024 at 12:31:54 PM UTC-8 Pierre-Yves wrote: Weewx and webserver are perfectly working in simulator mode with "sudo systemctl start weewx" command Good. That means your problem appears to be related to getting weewx as a non-privileged user to access your RTL-STR hardware. When running weewx using the Simulator does "ps aux|grep weewxd" show it running as weewxd ? Or pi ? Or something else ? -- 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/19464c0f-0897-44e1-971d-982479ca28ben%40googlegroups.com.
Re: [weewx-user] unable to save to file '/var/www/html/weewx/...
Yes With simulator, ps aux|grep weewxd shows that weewx user exixts... pi@raspberrypi:~ $ ps aux|grep weewxd weewx17482 1.0 1.6 52056 32100 ?Ss 21:28 0:06 python3 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf pi 19150 0.0 0.0 7460 592 pts/1S+ 21:38 0:00 grep --color=auto weewxd PY Le mardi 13 février 2024 à 21:57:21 UTC+1, vince a écrit : > On Tuesday, February 13, 2024 at 12:31:54 PM UTC-8 Pierre-Yves wrote: > > Weewx and webserver are perfectly working in simulator mode with "sudo > systemctl start weewx" command > > > Good. That means your problem appears to be related to getting weewx as a > non-privileged user to access your RTL-STR hardware. > > When running weewx using the Simulator does "ps aux|grep weewxd" show it > running as weewxd ? Or pi ? Or something else ? > > > -- 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/125925e2-f2a6-4e8c-99e0-d1e0b26c0ebfn%40googlegroups.com.
Re: [weewx-user] unable to save to file '/var/www/html/weewx/...
oops, I meant running as 'weewx' or 'pi' or 'something else' The reason I'm asking is that your systemctl log shows a sudo error that means that the account you are trying to use sudo under is not permitted to do so. The default dpkg installation creates a weewx user and group but does not create a /etc/sudoers.d file for that user. So the weewx user is not going to be able to sudo if you specify that. Butyou should be able to add the weewx user to the correct group(s) that can access your hardware. I think there are other threads related to how to do that. On Tuesday, February 13, 2024 at 12:57:21 PM UTC-8 vince wrote: > On Tuesday, February 13, 2024 at 12:31:54 PM UTC-8 Pierre-Yves wrote: > > Weewx and webserver are perfectly working in simulator mode with "sudo > systemctl start weewx" command > > > Good. That means your problem appears to be related to getting weewx as a > non-privileged user to access your RTL-STR hardware. > > When running weewx using the Simulator does "ps aux|grep weewxd" show it > running as weewxd ? Or pi ? Or something else ? > > > -- 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/9e216d86-52d8-4cf8-a71b-74ba11a0f2efn%40googlegroups.com.
Re: [weewx-user] unable to save to file '/var/www/html/weewx/...
Thanks Vince. I'll try to find the way to do that Le mardi 13 février 2024 à 22:05:10 UTC+1, vince a écrit : > oops, I meant running as 'weewx' or 'pi' or 'something else' > > The reason I'm asking is that your systemctl log shows a sudo error that > means that the account you are trying to use sudo under is not permitted to > do so. The default dpkg installation creates a weewx user and group but > does not create a /etc/sudoers.d file for that user. So the weewx user is > not going to be able to sudo if you specify that. > > Butyou should be able to add the weewx user to the correct group(s) > that can access your hardware. I think there are other threads related to > how to do that. > > On Tuesday, February 13, 2024 at 12:57:21 PM UTC-8 vince wrote: > >> On Tuesday, February 13, 2024 at 12:31:54 PM UTC-8 Pierre-Yves wrote: >> >> Weewx and webserver are perfectly working in simulator mode with "sudo >> systemctl start weewx" command >> >> >> Good. That means your problem appears to be related to getting weewx as >> a non-privileged user to access your RTL-STR hardware. >> >> When running weewx using the Simulator does "ps aux|grep weewxd" show it >> running as weewxd ? Or pi ? Or something else ? >> >> >> > -- 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/9e85cf8d-d9ce-4490-8260-f075e81b2757n%40googlegroups.com.
Re: [weewx-user] unable to save to file '/var/www/html/weewx/...
I haven't found any thread related to the creation of weewx user and group... PY Le mardi 13 février 2024 à 22:14:40 UTC+1, Pierre-Yves a écrit : > Thanks Vince. > I'll try to find the way to do that > > Le mardi 13 février 2024 à 22:05:10 UTC+1, vince a écrit : > >> oops, I meant running as 'weewx' or 'pi' or 'something else' >> >> The reason I'm asking is that your systemctl log shows a sudo error that >> means that the account you are trying to use sudo under is not permitted to >> do so. The default dpkg installation creates a weewx user and group but >> does not create a /etc/sudoers.d file for that user. So the weewx user is >> not going to be able to sudo if you specify that. >> >> Butyou should be able to add the weewx user to the correct group(s) >> that can access your hardware. I think there are other threads related to >> how to do that. >> >> On Tuesday, February 13, 2024 at 12:57:21 PM UTC-8 vince wrote: >> >>> On Tuesday, February 13, 2024 at 12:31:54 PM UTC-8 Pierre-Yves wrote: >>> >>> Weewx and webserver are perfectly working in simulator mode with "sudo >>> systemctl start weewx" command >>> >>> >>> Good. That means your problem appears to be related to getting weewx as >>> a non-privileged user to access your RTL-STR hardware. >>> >>> When running weewx using the Simulator does "ps aux|grep weewxd" show it >>> running as weewxd ? Or pi ? Or something else ? >>> >>> >>> >> -- 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/1af5eb92-a0d1-41f9-8881-2e3b69045775n%40googlegroups.com.
Re: [weewx-user] unable to save to file '/var/www/html/weewx/...
You want to look for 'rtl' or 'sdr' and adding the weewx user to the appropriate group that has permissions to access the hardware. https://groups.google.com/g/weewx-user/c/7CIRRoo6Qdk/m/8dwn6EBiAQAJ is one link. Note that 'plugdev' is correct for that example. We cannot predict what 'your' system will require. On Tuesday, February 13, 2024 at 1:49:27 PM UTC-8 Pierre-Yves wrote: > I haven't found any thread related to the creation of weewx user and > group... > PY > > Le mardi 13 février 2024 à 22:14:40 UTC+1, Pierre-Yves a écrit : > >> Thanks Vince. >> I'll try to find the way to do that >> >> Le mardi 13 février 2024 à 22:05:10 UTC+1, vince a écrit : >> >>> oops, I meant running as 'weewx' or 'pi' or 'something else' >>> >>> The reason I'm asking is that your systemctl log shows a sudo error that >>> means that the account you are trying to use sudo under is not permitted to >>> do so. The default dpkg installation creates a weewx user and group but >>> does not create a /etc/sudoers.d file for that user. So the weewx user is >>> not going to be able to sudo if you specify that. >>> >>> Butyou should be able to add the weewx user to the correct group(s) >>> that can access your hardware. I think there are other threads related to >>> how to do that. >>> >>> On Tuesday, February 13, 2024 at 12:57:21 PM UTC-8 vince wrote: >>> On Tuesday, February 13, 2024 at 12:31:54 PM UTC-8 Pierre-Yves wrote: Weewx and webserver are perfectly working in simulator mode with "sudo systemctl start weewx" command Good. That means your problem appears to be related to getting weewx as a non-privileged user to access your RTL-STR hardware. When running weewx using the Simulator does "ps aux|grep weewxd" show it running as weewxd ? Or pi ? Or something else ? >>> -- 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/4b69c6da-c8ae-4a8a-98e5-9f071cec34acn%40googlegroups.com.
