[weewx-user] Once more: 100% cpu after update
I have read the threads of Bartosz and those cited there but could not find a solution for my problem there: After updating to weewx 5.01. without any flaws after a few weeks, when it got hot ouside, I realized, that my RPi4 had stopped working, because of getting too hot. After restart everything worked fine, until the temperature again rised over more than 60 °C. I checked with s-tui that one of the four cores remained ad 100%. Finally I found, that as soon as weewx generated the first record, the cpu usage was 100%. Now, I moved the RPi4 into a cool and dark room and leave the RPi case open, so that the temperature does not exceed 58 °C in average. The latest update (and system upgrade) was yesterday. My setup: Raspberry4 with Bookworm, connected per LAN cable Weewx 5.1 installed with Debian RPM Ecowitt GW1000, driver 0.6.3 Skin alltimeSeasons with forecast extension I replaced alltimeSeasons with regular Seasons skin, enabled debug = 1 and restarted weewx. Still the same result: journalctl -u weewx Aug 16 14:20:20 raspbee weewxd.py[4438]: historygenerator.py: Generated 5 tables in 0.20 seconds Aug 16 14:22:49 raspbee systemd[1]: Stopping weewx.service - WeeWX... Aug 16 14:22:50 raspbee systemd[1]: weewx.service: Deactivated successfully. Aug 16 14:22:50 raspbee systemd[1]: Stopped weewx.service - WeeWX. Aug 16 14:22:50 raspbee systemd[1]: weewx.service: Consumed 1d 21h 4min 31.966s CPU time. Aug 16 14:23:09 raspbee systemd[1]: Started weewx.service - WeeWX. Aug 16 14:23:16 raspbee weewxd.py[17471]: windy: version is 0.6 Aug 16 14:23:16 raspbee weewxd.py[17471]: windy: Data will be uploaded to https://stations.windy.com/pws/update Aug 16 14:25:16 raspbee weewxd.py[17471]: historygenerator.py: Generated 5 tables in 0.21 seconds Aug 16 14:30:18 raspbee weewxd.py[17471]: historygenerator.py: Generated 5 tables in 0.20 seconds Aug 16 14:35:19 raspbee weewxd.py[17471]: historygenerator.py: Generated 5 tables in 0.20 seconds Aug 16 14:40:21 raspbee weewxd.py[17471]: historygenerator.py: Generated 5 tables in 0.21 seconds Aug 16 14:45:22 raspbee weewxd.py[17471]: historygenerator.py: Generated 5 tables in 0.20 seconds Aug 16 14:50:24 raspbee weewxd.py[17471]: historygenerator.py: Generated 5 tables in 0.19 seconds Aug 16 14:52:31 raspbee systemd[1]: Stopping weewx.service - WeeWX... Aug 16 14:52:31 raspbee systemd[1]: weewx.service: Deactivated successfully. Aug 16 14:52:31 raspbee systemd[1]: Stopped weewx.service - WeeWX. Aug 16 14:52:31 raspbee systemd[1]: weewx.service: Consumed 27min 30.505s CPU time. Aug 16 14:52:54 raspbee systemd[1]: Started weewx.service - WeeWX. Aug 16 14:53:15 raspbee weewxd.py[18570]: windy: version is 0.6 Aug 16 14:53:15 raspbee weewxd.py[18570]: windy: Data will be uploaded to https://stations.windy.com/pws/update Aug 16 14:55:15 raspbee weewxd.py[18570]: historygenerator.py: Generated 5 tables in 0.20 seconds Aug 16 14:57:33 raspbee systemd[1]: Stopping weewx.service - WeeWX... Aug 16 14:57:33 raspbee systemd[1]: weewx.service: Deactivated successfully. Aug 16 14:57:33 raspbee systemd[1]: Stopped weewx.service - WeeWX. Aug 16 14:57:33 raspbee systemd[1]: weewx.service: Consumed 2min 22.493s CPU time. Aug 16 14:57:33 raspbee systemd[1]: Started weewx.service - WeeWX. Aug 16 14:57:40 raspbee weewxd.py[18714]: windy: version is 0.6 Aug 16 14:57:40 raspbee weewxd.py[18714]: windy: Data will be uploaded to https://stations.windy.com/pws/update Aug 16 15:00:20 raspbee weewxd.py[18714]: historygenerator.py: Generated 5 tables in 0.20 seconds Aug 16 15:05:22 raspbee weewxd.py[18714]: historygenerator.py: Generated 5 tables in 0.21 seconds Aug 16 15:10:24 raspbee weewxd.py[18714]: historygenerator.py: Generated 5 tables in 0.18 seconds Aug 16 15:15:25 raspbee weewxd.py[18714]: historygenerator.py: Generated 5 tables in 0.19 seconds Aug 16 15:20:27 raspbee weewxd.py[18714]: historygenerator.py: Generated 5 tables in 0.19 seconds (No success to formate the pasted lines above into Courier, sorry) No idea, where else to look at now. My intention now is, to install weewx on my other RPi5 from the scratch, and move the two databases (weewx.db and forecast.db) over and reestablish alltimeSeasons and forecast afterwards. So, is it possible to maintain weewx on different stations simultaneously? Would my approach work like that? Or should I first search for the cause for 100% CPU load? -- 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/e579d14f-7f1f-4362-9f8f-98fc3b413f86n%40googlegroups.com.
[weewx-user] Re: V5.1 pip insufficient permissions
Hello Vince, As I mentioned in the previous post, I have added the user to groups dialout and plugdev. Unfortunately, it did not work. Thank you. On Wednesday, August 14, 2024 at 8:21:44 PM UTC+2 vince wrote: > See > https://github.com/weewx/weewx/wiki/Understanding-permissions#more-details-about-which-groups-can-do-what > > - it might be the dialout group you need. > > On Wednesday, August 14, 2024 at 4:22:02 AM UTC-7 mgn...@gmail.com wrote: > >> >> Hola a todos, >> >> Siento informar que la v5.1 instalada con pip produce error por persmisos >> insuficientes cuando es ejecutada con usuario sin permisos de administrador: >> >> Aug 14 12:13:17 epops weewxd[1613]: CRITICAL weewx.engine: >> raise USBError(_strerror(ret), ret, _libusb_errno[ret]) >> Aug 14 12:13:17 epops weewxd[1613]: CRITICAL weewx.engine: >> usb.core.USBError: [Errno 13] Access denied (insufficient permissions) >> Aug 14 12:13:17 epops weewxd[1613]: CRITICAL weewxd: Unable to load >> driver: [Errno 13] Access denied (insufficient permissions) >> Aug 14 12:13:17 epops weewxd[1613]: CRITICAL weewxd: Exiting... >> >> Si se ejecuta con el usuario root el funcionamiento es correcto. >> He añadido el usuario no root a los grupos dialout y plugdev. El problema >> persiste. >> >> Gracias. >> Un saludo. > > -- 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/e260bbf7-c080-4c4a-b57f-4be6ce99542cn%40googlegroups.com.
[weewx-user] Re: V5.1 pip insufficient permissions
Sorry. I missed that in google translate. What os and version are you running? Are you running in a virtual machine or a container ? On Friday, August 16, 2024 at 8:42:35 AM UTC-7 mgn...@gmail.com wrote: > Hello Vince, > > As I mentioned in the previous post, I have added the user to groups > dialout and plugdev. > Unfortunately, it did not work. > > Thank you. > > On Wednesday, August 14, 2024 at 8:21:44 PM UTC+2 vince wrote: > >> See >> https://github.com/weewx/weewx/wiki/Understanding-permissions#more-details-about-which-groups-can-do-what >> >> - it might be the dialout group you need. >> >> On Wednesday, August 14, 2024 at 4:22:02 AM UTC-7 mgn...@gmail.com wrote: >> >>> >>> Hola a todos, >>> >>> Siento informar que la v5.1 instalada con pip produce error por >>> persmisos insuficientes cuando es ejecutada con usuario sin permisos de >>> administrador: >>> >>> Aug 14 12:13:17 epops weewxd[1613]: CRITICAL weewx.engine: >>> raise USBError(_strerror(ret), ret, _libusb_errno[ret]) >>> Aug 14 12:13:17 epops weewxd[1613]: CRITICAL weewx.engine: >>> usb.core.USBError: [Errno 13] Access denied (insufficient permissions) >>> Aug 14 12:13:17 epops weewxd[1613]: CRITICAL weewxd: Unable to load >>> driver: [Errno 13] Access denied (insufficient permissions) >>> Aug 14 12:13:17 epops weewxd[1613]: CRITICAL weewxd: Exiting... >>> >>> Si se ejecuta con el usuario root el funcionamiento es correcto. >>> He añadido el usuario no root a los grupos dialout y plugdev. El >>> problema persiste. >>> >>> Gracias. >>> Un saludo. >> >> -- 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/4f499c7c-3296-4820-9840-468b4c3d475dn%40googlegroups.com.
[weewx-user] Re: Once more: 100% cpu after update
Check your weewx.sdb file first if it was originally on a system running weewx v3 or earlier. As the other thread and multiple other ones have indicated, there 'is' a change in v5 that calculates elements present in a skin that are not in the db schema. Typically this is appTemp but there are others. This typically occurs for sites that started in weewx v3 or earlier. New sites that started at v4 should not see this issue usually. Check your schema to see how many elements are in your actual db schema. The big wview-extended schema that is the default in v4 and later will return 114 for the following command. The original wview compatible schema used in v3 and earlier will report a number around 50 or so (I forget the actual number). # use the full path to your db below # or cd into the archive directory before # running the following command echo ".schema" | sqlite3 weewx.sdb | wc -l On Friday, August 16, 2024 at 6:49:32 AM UTC-7 Vetti52 wrote: > I have read the threads of Bartosz and those cited there but could not > find a solution for my problem there: > After updating to weewx 5.01. without any flaws after a few weeks, when it > got hot ouside, I realized, that my RPi4 had stopped working, because of > getting too hot. After restart everything worked fine, until the > temperature again rised over more than 60 °C. I checked with s-tui that one > of the four cores remained ad 100%. Finally I found, that as soon as weewx > generated the first record, the cpu usage was 100%. Now, I moved the RPi4 > into a cool and dark room and leave the RPi case open, so that the > temperature does not exceed 58 °C in average. > The latest update (and system upgrade) was yesterday. > My setup: > Raspberry4 with Bookworm, connected per LAN cable > Weewx 5.1 installed with Debian RPM > Ecowitt GW1000, driver 0.6.3 > Skin alltimeSeasons with forecast extension > > I replaced alltimeSeasons with regular Seasons skin, enabled debug = 1 > and restarted weewx. Still the same result: > > journalctl -u weewx > > Aug 16 14:20:20 raspbee weewxd.py[4438]: historygenerator.py: Generated 5 > tables in 0.20 seconds > Aug 16 14:22:49 raspbee systemd[1]: Stopping weewx.service - WeeWX... > Aug 16 14:22:50 raspbee systemd[1]: weewx.service: Deactivated > successfully. > Aug 16 14:22:50 raspbee systemd[1]: Stopped weewx.service - WeeWX. > Aug 16 14:22:50 raspbee systemd[1]: weewx.service: Consumed 1d 21h 4min > 31.966s CPU time. > Aug 16 14:23:09 raspbee systemd[1]: Started weewx.service - WeeWX. > Aug 16 14:23:16 raspbee weewxd.py[17471]: windy: version is 0.6 > Aug 16 14:23:16 raspbee weewxd.py[17471]: windy: Data will be uploaded to > https://stations.windy.com/pws/update > Aug 16 14:25:16 raspbee weewxd.py[17471]: historygenerator.py: Generated 5 > tables in 0.21 seconds > Aug 16 14:30:18 raspbee weewxd.py[17471]: historygenerator.py: Generated 5 > tables in 0.20 seconds > Aug 16 14:35:19 raspbee weewxd.py[17471]: historygenerator.py: Generated 5 > tables in 0.20 seconds > Aug 16 14:40:21 raspbee weewxd.py[17471]: historygenerator.py: Generated 5 > tables in 0.21 seconds > Aug 16 14:45:22 raspbee weewxd.py[17471]: historygenerator.py: Generated 5 > tables in 0.20 seconds > Aug 16 14:50:24 raspbee weewxd.py[17471]: historygenerator.py: Generated 5 > tables in 0.19 seconds > Aug 16 14:52:31 raspbee systemd[1]: Stopping weewx.service - WeeWX... > Aug 16 14:52:31 raspbee systemd[1]: weewx.service: Deactivated > successfully. > Aug 16 14:52:31 raspbee systemd[1]: Stopped weewx.service - WeeWX. > Aug 16 14:52:31 raspbee systemd[1]: weewx.service: Consumed 27min 30.505s > CPU time. > Aug 16 14:52:54 raspbee systemd[1]: Started weewx.service - WeeWX. > Aug 16 14:53:15 raspbee weewxd.py[18570]: windy: version is 0.6 > Aug 16 14:53:15 raspbee weewxd.py[18570]: windy: Data will be uploaded to > https://stations.windy.com/pws/update > Aug 16 14:55:15 raspbee weewxd.py[18570]: historygenerator.py: Generated 5 > tables in 0.20 seconds > Aug 16 14:57:33 raspbee systemd[1]: Stopping weewx.service - WeeWX... > Aug 16 14:57:33 raspbee systemd[1]: weewx.service: Deactivated > successfully. > Aug 16 14:57:33 raspbee systemd[1]: Stopped weewx.service - WeeWX. > Aug 16 14:57:33 raspbee systemd[1]: weewx.service: Consumed 2min 22.493s > CPU time. > Aug 16 14:57:33 raspbee systemd[1]: Started weewx.service - WeeWX. > Aug 16 14:57:40 raspbee weewxd.py[18714]: windy: version is 0.6 > Aug 16 14:57:40 raspbee weewxd.py[18714]: windy: Data will be uploaded to > https://stations.windy.com/pws/update > Aug 16 15:00:20 raspbee weewxd.py[18714]: historygenerator.py: Generated 5 > tables in 0.20 seconds > Aug 16 15:05:22 raspbee weewxd.py[18714]: historygenerator.py: Generated 5 > tables in 0.21 seconds > Aug 16 15:10:24 raspbee weewxd.py[18714]: historygenerator.py: Generated 5 > tables in 0.18 seconds > Aug 16 15:15:25 raspbee weewxd.py[18714]: historygenerator.py: Generated 5 > tables in 0.19 seconds > Aug 16 15:20
[weewx-user] problem with ftp upload ("class 'ftplib.error_perm")
I ve updated to last Wewx version When I want to use ftp skin : ERROR weeutil.ftpupload: Failed uploading /var/www/html/weewx/BRESSER/belchertown/index.html to server ftp.X.odns.fr. Reason: '553 Can't open that file: No such file or directory' Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: ftpgenerator: (0): caught exception '': 553 Can't open that file: No such file or directory Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: Traceback (most recent call last): Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: File "/usr/share/weewx/weewx/reportengine.py", line 519, in run Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: n = ftp_data.run() Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: File "/usr/share/weewx/weeutil/ftpupload.py", line 208, in run Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: ftp_server.storbinary(stor_cmd, fd) Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: File "/usr/lib/python3.10/ftplib.py", line 498, in storbinary Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: with self.transfercmd(cmd, rest) as conn: Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: File "/usr/lib/python3.10/ftplib.py", line 393, in transfercmd Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: return self.ntransfercmd(cmd, rest)[0] Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: File "/usr/lib/python3.10/ftplib.py", line 793, in ntransfercmd Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: conn, size = super().ntransfercmd(cmd, rest) Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: File "/usr/lib/python3.10/ftplib.py", line 359, in ntransfercmd Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: resp = self.sendcmd(cmd) Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: File "/usr/lib/python3.10/ftplib.py", line 281, in sendcmd Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: return self.getresp() Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: File "/usr/lib/python3.10/ftplib.py", line 254, in getresp Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: raise error_perm(resp) Aug 17 00:50:31 meteo-Ubuntu weewx-BRESSER[110516]: ERROR weewx.reportengine: ftplib.error_perm: 553 Can't open that file: No such file or directory I m tryingh whith filezilla my ftp parameters ... It s ok :) Can someone help me ? -- 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/9a78301d-ac4a-489b-bcc4-efd4cd3f1c71n%40googlegroups.com.
[weewx-user] Re: Fixing values in rainRate table
Is there any case where rainRate will be > 0, but rain = 0 for a time period? What do sum, count, wsum, sumtime account for in the rainRate table? I suspect that if these values are off in the archive table, is a safe to assume that they are off in the archive_day_rain table as well? Should i rebuild the daily summaries as part of this cleanup also? Thanks, On Thursday, August 15, 2024 at 9:32:44 PM UTC-6 vince wrote: > Each will be so fast running a couple commands won’t take long.. > > On Thursday, August 15, 2024 at 7:58:36 PM UTC-7 Thomas Carlin wrote: > >> I also ran the queries below. Obviously all the archive records that >> relate to the records in my original post need to be updated, but is it >> safe to assume that all of the records that are in these queries will need >> to be updated as well, or is there a case where rainRate > 0 but rain=0.0? >> >> sqlite> select count(*) from archive where rainRate > 0 and rain=0.0; >> count(*) >> 4464 >> sqlite> select count(*) from archive where rainRate > 0 and rain is NULL; >> count(*) >> 185 >> sqlite> select count(*) from archive where rain is NULL; >> count(*) >> 317 >> >> These are easy, I expect, to fix, i expect. Simply: >> update archive set rain=0.0 where rain is NULL; >> update archive set rainRate = 0 where rainRate > 0 AND rain=0.0; >> >> Is there a better way to fix all these things in one shot? >> >> Thanks again! >> >> On Thursday, August 15, 2024 at 8:39:06 PM UTC-6 Thomas Carlin wrote: >> >>> Hi All! I've been playing with some skin modifications on my weather >>> station again, and found some strange values in a few tables. Most of them >>> i have been able to clean up without any issue, but I feel like there is >>> more to the rainRate table. >>> >>> I found the following table of values, obviously the min and max are >>> false. I can't however reason out how, if at all the sum, count, wsum >>> relate to the other values. >>> >>> What is the best way to clear out these bad values? I am guessing on >>> some of the min values, I already ran an update command before pulling this >>> full list, and because i live dangerously, didn't pull a backup first, but >>> i do know that the first 10 entries are 100 percent accurate. >>> >>> sqlite> select * from archive_day_rainRate where max >10; >>> dateTime|min|mintime|max|maxtime|sum|count|wsum|sumtime >>> >>> 1605164400|0.0|1605164402|655.3501|1605188100|2136.40082144|287|640920.246432|86100 >>> >>> 1618898400|0.0|1618898403|655.3501|1618930800|26711.4767995|288|8013443.03985|86400 >>> >>> 1643439600|0.0|1643439601|655.3501|1643465400|2551.68191489362|244|765504.574468086|73200 >>> >>> 1645513200|0.0|1645513203|655.3501|1645584600|31106.9906622517|287|9332097.19867551|86100 >>> >>> 1645599600|0.0|1645599603|655.3501|1645680600|8779.61978259878|288|2633885.93477963|86400 >>> 1662703200|0.0|1662703202|655.3501|1662706200|40020.4846440398 >>> <(484)%20644-0398>|288|12006145.3932119|86400 >>> >>> 166815|0.0|1668150004|655.3501|1668153600|8030.40075523906|254|2409120.22657172|76200 >>> 1668754800|655.35|1668817498|655.35|1668817498|655.35|1|196605.0|300 >>> 1668841200|655.35|1668856799|655.35|1668856799|1966.05|3|589815.0|900 >>> 1668927600|655.35|1668940798|655.35|1668940798|2621.4|4|786420.0|1200 >>> 1669014000|655.35|1669023898|655.35|1669023898|3932.1|6|1179630.0|1800 >>> 1669100400|655.35|1669109698|655.35|1669109698|4587.45|7|1376235.0|2100 >>> 1669186800|655.35|1669187699|655.35|1669187699|6553.5|10|1966050.0|3000 >>> 1669273200|655.35|1669278900|655.35|1669278900|7208.85|11|2162655.0|3300 >>> 1669359600|655.35|1669365300|655.35|1669365300|7864.2|12|2359260.0|3600 >>> 1669446000|655.35|1669451697|655.35|1669451697|7208.85|11|2162655.0|3300 >>> 1669532400|655.35|1669536899|655.35|1669536899|9830.25|15|2949075.0|4500 >>> 1669618800|655.35|166962|655.35|166962|9174.9|14|2752470.0|4200 >>> 1669705200|655.35|1669719897|655.35|1669719897|9174.9|14|2752470.0|4200 >>> 1669791600|655.35|1669793098|655.35|1669793098|11140.95|17|3342285.0|5100 >>> 1669878000|655.35|1669879500|655.35|1669879500|13107.0|20|3932100.0|6000 >>> 1669964400|655.35|1669966800|655.35|1669966800|10485.6|16|3145680.0|4800 >>> 1670050800|655.35|1670052899|655.35|1670052899|7864.2|12|2359260.0|3600 >>> 1670137200|655.35|1670194711|655.35|1670138996|7864.2|109|2359260.0|32700 >>> >>> 1670396400|0.0|1670396403|655.3501|1670407500|37676.1049695061|287|11302831.4908518|86100 >>> >>> 1672297200|0.0|1672297201|655.3501|1672323300|22253.0669985626|287|6675920.09956877|86100 >>> >>> 1676098800|0.0|1676098802|655.3501|1676113800|28772.4393132542|288|8631731.79397624|86400 >>> >>> 1676185200|0.0|1676185202|655.3501|1676209500|13341.363576159|268|4002409.07284769|80400 >>> >>> 1676703600|0.0|1676703602|655.3501|1676716500|8775.40582191782|287|2632621.74657535|86100 >>> >>> 1698991200|0.0|1698991202|655.350
