Nut Upgrade Broke

Rickinfl

Hi, Nut was working just fine unitl this last upgrade now nothing works and the GUI is missing the link also.

Here is my 1st error I got:

starting NUT
Network UPS Tools upsmon 2.7.4
fopen /var/db/nut/upsmon.pid: No such file or directory
UPS: APC-Smart-UPS-1500 (master) (power value 1)
Using power down flag file /etc/killpower
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
Using subdriver: APC HID 0.96
Network UPS Tools upsd 2.7.4
fopen /var/db/nut/upsd.pid: No such file or directory
listening on ::1 port 3493
listening on 127.0.0.1 port 3493
Can't connect to UPS [APC-Smart-UPS-1500] (usbhid-ups-APC-Smart-UPS-1500): No such file or directory

Here is the second error I got:

starting NUT
Network UPS Tools upsmon 2.7.4
kill: No such process
UPS: APC-Smart-UPS-1500 (master) (power value 1)
Using power down flag file /etc/killpower
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
Duplicate driver instance detected! Terminating other driver!
Network UPS Tools upsd 2.7.4
kill: No such process
listening on ::1 port 3493
listening on 127.0.0.1 port 3493
Can't connect to UPS [APC-Smart-UPS-1500] (usbhid-ups-APC-Smart-UPS-1500): Connection refused

AR15USR

I got bit as well. NUT doesn't even show up in the system after the upgrade..

cciechad

Same problem here. Config page and service missing since update.

jbhowlesr

I have an APC Back-Ups 1300x connected to my pfsense box. All was working well with the previous version of NUT; meaning it read my UPS and display data as advertised. When I installed the upgrade of NUT last night, it will not longer read my UPS with the following error message:

Status Alert: The UPS requires attention

I have tried numerous driver/UPS type possibilities with no luck. My UPS is connected via a black cable with USB on one end and an RJ-45 connector on the other; which I believe to be serial. Anyhow; some resolution would be nice.

Incidentally, uninstalling and reinstalling NUT I receive this installation output. I am hoping this is what we are supposed to see.

Installing pfSense-pkg-nut…
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Checking integrity... done (0 conflicting)
The following 4 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
pfSense-pkg-nut: 2.7.4_1 [pfSense]
nut: 2.7.4 [pfSense]
neon: 0.30.1 [pfSense]
net-snmp: 5.7.3_11 [pfSense]

Number of packages to be installed: 4

The process will require 17 MiB more space.
[1/4] Installing neon-0.30.1…
[1/4] Extracting neon-0.30.1: …....... done
[2/4] Installing net-snmp-5.7.3_11…
[2/4] Extracting net-snmp-5.7.3_11: …....... done
[3/4] Installing nut-2.7.4…
[3/4] Extracting nut-2.7.4: …....... done
[4/4] Installing pfSense-pkg-nut-2.7.4_1…
[4/4] Extracting pfSense-pkg-nut-2.7.4_1: …....... done
XML error: PKGINFOLINK at line 8 cannot occur more than once
Message from net-snmp-5.7.3_11:
**** This port installs snmpd, header files and libraries but does not
start snmpd by default.
If you want to auto-start snmpd and snmptrapd:, add the following to
/etc/rc.conf:

snmpd_enable="YES"
snmpd_flags="-a"
snmpd_conffile="/usr/local/share/snmp/snmpd.conf /etc/snmpd.conf"
snmptrapd_enable="YES"
snmptrapd_flags="-a -p /var/run/snmptrapd.pid"

**** You may also specify the following make variables:

NET_SNMP_SYS_CONTACT="zi@FreeBSD.org"
NET_SNMP_SYS_LOCATION="USA"
DEFAULT_SNMP_VERSION=3
NET_SNMP_MIB_MODULES="host smux mibII/mta_sendmail ucd-snmp/diskio"
NET_SNMP_LOGFILE=/var/log/snmpd.log
NET_SNMP_PERSISTENTDIR=/var/net-snmp

to define default values (or to override the defaults). To avoid being
prompted during the configuration process, you should (minimally) define
the first two variables. (NET_SNMP_SYS_*)

You may also define the following to avoid all interactive configuration:

BATCH="yes"

Cleaning up cache... done.
Success

w0w

I think, before creating new topic you need to calm down, don't panic, do not to tear one's hair and read what people are writing about released version and you will find out what is current workaround for your problem.

https://forum.pfsense.org/index.php?topic=114871.105
or
https://forum.pfsense.org/index.php?topic=115349.0