Hello Charles, Thank you for your advice!
I think an old version of nut might have had something to do with it. I rebooted the system after I wrote this and things began to get a lot better. Then, I found that my LISTEN statement was not really appropriate. All working now! Best Regards, Drew V-S -----Original Message----- From: Charles Lepple [mailto:[EMAIL PROTECTED] Sent: Saturday, October 27, 2007 19:59 To: Drew Vonada-Smith Cc: Nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Trouble with NUT? On 10/27/07, Drew Vonada-Smith <[EMAIL PROTECTED]> 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.9 This 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 3493 First, 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 _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser