Bug#1059922: nut-server: upsd fails to start since version 2.8.1

2024-01-21 Thread Jörg-Volker Peetz

nut version: 2.8.1-3

Hello Laurent,

sometimes it helps to read the documentation :$
In the man page of upsd.conf I read:

  "LISTEN interface port"
...
Multiple LISTEN addresses may be specified. The default is to bind
to 127.0.0.1 if no LISTEN addresses are specified (and also ::1 if
IPv6 support is compiled in).

Assuming upsd is listening on ::1 only, I inserted the line

LISTEN 127.0.0.1

into '/etc/nut/upsd.conf' and the UPS can be accessed again.
Therefore, I think this bug report should be closed. Could you do that?

Thanks for your help and sorry for the noise.

Regards,
Jörg.



Bug#1059922: nut-server: upsd fails to start since version 2.8.1

2024-01-15 Thread Jörg-Volker Peetz

nut version: 2.8.1-3

Hello Laurent,

it took me a while to set up another computer now with a Debian kernel.
I can affirm that nut in my configuration is working as expected.
After connecting the UPS via USB cable I had to restart the nut-server:
  # service nut-server restart
resulting in the output
> Restarting NUT - power devices information server and drivers: upsd
(driver(s) failed)  driver(s). upsd.


Then I switched off IPv6 again by adding 'ipv6.disable=1' to the variable
'GRUB_CMDLINE_LINUX' in '/etc/default/grub', commanding
  update-grub
as root and restarting the computer.
Now the daemon 'upsd' fails to start:

  # service nut-server restart
  Restarting NUT - power devices information server and drivers:No upsd found
running; none killed.
   upsd driver(s)  (driver(s) failed). (upsd failed).

Therefore, I think the severity could be changed to 'minor'.

Do you think it might be possible to make nut working without IPv6?

Regards,
Jörg.



Bug#1059922: nut-server: upsd fails to start since version 2.8.1

2024-01-12 Thread Laurent Bigonville

Le 12/01/24 à 12:46, Jörg-Volker Peetz a écrit :

Hello Laurent,


Hello Jörg,

Thanks for your reply


[...]
Concerning the loopback (127.0.0.1/::1) interface, here is the output 
of the

command 'ip ad':

1: lo:  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.,

For debugging purpose, could you try to re-enable IPv6 in the kernel and 
check that the lo interface has the ::1 address assign to it and then 
try again?


Kind regards,

Laurent Bigonville



Bug#1059922: nut-server: upsd fails to start since version 2.8.1

2024-01-12 Thread Jörg-Volker Peetz

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:  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





Bug#1059922: nut-server: upsd fails to start since version 2.8.1

2024-01-12 Thread Laurent Bigonville

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



Bug#1059922: nut-server: upsd fails to start since version 2.8.1

2024-01-03 Thread Jörg-Volker Peetz

Package: nut-server
Version: 2.8.1-1
Severity: grave

Dear Laurent Bigonville,

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?

Regards,
Jörg.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.9 (SMP w/16 CPU threads)
Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages nut-server depends on:
ii  adduser3.137
ii  init-system-helpers1.66
ii  libc6  2.37-12
ii  libmodbus5 3.1.10-1
ii  libnspr4   2:4.35-1.1
ii  libnss32:3.96.1-1
ii  libnutscan22.8.1-1
ii  libupsclient6  2.8.1-1
ii  libusb-1.0-0   2:1.0.26-1
ii  libwrap0   7.6.q-32
ii  nut-client 2.8.1-1
ii  sysvinit-utils [lsb-base]  3.08-5
ii  udev   255.2-2

nut-server recommends no packages.