Hello Laurent,
thanks for taking care.
Concerning the configuration files in /etc/nut/, I only changed nut.conf and
ups.conf. I described the change in ups.conf in my previous e-mail. In nut.conf
I changed only the line
MODE=none
to
MODE=standalone
Concerning the loopback (127.0.0.1/::1) interface, here is the output of the
command 'ip ad':
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
I disabled IPv6 on my system (the linux kernel is locally configured and
compiled). Ssh has no problems on the loopback device, i.e.,
ssh localhost
works.
Best regards,
Jörg.
Laurent Bigonville wrote on 12/01/2024 11:12:
severity 1059922 important
thanks
> Dear Laurent Bigonville,
Hello Jörg,
> with version 2.8.0-7 an EATON UPS connected to a debian computer via
> USB was working in standalone mode as expected. The only change in the
> config files was in /etc/nut/ups.conf where I added the following lines:
>
> [Eaton]
> driver = usbhid-ups
> port = auto
> vendorid = 0463
> pollfreq = 30
>
> After the upgrade to version 2.8.1-1 the upsd daemon would fail to
> start. The output in /var/log/syslog is
>
> upsd[12132]: not listening on ::1 port 3493
> upsd[12132]: listening on 127.0.0.1 port 3493
> upsd[12132]: no listening interface available
>
> instead of
>
> upsd[12553]: listening on 127.0.0.1 port 3493
> upsd[12553]: not listening on ::1 port 3493
> upsd[12553]: Connected to UPS [Eaton]: usbhid-ups-Eaton
> upsd[12555]: Startup successful
>
> for the working version 2.8.0.
> Any ideas?
Could you please attach the other configuration files here (please check for
clear-text passwords)?
Do you have the loopback (127.0.0.1/::1) interface properly working?
I cannot reproduce this at home where I have also an EATON UPS
Kind regards,
Laurent Bigonville
