On 07/27/2011 08:51 AM, David C. Rankin wrote:
Arjen, All,
I need help unwrapping my head from around the problem of getting nut running on
the same machine it runs fine with on another drive!! Sound easy -- not here :)
I have network-ups-tools 2.4.1-2 on two servers. On one server I had a raid
drive fail (which I'm still booting from and running nut on just fine). I bought
a second pair of drives to establish a new array in the box which is up and
running just fine except for nut. The daemon.log shows the following error:
Jul 26 21:09:11 nirvana usbhid-ups[2139]: Startup successful
Jul 26 21:09:11 nirvana upsmon[2142]: Startup successful
Jul 26 21:09:11 nirvana upsmon[2143]: UPS [nirvana_ups@localhost]: connect
failed: Connection failure: Connection refused
Jul 26 21:09:11 nirvana upsmon[2143]: Communications with UPS
nirvana_ups@localhost lost
Jul 26 21:09:16 nirvana upsmon[2143]: UPS [nirvana_ups@localhost]: connect
failed: Connection failure: Connection refused
Jul 26 21:09:16 nirvana upsmon[2143]: UPS nirvana_ups@localhost is unavailable
Jul 26 21:09:21 nirvana upsmon[2143]: UPS [nirvana_ups@localhost]: connect
failed: Connection failure: Connection ref
I have the exact same nut user and nut groups on this new install, both same UID
and GID. I have copied my /etc/ups file-for-file from old-array to new-array,
but still I get the connection refused error with 'upsc ups_name@localhost. If I
boot back to the old array drive (old drive)G, then it works perfectly. I have
been focusing my feeble mind on this task this evening, and I'm out of ammo.
Where can the hidden causes of this Connection failure: Connection refused error
be coming from?
Solved:
error while loading shared libraries: libwrap.so.0: cannot open shared object
file: No such file or directory
Sorry for the noise :)
--
David C. Rankin, J.D.,P.E.
_______________________________________________
Nut-upsdev mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
