On Sep 21, 2015, at 7:38 AM, Charles Lepple <[email protected]> wrote: > > (please keep the list CC'd) > >> On Sep 21, 2015, at 5:09 AM, Uroš Gaber <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi. >> No for me nutdrv_qx driver is not working with this UPS. >> Here's log: >> Sep 21 11:06:39 server_main upsd[50449]: listening on 127.0.0.1 port 3493 >> Sep 21 11:06:39 server_main upsd[50449]: Can't connect to UPS [ups] >> (nutdrv_qx-ups): No such file or directory >> Sep 21 11:06:39 server_main upsd[50450]: Startup successful >> Sep 21 11:06:39 server_main kernel: [255930.977833] usb 2-1.6: usbfs: >> USBDEVFS_CONTROL failed cmd nutdrv_qx rqt 128 rq 6 len 255 ret -110 >> Sep 21 11:06:40 server_main upsd[50450]: User [email protected] >> <mailto:[email protected]> logged into UPS [ups] >> Sep 21 11:06:35 server_main upsmon[50420]: UPS [ups@localhost]: connect >> failed: Connection failure: Connection refused >> Sep 21 11:06:40 server_main upsmon[50420]: Poll UPS [ups@localhost] failed - >> Driver not connected > > That's strange. Can you make sure that both the old blazer_usb and nutdrv_qx > processes have been killed, and start nutdrv_qx with one or two -D flags? > >
_______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
