Displaying 20 results from an estimated 5000 matches similar to: "How to shutdown macOS / mac OSX from Network UPS Tools client - NUT"
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
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
2014 Jan 21
0
Shutdown when both (all) UPS on battery / low battery
> What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines when to shut down.
>
> Also, if you don't want to wait for both UPSes to drain to the low battery state, you can set up a pair of dummy-ups drivers. I'm
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
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
2019 Apr 03
2
upssched Not Running
Was /etc/nut/upssched-cmd automatically installed?
I don't have it on my raspberry pi. :-(
On 2019-04-03 1:54 p.m., Mike wrote:
> I figured this out and it is working now. This fix seems strange to me
> and is possibly a bug. I'm sharing in case it might help others.
>
> I had to uncomment all of the NOTIFYFLAG statements whether I was
> changing them or not.
2019 May 25
2
Low Battery False Alarms
2017 Jan 11
3
NUT Client shuts down when performing runtime calibration on APC UPS
I've setup nas4free (latest version 11.0.0.4, which has NUT 2.7.4) in a VM and configured it via webinterface to my APC UPS and set "shutdown mode" to "UPS goes on battery" with a timer of 30s. Then I started runtime calibration on the UPS and after 30s nas4free has shut down! I think this is not the correct behavior, since the status was "OB CAL". The system
2019 Mar 30
2
upssched Not Running
2016 Jun 14
5
Besoin d’aide pour upssched
Bonjour
je n?arrive pas ? configurer convenablement NUT pour qu?il m?adresse
des SMS en cas de coupure de courant.
C?est important pour moi car dans ma maison les coupures sont tr?s fr?quentes.
Voici ma configuration :
******************************************************************
1/ dans /etc/nut/upsmon.conf
MONITOR eaton at localhost 1 admin motdepasse master
MINSUPPLIES 1
SHUTDOWNCMD
2023 Jun 13
1
Upssched 100% CPU after updating Debian 12
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,
2023 Jun 13
1
Upssched 100% CPU after updating Debian 12
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,
2020 Aug 09
3
Synology NAS is shutting down Ubuntu servers after very brief power outage (fwd)
> Since it's NUT in the NAS which is deciding to order the shutdown, it would be
> useful to see upsmon.conf, upssched.conf and upssched-cmd (or whatever Synology
> use if anything) from the NAS to see what criteria they use.
upsmon.conf (on Synology):
RUN_AS_USER root
MONITOR ups at localhost 1 monuser secret master
MINSUPPLIES 1
SHUTDOWNCMD ""
NOTIFYCMD /usr/sbin/upssched
2017 Jul 03
2
Help with Elite 800VA usb UPS
Ok, I am running NUT in dummy mode.
I have added a new ups in ups.conf
[dummy]
driver = dummy-ups
port = upsc.dev
desc = "dummy ups for testing purposes"
upsc.dev has been generated by exporting the Elit configuration.
I have added the monitor line in upsmon.conf and the "exec" flags (all the
events)
MONITOR dummy at artu 1 user pass master
SHUTDOWNCMD
2017 Jun 10
1
Apple Mac slave
On Fri, 9 Jun 2017, Robbie van der Walle wrote:
> ... and also still open is the notification on the Mac.
If notify-send is available on the Mac, then perhaps this will work:
In upsmon.conf on the Mac you need
NOTIFYCMD /usr/sbin/upssched (or wherever this goes on a Mac)
NOTIFYFLAG ONBATT SYSLOG+EXEC
In upssched.conf you need
CMDSCRIPT /usr/sbin/upssched-cmd (or wherever this
2023 Jan 12
1
NUT & UPS, how to shut down client after 2 min on battery?
Now I have this in /etc/nut/upsmon.conf (my QNAP NAS wants admin and 123456 or not working)
RUN_AS_USER root
MONITOR qnapups at localhost 1 admin 123456 master
MONITOR qnapups at 192.168.222.252 3493 admin 123456 slave
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h +0"
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME 15
POWERDOWNFLAG /etc/killpower
NOTIFYFLAG ONLINE SYSLOG+EXEC
2011 Jul 19
2
KIN-1500AP RM + Windows 2008 64-bit Standard R2 SP1 (nut 2.6.1)
I have only RS-232 on the box (meanwhile, it was manufactured on march of
2011)
Here is my configs:
nut.conf:
*
*
MODE = netserver
ups.conf:
*
*
[KIN1500]
driver = powercom
port = notUsed
desc = "Powercom KING PRO KIN-1500AP RM"
upsd.conf:
*
*
LISTEN 192.168.1.2 3493
upsd.users:
*
*
[monuser]
password = xxxxxxxx
upsmon master
2015 Oct 29
2
The system doesn't shutdown
P.S.2
Today I experienced something weird. As I was working, the system started a
shutdown and did shut down, then the UPS got powered off and then back on -
an expected behavior for a power fail situation. However there was no power
failure!
I ran nut-journal to check what happened:
Previous complete boot through shutdown
Oct 29 10:09:33 i7 upsdrvctl[1966]: Using subdriver: MGE HID
2016 May 09
2
cyberpower ups need to manully turn on the switch
HI
in centos: C="/usr/bin/upssched-cmd"
here is the output of that file:
# more /tmp/NUT.report
NUT configuration 2016-05-10 03:02:20 UTC
########### /etc/ups/nut.conf ###########
MODE=netserver
########### /etc/ups/ups.conf ###########
[cyberpower]
#driver = powerpanel
#port = auto
driver = usbhid-ups
port = auto
vendorid = 0764
desc = " My main
2019 Jun 08
0
How to shutdown macOS / mac OSX from Network UPS Tools client - NUT
On Sat, 8 Jun 2019, Joe Gervasio wrote:
> ETC/UPSMON.CONF
>
> NOTIFYFLAG LOWBATT EXEC+SYSLOG+WALL
>
> ETC/UPSSCHED.CONF
>
> CMDSCRIPT /opt/local/bin/upssched-cmd
> PIPEFN /opt/local/var/db/ups/upssched/upssched.pipe
> LOCKFN /opt/local/var/db/ups/upssched/upssched.lock
> AT ONBATT ups at xxx.xxx.xxx.xxx EXECUTE on-battery
> AT ONLINE ups at