search for: nut_release_notes

...pssched is taking 100% CPU. Debian 11 (PI Os). > I have two others running the same configuration, 2.8.1 with no > problems. I have no first hand knowledge of this issue, but in the change log for the 2.8.1 release: https://networkupstools.org/historic/v2.8.1/docs/release-notes.chunked/NUT_Release_Notes.html#_release_notes_for_nut_2_8_1_what_8217_s_new_since_2_8_0 A bug in upssched was discovered and fixed, where it ran a tight loop stressing the CPU; it was presumably introduced between NUT v2.7.4 and v2.8.0 releases [#1964, #1965] I expect your Debian 11 Pi OS does not have 2.8....

...pssched is taking 100% CPU. Debian 11 (PI Os). > I have two others running the same configuration, 2.8.1 with no > problems. I have no first hand knowledge of this issue, but in the change log for the 2.8.1 release: https://networkupstools.org/historic/v2.8.1/docs/release-notes.chunked/NUT_Release_Notes.html#_release_notes_for_nut_2_8_1_what_8217_s_new_since_2_8_0 A bug in upssched was discovered and fixed, where it ran a tight loop stressing the CPU; it was presumably introduced between NUT v2.7.4 and v2.8.0 releases [#1964, #1965] I expect your Debian 11 Pi OS does not have 2.8....

My Raspberry PI 3B was overheating - 70 degrees C. I used Top and it turns out that upssched is taking 100% CPU. Debian 11 (PI Os). I have two others running the same configuration, 2.8.1 with no problems. If I kill upssched, it soon reestablishes the 100% CPU usage. Any ideas on how to diagnose the issue? Dan -------------- next part -------------- An HTML attachment was scrubbed... URL:

...APC ModBus protocol (currently for read-only monitoring - I am not sure if development for commands and writable variables would land before the end of month). Generally you can preview the live list of notable changes since 2.8.0 release at https://networkupstools.org/docs/release-notes.chunked/NUT_Release_Notes.html#_planned_release_notes_for_nut_2_8_1_what_8217_s_new_since_2_8_0 and for things that are expected to impact packaging and upgrades (whether by possibly breaking disruption, or by adding new ways to automate things more efficiently that the audience could benefit from) - at https://networkupsto...

...APC ModBus protocol (currently for read-only monitoring - I am not sure if development for commands and writable variables would land before the end of month). Generally you can preview the live list of notable changes since 2.8.0 release at https://networkupstools.org/docs/release-notes.chunked/NUT_Release_Notes.html#_planned_release_notes_for_nut_2_8_1_what_8217_s_new_since_2_8_0 and for things that are expected to impact packaging and upgrades (whether by possibly breaking disruption, or by adding new ways to automate things more efficiently that the audience could benefit from) - at https://networkupsto...

Seconding ... or firsting, considering the recent call to testing hidden somewhere in a recent mail post ;) Currently I'm aiming at cutting a NUT 2.8.1 release during October. As a bit of self-imposed retrospective: I did hope for a faster (quarterly or so) cadence when I made the 2.8.0 release, but then a few issues came up as regressions of 2.8.0 and it became a sort of crusade to fix

Seconding ... or firsting, considering the recent call to testing hidden somewhere in a recent mail post ;) Currently I'm aiming at cutting a NUT 2.8.1 release during October. As a bit of self-imposed retrospective: I did hope for a faster (quarterly or so) cadence when I made the 2.8.0 release, but then a few issues came up as regressions of 2.8.0 and it became a sort of crusade to fix