similar to: Belkin USB UPS Not Turning Off

Thanks Roger for all your help here. I hope the 2 attachments come through. The .sh is my doctored version of the script and the .report is its output. I welcome any suggestions or ideas about what might be causing my problems with monitoring to the Belkin UPS. Cheers On 7/12/2019 10:12 AM, Roger Price wrote: > On Fri, 12 Jul 2019, David White wrote: > >> Hello, thanks, and sorry

On Fri, 12 Jul 2019, David White wrote: > Hello, thanks, and sorry for the delay in getting back. I am running the > script and have move the comment from one D= line to the other. I am, > however, seeing some errors written to the console. They are from line > 64-65 of the script. > > Regarding line 64, I have no /usr/sbin/ups* and suspect the proper > location on my

Hi Roger and thanks! I have attached my nut report from the new script (sans journal). I saw nothing that looked like a problem with the report save the sections <scriptname> "Cannot access <scriptname>. Perhaps this is from the missing journal? On 7/14/2019 7:52 AM, Roger Price wrote: > On Tue, 9 Jul 2019, Charles Lepple wrote: > >> Can you please run this script

On Tue, 31 Dec 2019, David White wrote: > ... But it did not actually turn off the UPS at all. The UPS kept > beeping and I had to turn it off manually. > > I thought that NUT would handle this. But perhaps it cannot for my unit? Or > perhaps I have things improperly configured? Any suggestions? Thanks and > happy new year! > ########### /etc/nut/upsmon.conf

On Jul 9, 2019, at 12:22 PM, David White wrote: > > So I guess I am wondering if this is related to my problem. I have no idea how the blazer_usb driver works. For the most part, NUT drivers ending in “_usb” (including blazer_usb) do not need a serial device node in /dev. They use libusb to talk directly to the UPS. (If you can reliably read the UPS status with upsc, then the connectivity

On 1/1/2020 2:21 AM, Roger Price wrote: > On Tue, 31 Dec 2019, David White wrote: > >> ... But it did not actually turn off the UPS at all. The UPS kept >> beeping and I had to turn it off manually. >> >> I thought that NUT would handle this. But perhaps it cannot for my >> unit? Or perhaps I have things improperly configured? Any suggestions? >> Thanks

On Thu, 8 Jun 2017, Robbie van der Walle wrote: > After the first test and the NAS is restarted I had to change the > setting battery.charge.low again to 80? Does the NAS DSM reset battery.charge.low to 10 or is it internal to the UPS? You will have to experiment by disconnecting the UPS control lead from the NAS and connecting it (if possible) to the Mac. After setting to 80 and a

Hi centos 6.3 uses traditional SysV script ( not systemctl) here is the /etc/init.d/ups ( script) assuming it similar to nutshutdown # more /etc/init.d/ups #! /bin/bash # # ups: Starts the Network UPS Tools # # chkconfig: - 26 74 # description: Network UPS Tools is a collection of programs which provide a common \ # interface for monitoring and administering UPS hardware. # processname: upsd #

Hi, I have been running nut successfully for a long time with my Debian 11 server. I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13 to 2.8.0-7. I noticed that after upgrade there was a upssched process running and taking 100% cpu time. I checked if there were any changes to configuration file formats with nut upgrade and only differences I noticed were a terminology

On Tue, 4 Apr 2017, Arnaud Quette wrote: > Hi Jon, Stuart and the list > > 2017-04-04 1:09 GMT+02:00 Stuart Gathman <stuart at gathman.org>: > Which NOTIFYCMD is run when there is an ALARM? > Have you specified that in your upsmon.conf? > > And that is the question of the hour.? How do you specify that?? Note > that this is not the REPLBATT

Hi everyone, new to the list but a long time nut user. I've tried a couple of times to set up a timer to avoid getting annoying messages when the system goes on battery for only a few seconds. in uppsched.conf I added this at the bottom: AT ONBATT * START-TIMER onbattwarn 60 AT ONLINE * CANCEL-TIMER onbattwarn What am I missing? it still doesn't wait before alerting me.

Ah! So I can detect the source UPS in the upssched.conf and pass it as a distinct event to the shell script. That sounds like an excellent approach. Thanks! GMH From: O'Shaughnessy, Mike [mailto:Mike.OShaughnessy at gd-ms.com] Sent: Tuesday, October 31, 2017 12:46 PM To: Garrett Michael Hayes <Garrett at VerbalImaging.com>; nut-upsuser at lists.alioth.debian.org Subject: RE: Email

Hello, I set up a FreeBSD 8.2 system with nut 2.6.1 and a Powerware 5115 connected by RS-232. I expected this setup to shut down before running out of battery power, but I either missed some important configuration or something else went wrong: The syslog says: Jan 9 05:03:42 b1 upsmon[67752]: UPS upsb1 at localhost on battery Jan 9 05:04:42 b1 upsmon[67752]: UPS upsb1 at localhost on line

hello, i've got a problem with the notifycmd here is a part of my upsmon.conf : NOTIFYCMD /usr/local/ups/bin/nut_notify NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "UPS %s is on battery" NOTIFYMSG REPLBATT "The UPS %s battery is bad and needs to be replaced" NOTIFYMSG LOWBATT "UPS %s is being shutdown by the master" NOTIFYMSG FSD

Yes, that was the power off test. However the upssched-cmd script gave absolutely no signs of activity. Even it's logger lines don't show up in journalctl. No any permission error messages - nothing. Only the 2 messages from upsmon - on battery and then on line power. Here is the nut-report: http://www.filehosting.org/file/details/518300/NUT.report --- George Anchev On Tue, Oct 27,

Hello guys Yesterday i started do configure my Mustek Powermust650 with nut using the megatec_usb driver. Everything works fine except for the mailing when something happens. My upsmon looks like this: MONITOR powermust650 at localhost 1 local controller master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /root/upsmailer POLLFREQ 10 POLLFREQALERT 5 HOSTSYNC 15

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

OS name and version, MASTER SYSTEM has three APC smart UPS 3000 UPS connected via USB debian 8 "jessie" Linux pdxvhtst01 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux SLAVE SYSTEMS monitoring MASTER via IP debian 8 "jessie" Linux geaaetst01

Hello dear all, I try to use NUT for windows (not WinNUT), and stuck with launching NOTIFYCMD. On any event marked as SYSLOG+WALL+EXEC syslog entry appears, popup window appears, but NOTIFYCMD script doesn't run. If I run upsmon.exe in cmd (i. e. not as a service) everything works fine. Here is my upsmon.conf: MONITOR central at 10.35.0.180 1 user password slave MINSUPPLIES 1 SHUTDOWNCMD