Displaying 20 results from an estimated 1000 matches similar to: "No shutdown on empty battery"
2010 Jan 09
2
problem with mailing (nut 2.4.1 and a powermust650 -> megatec_usb)
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
2024 Jul 27
1
Fedora 40 nut-server not starting at boot
Hi folks, I'm having an issue with getting nut-server to start at boot on a
freshly installed Fedora 40 desktop. Seems once the machine is up, I can
manually start with systemctl start nut-server and everythings fine.
dnf info nut
Last metadata expiration check: 2:08:11 ago on Sat 27 Jul 2024 03:48:13 PM
EDT.
Installed Packages
Name : nut
Version : 2.8.2
Release : 1.fc40
2020 Apr 28
2
Tripp-Lite SMART1500LCD: powers off with /etc/killpower...then powers back on...
Hi Everyone,
I recently bought a Tripp-Lite SMART1500LCD for my Linux Mint 19.3 machine,
connected via a USB cable. I installed Nut 2.7.4 from the Mint package
repository via sudo apt update && sudo apt install nut. Everything works
great: NUT issues low battery warning when it reaches the set low
battery point and then issues shutdown commands...computer shuts
down..then the UPS shuts
2023 Jun 11
1
Upssched 100% CPU after updating Debian 12
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
2006 Jul 11
2
notifycmd problem
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
2023 May 27
2
unable to connect to APC UPS Connection Refused
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
2017 Jun 09
2
Apple Mac slave
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
2024 Nov 01
1
NUT 2.8.1-3 " Can't claim USB device [051d:0002]@0/0: Entity not found" using usbhid-ups
Hello,
I was thinking about what could be going wrong here, and a few ideas pop
up:
1) If you installed NUT from packaging, there should have been no need to
add OS groups/users manually. There is a valid use-case for running
different daemons under different accounts, as long as they talk over
network and access same files or UNIX sockets at best by sharing a group
for that, but it does need
2024 Nov 01
1
NUT 2.8.1-3 " Can't claim USB device [051d:0002]@0/0: Entity not found" using usbhid-ups
Hi Jim,
Thanks for your help. I'll respond in the same order as you did:
1. Unfortunately, I did "chown" stuff to these created users... Since
the other three responses don't seem to be what you're looking for (but
that's only my uninformed interpretation), I suppose the problem lies here?
Is there a number of files/directories that I should
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
2017 Apr 04
2
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
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
2017 Oct 31
2
Email Alerts for Multiple UPSs with upssched
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
2012 Apr 11
1
NOTIFYCMD doesn't work from Windows service
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
2015 Oct 27
0
The system doesn't shutdown
On Tue, 27 Oct 2015, George Anchev wrote:
> 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:
>
2020 Jun 21
2
Server did not shut down
2023 Jun 10
1
Fopen upsmon.pid - no such file or directory - Nut 2.8.0 built from source
I've built NUT 2.8.0 from source. When the nut-monitor runs: fopen upsmon.pid fails. I'm running as root, upsmon has root:root permissions as well as the other daemons and .conf files. I've tried configuring with and without --prefixpath --prefixaltpath.
Is there something I am missing?
Please see attached.
Dan
-------------- next part --------------
An HTML attachment was
2015 Jul 15
3
No messages
Charles,
This is how I have the upsmon.conf set up. ?The only time I get a message is if the?NUT Monitor gui is running. ?I open LXterminal, pull the wall plug, and I get no messagesin the terminal.
?MONITOR Asium_p700 at localhost 1 upsmon jsamcr master?MINSUPPLIES 1?SHUTDOWNCMD "/sbin/shutdown -h +0"?NOTIFYCMD /sbin/upssched?POLLFREQ 5?POLLFREQALERT 5?HOSTSYNC 15?DEADTIME
2018 Sep 20
3
Upssched not getting called from UPSMON
Hi, I cant seem to get my upssched to get called by upsmon. Upsmon -c fsd just shuts down without the message I set or the one in upssched-cmd
/etc/ups/upsmon.conf:
MONITOR ups6 at localhost 1 <user> <pass> master
MONITOR ups8 at localhost 1 <user> <pass> master
SHUTDOWNCMD "/sbin/shutdown -h +0"
NOTIFYCMD /usr/sbin/upssched
NOTIFYMSG
2017 Jun 16
3
Help with Elite 800VA usb UPS
Thanks mates,
as suggested I have added
runtimecal = 240,100,720,50
default.battery.voltage.low = 10.4
default.battery.voltage.high = 13.8 (the actual charging voltage)
In ups.conf
I have also added the startup procedure in rc.local file, everything is
fine...
I have only to make a deep test.
Is there a way to add a NOTIFYMSG value for the battery test?
Thank you lots
Andrea
2023 Jun 16
1
Dummy-ups cycles between online and onbatt every 5 minutes. (Nut 2.8.0)
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
2020 Mar 10
2
Fwd: Windows upssched does not work
Hi,
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 windows installer 2.6.5-6 from NUT.
Here are my configs:
--- nut.conf
MODE=netclient
--- upsmon.conf
MONITOR ups_1000 at 192.168.3.95 1 <user> <password> slave