NUT package under pfSense 2.3.2: Status and configuration page not accessible

pvoigt

I have installed pfSense 2.3.2 (fresh installation, full installation on mSATA, amd64) on an apu1d4. After the import of my 2.2.6 configuration I reinstalled the NUT package. The NUT package is obviosuly installed correctly and can be started and stopped from the dashboard.

When I try to access NUT via "Services -> NUT" I obtain

404 Not Found

This means I can make no longer any changes to the NUT configuration.

dennypage

I believe this is my fault. I had some files missing from the commit for the new NUT package. I believe it's fixed now. Sorry for the problem.

dennypage

It's currently fixed for community, but not fixed yet for factory. The fixed version is 2.7.4.

pvoigt

Thank your for the quick reply. It's good to know that the issue is fixed.

However, I am not sure about correct understanding of "fixed for community". Does it mean that it is just fixed in the github repository (https://github.com/pfsense/FreeBSD-ports/commits/devel/sysutils/pfSense-pkg-nut) but not yet repackaged for regular package update using the pfSense webGUI?

Is there a way to pull in your recent changes of the NUT package or do I have to wait for version 2.7.3?

dennypage

Community refers to the Community Edition of pfSense. If you are using the community edition, you should see version 2.7.4 as available. Re-install the NUT package and it should be correct.

pvoigt

Yes, I am using the community edition and reinstallation of the package has even been my first thought. But when using the package management I would have expected a newer package version than 2.3.1 and therefore I did not go further in my first attempt.

Now I have reinstalled the package and everything works as expected.

Thank you.

knight-of-ni

I just upgraded from 2.3.1_5 to 2.3.2 (Community Edition) and have the same issue. ups_status.php returns 404 not found.

I have uninstalled and then reinstalled nut 2.7.4_1
This did not resolve the issue.

Perhaps the error "XML error: PKGINFOLINK at line 8 cannot occur more than once" shown in the installation log below is a relevant clue.


>>> 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.
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 MiB to be downloaded.
Fetching nut-2.7.4.txz: .......... done
Fetching neon-0.30.1.txz: .......... done
Checking integrity... done (0 conflicting)
[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

Ramosel

Same here. No service showing in dropdown and although UPS widget is available show the "Monitoring is not Enabled"

From the reinstall:

Installed packages to be REINSTALLED:
pfSense-pkg-nut-2.7.4_1 [pfSense]

Number of packages to be reinstalled: 1
[1/1] Reinstalling pfSense-pkg-nut-2.7.4_1…
[1/1] Extracting pfSense-pkg-nut-2.7.4_1: …....... done
The nut package is not installed.

Deletion aborted.XML error: PKGINFOLINK at line 8 cannot occur more than once

Cleaning up cache... done.
Success

Package shows installed in the dashboard??

dennypage

@abauer:

I just upgraded from 2.3.1_5 to 2.3.2 (Community Edition) and have the same issue. ups_status.php returns 404 not found.

I have uninstalled and then reinstalled nut 2.7.4_1
This did not resolve the issue.

Perhaps the error "XML error: PKGINFOLINK at line 8 cannot occur more than once" shown in the installation log below is a relevant clue.

As noted in other threads, 2.7.4_1 from the community and factory package servers are corrupt and will not install. The version from the beta package server is correct. I expect that the community and factory packages will be fixed as soon as someone is available on Monday.

If you have a critical need to install the package before then, you can PM me with an email address and I will send you a copy of the package.

val

It's all fixed now and tagged with 2.7.4_2

knight-of-ni

Thanks for the update and for fixing the issue.

tweek

I'm on pfSense 2.3.2, I did an update to NUT package 2.7.4_1. The service wouldn't start and the NUT services page didn't appear in the Services drop-down menu. This evening I updated to the NUT 2.7.4_2 package and am having the same problems, even following a service reinstall.

tweek

Ok, got it figured out. I had to do a full uninstall/reinstall, then realize that the name of the service in Services changed from NUT to UPS, then had to visit Services | UPS and review the settings and accept the changes to accommodate version changes to the settings. The service was then able to start and all seems to be working now.

dennypage

Glad you got it sorted. Btw, there is an info link for the package. It shows up as an i in a circle in the package manager. This thread has information on the package that might be helpful.

Ramosel

using the command line from the other thread to completely remove, then reinstalling with the _2 package, all is well. Thanks.
Nice detail on the settings page as far parameters being seen.

pvoigt

I have just upgraded to NUT 2.7.4_2 package without any issues. A prior deinstallation was not neccessary. Configuration was automatically converted to the new version. I just had to confirm the auto-conversion.

The dashboard UPS widget, however, was automatically removed. But it could be installed again.

I should mention, that my pfSense machine is not the NUT master of my UPS.

Currently I am very happy with the new NUT package.

dennypage

@pvoigt:

Currently I am very happy with the new NUT package.

Good to hear, thanks!

nmaster

Hi, I just upgraded my pfsense box from 2.3.1_5 to 2.3.2 and I got same issue with NUT.
I uninstalled the NUT package and reinstalled it to get it working again.

BUT: un the Services Tab, I now have 2 entries: NUT (old one that brings me a 404 error) and UPS the actual ups setup page.

Do you know how can I remove the old NUT entry of the Services menu ?

Thanks.

dennypage

https://forum.pfsense.org/index.php?topic=115349.msg650408#msg650408

nmaster

Thanks dennypage, config file edited successfully.