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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e579d14f-7f1f-4362-9f8f-98fc3b413f86n%40googlegroups.com.
