Displaying 20 results from an estimated 7000 matches similar to: "POWERDOWNFLAG Confusion.."
2006 Sep 13
2
POWERDOWNFLAG (/etc/killpower) does not contain the upsmon magic string!!!
Hi to all, i install nut and it's work perfectly but when i start upsmon i recive the message:
POWERDOWNFLAG (/etc/killpower) does not contain the upsmon magic string
My upmon.conf contain:
MONITOR myups@theseo 1 orion91 carlos81 master
SHUTDOWNCMD "/sbin/shutdown -h +0"
HOSTSYNC 15
POWERDOWNFLAG /etc/killpower
FINALDELAY 5
My killpower scrit in /etc/killpower
2012 Nov 28
1
upsmon.conf::POWERDOWNFLAG
?Hello everybody,
I've just noticed that POWERDOWNFLAG defaults to
/etc/killpower in upsmon.conf.
I believe that such files belong to the /run sub-tree.
Not only because it's not a config. file; mainly because
many embedded systems actually have most of the FS
read-only and have only the /tmp, /var and /run
writable...
Is there any particular reason to keep the file in /etc?
Thanks,
2023 Jan 09
0
How verbose should NUT be by default?
Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes:
> The opposite opinion is that programs should be quiet until asked to
> squeak (e.g. by restarting with higher debug verbosity... "that would help
> troubleshooting why the rack went down last week, right!" says the sysadmin
> me).
That's a fair summary but my opinion is:
daemon-type
2023 Jan 09
0
[Nut-upsdev] How verbose should NUT be by default?
Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes:
> The opposite opinion is that programs should be quiet until asked to
> squeak (e.g. by restarting with higher debug verbosity... "that would help
> troubleshooting why the rack went down last week, right!" says the sysadmin
> me).
That's a fair summary but my opinion is:
daemon-type
2015 Jan 31
0
Start up script fails [/etc/killpower]
On Jan 31, 2015, at 3:09 PM, Melvin Call <melvincall979 at gmail.com> wrote:
> One last question if you don't mind. I noticed the "default" POWERDOWNFLAG is
> set to /etc/killpower, but I changed that to /tmp and modified my umountroot
> script to mount it read only too, because I know it gets wiped on reboot. Is
> there anything that removes /etc/killpower on
2018 Sep 07
0
WinNUT Client Logs
How do you setup the debug options in WinNUT?
Correct, it sets the POWERDOWNFLAG when it receives an FSD but only if it acts as a NUT MASTER (since the UPS is connected locally to the NUT MASTER and can issue a killpower). This is the default value and I did not care to change it because it won't be use on my Windows machine anyway as it is working as a NUT SLAVE.
Thank you.
Regards,
Kevin
2015 Jan 31
2
Start up script fails
On 1/31/15, Charles Lepple <clepple at gmail.com> wrote:
> On Jan 31, 2015, at 9:17 AM, Melvin Call <melvincall979 at gmail.com> wrote:
>
>> There is no other information provided, and there is nothing in the log to
>> help
>> either. Can anyone tell me what I need to do to make this output some
>> useful
>> information that I can use to further
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
2024 Sep 08
0
Nut-upsuser Digest, Vol 231, Issue 4
This is the first time that i had to use E-mail like forums i'm only hitting reply to mail NOT replay to all mails
THIS IS upssched.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
CMDSCRIPT /usr/bin/upssched-cmd
PIPEFN /run/nut/upssched.pipe
LOCKFN /run/nut/upssched.lock
AT COMMOK * EXECUTE
2024 Sep 08
0
Nut-upsuser Digest, Vol 231, Issue 2
By side effect, lack of "killpower" touch file works to not-tell the OS
shutdown integration on OMV to turn off the UPS. A more proper way about
this is generally to change
MONITOR back-ups 1 monmaster 4L[p9<0Vi|Z>xKgK master
(see my earlier message or docs about primary/master vs. secondary/slave
clients), to
MONITOR back-ups 1 monmaster 4L[p9<0Vi|Z>xKgK slave
and it
2006 Nov 21
1
MGE Nova 1100 AVR + upssched
Hi, I'm having problems to configure upssched in order to notify me only
when the disconnection exceeds the 30 seconds.
Now, I'm getting a mail if it is disconnected just for a second, or even
worse, when I got low tension.
So, mail notifications are well configured, I guess...
I think the problem is in upssched.
I'm new to this, so it could be a stupid thing that I'm missing...
2015 Feb 01
2
Start up script fails [/etc/killpower]
On 1/31/15, Charles Lepple <clepple at gmail.com> wrote:
> On Jan 31, 2015, at 3:09 PM, Melvin Call <melvincall979 at gmail.com> wrote:
>
>> One last question if you don't mind. I noticed the "default" POWERDOWNFLAG)
>> is
>> set to /etc/killpower, but I changed that to /tmp and modified my
>> umountroot
>> script to mount it read only
2015 Jul 14
1
New questions
Here is the previous email that I sent directly to Charles Lepple. ?I am now sending to the correct email with cc to Charles.
----------------
I am looking at, and trying to understand the rest of the conf files. ?But first want to askabout something from this message:[CODE]root at debian:/home/john# upsdrvctl startNetwork UPS Tools - UPS driver controller 2.7.2Network UPS Tools - Megatec/Q1
2018 Sep 04
2
WinNUT Client Logs
Hi Charles,
Are there any logs generated by the WinNUT client? I'm trying to configure it for the first time and I cannot make it to work. Here are my settings:
Nut.conf
MODE=netclient
Upsmon.conf
MONITOR ups at pfsense 1 <username> <password> slave
MINSUPPLIES 1
SHUTDOWNCMD "C:\\WINDOWS\\system32\\shutdown.exe -s -t 0"
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME
2005 Jun 02
0
"UPS myups@localhost is unavailable" from upsmon
Greetings,
I imagine this question must have been answered previously on the
list, but I can't search for the answer because the archives are gone.
Executive summary: I am trying to install and configure nut 2.0.1 on
Fedora Core. I have a SmartUPS Pro plugged into a USB port. Upsmon
is logging "UPS myups@localhost is unavailable" to syslog and via wall
when it starts up and
2010 Nov 16
2
Shutdown script does not trigger
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
2018 Jun 19
2
upsmon Can not initialize SSL context (letsencrypt) #563
those mails list are from last century but i give it a try !
created : https://github.com/networkupstools/nut/issues/563
Hello all,
Trying to run an EATON 850pro via USB on a Debian Stretch Stable.
I have letsencrypt certificate installed and working.
When trying to manage the EATON device, i got:
upsmon Can not initialize SSL context
When 850pro is connected via USB, i can:
lsusb
Bus 009
2008 Mar 20
1
NUT behaviour when master system fails
Hi all,
We have recently bought an APC UPS and are in the process of setting up
the NUT software to make use of it. We are experiencing a problem with
the behaviour of the slave systems when the master system goes off line.
Although the failure of our master system will (hopefully) be a rare
event, and we hope not to experience too many power outages, it is
possible (if unlikely) that both
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
2006 Mar 12
0
upsmon not authenticating (I've read the FAQ)
An update -
I ran a test by unplugging my UPS and letting it run down. The system shut
down as it should.
However, the /etc/killpower file was not created, and the UPS did not shut
off power as it should from the shutdown scripts. This may be because the
command to kill the output of the UPS isn't available, or that by not being
able to log in as master prevents this. The permissions on the