NUT package (2.8.0 and below)

4o4rh

@Teken did you look at my post above?

http://rogerprice.org/NUT/ConfigExamples.A5.pdf
i believe the scenario you require is covered in the examples.

I was also told the scenario i wanted is not supported....just needed to change from a bash based script to a shell based on and everything turned on.

Teken

@gwaitsi

Having quickly scanned this fantastic document on page 54. I do not see an obvious example of how to add say five UPS systems. If someone can give me a working example to test that would be greatly appreciated!

And just to be clear my expectations is to be able to add & see the additional four UPS units (status) in the dashboard.

If I can see four ill work my way up to the remaining sixteen. I can’t believe I’m the only person who has ever needed pfSense to monitor more and than one UPS?!?

Thank you to all who took the time to chime in!

dennypage

@Teken said in NUT package:

Having quickly scanned this fantastic document on page 54. I do not see an obvious example of how to add say five UPS systems. If someone can give me a working example to test that would be greatly appreciated!
And just to be clear my expectations is to be able to add & see the additional four UPS units (status) in the dashboard.
If I can see four ill work my way up to the remaining sixteen. I can’t believe I’m the only person who has ever needed pfSense to monitor more and than one UPS?!?

I'm glad you like the thread... With specific regard to your question, please see my response to your same question above. You can not, and should not, do this with pfSense. pfSense is not a network monitoring solution.

You need a network monitoring solution for what you want to do. There are at least a dozen good ones to choose from. Many of which are free: Librenms, cacti, Zabbix, etc.

And yes, you are the only one who has ever asked.

4o4rh

@Teken p54 UPS2 & UPS3 are connected to the same device and you can see their config details on p56. Isn't that the scenario you are trying to create?

mcarson75

I have been having an odd problem with NUT. I have a Cyperpower UPS connected via USB, and all was working well with it. For some reason, it suddenly stopped reporting status, and said "Waiting for daemon" or something like that.

I did some digging and it appeared that the driver was not loaded. I tried to load it manually with upsdrvctl start office but that said "Driver failed to start." I then loaded it with upsdrvdtl -u root start office and it loaded and now works. I have to do this every time I boot pfsense.

It did this with 2.4.5 and now with 2.5.0. Any ideas on what the issue might be?

Sir_SSV

@mcarson75 said in NUT package:

I have been having an odd problem with NUT. I have a Cyperpower UPS connected via USB, and all was working well with it. For some reason, it suddenly stopped reporting status, and said "Waiting for daemon" or something like that.

I did some digging and it appeared that the driver was not loaded. I tried to load it manually with upsdrvctl start office but that said "Driver failed to start." I then loaded it with upsdrvdtl -u root start office and it loaded and now works. I have to do this every time I boot pfsense.

It did this with 2.4.5 and now with 2.5.0. Any ideas on what the issue might be?

What a coincidence. I haven’t upgraded to 2.5.0 (still on 2.4.5) and the other night I rebooted pfSense and the nut Daemon was reporting the same error.

I thought it was because I haven’t upgraded to 2.5.0.

For now I have stopped the nut service

mcarson75

@sir_ssv It's interesting - just after I posted I decided to unplug my USB wireless keyboard/mouse adapter from pfsense and reboot. Surprisingly - NUT works as expected now. So if you have any other USB devices maybe try unplugging them?

Sir_SSV

@mcarson75 said in NUT package:

@sir_ssv It's interesting - just after I posted I decided to unplug my USB wireless keyboard/mouse adapter from pfsense and reboot. Surprisingly - NUT works as expected now. So if you have any other USB devices maybe try unplugging them?

I have a Eaton ups and it is connected via ethernet. I’m thinking the nut daemon was updated however because I’m holding out on upgrading to pfSense 2.5.0 it is causing some conflicts.

Same thing happened just prior to me upgrading to 2.4.5

DurUser

@sir_ssv
I think you have to set the branch manually to 2.4.5.
Mine was set to 2.5 automatically and then I experienced all kinds of weirds things.
Once set back to 2.4.5 and forced package re-install everything was fine again.
Not sure if it's related but....
(https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html)

dennypage

@duruser said in NUT package:

I think you have to set the branch manually to 2.4.5.
Mine was set to 2.5 automatically and then I experienced all kinds of weirds things.
Once set back to 2.4.5 and forced package re-install everything was fine again.

Yea, definitely have to explicitly set the branch. I ran into that issue when I had to roll back to 2.4.5 to diagnose a IPsec issue. When the install started automatically installing packages, things started going wrong all over the place. I ended up having to force a reinstall of all packages in the system.

I'm now back to running 24.02, but my main UPS is SNMP so I haven't tried a USB based UPS with the new version. Please let me know if you run into a problem with USB after upgrading.

DurUser

@dennypage Same here.
It had switched the brach to 2.5 automatically and that caused issues. I didn't know it would do that.

Gertjan

@dennypage said in NUT package:

so I haven't tried a USB based UPS with the new version.

Didn't even know that there was an issue with NUT.
My APC USB UPS's, connected directly, or indirectly, over to an Syno NAS, works just fine.

@mcarson75 said in NUT package:

upsdrvdtl -u root start office and it loaded and now works. I have to do this every time I boot pfsense.

A candidate for the Shellcmd package ?
Btw : how is it connected ? Is it found during the kernel - hardware detection phase ? - see de boot or dmesg log.

Sir_SSV

@dennypage said in NUT package:

@duruser said in NUT package:

I think you have to set the branch manually to 2.4.5.
Mine was set to 2.5 automatically and then I experienced all kinds of weirds things.
Once set back to 2.4.5 and forced package re-install everything was fine again.

Yea, definitely have to explicitly set the branch. I ran into that issue when I had to roll back to 2.4.5 to diagnose a IPsec issue. When the install started automatically installing packages, things started going wrong all over the place. I ended up having to force a reinstall of all packages in the system.

I'm now back to running 24.02, but my main UPS is SNMP so I haven't tried a USB based UPS with the new version. Please let me know if you run into a problem with USB after upgrading.

Thanks!
Took your advice and rolled back to 2.4.5 (had no idea that was an option in pfSense)
Reinstalled the nut package and everything is working perfectly again :)

kesawi

@sir_ssv said in NUT package:

What a coincidence. I haven’t upgraded to 2.5.0 (still on 2.4.5) and the other night I rebooted pfSense and the nut Daemon was reporting the same error.

My NUT driver suddenly started reporting the error about 24 hours ago. Still on 2.4.5 and hadn't rebooted, upgraded or changed anything in pfSense. Running through SNMP on a Cyberpower RMCARD203.

@duruser said in NUT package:

I think you have to set the branch manually to 2.4.5.

I reset the branch manually and reinstalled NUT which has appeared to have fixed the issue.

Not sure why things just stopped working.

dennypage

@kesawi said in NUT package:

Not sure why things just stopped working.

Strange. You didn't update or install any new package since February 15th?

FWIW, the core reason this happens is because the latest stable repo doesn't have a version number in the name. When a new stable is released, it overwrites the prior repo configuration. When you explicitly set the branch, it uses the repo that specifically matches that version.

You can see the current repo in <pkg_repo_conf_path> in the config file. Your system likely has three repos to choose from:

pfSense-repo-245.conf (2.4.5 repo)
pfSense-repo-devel.conf (current stable repo)
pfSense-repo.conf (dev snapshot repo)

pfSense-repo-245.conf was pfSense-repo.conf until 2.5.0 was released.

Teken

@dennypage Is this why NUT has suddenly stopped working on my 2.4.5 release? NUT Error.PNG

What exactly do I need to do to resolve this issue? I've already stopped and started the service. I haven't uninstalled and reinstalled the NUT application as I was going to upgrade to 2.5.0 but have read of some issues. So, will sit on the side lines until another release is out.

Everything was working just great since my 2.4.5 install which covers more than nine months if not longer. Now all of the sudden it's broken out of no where?!?

dennypage

@teken If you wanting to stay on 2.4.5, you need to explicitly set the branch in System -> Update to "Previous stable version (2.4.5 DEPRECATED)". Following that, re-install the NUT package via System -> Package Manager.

Teken

@dennypage If it hasn't been stated today your continued support and insight in the forums with respect to NUT is greatly appreciated!

Followed your steps and had to reboot a couple of times for the system to allow me to install NUT.

Your Rock & Know It . . .

Thank You ~ Sir!

kesawi

@dennypage said in NUT package:

Strange. You didn't update or install any new package since February 15th?

No I haven't done either of those. The only thing that changed in my pfSense configuration was adding two extra dynamic DNS providers last week. The errors just started suddenly yesterday with no changes made.

dennypage

@teken Very kind of you to say. Thank you.