[Nut-upsuser] NUT 2.6.3-1 Windows package

Frédéric Bohé fredericbohe at eaton.com
Wed May 2 08:59:18 UTC 2012


On Wed, 2012-05-02 at 15:20 +1100, Dmitry Ogorodnikov wrote:
> Oops, my bad, upsd not running.
> 
> upsd won't work with "LISTEN ::1 3493":
> 
> Network UPS Tools upsd 2.6.3-3534:3540M
>    0.000000	fopen C:\NUT\sbin\..\var\run/upsd.pid: No such file or
> directory [Не удается найти указанный файл. ]
>    0.000000	listen_add: added ::1:3493
>    0.000000	setuptcp: try to bind to ::1 port 3493
>    2.265625	getaddrinfo: Этот хост неизвестен.
> 
> ... and exits. Last line means "This host is unknown.".
> According to comments, NUT should ignore IPv6 when IPv6 disabled. But
> looks like NUT fails while binding to IPv6 address.

The comments are right for unix platforms, but indeed this behavior is
wrong for Windows. I will update the comments.


> So I use "LISTEN 0.0.0.0 3493", it works as expected.
> 
> 
> Also, while starting upsd writes:
> 
> Network UPS Tools upsd 2.6.3-3534:3540M
>    0.000000	fopen C:\NUT\sbin\..\var\run/upsd.pid: No such file or
> directory [Не удается найти указанный файл. ]
>    0.000000	listen_add: added 127.0.0.1:3493
>    0.000000	setuptcp: try to bind to 127.0.0.1 port 3493
>    0.015625	listening on 127.0.0.1 port 3493
>    0.015625	Connected to UPS [repeater]: dummy-ups-repeater
>    0.015625	Connected to UPS [central]: snmp-ups-central
>    0.015625	Can't open C:\NUT\sbin\..\etc/upsd.users: No such file or directory
> ...
> 
> C:\NUT\var\run\upsd.exe.pid are being created anyways, so I think we
> have no need in this error message.

When starting, upsd tries to know if another instance of upsd is
running. To do so it tries to read upsd.pid file. When there are no upsd
running you get this message which is just informative, not even a
warning. Anyway I agree it may be confusing.

regards,
Fred

> 
> Regards,
> Dmitry
> 
> 2012/5/2 Dmitry Ogorodnikov <dmitry.b.ogorodnikov at gmail.com>:
> > Hello,
> >
> > snmp-ups won't run without libnetsnmp-30.dll, but NUT doesn't contain
> > such file, and I can't find it over the Internet.
> >
> > Renaming libnetsnmp.dll to libnetsnmp-30.dll doesn't work, snmp-ups
> > runs but can't connect to my Symmetra.
> >
> > C:\NUT\bin>snmp-ups -a central
> > Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.3-3534:3540M)
> > No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.23.1'!
> > Please report it to NUT developers, with an 'upsc' output for your device.
> > Going back to the classic MIB detection method.
> > Detected Symmetra 48K on host 10.35.200.80 (mib: apcc 1.1)
> >
> > ... and stucks.
> >
> > C:\NUT\bin>upsc central
> > Error: Connection failure: Unknown error
> >
> > My ups.conf:
> >
> > [central]
> >  driver = snmp-ups
> >  port = 10.35.200.80
> >  community = public
> >
> > Is snmp-ups implemented in Windows? If yes, where can I find libnetsnmp-30.dll?
> >
> > Thanks.
> >
> > Regards,
> > Dmitry.

-- 
Eaton Opensource Team - http://opensource.eaton.com

--------------------------------------------------------------------------



More information about the Nut-upsuser mailing list