(megatec_usb) error: Driver not connected

[François Marier]

Binary package hint: nut

Since upgrading to lucid, nut can no longer connect to my UPS, a Belkin 600VA USB. ( My setup is described here: http://feeding.cloud.geek.nz/2010/04/monitoring-belkin-600va-ups-with-nut-on.html )

This is what I see in my logs:

  upsd[25112]: Can't connect to UPS [belkinusb] (megatec_usb-belkinusb): No such file or directory
  upsmon[25118]: Poll UPS [belkinusb@localhost] failed - Driver not connected
  upsmon[25118]: Communications with UPS belkinusb@localhost lost
  upsmon[25118]: Poll UPS [belkinusb@localhost] failed - Driver not connected
  upsmon[25118]: UPS belkinusb@localhost is unavailable

I have downgraded (the libusbclient1 and nut packages) to the version of nut from karmic and it has started to work again. So something in between those two version has broken that driver I guess.

Is there anything I can do to help in troubleshooting this problem some more?

[Chuck Short (zulcss)]

Can you attach the output of sudo lsusb -vvv?

Thanks
chuck

[François Marier (fmarier)]

Here is, as requested, the output of "sudo lsusb -vvv"

[François Marier (fmarier)]

After reinstalling the karmic packages (which I have added to my lucid PPA: deb http://ppa.launchpad.net/fmarier/ppa/ubuntu lucid main) and unplugging and re-plugging the UPS, here's the new lsusb output I get.

[James Thomas (thomasjj)]

I have the same problem with a Belkin F6C550-AVR 550VA USB. I had to downgrade to the karmic package to get it working again. Attached is my current (working) lsusb output. I'll switch back to the current lucid packages later today if needed.

[Arnaud Quette (aquette)]

guys,

I'd be interested in a driver debug output, ie:
$ export USB_DEBUG=3
$ /lib/nut/megatec_usb -DDDDD -a <upsname>

let it run for a couple of minutes, then break it (using Ctrl+C) and send
back the trace.

cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

[James Thomas (thomasjj)]

Tried your suggestion with my current working setup and it couldn't claim the interface and timed out after about 10 seconds. Then I stopped nut and tried it again and it stopped in 5 seconds. Restarting nut produces output again. I attached the log.

I'm not sure what else needs to be done. Maybe unplug and replug the usb. Anything else that might help?

[Nuno Santos (nuno-santos-vigiesolutions)]

Hi guys,

I'm using nut 2.4.3 in ubuntu 10.4 and I got the same problem. "Driver not connected". Some times I got "Data stale" also.
Have you experienced that on these versions too? Have some of you solved the issue?

Best regards,
Nuno

[Arnaud Quette (aquette)]

guys,

this seems related to a udev issue.
things to try:
- stop nut (sudo service nut stop ; killall -9 megatec_usb)
- start the driver and server as root (sudo /lib/nut/megatec_usb -u root -a belkin-ups && sudo upsd -u root)
- then check using upsc

you should also try the blazer_usb driver, as it has since replaced megatec_usb.
finally, using packages from natty or maverick may be an option

[Arnaud Quette (aquette)]

NUT release 2.6.2 has fixed the regression in udev rules file creation.

In case you're stuck with an older version, I've attached a udev rules file.
Just overwrite the one on your system, using:
1) first, identify the current location of the udev file:
$ ls /???/udev/rules.d/*nut*

This should point either '/etc/udev/rules.d/52-nut-usbups.rules' (older release) or '/lib/udev/rules.d/52-nut-usbups.rules'

2) now, overwrite this file using the one provided here:
$ cp -f /path/to/new/52-nut-usbups.rules /???/udev/rules.d/52-nut-usbups.rules

Remember to replace '???' by either 'etc' or 'lib', according to the result of (1).

Arnaud

[Arnaud Quette (aquette)]

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad