Displaying 20 results from an estimated 3000 matches similar to: "Fedora 40 nut-server not starting at boot"
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
2012 Jan 28
2
No shutdown on empty battery
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
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
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
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
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
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 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
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
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 Jun 21
2
Server did not shut down
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 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
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
2014 Feb 25
3
NUT on Windows, Wall->message.exe
If there is a next Windows release, perhaps the default NOTIFYFLAG's
should be adjusted?
NOTIFYFLAG ONLINE SYSLOG
NOTIFYFLAG ONBATT SYSLOG
NOTIFYFLAG LOWBATT SYSLOG
NOTIFYFLAG FSD SYSLOG
NOTIFYFLAG COMMOK SYSLOG
NOTIFYFLAG COMMBAD SYSLOG
NOTIFYFLAG SHUTDOWN SYSLOG
NOTIFYFLAG REPLBATT SYSLOG
NOTIFYFLAG NOCOMM SYSLOG
NOTIFYFLAG NOPARENT SYSLOG
The 'wall'
2017 Oct 31
0
Email Alerts for Multiple UPSs with upssched
There's supposedly another way with a custom upsmon.conf:
NOTIFYMSG type message
upsmon comes with a set of stock messages for various events. You can change them if you like.
NOTIFYMSG ONLINE "UPS %s is getting line power"
NOTIFYMSG ONBATT "Someone pulled the plug on %s"
Note that %s is replaced with the identifier of the UPS in question.
The message must be one
2014 Feb 28
0
NUT on Windows, Wall->message.exe
On Feb 25, 2014, at 1:13 AM, Kris Jordan wrote:
> If there is a next Windows release, perhaps the default NOTIFYFLAG's should be adjusted?
>
> NOTIFYFLAG ONLINE SYSLOG
> NOTIFYFLAG ONBATT SYSLOG
> NOTIFYFLAG LOWBATT SYSLOG
> NOTIFYFLAG FSD SYSLOG
> NOTIFYFLAG COMMOK SYSLOG
> NOTIFYFLAG COMMBAD SYSLOG
> NOTIFYFLAG SHUTDOWN SYSLOG
> NOTIFYFLAG
2017 Oct 18
2
debian 8 "jessie" nut 2.7.2 slaves not shutting down
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
2015 Oct 27
2
The system doesn't shutdown
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,
2011 Sep 02
2
NUT 2.6.1+ Windows 2008 R2 - NOTIFYCMD not being called
Hi All,
I'm using a recent post 2.6.1 build provided by Fred (executables have modified date of 9th August)
I have configured upsmon.conf with :-
NOTIFYCMD C:\NUT\etc\NotifyCmd.bat
and :-
NOTIFYFLAG ONLINE SYSLOG+EXEC
NOTIFYFLAG ONBATT SYSLOG+EXEC
NOTIFYFLAG LOWBATT SYSLOG+EXEC
NOTIFYFLAG FSD SYSLOG+EXEC
NOTIFYFLAG COMMOK SYSLOG+EXEC
NOTIFYFLAG COMMBAD SYSLOG+EXEC