usbhid-ups disconnected message, yet UPS is communicating

Status
Not open for further replies.

GaiusBaltar

Explorer
Joined
Jan 15, 2014
Messages
61
Weird issues that i'm not sure if are serious or just false positives that i can ignore.
I've got a CyberPower CTS1300AL UPS (costco rebranded CPS1350AVRLCD) connected to my server
settings under the UPS service are:
  • mode: Master
  • port: /dev/ugen1.3
  • Driver: CyberPower Systems UPS 2 CPS1350AVRLCD USB (usbhids-ups)
  • shutdown mode: goes on battery
  • shutdown timer: 300
Configured and started the service and everything was fine.

About 3o mins later i would keep getting this event in my syslog:
Code:
root: Unknown USB device: vendor 0x0764 product 0x0501 bus /dev/ugen1.3

i'd see that pop up every 15-30 mins or so.
after doing some research, i followed the guidelines from this blog and hid the annoyingmessages by adding the below code to to the necessary devd.conf file locations:
Code:
nomatch 10 {
    match "bus" "uhub[0-9]+";
    match "vendor" "0x0764";
    match "product" "0x0501";
};


Everything was fine until about 2-3 hrs after enabling the UPS service. then i started seeing the following syslog messages below.
These started about 3 hrs after the last reboot (which was Feb2 @ 8:30pm):

Code:
Feb  3 23:01:20 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver
Feb  3 23:01:23 freeNAS upsmon[2725]: Poll UPS [CyberPower_CTS1300AL] failed - Data stale
Feb  3 23:01:23 freeNAS upsmon[2725]: Communications with UPS CyberPower_CTS1300AL lost
Feb  3 23:01:24 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale
Feb  3 23:01:28 freeNAS upsmon[2725]: Communications with UPS CyberPower_CTS1300AL established
Feb  4 01:18:51 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver
Feb  4 01:18:52 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale
Feb  4 01:36:29 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver
Feb  4 01:36:30 freeNAS upsmon[2725]: Poll UPS [CyberPower_CTS1300AL] failed - Data stale
Feb  4 01:36:30 freeNAS upsmon[2725]: Communications with UPS CyberPower_CTS1300AL lost
Feb  4 01:36:34 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale
Feb  4 01:36:35 freeNAS upsmon[2725]: Communications with UPS CyberPower_CTS1300AL established
Feb  4 01:38:36 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver
Feb  4 01:38:36 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale
Feb  4 02:59:21 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver
Feb  4 02:59:22 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale
Feb  4 03:15:49 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver
Feb  4 03:15:49 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale
Feb  4 03:19:44 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver
Feb  4 03:19:47 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale
Feb  4 06:32:39 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver
Feb  4 06:32:39 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale
Feb  4 09:06:51 freeNAS usbhid-ups[2715]: Got disconnected by another driver: Device busy
Feb  4 09:28:24 freeNAS usbhid-ups[2715]: Got disconnected by another driver: Device busy


i've checked the ups conf files and everything appears in order:
Code:
[root@freeNAS ~]# cat /usr/local/etc/nut/upssched.conf                 
CMDSCRIPT  /usr/local/bin/custom-upssched-cmd                         
PIPEFN      /var/db/nut/upssched.pipe                                 
LOCKFN      /var/db/nut/upssched.lock                         
AT NOCOMM  * EXECUTE EMAIL                                           
AT COMMBAD  * START-TIMER COMMBAD 10                                   
AT COMMOK  * CANCEL-TIMER COMMBAD COMMOK                             
AT FSD      * EXECUTE EMAIL                                           
AT LOWBATT  * EXECUTE EMAIL                                           
AT ONBATT  * START-TIMER ONBATT 300                                   
AT ONBATT  * EXECUTE EMAIL                                           
AT ONLINE  * CANCEL-TIMER ONBATT ONLINE                               
AT ONLINE  * EXECUTE EMAIL                                           
AT REPLBATT * EXECUTE EMAIL                                           
AT SHUTDOWN * EXECUTE EMAIL       
 
_______________________________________________________
 
[root@freeNAS ~]# cat /usr/local/etc/nut/upsmon.conf                   
FINALDELAY 300                                                         
MONITOR CyberPower_CTS1300AL 1 upsmon fixmepass master                 
NOTIFYCMD "/usr/local/sbin/upssched"                                   
NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC                                     
NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC                                   
NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC                                     
NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC                                   
NOTIFYFLAG COMMOK SYSLOG+WALL+EXEC                                     
NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC                                   
NOTIFYFLAG NOCOMM SYSLOG+EXEC                                         
NOTIFYFLAG FSD SYSLOG+EXEC                                             
NOTIFYFLAG SHUTDOWN SYSLOG+EXEC                                       
SHUTDOWNCMD "/sbin/shutdown -p now"
 
________________________________________________________     
 
[root@freeNAS ~]# cat /usr/local/etc/nut/ups.conf                     
[CyberPower_CTS1300AL]                                                 
    driver = usbhid-ups                                               
    port = /dev/ugen1.3                                               
    desc = "UPS"                


I also checked to ensure i only have 1 copy of the upsmon and usbhids daemons running:
Code:
[root@freeNAS ~]# ps -aux | grep ups                                                                            
uucp        2715   0.0  0.0  14232   2480 ??  Ss    8:30PM    0:04.27 /usr/local/libexec/nut/usbhid-ups -a CyberPower_CTS1300AL     
uucp        2717   0.0  0.0  20356   3712 ??  Ss    8:30PM    0:00.83 /usr/local/sbin/upsd                                          
uucp        2720   0.0  0.0  20332   3676 ??  Is    8:30PM    0:00.05 /usr/local/bin/upslog -s CyberPower_CTS1300AL -l /var/log/ups.
root        2723   0.0  0.0  20336   3680 ??  Is    8:30PM    0:00.00 /usr/local/sbin/upsmon localhost                              
uucp        2725   0.0  0.0  20336   3704 ??  S     8:30PM    0:00.72 /usr/local/sbin/upsmon localhost                      
___________________________________________________________________________________                                 
[root@freeNAS ~]# top | grep ups                                       
2715 uucp          1  20    0 14232K  2436K select  6  0:04  0.00% usbhid-ups
2717 uucp          1  20    0 20356K  3712K select  0  0:01  0.00% upsd
2725 uucp          1  20    0 20336K  3704K nanslp  3  0:01  0.00% upsmon    


(I assume it is correct behavior to have 2 upsmon processes: 1 under root's account and one under uucp's account)

given all that, communication still looks good/normal:
Code:
[root@freeNAS ~]# upsc CyberPower_CTS1300AL
battery.charge: 100   
battery.charge.low: 10   
battery.charge.warning: 20
battery.mfr.date: CPS   
battery.runtime: 3932   
battery.runtime.low: 300
battery.type: PbAcid   
battery.voltage: 13.9   
battery.voltage.nominal: 12
device.mfr: CPS       
device.model:  CP 1350C   
device.type: ups         
driver.name: usbhid-ups   
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ugen1.3
driver.version: 2.6.5       
driver.version.data: CyberPower HID 0.3
driver.version.internal: 0.37
input.transfer.high: 140
input.transfer.low: 90
input.voltage: 123.0
input.voltage.nominal: 120
output.voltage: 123.0
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 7       
ups.mfr: CPS     
ups.model:  CP 1350C
ups.productid: 0501
ups.realpower.nominal: 298
ups.status: OL   
ups.test.result: Done and warning
ups.timer.shutdown: -60
ups.timer.start: 0
ups.vendorid: 0764  



