Nut upsuser - Oct 2022 - APC SmartUPS powercycles when power returns

Hello.

I've got an APC SmartUPS 1500: it's connected via USB and I'm using
the
usbhid-ups driver. This used to work properly until recently.

Now, when power goes out it keeps on going on battery potentially for 
several minutes, but, the moment line returns, I hear a click and power 
is cycled on the outlets (so every computer is rebooted forcily).

I'm thinking about a hardware issue, but could it be that NUT is 
instructing it to do so?

All I see in the logs before the nasty event is: "upsmon[89989]: UPS 
APC at localhost on battery".
So I don't think a low battery status was reached and/or a shutdown 
initiated.



# upsc APC
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.runtime: 3540
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 27.1
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 1500
device.serial: AS1425215186
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 15
driver.parameter.pollinterval: 2
driver.parameter.pollonly: true
driver.parameter.port: auto
driver.parameter.synchronous: auto
driver.version: 2.8.0
driver.version.data: APC HID 0.98
driver.version.internal: 0.47
driver.version.usb: libusb-1.0.0 (API: 0x1000102)
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: UPS 08.8 / ID=18
ups.mfr: American Power Conversion
ups.mfr.date: 2014/06/20
ups.model: Smart-UPS 1500
ups.productid: 0003
ups.serial: AS1425215186
ups.status: OL
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.vendorid: 051d



  bye & Thanks
	av.

Andrea Venturoli via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>
writes:
> I've got an APC SmartUPS 1500: it's connected via USB and I'm
using
> the usbhid-ups driver. This used to work properly until recently.
>
> Now, when power goes out it keeps on going on battery potentially for
> several minutes, but, the moment line returns, I hear a click and
> power is cycled on the outlets (so every computer is rebooted
> forcily).
>
> I'm thinking about a hardware issue, but could it be that NUT is
> instructing it to do so?
I suggest an experiment:

  disconnect the USB cable to the NUT computer

  turn off power for 5 minutes

  turn power back on

and see what happens
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20221011/130493d4/attachment.sig>

On October 11, 2022 3:29:46 PM GMT+03:00, Andrea Venturoli via Nut-upsuser
<nut-upsuser at alioth-lists.debian.net> wrote:
>Hello.
>
>I've got an APC SmartUPS 1500: it's connected via USB and I'm
using the usbhid-ups driver. This used to work properly until recently.
>
>Now, when power goes out it keeps on going on battery potentially for
several minutes, but, the moment line returns, I hear a click and power is
cycled on the outlets (so every computer is rebooted forcily).
>
>I'm thinking about a hardware issue, but could it be that NUT is
instructing it to do so?
Do a test with the data cable disconnected so that nut cannot
"instruct" it to do anything.



>
>All I see in the logs before the nasty event is: "upsmon[89989]: UPS
APC at localhost on battery".
>So I don't think a low battery status was reached and/or a shutdown
initiated.
Indeed, you should also see a sequence corresponding to LB and shutdown.


wolfy

On Tue, 11 Oct 2022, Andrea Venturoli via Nut-upsuser wrote:
> I've got an APC SmartUPS 1500: it's connected via USB and I'm
using the
> usbhid-ups driver. This used to work properly until recently.
>
> Now, when power goes out it keeps on going on battery potentially for
several
> minutes, but, the moment line returns, I hear a click and power is cycled
on
> the outlets (so every computer is rebooted forcily).
>
> I'm thinking about a hardware issue, but could it be that NUT is
instructing
> it to do so?
>
> All I see in the logs before the nasty event is: "upsmon[89989]: UPS 
> APC at localhost on battery".
> So I don't think a low battery status was reached and/or a shutdown 
> initiated.
>
> # upsc APC
> battery.charge: 100
> battery.charge.low: 10
> battery.charge.warning: 50
...
> ups.beeper.status: enabled
> ups.delay.shutdown: 20
I do not see a line such as ? ups.delay.start: 30 ? in the upsc output.  Is this
UPS capable of reacting to an early power-return and cancelling the shutdown?
> ups.firmware: UPS 08.8 / ID=18
> ups.mfr: American Power Conversion
> ups.mfr.date: 2014/06/20
How old is the battery?
> ups.model: Smart-UPS 1500
It's difficult to say more without knowing exactly where you are in the
sequence
of events and the timing as listed in 
https://rogerprice.org/NUT/ConfigExamples.A5.pdf chapter 2.6 The shutdown story 
for a simple server.

Roger