I'm a linux newbie and having some trouble with NUT, can anyone assist? I've read the FAQ and various articles online by Peter Sellinger and others thoroughly. OS is ClarkConnect 4.2, which is based on CentOS4/RHEL 4. UPS is an APC SmartUPS 1500 (USB). Correct driver is believed to be usbhid-ups. No RPM for my OS was available past 2.0, so I built from source using NUT 2.2. I think this all worked OK, did not see anything suspicious. (But again, compiling on linux is also new to me.) PC is a pretty generic ASUS motherboard with an AMD X2 proc and nVidia chipset (MCP55 USB). The setup had some USB issues causing initial confusion. I'm running a workaround to get EHCI and OHCI loaded instead of UHCI; USB appears fine now, although I am not successful using hotplug. CC does not use udev and thus I presume should be using "old-style" hotplug scripts. The scripts look fine but I can never get the files to show as owned by "ups" as described. However, -u root workaround seems OK. Concluded this was not a core issue. When I run: upsdrvctl -u root start upsserver all looks OK on results: Network UPS Tools - UPS driver controller 2.2.0- Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.2.0-) Detected a UPS: American Power Conversion/Smart-UPS 1500 RM FW:617.3.D USB FW:8.1 Using subdriver: APC/CyberPower HID 0.9 But when I run: upsd -u root I get: Network UPS Tools upsd 2.2.0- not listening on 192.168.0.20 port 3493 That's the correct IP for the local machine; same results if I use localhost instead. Of course, upsc and upsmon are also unsuccessful. It feels like I'm allllllllmost there. Any ideas for me? Thanks group! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20071027/9581f5f8/attachment.htm
On 10/27/07, Drew Vonada-Smith <drew at whisperingwoods.org> wrote:> OS is ClarkConnect 4.2, which is based on CentOS4/RHEL 4.Which version of the kernel? Do you know if anything like SELinux or grsecurity are enabled?> upsdrvctl -u root start upsserver > > > > all looks OK on results: > > Network UPS Tools - UPS driver controller 2.2.0- > > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.2.0-) > > Detected a UPS: American Power Conversion/Smart-UPS 1500 RM FW:617.3.D USB > FW:8.1 > > Using subdriver: APC/CyberPower HID 0.9This confirms your suspicion that usbhid-ups is the correct driver.> But when I run: > > upsd ?u root > > > > I get: > > Network UPS Tools upsd 2.2.0- > > not listening on 192.168.0.20 port 3493First, is there anything that might have already bound to that port? (An old copy of NUT, for instance?) I think you can find out by running "lsof -n | grep 3493" as root. You can also get more verbose debugging output by specifying "-DDD" on the upsd command line. If that doesn't work - what does config.log say about IPv6 support? -- - Charles Lepple
Charles has answered most other questions, so I'll skip those.> But when I run: > > upsd -u root > > > > I get: > > Network UPS Tools upsd 2.2.0- > > not listening on 192.168.0.20 port 3493You apparently have configured a LISTEN address in 'upsd.conf'. Unless you know exactly what you're doing, don't configure *anything* here. In that case, the server will listen to 0.0.0.0 port 3493. If it still attempts to listen to another address then, something is really broken in CC. In that case, you may wish to configure NUT to not use IPv4/IPv6 code, but instead use IPv4 only by adding the configure option --with-ipv6=no. Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57