Finally after all that post spam above, i tried unplugging the UPS from the wall.
I immediately got the UPS ONBATT alert email. and after 5 mins, the SHUTDOWN email (tho even tho the console message said the system was shutting down, it still took an additional 3-5 mins or so (wasn't timing it like i should have) before the shutdown actually commenced.

Sorry for this long as hell mega-post
Any ideas?
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
I'm not a UPS pro. I know enough to be very dangerous, but not enough to really fix anything. But that looks like a device that isn't compatible with the included driver.
 

GaiusBaltar

Explorer
Joined
Jan 15, 2014
Messages
61
I'm not a UPS pro. I know enough to be very dangerous, but not enough to really fix anything. But that looks like a device that isn't compatible with the included driver.


which is frustrating since it shows up as "CP 1350C CPS" which is the correct model ID for the CP1350AVRLCD:
Code:
[root@freNAS ~]# usbconfig | grep ugen1.3                                 
ugen1.3: <CP 1350C CPS> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (50mA)

so in theory, it should work with the included driver.

i don't THINK any permissions are incorrect for anything NUT related:
Code:
[root@freeNAS ~]# ls -l /usr/local/etc/nut | grep -v sample               
total 193                                                                 
-r--r--r--  1 root  wheel  10494 Dec 20 16:36 cmdvartab                   
-r--r--r--  1 root  wheel  50980 Dec 20 16:36 driver.list                 
-r--r-----  1 root  uucp      89 Feb  3 20:30 ups.conf                     
-r--r-----  1 root  uucp      17 Feb  3 20:30 upsd.conf                   
-r--r-----  1 root  uucp      54 Feb  3 20:30 upsd.users                   
-r--r-----  1 root  uucp    446 Feb  3 20:30 upsmon.conf                 
-r--r-----  1 root  uucp    477 Feb  3 20:30 upssched.conf
 
[root@freeNAS ~]# ls -l /dev/ugen1.3                                       
lrwxr-xr-x  1 root  wheel  9 Feb  3 20:29 /dev/ugen1.3 -> /dev/usb/1.3.0
   
[root@freeNAS ~]# ls -l /dev/usb/1.3.0                                     
crw-rw----  1 root  uucp  0x9e Feb  3 20:29 /dev/usb/1.3.0      


again, it does seem to work (when unplugged from the wall) and report data (upsc command). just annoying/concerning that it's filling up my syslog.
 

Dusan

Guru
Joined
Jan 29, 2013
Messages
1,165
I also see brief (10 seconds) UPS USB disconnects (Eaton Ellipse ECO 650). However, it only happens about once per two weeks. I increased the upssched.conf COMMBAD timeout (to 30 seconds) so that it doesn't email me, however it still triggers the nightly (periodic) mail with kernel USB messages.
 

GaiusBaltar

Explorer
Joined
Jan 15, 2014
Messages
61
I also see brief (10 seconds) UPS USB disconnects (Eaton Ellipse ECO 650). However, it only happens about once per two weeks. I increased the upssched.conf COMMBAD timeout (to 30 seconds) so that it doesn't email me, however it still triggers the nightly (periodic) mail with kernel USB messages.


oddly enough, i haven't gotten a single COMMBAD alert during all of this. I upped the pollinterval in the ups.conf (via the auxillary field in the GUI) to 5 (from the default 2 reported via running the upsc command). this seemed to decrease the frequency of the disconnect and stale messages in the syslog.
perhaps I'll up it to 10 (and leave upsmon's pollfreq set to 30) and see if the messages stop.
 

GaiusBaltar

Explorer
Joined
Jan 15, 2014
Messages
61
on a related note, is my thinking correct with this....
in upssched.conf, the value: START-TIMER ONBATT is set to 300. I assume that this is what is set and changed when i set the SHUTDOWN TIMER value to 300 in the GUI.

I noticed that in upsmon.conf that FINALDELAY is also set to 300.
Given that FINALDELAY is the time (in seconds) between sending the SHUTDOWN notify (and associated SHUTDOWN console message and email) and actually issuing the shutdown command to the system, I have the following question:
Does this mean that once on battery, my system will wait 300 seconds (5mins), then issue the NOTIFY_SHUTDOWN message/email, but then wait another 300 sec before shutting down - meaning a total 10 min batt run time before shutdown commences?

obviously i can test this to see if im right, but i figured id ask as i haven't have a chance to time and test that.
 

jyavenard

Patron
Joined
Oct 16, 2013
Messages
361
does this UPS has a serial port?

it may be more reliable to use that.

On the new ASRock board I got, I see USB messages very often, even for gears that have otherwise worked fine for years.
So in the mean time, I've plugged the UPS to the serial port to avoid this problem
 

Dusan

Guru
Joined
Jan 29, 2013
Messages
1,165
in upssched.conf, the value: START-TIMER ONBATT is set to 300. I assume that this is what is set and changed when i set the SHUTDOWN TIMER value to 300 in the GUI.I noticed that in upsmon.conf that FINALDELAY is also set to 300.

Given that FINALDELAY is the time (in seconds) between sending the SHUTDOWN notify (and associated SHUTDOWN console message and email) and actually issuing the shutdown command to the system, I have the following question:
Does this mean that once on battery, my system will wait 300 seconds (5mins), then issue the NOTIFY_SHUTDOWN message/email, but then wait another 300 sec before shutting down - meaning a total 10 min batt run time before shutdown commences?
FreeNAS actually sets both the ONBATT timer and the FINALDELAY to the same value you enter in GUI. So, in reality the shutdown delay is twice as long as what you set in GUI.
 

GaiusBaltar

Explorer
Joined
Jan 15, 2014
Messages
61
does this UPS has a serial port?

it may be more reliable to use that.

On the new ASRock board I got, I see USB messages very often, even for gears that have otherwise worked fine for years.
So in the mean time, I've plugged the UPS to the serial port to avoid this problem


unfortunately, it does not. just has the USB connection.

increasing the POLLINTERVAL to 10 though has pretty much eliminated the stale/no longer stale messages. but i still receive the disconnected messages about once every 2-3hrs.


FreeNAS actually sets both the ONBATT timer and the FINALDELAY to the same value you enter in GUI. So, in reality the shutdown delay is twice as long as what you set in GUI.

ah, so my thinking was correct. guess if i want it to power down after 5 mins, i need to set it to 150secs. thanks for confirming that for me! :)
 

GaiusBaltar

Explorer
Joined
Jan 15, 2014
Messages
61
small update:

in the GUI, i changed the port from /dev/ugen1.3 to "Auto".

This seems to oddly have made a positive impact. Though I wouldn't say it's fixed, (and ill probably be proved wrong in the syslog in the morning), but, so far, after making that change and restarting the UPS services via the GUI around 11:30am today, i've only see the usbhid-ups disconnect twice (4-5hrs apart) and have yet to see the DATA STALE/NO LONGER STALE messages at all.

Code:
Feb  6 11:58:54 freeNAS notifier: Starting nut_upslog.
Feb  6 16:48:51 freeNAS usbhid-ups[65586]: Got disconnected by another driver: Device busy
Feb  6 20:48:27 freeNAS usbhid-ups[65586]: Got disconnected by another driver: Device busy


to recap, the only change's ive made from the original config were:
adding auxiliary parameter "pollinterval=10" to usp.conf via GUI
changing port to "auto" via GUI
 

jyavenard

Patron
Joined
Oct 16, 2013
Messages
361
small update:

in the GUI, i changed the port from /dev/ugen1.3 to "Auto".


according to nut documentation, the port value is ignored when you choose usbhid as drivers... You could put whatever you want in there, not just auto and it would still work

so it's likely what you're seeing is pure coincidence and not related to the change of port value
 

Pete

Dabbler
Joined
Oct 1, 2013
Messages
12
Noob question: how do I edit /usr/local/etc/nut/upssched.conf and make the changes stick?

Thanks.
 

SkyMonkey

Contributor
Joined
Mar 13, 2013
Messages
102
I have the exact same UPS and have similar errors logged from time to time. Never caused any issues as far as I could tell (through many tests and a few actual outages). The console errors seem to be gone with 9.1.2.x as far as I've noticed.
 

GaiusBaltar

Explorer
Joined
Jan 15, 2014
Messages
61
Noob question: how do I edit /usr/local/etc/nut/upssched.conf and make the changes stick?

Thanks.

you need to mount the filesystem in write mode first:
Code:
mount -uw /

and then remount in readonly mode once you're done editing:
Code:
mount -ur /




I have the exact same UPS and have similar errors logged from time to time. Never caused any issues as far as I could tell (through many tests and a few actual outages). The console errors seem to be gone with 9.1.2.x as far as I've noticed.

i still get the device busy errors every few hours, even on 9.2.1.3. as you can see its sporadic throughout the day.

Code:
Mar 24 18:04:41 freeNAS usbhid-ups[2836]: Got disconnected by another driver: Device busy
Mar 24 19:36:32 freeNAS usbhid-ups[2836]: Got disconnected by another driver: Device busy
Mar 25 02:41:44 freeNAS usbhid-ups[2836]: Got disconnected by another driver: Device busy
Mar 25 04:07:45 freeNAS usbhid-ups[2836]: Got disconnected by another driver: Device busy
Mar 25 11:47:48 freeNAS usbhid-ups[2836]: Got disconnected by another driver: Device busy
Mar 25 15:56:59 freeNAS usbhid-ups[2836]: Got disconnected by another driver: Device busy
Mar 25 17:54:00 freeNAS usbhid-ups[2836]: Got disconnected by another driver: Device busy


it doesn't seem to impact the functionality of the UPS, just mucks up my syslog and console screen.

i also still get the unknown device... (as mentioned my original post) from the devd service every time i upgrade to a new version of freenas. but that's still solved by adding the code snippet to the devd.conf file
 

Pete

Dabbler
Joined
Oct 1, 2013
Messages
12
  1. mount -uw /

I tried this before but the changes I make to /usr/local/etc/nut/upssched.conf do not survive a reboot.

I ssh into my box (FreeNAS-9.2.1.3), mount the fs in write mode, edit upssched.conf (I checked that the changes have been saved), put the fs back in read only mode (which takes a while) and then reboot. Am I missing any steps?

Thanks.
 
D

dlavigne

Guest
The only way to get it to survive a reboot is to put in a feature request at bugs.freenas.org, asking that the ability to edit this file be added to the GUI. If you do so, post the issue number here.
 

Yatti420

Wizard
Joined
Aug 12, 2012
Messages
1,437
This doesn't make sense to me.. Cyber Power must of changed something hardware (USB controller?) wise.. The 850 PFC is perfect but seems any other model (in the same family) has issues with USB disconnects.. The only way I got any errors is wwhen I plug USB into NAS and the power cord into the wrong computer.. I'm doing a clean setup today so will see if it appears afterwards..
 

Pete

Dabbler
Joined
Oct 1, 2013
Messages
12
The only way to get it to survive a reboot is to put in a feature request at bugs.freenas.org, asking that the ability to edit this file be added to the GUI. If you do so, post the issue number here.

I see. So after I edit upssched.conf I have to restart the PSU service to make the changes stick until the next restart?

I am having a similar problem with a Supermicro X9SCL-F-O and an Eaton Ellipse ECO 800 btw., it is not a mayor issue, but still slightly worrisome. This is a new setup and I have yet to test the automatic shutdown functionality with a simulated power failure, so other than the log entries it seems to work fine (no false alarm shutdowns).

So far a typical day looks like this:
Code:
ugen1.3: <EATON> at usbus1 (disconnected)
uhub_reattach_port: giving up port reset - device vanished
ugen1.3: <EATON> at usbus1
ugen1.3: <EATON> at usbus1 (disconnected)
uhub_reattach_port: giving up port reset - device vanished
ugen1.3: <EATON> at usbus1
ugen1.3: <EATON> at usbus1 (disconnected)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
ugen1.3: <Unknown> at usbus1 (disconnected)
uhub_reattach_port: could not allocate new device
ugen1.3: <EATON> at usbus1
ugen1.3: <EATON> at usbus1 (disconnected)
uhub_reattach_port: giving up port reset - device vanished
ugen1.3: <EATON> at usbus1
ugen1.3: <EATON> at usbus1 (disconnected)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
ugen1.3: <Unknown> at usbus1 (disconnected)
uhub_reattach_port: could not allocate new device



Originally I got see these vendor id message more often, but not lately:
Code:
ugen1.3: <EATON> at usbus1 (disconnected)
usb_alloc_device: Failure selecting configuration index 0:USB_ERR_STALLED, port 1, addr 3 (ignored)
ugen1.3: <vendor 0x0463> at usbus1
ugen1.3: <vendor 0x0463> at usbus1 (disconnected)
ugen1.3: <EATON> at usbus1
ugen1.3: <EATON> at usbus1 (disconnected)


I thought these issues might be related.

- Edited for proper code display.
 

GaiusBaltar

Explorer
Joined
Jan 15, 2014
Messages
61
so. very interesting update. i happened to notice that my IPMI KVM wasnt responding today. i could log into the IPMI interface just fine, but when launching the KVM, the screen wouldnt accept any input.
performing an IKVM reset didn't work either. i ended up having to reset the entire BCM unit. doing so i saw in the freenas console the kvm virtual usb device get disconnected and reconnected. after the IPMI interface finished rebooting, i was able to successfully log in and get keyboard/mouse control via IPMI.

