similar to: Upssched 100% CPU

Thanks for the tip. I had downloaded a prerelease source version of NUT 2.8.1, built and installed it. Evidently there was an issue with upssched consuming 100% CPU. I downloaded the current release and the issue has been resolved. Updating all 3 systems. Dan ________________________________ From: Nut-upsuser <nut-upsuser-bounces+danpower2023=outlook.com at alioth-lists.debian.net> on

Hi, On Tue, Mar 05, 2024 at 08:37:32AM +0000, Dan Grostick via Nut-upsuser wrote: > 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. I have no first hand knowledge of this issue, but in the change log for the 2.8.1

Am i the only user who has no glue about how to build a new version for my system? I?m running on Raspberry GNU/Linux (bullseye) v 11, which might be similar to your system? Sounds as if it is not a big issue to download the version and build it and install it. Is there anybody out there who might be able to give me a kickoff, how to do that? Have found various built versions here at Binary

PI OS - Debian12 - Raspberry PI 5 NUT 2.8.1 I'm building from source just downloaded from GITHUB. The error when starting NUT: nut-monitor: /usr/sbin/upssched not found I did a 'find / ' and upssched is not in the filesystem. I've done a make clean, make uninstall. then autogen.sh, make, make install 1. is there an option to make that completely removes everything? In

On 19.02.24 14:48, Dan Grostick via Nut-upsuser wrote: >Msmtp is not sending messages when invoked from upssched-cmd. >I can manually invoke it from the command line. where is its config file? >There is a 's' instead of an 'x' in the ls -l. Might this be some sort of >permission problem? Should not be the case. >upsmon.conf has run user as root. msmtp may use

On Fri, 29 Mar 2024, Dan Grostick wrote: > It is consistently happening 14-15 minutes after starting. Please see attached > upssched-cmd and upssched.conf. I don't have a upssched.cmd. The binary > upssched is used. After the heartbeat failure, is upsd still running? Does the command "upsc -L" report the UPS's? If you use systemd, what does the command

On Thu, 28 Mar 2024, Dan Grostick via Nut-upsuser wrote: > All three systems have a heartbeat-timer failure approximately 15 minutes > after starting NUT. No subsequent failures. Any ideas on what is happening? I've seen the timers: heartbeat.conf has two 300 sec timers, upssched.cmd looks like what is often called upssched.conf and has a 660 sec timer. So it looks as if the

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

On Mar 8, 2024, at 8:22?AM, Dan Grostick via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: > > I've installed 2.8.1 on a Raspberry PI 5 using Pi OS bookworm 64 bit (Debian 12) with success. > > When I take that same configuration to a PI 3B running bookworm 32 bit, compile from source, use the same files from /etc/nut, I get a 'nut-monitor ups at

Hello, fellow NUTs! This October proved to be a rather productive month, with several developments wrapped up, as well as some issues with master codebase behavior created, reported, fixed and tested :) While we were not part of some official Hacktoberfest this year, it pretty much felt like one - great thanks to everyone involved! The month is also ending soon, so if we're to follow

Hello, fellow NUTs! This October proved to be a rather productive month, with several developments wrapped up, as well as some issues with master codebase behavior created, reported, fixed and tested :) While we were not part of some official Hacktoberfest this year, it pretty much felt like one - great thanks to everyone involved! The month is also ending soon, so if we're to follow

It is consistently happening 14-15 minutes after starting. Please see attached upssched-cmd and upssched.conf. I don't have a upssched.cmd. The binary upssched is used. Dan ________________________________ From: Nut-upsuser <nut-upsuser-bounces+danpower2023=outlook.com at alioth-lists.debian.net> on behalf of Roger Price via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>

Msmtp is not sending messages when invoked from upssched-cmd. I can manually invoke it from the command line. There is a 's' instead of an 'x' in the ls -l. Might this be some sort of permission problem? upsmon.conf has run user as root. Dan -------------- next part -------------- An HTML attachment was scrubbed... URL:

I've not been able to connect to my ups using NUT 2.7.4 or NUT 2.8.0. 2.7.4 was installed as a package, 2.8.O was compiled from source. I've messed with permissons, everything is root:root and has the approprate read/execute permissons. I've tried two differnt UPS(es) APC & CyperPower. I'm running PI OS (Raspbian) on a Raspberry Pi3 model B. The port 3493 is open (UFW). I can

Thanks for the interesting puzzle to crunch! Looking at these few bread-crumbs, I wager an educated guess that this loops in `sendcmd()` (where CLI child processes talk to a daemonized copy which tracks the timers for events), around here: https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626 for the daemon and here for the child:

Thanks for the interesting puzzle to crunch! Looking at these few bread-crumbs, I wager an educated guess that this loops in `sendcmd()` (where CLI child processes talk to a daemonized copy which tracks the timers for events), around here: https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626 for the daemon and here for the child:

On Fri, 16 Feb 2024, Dan Grostick via Nut-upsuser wrote: > Is there any way to stop dummy ups from continuously broadcasting status? > (onbatt)? I want to keep the broadcasts from the ups itself. Could you show us your entry in ups.conf for the dummy ups ? If you have an entry "port = file" in that section of ups.conf, could you show us the contents of "file" ?

Dan Grostick via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > When Apache starts is complains about not finding the fully qualified domain name. That seems normal > In the past, upsstats.cgi would just load. I didn?t have to do any Apache2 configuration. I don?t know what has changed. in general this does need configuration. read the apache config file. read the

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,