Displaying 20 results from an estimated 10000 matches similar to: "suspend to ram"
2016 Apr 22
2
upsmon errors with /usr/sbin/pm-suspend as the shutdown command
Hi,
While using pm-suspend script as the SHUTDOWNCMD, upsmon does not
correctly handle its returned values and leaves UPS in the "ups.status:
FSD OL CHRG" state forever.
This is with upsmon 2.6.5 from official Fedora Project packager. Box
running Centos 6.7.
Initially, upsmon would not execute pm-suspend at all. Creation of a
custom SELinux module or changing to Permissive mode
2015 Sep 11
3
"upsmon -c fsd" cause system shutdown
hi:
my testing server has two power supply and attach to two ups. one
of the ups is connect to the server with usb.
my upsmon.conf like below:
# for two ups
MONITOR ftups at localhost 1 monmaster nutmaster master
MONITOR ftups at 10.1.1.2 1 monslave nutslave slave
MINSUPPLIES 1
# for early shutdown
NOTIFYFLAG ONBATT EXEC+WALL+SYSLOG
NOTIFYFLAG ONLINE EXEC+WALL+SYSLOG
NOTIFYCMD
2006 Aug 17
1
powercom issues
And something else, that previously eluded from my thoughts:my "notifyme" script,i.e the script that is executed at an ups.status="OB" event, is:
echo `date` >> /root/upsLog
echo " No power, shutting down the system!" >> /root/upsLog
sleep 30
control=`/usr/local/ups/bin/upsc Inform@localhost ups.status`
if [ $control != OL ]
then
2008 Apr 29
5
NUT 2.0.4-4 - Debian stable - /etc/killpower not created?
Hello....
I'm testing the functionality of my NUT-setup (NUT 2.0.4-4 - Debian
stable). The system is connected to the UPS, but is not powered by it.
When running "upsmon -c fsd", upsmon says "Auto logout and shutdown
proceeding". This is all well and good, but I never see the machine
waiting for the UPS to cut the power. Instead it shuts down.
It's my
2018 Sep 07
2
WinNUT Client Logs
On Fri, 7 Sep 2018, Ong, Kevin wrote:
> Any comments here?
I am not a WinNUT user, but in general NUT clients do not produce their own log
files. If you want more detail, you have to set the debug options and then look
in your system logs.
Upsmon.conf
MONITOR ups at pfsense 1 <username> <password> slave
...
POWERDOWNFLAG /usr/local/ups/etc/killpower
My
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
2009 Jun 19
1
UPS does not want to power off itself
Greetings!
I have successfully installed and configured nut package. All i want now
is to power off ups. If i run upsmon -c fsd as root - everything goes
fine, system and ups gracefully shutting down. If i unplug power cable
from an ups, then system is down, but ups still on load. Any help would
be appreciated.
Debian Lenny x86
ups.conf
[ippon]
driver = megatec
port = /dev/ttyS0
2018 Sep 01
2
upsmon fails to start
On Saturday, 1 September 2018 17:50:13 BST Charles Lepple wrote:
> I don’t have the code in front of me at the moment, but my guess is that the
> config parser stopped parsing at the “#” character.
I suspected a rogue character was being interpreted and used `backticks`,
'single quotes' and then "double quotes", but all failed. I ended up removing
the offending #
2024 Feb 21
1
System keeps going into FSD mode after power on
Hello,
I am a new user of NUT and trying to wrap my ahead around a couple of
things. I installed NUT 2.7.4-13 from package on RasPi 4, running Raspbian
Linux 11 (bullseye). I have Cyberpower SL700U connected to it. For testing
I set battery.charge.low to 90, so I wouldn't have to wait a long time. See
all relevant config below.
First of all, what seems to happen is that UPS gets to the low
2012 Jan 04
3
NUT Windows port questions
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120104/34be491b/attachment.html>
2012 Jan 06
1
upsmon+snmp-ups does not shut down system
I've googled and RTFM'ed, but still can't solve this one. I hope you folks can.
This affects my entire computer cluster, but let's start simple: I've got a
computer running NUT; OS is Scientific Linux 5.5; kernel 2.6.18-274.12.1.el5xen.
It connects to an APC SMART-UPS via an APC SmartCard using the snmp-ups driver.
It generally works: upsmon will detect if the battery is low
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,
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
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 Oct 27
2
FSD sequence: Waiting for bigger and slower clients before cutting power
Hi, this does sound like a useful idea - although for the principle of
least surprise and for variation in deployments, I'd rather have it as a
(non-default state of a) configuration toggle that can be set via
`upsmon.conf`: whether this particular client exits after processing FSD or
not. The onus for the rest would be on general systems integration - e.g.
ensure that init scripts `K*`ill the
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
2019 Jun 08
3
How to shutdown macOS / mac OSX from Network UPS Tools client - NUT
On Jun 8, 2019, at 4:16 PM, Roger Price wrote:
>
> Is your System Shutdown Plan to shut down using upsmon or using the script upsched-cmd? In upssched.conf you do not have a line
>
> AT LOWBATT ups at ... EXECUTE lowbatt
>
> and in upssched-cmd there is nothing to shut down the system.
Joe,
Roger has a good point - the SHUTDOWNCMD should work as long as the master system
2006 Feb 14
3
Master privileges unavailable on UPS
Hello all,
I'm having problems with what I'm told should be a straightforward
issue.
The message in /var/log/daemon is:
<quote>
Feb 13 10:37:57 lupin upsmon[31324]: Master privileges unavailable on
UPS [lupin1500AVR@localhost]
2015 Oct 28
5
The system doesn't shutdown
>
> Did you see a line in the journal similar to this ?
> Oct 06 22:49:54 pinta nut-delayed-ups-shutdown[1854]:
> nut-delayed-ups-shudown.service calling
> upsdrvctl to shut down UPS unit
Never after I disabled the service. I pasted the whole journal section of
the successful shutdown from last email. However I have been thinking about
this line
2023 Oct 31
1
FSD sequence: Waiting for bigger and slower clients before cutting power
fredag 27 oktober 2023 20:07:58 CET skrev Jim Klimov:
> Hi, this does sound like a useful idea - although for the principle of
> least surprise and for variation in deployments, I'd rather have it as a
> (non-default state of a) configuration toggle that can be set via
> `upsmon.conf`: whether this particular client exits after processing FSD or
> not. The onus for the rest