so, i waited until the next usbhid-ups device busy message. as soon as i saw that appear in the syslog, i logged into the IPMI interface again and launched the KVM window. sure enough, no keyboard/mouse activity.

restart the IPMI device and bam, KVM works as expected.

below is the output following the most recent upshid-ups device busy message followed by what gets logged in syslog when i perform an IPMI reset:
Code:
Apr  9 17:22:27 freeNAS usbhid-ups[2836]: Got disconnected by another driver: Device busy
 
Apr  9 18:16:18 freeNAS kernel: ums0: at uhub3, port 2, addr 3 (disconnected)
Apr  9 18:16:18 freeNAS kernel: ukbd0: at uhub3, port 2, addr 3 (disconnected)
Apr  9 18:16:19 freeNAS kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored)
Apr  9 18:16:19 freeNAS kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
Apr  9 18:16:20 freeNAS kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored)
Apr  9 18:16:20 freeNAS kernel: usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED
Apr  9 18:16:37 freeNAS kernel: ugen0.3: <Winbond Electronics Corp> at usbus0 (disconnected)
Apr  9 18:16:38 freeNAS kernel: ugen0.3: <Winbond Electronics Corp> at usbus0
Apr  9 18:16:38 freeNAS kernel: ums0: <Winbond Electronics Corp Hermon USB hidmouse Device, class 0/0, rev 1.10/0.01, addr 3> on usbus0
Apr  9 18:16:38 freeNAS kernel: ums0: 3 buttons and [XYZ] coordinates ID=0
Apr  9 18:16:38 freeNAS kernel: ukbd0: <Winbond Electronics Corp Hermon USB hidmouse Device, class 0/0, rev 1.10/0.01, addr 3> on usbus0
Apr  9 18:16:38 freeNAS kernel: kbd2 at ukbd0
Apr  9 18:16:50 freeNAS kernel: ugen0.3: <Winbond Electronics Corp> at usbus0 (disconnected)
Apr  9 18:16:50 freeNAS kernel: ums0: at uhub3, port 2, addr 3 (disconnected)
Apr  9 18:16:50 freeNAS kernel: ukbd0: at uhub3, port 2, addr 3 (disconnected)
Apr  9 18:16:51 freeNAS kernel: ugen0.3: <Winbond Electronics Corp> at usbus0
Apr  9 18:16:51 freeNAS kernel: ums0: <Winbond Electronics Corp Hermon USB hidmouse Device, class 0/0, rev 1.10/0.01, addr 3> on usbus0
Apr  9 18:16:51 freeNAS kernel: ums0: 3 buttons and [Z] coordinates ID=0
Apr  9 18:16:51 freeNAS kernel: ukbd0: <Winbond Electronics Corp Hermon USB hidmouse Device, class 0/0, rev 1.10/0.01, addr 3> on usbus0
Apr  9 18:16:51 freeNAS kernel: kbd2 at ukbd0
Apr  9 18:17:04 freeNAS kernel: em1: link state changed to DOWN
Apr  9 18:17:08 freeNAS kernel: em1: link state changed to UP
Apr  9 18:18:24 freeNAS dhclient: New IP Address (em1): 192.168.1.xxx
Apr  9 18:18:24 freeNAS dhclient: New Subnet Mask (em1): 255.255.255.0
Apr  9 18:18:24 freeNAS dhclient: New Broadcast Address (em1): 192.168.1.255
Apr  9 18:18:24 freeNAS dhclient: New Routers (em1): 192.168.1.xxx
Apr  9 18:18:25 freeNAS dhclient: New Routers (em1): 192.168.1.xxx


so. my working theory. IMPI KVM virtual USB device is conflicting with my UPS.

anyone have any thoughts/theories/suggestions?
my current Supermicro IPMI firmware is 3.15
 

deanhuff

Dabbler
Joined
May 25, 2014
Messages
14
Gaius,

We've got similar FreeNAS configurations. I'm also running super micro x9sca-f + 1230-v2 + cyberpower ups. I also see similar log entries. I recently updated my IPMI and BIOS...too early to tell if it fixes anything w/ regard to seeing the UPS reloads. I read that there is a nasty security issue related to IPMI on SuperMicros: http://threatpost.com/plaintext-supermicro-ipmi-credentials-exposed

-Dean
 
Status
Not open for further replies.
Top