Displaying 9 results from an estimated 9 matches for "u830".
Did you mean:
830
2018 Feb 01
10
testing shutdown: pc not restarting; and "ups unavailable" messages
> When a UPS unit performs a delayed power off (NUT sets the delay to 20 seconds
> by default) it deconnects its power outlets which in some UPS units produces an
> audible "clunk". The display of lights on the front panel changes, and the
> beeping stops. The delayed power off can be demonstrated with a light bulb or a
> mains circuit tester connected to one of the
2018 Feb 01
1
testing shutdown: pc not restarting; and "ups unavailable" messages
> Have you checked the BIOS option "Power on when AC Returns"?
Yes, and I have set it to "always on" as opposed to "always off" or "last state".
> Does the UPS unit perform a delayed power off some time after the box shuts
> down?
I have no idea. How would I find out?
-------------- next part --------------
An HTML attachment was scrubbed...
2018 Feb 02
0
Default value for ondelay
On Fri, 2 Feb 2018, nut.user.u830 at neverbox.com wrote:
> I have an older box set up this way for continuous integration, and it needs to see more than a few seconds of power loss for the "always turn
> on" BIOS setting to work. I forget how many different intervals I tried, but 30 seconds of off time...
2018 Feb 01
1
testing shutdown: pc not restarting; and "ups unavailable" messages
Executive summary:
I am installing a UPS with NUT on Ubuntu for the first time. I could
follow the instructions up to "testing shutdowns" but on executing the
recommended command the computer shuts down and never comes back on,
contrary to what the instructions suggest.
I am also seeing regular broadcast messages on the console that the UPS
is unavailable (and in the? syslog that
2018 Feb 01
3
testing shutdown: pc not restarting; and "ups unavailable" messages
> It actually occurred to me that I could try this with another (any other) computer here at work, so I did. I set the BIOS to "always on" after power cut. I booted ubuntu. I did "sudo shutdown -h now" from the console. The pc switched off as expected. Then I removed the power cable and then plugged it back in. According to the theory above, this should have caused the
2018 Feb 01
0
testing shutdown: pc not restarting; and "ups unavailable" messages
> Out of curiosity: if the PC has already been switched off from software by the shutdown script, how would it know that the power has been cut while it was off? Are you telling me that the power supply of the PC keeps checking its incoming AC supply even while off, and that with the BIOS setting I selected it will wake up the PC even after a power cut DURING WHICH the PC was already off? I
2018 Feb 01
0
testing shutdown: pc not restarting; and "ups unavailable" messages
> > where in the filesystem should I be looking for the NUT shutdown script please?
>
> It's the SHUTDOWNCMD in upsmon.conf
Thanks!
2018 Feb 01
0
testing shutdown: pc not restarting; and "ups unavailable" messages
>
>> I see at http://networkupstools.org/ddl/Cyber_Power_Systems/Value_800E.html that
>> the Value 800E does not have variables such as
>> load.off.delay - Turn off the load with a delay (seconds)
>> load.on.delay - Turn on the load with a delay (seconds)
>>
>> What does command ? upscmd -l <UPS> ? report?
>
> I'll try this tonight when
2018 Feb 01
1
testing shutdown: pc not restarting; and "ups unavailable" messages
>
>>> where in the filesystem should I be looking for the NUT shutdown script please?
>>
>> It's the SHUTDOWNCMD in upsmon.conf
Excellent. And in my case (default) it says
SHUTDOWNCMD "/sbin/shutdown -h +0"
I have tried that command and, as expected, it has shut down the pc. Then I have disconnected the power cord for one minute and plugged it back in,