Hello, Thanks for the report and sorry about any complications.
A few first questions: * is this setup known to have been working with earlier NUT releases (e.g. same OS and devices, older NUT - can try with a custom build of older tags)? Is this a regression, or we never knew the correct mappings for timeouts and/or shutdown commands used by this model? * is there the `select` error when starting the driver not for shutdowns? (is it part of the problem actually?) Jim On Mon, Dec 16, 2024, 23:03 Lee Damon via Nut-upsuser < [email protected]> wrote: > I'm still digging into this but thought I'd post what I have so far in > case there's a known issue that's easily fixed. > > I'm using the version of NUT that's in the ports tree (see the info at the > bottom). Using the SNMP drivers to talk with two ACP SmartUPSs. > > NUT is functional about monitoring and initiating host shutdown. However, > when it comes time to shut down the UPSs it complains about "select with > socket: Invalid argument" then fails entirely to shut down the UPSs. > > root@castle:/usr/local/etc/rc.d # upsdrvctl shutdown > Network UPS Tools - UPS driver controller 2.8.2 > Network UPS Tools - Generic SNMP UPS driver 1.31 (2.8.2) > select with socket: Invalid argument > Detected Smart-UPS 3000 RM on host 192.5.37.78 (mib: apcc 1.60) > Initiating UPS shutdown > [upstop] nut_snmp_set: can't set .1.3.6.1.4.1.318.1.1.1.6.1.1.0: Timeout > Shutdown failed! > upsnotify: failed to notify about state 4: no notification tech defined, > will not spam more about it > Driver failed to start (exit status=1) > Network UPS Tools - Generic SNMP UPS driver 1.31 (2.8.2) > select with socket: Invalid argument > Detected Smart-UPS 3000 RM on host 192.5.37.79 (mib: apcc 1.60) > Initiating UPS shutdown > [upsbottom] nut_snmp_set: can't set .1.3.6.1.4.1.318.1.1.1.6.1.1.0: Timeout > Shutdown failed! > upsnotify: failed to notify about state 4: no notification tech defined, > will not spam more about it > Driver failed to start (exit status=1) > > : || nomad@castle ~ [51] ; pkg info nut > nut-2.8.2 > Name : nut > Version : 2.8.2 > Installed on : Mon Jun 17 12:06:50 2024 PDT > Origin : sysutils/nut > Architecture : FreeBSD:14:amd64 > Prefix : /usr/local > Categories : sysutils > Licenses : GPLv3+ and GPLv2+ and GPLv1+ and ART10 > Maintainer : [email protected] > WWW : https://www.networkupstools.org/ > Comment : Network UPS Tools > Options : > AVAHI : on > BASH : on > CGI : on > DEV : off > DOCS : on > FREEIPMI : on > IPMIPSU : off > MANPAGES : on > MODBUS : on > NEON : on > NSS : off > OPENSSL : on > PDU : on > SERIAL : on > SNMP : on > SSL_OFF : off > USB : on > Shared Libs required: > libpowerman.so.0 > libnetsnmp.so.40 > libneon.so.27 > libmodbus.so.5 > libltdl.so.7 > libgd.so.6 > Shared Libs provided: > libupsclient.so.6 > libnutscan.so.2 > libnutclientstub.so.1 > libnutclient.so.2 > Annotations : > FreeBSD_version: 1400097 > build_timestamp: 2024-06-11T10:20:37+0000 > built_by : poudriere-git-3.4.1-30-g79e3edcd > port_checkout_unclean: no > port_git_hash : b3aa1ea86 > ports_top_checkout_unclean: no > ports_top_git_hash: 492f5a54a > repo_type : binary > repository : FreeBSD > Flat size : 12.9MiB > > Is there anything obvious I should be checking? > > thanks, > nomad > _______________________________________________ > Nut-upsuser mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
