UPS, libusb_get_interrupt & mon password

[TeChn4K]

Hi all,

I currently have two issues with my UPS service :

See my debug.log when I start my UPS service.

Code:

  File "./freenasUI/services/models.py", line 1354, in __init__
    self.ups_monpwd = notifier().pwenc_decrypt(self.ups_monpwd)
  File "./freenasUI/middleware/notifier.py", line 3284, in pwenc_decrypt
    encrypted = base64.b64decode(encrypted)
  File "/usr/local/lib/python3.6/base64.py", line 87, in b64decode
    return binascii.a2b_base64(s)
binascii.Error: Incorrect padding

Feb  8 15:02:42 freenas usbhid-ups[7992]: libusb_get_interrupt: Unknown error
Feb  8 15:03:04 freenas usbhid-ups[75595]: libusb_get_interrupt: Unknown error
Feb  8 15:03:19 freenas usbhid-ups[75595]: libusb_get_interrupt: Unknown error

On this bug report (https://redmine.ixsystems.com/issues/34327), I can read an advice to get ride of the first error in my log. I have to set a new password in my UPS service form. But the issue is still here after...

On this same bug report (and the FreeNAS guide, section UPS), the advice to get ride of the annoying interrupt error is to set a larger pollinterval (pollinterval = 15) in ups.conf of my UPS service form. But guess what... the issue is still here, every 15s !

By the way, my upsd works great in case of power loss or every thing else ...

UPS: Eaton PRO 650
driver: usbhid-ups

Any help ?
Thanks!

 

[dlavigne]

Were you able to resolve this?

 

[TeChn4K]

unfortunately no ...
Same issue on your side?

 

[dlavigne]

Does a larger polling interval resolve it?

 

[TeChn4K]

I have already tried 15, 20 or 30s.. Without any success

 

[2nd-in-charge]

libusb_get_interrupt: Unknown error

I've been having the same issue with Eaton 5S700. Setting Poll interval to 30s reduces the amount of spam, but the error comes every 30 seconds without fail. I then found this thread on Nas4Free forums:
https://www.xigmanas.com/forums/viewtopic.php?t=13770
setting "pollonly" instead of "pollinterval=30" in ups.conf via the GUI seems to fix the problem.
Or at least that's a workaround.

 

[Sneffets]

Any resolution? Same issue here with an running on FreeNAS-11.2-U4.1

Jun 21 15:26:32 freenas uwsgi: [services.forms:1383] Failed to decrypt UPS mon password

Traceback (most recent call last):

File "./freenasUI/services/models.py", line 1381, in __init__

self.ups_monpwd = notifier().pwenc_decrypt(self.ups_monpwd)

File "./freenasUI/middleware/notifier.py", line 3173, in pwenc_decrypt

encrypted = base64.b64decode(encrypted)

File "/usr/local/lib/python3.6/base64.py", line 87, in b64decode

return binascii.a2b_base64(s)

binascii.Error: Incorrect padding

Jun 21 15:26:32 freenas uwsgi: [services.forms:1383] Failed to decrypt UPS mon password

Traceback (most recent call last):

File "./freenasUI/services/models.py", line 1381, in __init__

self.ups_monpwd = notifier().pwenc_decrypt(self.ups_monpwd)

File "./freenasUI/middleware/notifier.py", line 3173, in pwenc_decrypt

encrypted = base64.b64decode(encrypted)

File "/usr/local/lib/python3.6/base64.py", line 87, in b64decode

return binascii.a2b_base64(s)

binascii.Error: Incorrect padding

root@freenas:~ # usbconfig
ugen6.1: <Intel UHCI root HUB> at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
ugen8.1: <Intel EHCI root HUB> at usbus8, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen1.1: <Intel UHCI root HUB> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
ugen2.1: <Intel UHCI root HUB> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
ugen3.1: <Intel UHCI root HUB> at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
ugen5.1: <Intel UHCI root HUB> at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
ugen7.1: <Intel UHCI root HUB> at usbus7, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
ugen4.1: <Intel EHCI root HUB> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen0.1: <0x1106 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
ugen0.2: <vendor 0x2109 USB2.0 Hub> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA)
ugen5.2: <CPS CP1500AVRLCDa> at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (2mA)
ugen3.2: <American Megatrends Inc. Virtual Keyboard and Mouse> at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (0mA)
ugen8.2: <Lexar microSD RDR> at usbus8, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)
ugen8.3: <Lexar microSD RDR> at usbus8, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)

 

[TackleMcClean]

I had the same issue, the error being spammed every 2 seconds.
Added "pollonly" to the ups.conf section via the GUI and it only shows upp the one time when the service is restarted at save.

However, I have this problem that FreeNAS does not shutdown after the set 30 seconds, despite using the "UPS goes on battery" setting. No idea how to fix.

 

[Sneffets]

I would assume reason that it isn't shutting down is due to the error...my assumption is that "Failed to decrypt UPS mon password" and repeated attempts are due to the lack of FreeNAS to connect to the UPS...as this used to work in previous versions (I don't know when I started having the issues, as I noticed the error when searching the logs for the reasons my Snapshot Sync Tasks aren't working).