Re: [Nut-upsuser] testing shutdown: pc not restarting; and "ups unavailable" messages

[nut . user . u830]

> NUT takes charge of sending the required commands through the driver; the 
> default values are load.off.delay 20 and load.on.delay 30.  These values can 
> be 
> changed by adding lines such as
> 
> offdelay = 30
> ondelay = 100
> 
> to the corresponding UPS section in file ups.conf.

This sounded like a very appealing and sensible suggestion, thanks, so I just 
tried it.

I edited /etc/nut/ups.conf to contain the following stanza

[cyber]
driver = usbhid-ups
port = auto
desc = "Cyber Power Systems VALUE800EILCD"
offdelay = 30
ondelay = 100

and then I "tested the shutdown sequence" with

sudo upsmon -c fsd

The computer duly shut down but then didn't come back up for 3 minutes, at 
which point I power-cycled it by removing and re-inserting the cable. (By the 
way, 5 seconds of off time wasn't enough to wake it up, but 30 was.)

So what else could be wrong? 

- Should I have written load.off.delay instead of offdelay?

- Should I have issued any other command to cause the driver to read its 
ups.conf file?

- Could it be that the second issue I reported in my original message to the 
list is also affecting what happens?
http://lists.alioth.debian.org/pipermail/nut-upsuser/2018-February/011034.html 


I am still getting quite a few console broadcasts that "UPS cyber@localhost is 
unavailable" and (a) I don't know why (b) I wonder if this is preventing nut 
from telling the UPS those new values for the on-delay and off-delay.

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] testing shutdown: pc not restarting; and "ups unavailable" messages

[nut . user . u830]

> 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 is reliable for that particular box.

Thanks. This matches my limited experience from yesterday with 2 computers 
including the one that's actually attached to the UPS I'm trying to get to 
work. 

If power is cut and restored when the computer is already off (and with the 
always-on BIOS setting), then: short off time, it doesn't notice and it remains 
off; long off time, it does come back on. I did one minute for "long" but 
didn't do binary partitioning of the interval to assess the exact threshold.___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] testing shutdown: pc not restarting; and "ups unavailable" messages

[Charles Lepple]

On Feb 1, 2018, at 10:58 AM, nut.user.u...@neverbox.com wrote:
> 
> According to the theory above, this should have caused the computer to detect 
> a power loss and turn itself back on. Instead it remained off (as I expected).

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 is reliable for that particular box.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] testing shutdown: pc not restarting; and "ups unavailable" messages

[nut . user . u830]

> > where in the filesystem should I be looking for the NUT shutdown script 
> > please?
> 
> It's the SHUTDOWNCMD in upsmon.conf

Thanks!

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] testing shutdown: pc not restarting; and "ups unavailable" messages

[nut . user . u830]

> 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 computer 
> to detect a power loss and turn itself back on. Instead it remained off (as I 
> expected).

In light of the last few messages I tried again but this time I kept it off for 
a few minutes rather than a few seconds before plugging the power cord back in, 
and this time it did come back on. Wow! (That's still the computer at work, 
though.)

If it is possible that this is motherboard-dependent I shall have to try again 
with the media server computer at home that is supposed to be rescued by the 
UPS. I envisage two cases.

1) if the computer does restart after I switch it off and then pull and (a 
while later) reinsert the power cord, then it stands a chance of working with 
the UPS, but I still need to understand why it hasn't worked so far.

2) if the computer stays off, there is little hope that any software 
configuration of nut will make the ups turn it back on; except perhaps for 
Lee's suggestion of "turning it off but not quite". On that note, where in the 
file system should I be looking for the NUT shutdown script please?




___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] testing shutdown: pc not restarting; and "ups unavailable" messages

[Ken Olum]

After you shut down your PC, it should be in a state where it knows that
it was shut down manually and should stay shut down.  When the line
power goes off, it forgets this state, so when you restore the line
power it should boot.  That is what the BIOS setting is supposed to
provide.  This is how it works, for example, on my Dell Inspiron 3668
running Ubuntu.

If it doesn't work, I don't see any way that you can get automatic
restart after the power is restored.

Ken

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] testing shutdown: pc not restarting; and "ups unavailable" messages

[nut . user . u830]

> 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 UPS power outlets.


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 never imagined that... I guess it's something I could try independently, once 
I find a quiet time with no disk activity when it's OK to shut down that 
computer.

> I looked at the product documentation at 
> https://www.cyberpower.com/uk/en/product/sku/Value800EILCD and could find 
> nothing about shutting down the UPS power outlets. Although the 800EILCD is 
> able 
> to turn off the beeper, this in itself is not sufficient. The proposed 
> typical 
> applications include NAS & Servers so it should be possible. Perhaps you 
> could 
> ask the Cyber Power support people if the 800EILCD has this function.

What exactly should I be asking? "Is it possible to switch off the power to the 
outgoing outlet by sending a command to the UPS via USB, and what is that 
command?" They provide their own Linux software, which I ignored in favour of 
NUT, so I suspect their answer, if any, might be limited to what can be done 
through that.

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

I'll try this tonight when I'm back home.

Many thanks for your help.

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] testing shutdown: pc not restarting; and "ups unavailable" messages

[Roger Price]

On Thu, 1 Feb 2018, nut.user.u...@neverbox.com wrote:

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,


Have you checked the BIOS option "Power on when AC Returns"?

Does the UPS unit perform a delayed power off some time after the box shuts 
down?


Roger

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser