similar to: NUT 2.8.1 build from source - upssched missing

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

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 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

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

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:

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:

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>

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

I have 3 Raspberry Pi NUT 2.8.1 systems running PI OS. (Debian 11 and 12) All three systems have a heartbeat-timer failure approximately 15 minutes after starting NUT. No subsequent failures. Any ideas on what is happening? Dan -------------- next part -------------- An HTML attachment was scrubbed... URL:

Roger, I did and it didnt work. Hence why I was trying to run just the shell script manually. I am not sure if this works though with the timer defined in it? Cheers, James Date: Mon, 27 Apr 2015 15:03:44 +0200 From: roger at rogerprice.org To: nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] upssched setup On Mon, 27 Apr 2015, James Hammond wrote: > I am unable to get

Now that upsstats.cgi works, I've noticed that dummy-ups changes state every 5 minutes between OL and OB (probably when the 300 second timer expires). The UPS state stays online. Also "online" and "onbatt" are broadcast to the console probably via WALL. (The state changes don't seem to be form the ups as upsshed-cmd doesn't run). Upssched-cmd does run when the UPS

Hi, I'm having problems to configure upssched in order to notify me only when the disconnection exceeds the 30 seconds. Now, I'm getting a mail if it is disconnected just for a second, or even worse, when I got low tension. So, mail notifications are well configured, I guess... I think the problem is in upssched. I'm new to this, so it could be a stupid thing that I'm missing...

ut 10. 3. 2020 o 16:34 Roger Price <roger at rogerprice.org> napísal(a): > > On Tue, 10 Mar 2020, Radoslav Chovan wrote: > > > I have problem with upssched on windows. Upssched is not executed. I > > have 2 scripts, 1 for notification in upsmon and second for scheduling > > in upssched. Monitoring is working fine, script write to log. I'm > > using binary

Hi Roger, I get: Apr 27 20:50:05 unifi upsmon[1022]: UPS ups on batteryApr 27 20:50:05 unifi upssched[2688]: Timer daemon startedApr 27 20:50:06 unifi upssched[2688]: New timer: onbatt (20 seconds)Apr 27 20:50:26 unifi upssched[2688]: Event: onbattApr 27 20:50:26 unifi upssched[2688]: exec_cmd(/sbin/upssched-cmd.sh onbatt) returned 126Apr 27 20:50:41 unifi upssched[2688]: Timer queue empty,

Dear list, Can't make upssched notify me on event occured. OS: Debian, 2.6.26-1-amd64 Nut: 2.4.3-1.1squeeze1 UPS: Ippon Smart Winner 3000 connected via COM On event ( plug out the cord from UPS ) upsmon detect's status change to OB and gives WALL and syslog notify, but no script starting. In syslog no errors and no upssched process occured, just upsmon. There're no PIPE and LOCK

Hi, i am running nut-2.0.0-5 on Fedora core 3. I have the following Problem: In my upssched.conf i have set the Following Parameter: CMDSCRIPT /usr/local/guzman/sbin/upssched-cmd ... AT COMMBAD * START-TIMER upsgone 10 AT COMMOK * CANCEL-TIMER upsgone ... Now if I pull the serial Plug, in my log i see the following error: Event: upsgone Execute command failure:

Hi, I am unable to get upssched working correctly as my UPS calls low battery too late and there is no way to change it. I am running Nut 2.7.3 on Ubuntu 14.04 I have made this script, called /sbin/upssched-cmd.sh #!/bin/sh case $1 in onbatt) /sbin/upsmon -c fsd;; *) echo "shutdown implemented";; esac I am trying to run the script manually to break down my issues. All that

Hello, I'm using nut with my MG Ellipse on serial port. No problem since one year. Two days ago, I wanted to add a phone alert through my asterisk box when power is down. Since then, upssched doesn't make his job anymore. here is the "syslog" I get when the power cord is unplugged : > > May 9 11:39:34 serveur upsmon[6411]: UPS ellipse@localhost on battery > May 9

Hello, I am currently building a new server using debian amd64. Therefore I need to use my UPS EATON Evolution 1550 on it, using usbhid-ups driver. I installed nut with apt (version 2.4.3-1.1squeeze1) on debian 2.6.32-5 amd64. I can currently use nut with the drivers, upsc and upsmon: my UPS is detected and works. Actually everything works except upssched: I can shut down the server using