On Wed, 28 Nov 2012 17:36:28 +0400
sergio <mail...@sergio.spb.ru> wrote:
> Looks like nut-snmp is totally unusable:
>
> # upsd -DD
> Network UPS Tools upsd 2.6.5
> 0.000000 fopen /var/run/nut/upsd.pid: No such file or directory
> 0.001154 listening on 127.0.0.1 port 3493
> 0.001658 listening on ::1 port 3493
> 0.002385 Can't connect to UPS [apcpdu] (snmp-ups-apcpdu): No
> such file or directory
>
> # apt-cache policy nut-snmp
> ....
> connect(6, {sa_family=AF_FILE, path="snmp-ups-apcpdu"}, 110) = -1
> ENOENT (No such file or directory) ....
I am by no means a NUT expert (or even user), but it seems to me like
upsd not being able to connect to a particular driver process is normal
when that driver process has an issue and therefore did not start up
properly.
> ups.conf
> [apcpdu]
> driver = snmp-ups
> port = apc
> mibs = apcc
> community = public
Try removing the “mibs = apcc” line.
Also, maybe specify “snmp_version = v1”.
What is the result of running “upsdrvctl start” as root?
--
Best regards,
Michael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
