[Nut-upsuser] MGE EllipseMAX 1500 shuts down after a few hours

[raul]

> If there is no message to NUT, I would consider opening a trouble 
> ticket with Eaton. It is possible that there is a known issue and/or 
> a firmware upgrade.
What kind of message to NUT? In the log (syslog) there is no other 
message registered. In nut.log only this appears:

> Dec  1 08:10:54 openmediavault upsd[5284]: Data for UPS [ellipsemax] 
> is stale - check driver
> Dec  1 08:10:56 openmediavault upsmon[5313]: Poll UPS 
> [ellipsemax at localhost] failed - Data stale
> Dec  1 08:10:56 openmediavault upsmon[5313]: Communications with UPS 
> ellipsemax at localhost lost
> Dec  1 08:10:56 openmediavault upssched[10965]: Executing command: 
> notify
> Dec  1 08:10:56 openmediavault upssched-cmd: Communications with the 
> UPS ellipsemax at localhost are lost
> Dec  1 08:10:58 openmediavault upsd[5284]: UPS [ellipsemax] data is 
> no longer stale
> Dec  1 08:11:01 openmediavault upsmon[5313]: Communications with UPS 
> ellipsemax at localhost established
> Dec  1 08:11:01 openmediavault upssched[10998]: Executing command: 
> notify
> Dec  1 08:11:01 openmediavault upssched-cmd: Communications with the 
> UPS ellipsemax at localhost are established
> Dec  1 13:02:51 openmediavault upsd[2185]: fopen 
> /var/run/nut/upsd.pid: No such file or directory
> Dec  1 13:02:51 openmediavault upsd[2185]: listening on 0.0.0.0 port 
> 3493
[...]


Note the time lapse from 08:11 to 13:02. The UPS shutdown at 08:11. 
These shutdowns only happen when the UPS has the USB cable connected 
and being monitored. I have not tested with the serial port. At least 
the times I have checked, the UPS shuts down after those messages 
appear.

The UPS is EOL (is quite old), so there is no support from them. This 
UPS was working but something has been changed in NUT that now the 
device turns off.
I have increased pollfreq value in the driver to 45 seconds. In 
upsmon.conf POLLFREQ is set to 10 seconds, POLLFREQALERT 10 seconds, 
HOSTSYNC 15, DEADTIME 30. MAXAGE is 60 seconds. This has turned into an 
earlier shutdown. Instead of around 6 hours it cut the power in 45 
minutes. Previous values were POLLFREQ 5, POLLFREQALERT 5, HOSTSYNC 15, 
DEADTIME 15 and MAXAGE 15.

> Also, given that the load is only 12%, double-check that the UPS is 
> not configured for any power saving features that might cause the 
> shutdown ("ECO mode" or similar). NUT does not get a notification for 
> that event the way that it gets a normal LB shutdown notification.

Are you referring to NUT (ups.conf) or to the UPS itself? I have 
checked the instruction manual and it says nothing about ECO modes. It 
talks only about disabling alarms or changing sensitivity to source 
voltage variations.

Thanks.


En ds., 1 de de des. 2018 a les 11:48 P. M., Charles Lepple 
<clepple at gmail.com> ha escrit:
> On Dec 1, 2018, at 3:45 PM, raul <raulvior.bcn at gmail.com> wrote:
>> 
>>  The UPS is connected to the following environment:
>>  OS: Debian GNU/Linux 9.6 (stretch)
>>  NUT version: 2.7.4-5
>>  Device output from lsusb: 0463:ffff MGE UPS Systems UPS
>>  Model name: MGE EllipseMAX 1500
>>  URLs:
>>  
>> http://powerquality.eaton.com/Products-services/Backup-Power-UPS/Ellipse-MAX-eol.aspx?cx=97&GUID=7BB6CD53-9F6D-4D62-B326-1099F137BF8D
>>  http://powerquality.eaton.com/68558.aspx?cx=97
>> 
>>  The problem is that at some point, after being online for a while, 
>> the UPS shuts down, cutting the power of all devices without sending 
>> any command. The log of the master monitor registers a USB error 
>> before the events of the OS booting process after turning on again 
>> the UPS. I have attached the output
>> 
>>  Dec  1 21:35:18 openmediavault kernel: [19503.643123] usb 3-2: 
>> usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 6 ret 
>> -110
>>  Dec  1 21:35:26 openmediavault kernel: [19511.835644] usb 3-2: 
>> usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret 
>> -110
> 
> "ret -110" is a timeout, and on other MGE models, I see those 
> sporadically throughout the day. Those might even correspond to the 
> "libusb_get_interrupt: Connection timed out" lines in the debug log.
> 
> If there is no message to NUT, I would consider opening a trouble 
> ticket with Eaton. It is possible that there is a known issue and/or 
> a firmware upgrade.
> 
> Also, given that the load is only 12%, double-check that the UPS is 
> not configured for any power saving features that might cause the 
> shutdown ("ECO mode" or similar). NUT does not get a notification for 
> that event the way that it gets a normal LB shutdown notification.
> 
> --
> Charles Lepple
> clepple at gmail
> 
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20181202/4923192d/attachment.html>