Problems with Ever Duo II Pro UPS

[beton]

I've connected my UPS, the Ever Duo II Pro, via usb (no serial port unfortunately) to my freenas box with Asrock C2750D4I. The device is recognized, dmesg returns:

Code:

ugen0.6: <INNO TECH> at usbus0

After configuring the UPS service to use usb_blazer and enabling it, everything is fine for about 5-10 minuts. After that, there is COMMBAD event followed by NOCOMM. I've checked if maybe the device got somehow disconnected, however dmesg doesn't indicate anything like that. I've even replaced the usb cable, but nothing changed. Furthermore, if I restart the UPS service, everything is fine for another 5-10 minutes.

Am I doing something wrong (like using unsupported UPS - even though it's on NUT supported list), or maybe there's a bug that causes the connection to drop?

I've also attached /var/log/messages from the moment the service is started till COMMBAD

Code:

Sep 17 16:52:25 doomtrain notifier: nut not running? (check /var/db/nut/upsd.pid).
Sep 17 16:52:25 doomtrain notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid).
Sep 17 16:52:25 doomtrain notifier: nut_upslog not running? (check /var/db/nut/upslog.pid).
Sep 17 16:52:25 doomtrain notifier: nut not running? (check /var/db/nut/upsd.pid).
Sep 17 16:52:25 doomtrain root: Unknown USB device: vendor 0x0665 product 0x5161 bus uhub1
Sep 17 16:52:26 doomtrain notifier: Supported UPS detected with megatec protocol
Sep 17 16:52:29 doomtrain notifier: Vendor information unavailable
Sep 17 16:52:29 doomtrain notifier: No values provided for battery high/low voltages in ups.conf
Sep 17 16:52:29 doomtrain notifier:
Sep 17 16:52:29 doomtrain notifier: Using 'guestimation' (low: 10.400000, high: 13.000000)!
Sep 17 16:52:29 doomtrain notifier: Battery runtime will not be calculated (runtimecal not set)
Sep 17 16:52:29 doomtrain notifier: Network UPS Tools - UPS driver controller 2.7.1
Sep 17 16:52:29 doomtrain notifier: Starting nut.
Sep 17 16:52:29 doomtrain notifier: fopen /var/db/nut/upsd.pid: No such file or directory
Sep 17 16:52:29 doomtrain notifier: listening on 127.0.0.1 port 3493
Sep 17 16:52:29 doomtrain notifier: Connected to UPS [ups]: blazer_usb-ups
Sep 17 16:52:29 doomtrain notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid).
Sep 17 16:52:29 doomtrain notifier: Starting nut_upsmon.
Sep 17 16:52:29 doomtrain notifier: kill: No such process
Sep 17 16:52:29 doomtrain notifier: UPS: ups (master) (power value 1)
Sep 17 16:52:29 doomtrain notifier: nut_upslog not running? (check /var/db/nut/upslog.pid).
Sep 17 16:52:29 doomtrain notifier: Starting nut_upslog.
Sep 17 16:59:22 doomtrain blazer_usb[23959]: Permissions problem: Input/output error
Sep 17 16:59:22 doomtrain upsd[23961]: Can't connect to UPS [ups] (blazer_usb-ups): No such file or directory
Sep 17 16:59:24 doomtrain upsmon[23986]: Poll UPS [ups] failed - Driver not connected
Sep 17 16:59:24 doomtrain upsmon[23986]: Communications with UPS ups lost
Sep 17 16:59:29 doomtrain upsmon[23986]: Poll UPS [ups] failed - Driver not connected

 

[Yatti420]

Are you able to pull up any values from the UPS before it drops? Have you tried a different driver if available? New USB cable etc? it looks like near the end of the log you have permission issue and or IO error.. Does it usually make it about 7 minutes?

Make sure its on the NUT compatibility list..

 

[beton]

Are you able to pull up any values from the UPS before it drops? Have you tried a different driver if available? New USB cable etc? it looks like near the end of the log you have permission issue and or IO error.. Does it usually make it about 7 minutes?

Make sure its on the NUT compatibility list..

Yes, upsc returns UPS' values. I've already checked other cable to no avail. I guess it takes about 7 minutes, but sometimes it works longer.
I'm not sure about trying other driver - this UPS according to the NUT compatibility list is supposed to work with usb_blazer. The weird thing is that when the UPS service is restarted, the device is connected properly until the connection is dropped.
A really dirty workaround would be to have cron job restart the service every 5 minutes, but I don't know which script is started when the service is started via web interface.

 

[Yatti420]

I would probably post on the but forum to see if an issue exists.

Sent from my SGH-I257M using Tapatalk 2