<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>May be, I don't know. My UPS doesn't autopower on after charging
its batteries full.</p>
<p>Anyway how do I test it? There has to be some specific way of
shutting down to see if that works or not.<br>
</p>
<div class="moz-cite-prefix">01.01.2023 20:41, Jim Klimov пише:<br>
</div>
<blockquote type="cite"
cite="mid:CAJYg8vJAEYV2Zu45WmXWZQHoWEa+KfjOhpGsumxM058wJ5FzvQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">With some APC rack SmartUPSes of early 2000's, as
well as some larger Eaton devices, I remember them auto-powering
on the load only after they charge "enough" (configurable in
Eatons at least) to run for say 10 minutes - so they can tell
the load to power off and hold it up long enough to guarantee
safe shutdown if another outage happens. So those do turn on,
but after an hour or so. Can this be your case?
<div dir="auto"><br>
</div>
<div dir="auto">Jim </div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, Jan 1, 2023, 19:00
Gennadiy Poryev via Nut-upsuser <<a
href="mailto:nut-upsuser@alioth-lists.debian.net"
moz-do-not-send="true" class="moz-txt-link-freetext">nut-upsuser@alioth-lists.debian.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p>Yes, that one. It made me thinking there might be some
sidetrick to do an actual shutdown.return even if it is
currently reported as not available.</p>
<p>Yes, I know all these technicalities. Fortunately,
load.off.delay works as expected in my case, with a
granularity of a second, because of course I live-tested
it. Determinate or not, 15 seconds turned out to be enough
for all servers to shutdown themselves so by the time load
is turned off, nothing is working from it. That is not the
problem.<br>
</p>
<p>No, the power won't return that quick. It usually takes 3
to 4 hours. Local specifics, so no power races in this
case. Not the problem also.</p>
<p>I am not newbie to the Linux world as I use Gentoo
throughout, but I wasn't able to quickly figure out how to
setup upsmon(+upssched?) to perform the tasks I need. The
workflow I need seems to be marginal compared to the
typical scenarios. Custom solution also allows me to
integrate things like SMS notification in the process.</p>
<p>But once again, this is not the problem.</p>
<p>The problem is getting UPS to turn on the load as soon as
power mains returns. Servers will start automatically. If
a way to do this with my model is discovered, I will
modify my daemon to use it instead of just
load.off.delay'ing.</p>
<p>So, where do I look/dig ? Or is this a dead end and I
better buy other UPS model with an actual support?<br>
</p>
<p>Best regards,<br>
<br>
G.<br>
</p>
<blockquote type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"> So
the daemon I wrote connects to upsd and monitors
input.voltage and <br>
ups.status. BTW had to override pollinterval = 1 and
pollfreq = 1 in <br>
ups.conf to make input.voltage report input voltage in
more or less <br>
real-time instead of cached.<br>
<br>
The code logic is such that as soon as input.voltage
goes below <br>
input.transfer.low and ups.status goes from OL to OB
the farm shutdown <br>
is initiated and ups is issued INSTCMD load.off.delay
command and is <br>
smart enough to shut itself down too.<br>
<br>
So far this part of the project works OK -- the farm
turns itself off <br>
nicely and unattended.<br>
<br>
BUT.<br>
<br>
There seem to be lack of facility to do
shutdown.return though. Still <br>
have to to that manually each time.<br>
<br>
I've attached upsc/upscmd/upsrw outputs but so far
haven't figured out a <br>
combination that might do the trick. Provided my UPS
can do it, of <br>
course, but why shouldn't it?<br>
<br>
From what I've read in the certain discussion on this
maillist that <br>
occurred 12 years ago and from nut documentation I
suspect the hope is <br>
not lost and it is possible to somehow hack in proper
shutdown.return<br>
<br>
But my expertise ends here. Should anyone help me run
all the debug mode <br>
magic I've read of and make good use of it, my
thankfullness will have <br>
no bounds.<br>
<br>
Best regards,<br>
<br>
G.<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">Nut-upsuser@alioth-lists.debian.net</a><br>
<a
href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser"
rel="noreferrer noreferrer noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote>
</div>
</blockquote>
</div>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">Nut-upsuser@alioth-lists.debian.net</a><br>
<a
href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote>
</div>
</blockquote>
</body>
</html>