Guys, Below are the thoughts from the NUT developer on what to check in the Arch NUT package to see if recent changes to udev bus designations, and permission are incorporated. My guess is that it is udev related since 50% of the time it boots and loads usbhid-ups just fine and everything works, other times, it hangs loading usbhid-ups and nothing works. Hope this helps. -------- Original Message -------- Subject: Re: [Nut-upsdev] usbhid-ups causing hang on boot with 2.6.35 - any ideas? Date: Fri, 03 Sep 2010 10:49:27 +0200 From: Arjen de Korte <nut+devel@de-korte.org> To: nut-upsdev@lists.alioth.debian.org Citeren "David C. Rankin" <drankinatty>:

(Arjen - I apologize if you get two copies, I sent the first one to the old de-korte.org address)

That address isn't old, but the mailserver is configured to only accept messages from the mailinglist server.

Aug 30 20:31:03 archangel upsd[2295]: listening on 192.168.6.14 port 3493 Aug 30 20:31:03 archangel upsd[2295]: listening on 127.0.0.1 port 3493 Aug 30 20:31:03 archangel upsd[2295]: Can't connect to UPS [archangel_ups] (usbhid-ups-archangel_ups): No such file or directory

This means the driver isn't running (but you probably already knew that).

Aug 30 20:31:03 archangel upsd[2296]: Startup successful Aug 30 20:31:03 archangel upsmon[2298]: Startup successful Aug 30 20:31:03 archangel upsmon[2300]: Login on UPS [archangel_ups@localhost] failed - got [ERR ACCESS-DENIED] Aug 30 20:31:03 archangel upsmon[2300]: Login on UPS [nirvana_ups@nirvana.3111skyline.com] failed - got [ERR ACCESS-DENIED]

The above two error messages indicate there is a problem with logging into the server. You could run the server in debug mode, but my guess is this has to do with either NUT being build with tcp-wrappers support and you failed setting this up properly (see 'man 8 upsd') or the credentials you're using are incorrect. [...]

Looks like some type of udev issue or kernel issue, but I thought I would check here to see if you guys have any more info on the problem. Anybody seen this behavior before?

This looks like the udev rules are incorrect. If memory serves, there have been some changes in the syntax (BUS was changed to SUBSYSTEMS). Other than that, there are no known issues. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) _______________________________________________ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com