Beta test of new NUT UPS package

Starrbuck · Aug 4, 2016, 2:17 PM

I sent out a beta 6 version to everyone. The only change is the ups “pending” change discussed above. To avoid any confusion, please delete the prior version via pkg delete prior to installing the new version.

If you have time to give this version a test, I would really appreciate it. I'd like to put this to bed. Thanks!

Beta 6 working fine here.

dennypage · Aug 4, 2016, 5:59 PM

Thanks Starrbuck, much appreciated.

dennypage · Aug 4, 2016, 10:16 PM

The new NUT package has been merged. This version is identified as 2.7.4_1, and is equivalent to beta version 6. When the package becomes available via the package manager, I recommend that you delete the beta version prior to installing the production version.

Again, thank you for the help guys. It is greatly appreciated!

Starrbuck · Aug 5, 2016, 2:05 PM

Thank you, sir! It was fun.

th3r3isnospoon · Aug 5, 2016, 8:44 PM

Hello All,

Thank you for the work on this.

After installing the new version, I no longer see it listed in the services menu (neither NUT nor UPS). I tried the install on two different pfSense FW's running 2.3.2 (pfsense amd64 and nanobsd) and right now it doesn't work on either box.

When I do a full reinstall it says this:

Upgrading 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 1 package(s) will be affected (of 0 checked):

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

I tried a full uninstall and reinstall but the service is nowhere to be found. It shows that the package is installed, I just can't do anything besides that. Any ideas?

Thanks,

-th3r3isnospoon

dennypage · Aug 5, 2016, 10:14 PM

I am also seeing this error on factory, but not on beta. I don't have a community version at the moment to check on. Which version are you running? Community, factory, or beta?

timotl · Aug 5, 2016, 10:20 PM

If it helps, I tried to update from beta and see the same error on community.
Removed the package manually and still has the same error on install.

th3r3isnospoon · Aug 5, 2016, 10:28 PM

@dennypage:

I am also seeing this error on factory, but not on beta. I don't have a community version at the moment to check on. Which version are you running? Community, factory, or beta?

Using the Community edition.

Thanks,

-th3r3isnospoon

dennypage · Aug 5, 2016, 11:28 PM

Sorry about the problems. I'm not sure if it's something I need to change, or not. I've sent a note to one of the guys who manages the packages to ask.

In the interim, you should be able to reinstall the beta package via the command line as you did during the beta.

th3r3isnospoon · Aug 6, 2016, 4:41 AM

@dennypage:

Sorry about the problems. I'm not sure if it's something I need to change, or not. I've sent a note to one of the guys who manages the packages to ask.

In the interim, you should be able to reinstall the beta package via the command line as you did during the beta.

No problem man, bugs happen, just wanted to let you know!

Thanks,

-th3r3isnospoon

dennypage · Aug 6, 2016, 4:46 AM

It's been tracked down to a specific problem with a branch of the repo. I'm sure it will be fixed soon.

Thank you for your patience.

th3r3isnospoon · Aug 6, 2016, 4:49 AM

@dennypage:

It's been tracked down to a specific problem with a branch of the repo. I'm sure it will be fixed soon.

Thank you for your patience.

Awesome, thank you! :)

-th3r3isnospoon

val · Aug 6, 2016, 7:27 AM

On Community Edition here also seeing the XML error message.

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:

And uninstall show following:-

Removing pfSense-pkg-nut…
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
pfSense-pkg-nut-2.7.4_1

Number of packages to be removed: 1
[1/1] Deinstalling pfSense-pkg-nut-2.7.4_1…
The nut package is not installed.

Deletion aborted.[1/1] Deleting files for pfSense-pkg-nut-2.7.4_1: …....... done
The nut package is not installed.

Deletion aborted.>>> Removing stale packages... done.
Success

w0w · Aug 6, 2016, 7:46 AM

You can fix it right now by installing beta 6 back manually or change your firmware branch to development, re-install package (you can do it from GUI, even if package itself is broken) and then change branch to stable.
Or just wait for a fix in repo.

val · Aug 6, 2016, 9:05 AM

@w0w:

You can fix it right now by installing beta 6 back manually or change your firmware branch to development, re-install package (you can do it from GUI, even if package itself is broken) and then change branch to stable.
Or just wait for a fix in repo.

Thank you for the reply and I will wait for fix in repo.

markeby · Aug 7, 2016, 6:04 PM

Still waiting for NUT to be installed and usable.

lemonkey · Aug 7, 2016, 6:55 PM

The one package I decide to install on a Sunday… :-\

vbentley · Aug 8, 2016, 8:48 AM

@w0w:

You can fix it right now by installing beta 6 back manually or change your firmware branch to development, re-install package (you can do it from GUI, even if package itself is broken) and then change branch to stable.
Or just wait for a fix in repo.

I tried this today. I switched to the development branch in Updates, reinstalled the NUT package. Although the installation completed successfully, NUT would not start and there was no GUI menu for NUT either.
Configured my system back to stable branch, reinstalled NUT with the error and left it like that until a fix arrives.

dennypage · Aug 8, 2016, 1:06 PM

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

johnabbot · Aug 24, 2016, 6:49 AM

Hi Denny,

Just want to say thank you for the great work, I'm still on beta 3, it was working fine and I wanted to wait until the release had had feedback.

My set up here has had a power cut and everything worked perfectly both with the master and all of the slaves. Huge weight off my mind and key component in me being able to recommend pfsense to people.

Anything to bear in mind now upgrading from b3 to the latest version?

Thanks again.

John