Your message dated Fri, 27 Jun 2025 08:06:06 +0200
with message-id <aF40zoYldu4XpTjw@fenchel>
and subject line Re: severity of 1070205 is serious
has caused the Debian Bug report #1070205,
regarding nut-scanner: complains about missing libnetsnmp.so
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1070205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nut-snmp
Version: 2.8.1-3.1+b1
Severity: important
X-Debbugs-Cc: simon.harh...@muenster.de

Dear Maintainer,

'nut' and 'nut-snmp' are installed. I tried to query our ups via 'nut-scanner 
-S' and got following message:
'Cannot load SNMP library (libnetsnmp.so) : file not found. SNMP search 
disabled.'
This renders nut unusable with a UPS via snmp.

But the package 'libsnmp40t64' (in sid) is installed and following files are 
present:
root@host:~# ls /usr/lib/x86_64-linux-gnu/libnetsnmp.so*
/usr/lib/x86_64-linux-gnu/libnetsnmp.so.40  
/usr/lib/x86_64-linux-gnu/libnetsnmp.so.40.2.1

With bookworm 'nut-scanner -S' works without problems.

Thanks for your work and support!
Simon

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

Kernel: Linux 6.8.4-2-pve (SMP w/1 CPU thread; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nut-snmp depends on:
ii  libc6         2.37-19
ii  libsnmp40t64  5.9.4+dfsg-1.1+b1
ii  nut-server    2.8.1-3.1+b1

nut-snmp recommends no packages.

nut-snmp suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi Simon,

* Simon <simon.harh...@muenster.de> [2024-05-01 19:39]:
'nut' and 'nut-snmp' are installed. I tried to query our ups via 'nut-scanner 
-S' and got following message:
'Cannot load SNMP library (libnetsnmp.so) : file not found. SNMP search 
disabled.'
This renders nut unusable with a UPS via snmp.

But the package 'libsnmp40t64' (in sid) is installed and following files are 
present:
root@host:~# ls /usr/lib/x86_64-linux-gnu/libnetsnmp.so*
/usr/lib/x86_64-linux-gnu/libnetsnmp.so.40  
/usr/lib/x86_64-linux-gnu/libnetsnmp.so.40.2.1

You need to install the libsnmp-dev package.

Reproducer:

$ mmdebstrap --variant=essential 
--include=nut-snmp,nut,libusb-1.0-0,libusb-1.0-0-dev,libneon27-dev,libavahi-client-dev,libfreeipmi-dev,libupsclient-dev
 --chrooted-customize-hook=nut-scanner trixie /dev/null
[..]
I: running --chrooted-customize-hook in shell: sh -c 'nut-scanner'
Cannot load SNMP library (libnetsnmp.so) : file not found. SNMP search disabled.
Scanning USB bus.
Scanning XML/HTTP bus.
No start IP, skipping NUT bus (old connect method)
Scanning NUT bus (avahi method).
Scanning IPMI bus.
Failed to create Avahi client: Daemon not running
No USB device found: Resource temporarily unavailable


$ mmdebstrap --variant=essential 
--include=nut-snmp,nut,libusb-1.0-0,libsnmp-dev,libusb-1.0-0-dev,libneon27-dev,libavahi-client-dev,libfreeipmi-dev,libupsclient-dev
 --chrooted-customize-hook=nut-scanner trixie /dev/null
[..]
I: running --chrooted-customize-hook in shell: sh -c 'nut-scanner'
Scanning USB bus.
No start IP, skipping SNMP
Scanning XML/HTTP bus.
No start IP, skipping NUT bus (old connect method)
Scanning NUT bus (avahi method).
Scanning IPMI bus.
Failed to create Avahi client: Daemon not running
No USB device found: Resource temporarily unavailable

Cheers Jochen

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to