similar to: Client shutdown options?..

Hello, I'm using Archlinux x86_64 with linux-nouveau kernel (based on linux-mainline (that is linux-3.6)). I've installed nut-2.6.5. I first tried to use new systemctl .service scripts, but they are problematic. So I start and stop nut from /etc/rc.c script. This way, it "woks". Here are my config files : nut.conf : MODE=netserver ups.conf : [ellipse] driver = usbhid-ups

Hello, I have been following the details in this article to configure my UPS: http://rogerprice.org/NUT.html However the system won't shutdown although file permissions look ok: ls -alF /usr/sbin/ups* -rwxr--r-- 1 upsd daemon 64984 Oct 15 2014 /usr/sbin/upsd* -rwxr--r-- 1 upsd daemon 48584 Oct 15 2014 /usr/sbin/upsmon* -rwxr--r-- 1 upsd daemon 31536 Oct 15 2014 /usr/sbin/upssched*

On Sun, 9 Jun 2019, Joe Gervasio wrote: > This question undermines my reading of the documentation.  I had thought that > these were separate things:  > >     SHUTDOWNCMD "/sbin/shutdown -u -h +1"  >     NOTIFYCMD /opt/local/sbin/upssched > > I had assumed that the SHUTDOWNCMD would be used by the Nut client (upsmon) to > shutdown the slave system,  and that

Hi! Is there a way to tell upsd to initiate a shutdown sequence (i.e. run SHUTDOWNCMD) immediately after losing line power and switching the state to OB? I'm using an old battery and by the time it reaches LB state, it's already too late for a clean shutdown. Another solution would be to change the LB percentage. It currently reads (upsc): battery.charge.low: 10 Is there a way to

On Mon, 15 May 2017, Dinow Hsieh wrote: > ==> I have tried this command "upsdrvctl shutdown" as below results (However the UPS still sustain the power) > > ??? Network UPS Tools - UPS driver controller 2.7.1 > ??? Network UPS Tools - Generic HID driver 0.38 (2.7.1) > ??? USB communication driver 0.32 > ??? Using subdriver : PowerCOM HID 0.4 > ??? Initiating UPS

Dmitri Stepanov wrote on 7/14/2016 5:18 AM: > All the hosts are installed together in one rack and have fed from one > UPS (only I am remote from the system :) and I haven't ability to > connect to it. Some of hosts haven't NUT for a number of reasons. I > don't need to inform not-NUT hosts about any UPS events, heartbeat, > etc... but only shutdown all the hosts

On Jan 21, 2014, at 9:27 AM, Rafal Oleszek wrote: > So it's impossible to configure upssched to start timer only if all ups > are in status: OB or LB ? Not impossible, just not possible inside a single configuration file. You can always put that logic into an external script called by upssched. -- Charles Lepple clepple at gmail

On Feb 13, 2014, at 10:22 AM, Stoycho Ganev wrote: > Hi! > > Is there a way to tell upsd to initiate a shutdown sequence (i.e. run SHUTDOWNCMD) immediately after losing line power and switching the state to OB? > A generic way would be to have upsmon signal upssched, and run the shutdown command when upssched gets the OB signal: http://www.networkupstools.org/docs/man/upsmon.html

On Jan 21, 2014, at 3:16 AM, Rafa? Oleszek wrote: > I would like to mention that MINSUPPLIES manipulation doesn't work. My nut version is : 2.2.2-4 (RHEL 5) 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

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

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,

> > 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

Thank you for answer Stuart >?????, 13 ???? 2016, 17:54 +03:00 ?? Stuart Gathman <stuart at gathman.org>: > >On 07/13/2016 10:02 AM, Stuart Gathman wrote: >> On 07/13/2016 04:17 AM, Dmitri Stepanov wrote: >>> I need to shutdown a number of hosts which has not NUT from one which has it. >> Let's make sure you are not missing an obvious point. By

Hi, recently I observed that during a power outage, my NUT setup doesn't shutdown properly. Indeed it never reaches the LowBattery state to notify and initiate shutdown on clients. Reviewing my setup and logs I think I'm facing multiple problems and I'm unable to point to real root cause. First, let me focus on my scenario and current setup: In normal status (ONLINE, fully charged)

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

On Wed, 13 Jul 2016, Dmitri Stepanov wrote: >>> ?? shutdown-all-hosts.sh contains: >>> # Linux hosts >>> HOSTLIST="sim iogate br" >>> for host in $HOSTLIST >>> do >>> ... >>> ???? ssh $host halt -p >>> ... >>> done >>> ?? shutdown-all-hosts.sh works fine if it runned manually. >>> ?? But

On Wed, 13 Jul 2016, Dmitri Stepanov wrote: > Hi > > ?? I need to shutdown a number of hosts which has not NUT from one which has it. > > ?? I tried to do it from upssched script (after upssched's timer) like this: > > case $1 in > ??????? earlyshutdown) > ??????????????? logger -t upssched-cmd "Early shutdown is started" > ??????????????? /bin/sh

Yes: Previous complete boot through shutdown Oct 26 21:02:54 i7 upsdrvctl[1955]: Using subdriver: MGE HID 1.32 Oct 26 21:02:55 i7 upsdrvctl[1955]: Network UPS Tools - Generic HID driver 0.38 (2.7.1) Oct 26 21:02:55 i7 upsdrvctl[1955]: USB communication driver 0.32 Oct 26 21:02:56 i7 upsdrvctl[1955]: Network UPS Tools - UPS driver controller 2.7.1 Oct 26 21:02:56 i7 upsd[2226]: fopen

Hello to All! It might be not exactly NUT question but implementation. I have a rack with one UPS and several servers getting power from this device. One server is a master and other are slaves. All systems are running Debian 4.15.3 kernel and APC UPS. Everything works fine but what I need is to make an order for shutting down servers as they have different roles. Is it possible to configure SQL

Dear nut users, I am fighting to configure a smooth server shutdown with an ubuntu server and a dell usb ups using nut. It seems that the drivers connect properly (upsc gives very coherent outputs). However I can't get anything to happen when the ups goes on battery. How can I be sure the the UPS status is really monitored ? Is there a particular log file where I upsmon reports problems