NUT Package (2.8.1 and above)

bashers46899

Im having issues getting pfsense to conect to the NUT server on my Synology whilst that connection work on other servers on my system:
"ld-elf.so.1: Shared object "libssl.so.30" not found, required by "upsmon"
nut sysutils 2.8.2
PfSense Version 2.7.0-RELEASE (amd64). Installed clean, not upgraded

Synology 192.168.2.3
"synoups.conf"

ups_enabled="yes"
ups_mode="usb"
ups_safeshutdown="no"
ups_acl="192.168.2.1|192.168.2.12||||"

"upsd.users"

[monuser]
password = slave

Home Assistant connects to this and outputs ;

"domain": "nut",
      "title": "synology.home.lan:3493",
      "data": {
        "host": "synology.home.lan",
        "port": 3493,
        "username": "**REDACTED**",
        "password": "**REDACTED**"

Home Assistant Status 192.168.2.12 (excert):

"status": {
        "battery.capacity": "9.00",
        "battery.charge": "100",
        "battery.charge.low": "20",
        "battery.charge.restart": "0",
        "battery.energysave": "no",
        "battery.protection": "yes"

PfSense config 192.168.2.1

cat /usr/local/etc/nut/upsmon.conf
MONITOR ups@192.168.2.3 1 monuser slave slave

Log output when started manually:

starting NUT
ld-elf.so.1: Shared object "libssl.so.30" not found, required by "upsmon"

bashers46899

@bashers46899
Looked up the error "shared object "libssl.so.30" not found" and can see it was possibly resoloved by an upgrade from 2.7.0 to 2.7.3.
I've done this, reinstalled the NUT package amd it all seems fine now:

dennypage

@bashers46899 said in NUT Package (2.8.1 and above):

Im having issues getting pfsense to conect to the NUT server on my Synology whilst that connection work on other servers on my system:
"ld-elf.so.1: Shared object "libssl.so.30" not found, required by "upsmon"
nut sysutils 2.8.2
PfSense Version 2.7.0-RELEASE (amd64). Installed clean, not upgraded

The version of OpenSSL changed with 23.09/2.7.1. The error you experienced happens when a version of the package that is intended for 23.09/2.7.1 or above is installed on an older version of pfSense (23.05/2.7.0).

NUT 2.8.2 should not have been offered for installation with 23.05/2.7.0. That said, you are not the only person who has experienced this, so I think there is/was a hiccup related to the package repo.

EDIT: there is a note about resolving the package repo issue here.

Unoptanio

@dennypage
NUT 2.8.1
PFSENSE 2.7.1

Riello Sentinel Pro 2200 with USB cable

after 4 days of being connected the disconnection problems reoccur

only by restarting the service did it restart

various email notifications:

Notifications in this message: 3
================================

18:23:40 UPS Notification from xxx-pfSense.home.arpa - Sat, 09 Dec 2023 18:23:40 +0100

Communications with UPS SentinelPRO lost
18:23:44 UPS Notification from xxx-pfSense.home.arpa - Sat, 09 Dec 2023 18:23:44 +0100

Communications with UPS SentinelPRO lost
18:23:49 UPS Notification from xxx-pfSense.home.arpa - Sat, 09 Dec 2023 18:23:49 +0100

UPS SentinelPRO is unavailable

mlake

@dennypage I haven’t had a single erroneous ‘connection lost’ notification in the last week, so I’d guess that your patch did the trick. Thank you!

whoami TM

I'll apologize in advance, but I need some help getting pointed in the right direction.

I have a APC Back-UPS Pro Gaming 1500VA UPS BGM1500B that was working fine in 23.09 on my SG-4860. SG-4860 died and migrated to a XG-7100 that was still on 2.4.4 when I received it. Netgate sent me 23.09.1 and I haven't been able to get my APC to stay connected for longer than 24hrs.

This makes it harder for me to trouble shoot since I've never had it working on this box.

I had to use the "user=root" in ups.conf to get it to show when i first connected the usb. I also tried adding the quirk with

  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000
  bMaxPacketSize0 = 0x0040
  idVendor = 0x051d
  idProduct = 0x0002
  bcdDevice = 0x0106
  iManufacturer = 0x0001  <retrieving string failed>
  iProduct = 0x0002  <retrieving string failed>
  iSerialNumber = 0x0003  <retrieving string failed>
  bNumConfigurations = 0x0001
  
usbconfig add_dev_quirk_vplh 0x051d 0x0002 0x0000 0xffff UQ_HID_IGNORE

But still cant get past 24hrs. The 2 USB 2.0 ports on the XG-7100 will only stay connected to the UPS for a few hours at most. The USB 3.0 port will give me about 24hrs.

I remember reading in the old post about something to do specifically for APC but not sure if that applies to this version of NUT.

Thanks

Unoptanio

@whoami-TM

Sorry, for those who have APC UPS: isn't it better to use the specific package?

Unoptanio

此回覆已被刪除！

Unoptanio

@Unoptanio said in NUT Package (2.8.1 and above):

NUT 2.8.1
PFSENSE 2.7.1

Riello Sentinel Pro 2200 with USB cable

NUT 2.8.2
PFSENSE 2.7.2

Riello Sentinel Pro 2200 with USB cable

From December 9th to today December 17th it has no longer been disconnected.
In the meantime, however, I updated to pfsense 2.7.2

BaseBallHat

I have a UPS connected to my Synology NAS via USB port. Synology NAS acts as a UPS Server, which in turn is connected to the pfSense NUT service, 2.8.2, all on the same network. All is mostly working well with status displayed on both systems.

Recently, though, I had an automatic shutdown of my pfSense, which is good, but I want to have this automatic shutdown delayed by 10 minutes. I have ~1-2x/month a very brief power outage, only 1-2 seconds. It's enough to trigger the UPS and make me reset some clocks though!

Here are the pfsense logs implementing the shutdown process. Note, this was another brief power outage of a few seconds. This was not a long outage. How can I delay the pfSense shutdown process by 10 minutes, so the UPS recovers its normal operating status?

Screenshot from 2023-12-17 16-58-09_page1.jpg

pfpv

@BaseBallHat said in NUT Package (2.8.1 and above):

Recently, though, I had an automatic shutdown of my pfSense

I came here to post about the exact same problem. I have the same setup - an APC UPS connected to Synology that serves as a UPS server. I've had this setup for a couple of years without issues. I recently updated pfSense Plus to 23.09.1 and I guess this updated the nut package to 2.8.2.

Today my pfSense suddenly shut down. I got a message in Pushover "Auto logout and shutdown proceeding". I didn't understand what was going on as there was no power failure. I ran to the basement and everything was on except pfSense. The UPS's fan was on, so I guess the UPS did a self-test. I noticed before that my Back-UPS RS 1500G and other similar units do self-tests from time to time and those that have fans turn them on for some time. This never caused a problem.

I logged into Synology and there was no sign of any UPS event in the logs or anywhere, it was actually happily doing data scrubbing (and successfully finished it later). I went to check pfSense's logs and found what you found:

UPS ups@192.168.0.61: administratively OFF or asleep

And later:

Executing automatic power-fail shutdown
Auto logout and shutdown proceeding
halt by root:

I've never seen that "administratively OFF or asleep" message before but according to man for upsmon it's a valid message. But why does it cause shutdown? Logically it shouldn't. If the UPS is off it's too late to shutdown. Also, I wonder why Synology doesn't see such messages or maybe it ignores them.

If there are any developers here, please look into it. It started happening since nut was updated to 2.8.2. I think I would have to disable it until this is looked into. This message shouldn't cause shutdown.

P.S. Found posts about this issue with unraid: https://forums.unraid.net/topic/60217-plugin-nut-v2-network-ups-tools/page/40/
See the quoted post. Seems to be version-related. When rolled back to 2.8.0 the issue goes away. Is there any way to roll back to the previous version of NUT? It seems this may not be easy as there is something about SSL certificates and the recent update of OpenSSL. Can anyone advise?

dennypage

@BaseBallHat By default, NUT initiates a shutdown when the UPS declares a low battery situation. It's best to stay with this default behavior.

You may have gone into your Synology and set "Customize time" in the UPS configuration. If you have, I would suggest returning it to the default of "Until low battery" to restore the default NUT behavior.

dennypage

@pfpv said in NUT Package (2.8.1 and above):

I've had this setup for a couple of years without issues. I recently updated pfSense Plus to 23.09.1 and I guess this updated the nut package to 2.8.2.

Today my pfSense suddenly shut down. I got a message in Pushover "Auto logout and shutdown proceeding". I didn't understand what was going on as there was no power failure. I ran to the basement and everything was on except pfSense. The UPS's fan was on, so I guess the UPS did a self-test. I noticed before that my Back-UPS RS 1500G and other similar units do self-tests from time to time and those that have fans turn them on for some time. This never caused a problem.

A shutdown being initiated during a self test usually indicates that the batteries are failing. How old are the batteries? UPS batteries need to be replaced every three years or so.

pfpv

@dennypage You misunderstood the issue. Please re-read the posts and the link I provided. There was no shutdown initiated. The batteries are only about 1 year old. The Synology didn't even log anything.

Have you seen this message from a UPS before "administratively OFF or asleep"? In the link I posted it is explained that sometimes APC UPS's send an OFF message during self tests and at the same time they send NOTOFF. Before NUT 2.8.2 the OFF message was ignored. Now it causes a shutdown.

Interestingly, NUT is only at 2.8.1 version itself: https://github.com/networkupstools/nut/releases Where did the 2.8.2 come from?

We need to roll back to avoid APC UPS unexpected shutdowns. Is there a way to roll back?

dennypage

@pfpv I you would like my recommendation on a solution, the first thing I would do is connect the UPS to a system other than a Synology as Synology has a rather messed up NUT implementation, and only support Synology systems as clients.

In my opinion, it would be much better to use pfSense or a linux system as the server and have the Synology be a client. FWIW, after doing this I would also recommend a run-time calibration, regardless of how old your batteries are.

In answer to your questions about versions: The version of NUT is actually FreeBSD's nut-devel-2023.10.07_1, which is based on git just prior to the 2.8.1 release. You can see this on the Installed Packages screen. The upper level package, pfSense-pkg-nut-2.8.2, is labeled as 2.8.2 because of a mistake being made at the moment of package publication. This is mentioned earlier in this thread. The published package should have been pfSense-pkg-nut-2.8.1_1, but once it was published as 2.8.2 the version number could not be downgraded. It doesn't affect anything other than human perception. If you really want to know more, you can read the discussions in the Redmine and Git PRs.

hspindel

Have read through all the config recommendations above, and still not working.

pfSense+ 23.09-RELEASE running on Netgate 8200

Trying to connect Home Assistant to NUT. Eaton UPS already connected to NUT running locally on pfSense with no issues. NUT package 2.8.0_2. Quirk installed to make NUT work properly, but don't remember now what I did.

Changed nut.conf MODE=netserver
upsd.users: added a new user and password, upsmon slave
Changed upsd.conf. Added LISTEN <ipOfPFsense> 3493

Attempt to login to NUT from Home Assistant with:
Host: <ip of pFsense>
Port: 3493
Username: new user added above to upsd.users
Password: password for new user in upsd.users

Home Assistant always reports Failed to Connect to NUT Server.

Have tried many variations on the above, but no success. Restarted NUT after each attempted config change.

Home Assistant and pfSense are on the same network, so I don't think this is a firewall issue. Default allow LAN to any rule is present.

dennypage

@hspindel said in NUT Package (2.8.1 and above):

Changed nut.conf MODE=netserver
upsd.users: added a new user and password, upsmon slave
Changed upsd.conf. Added LISTEN <ipOfPFsense> 3493

nut.conf is not used on pfSense. You are not hand editing the ups config files are you? If you are, then that's not the right way to configure NUT on pfSense--every time you restart they will be overwritten.

Please post the configuration you have in Services / UPS / UPS Settings.

hspindel

@dennypage said in NUT Package (2.8.1 and above):

nut.conf is not used on pfSense. You are not hand editing the ups config files are you? If you are, then that's not the right way to configure NUT on pfSense--every time you restart they will be overwritten.

Please post the configuration you have in Services / UPS / UPS Settings.

nut.conf is the only file I hand edited because I couldn't see how to do it in the GUI. The rest of the files I used the GUI to modify.

What is the right way to specify MODE=netserver?

My config page looks like this:

UPS Type: Local USB
UPS Name: EatonUPS
Enable notifications: yes
Driver: usbhid
No extra arguments to driver
No extra arguments to upsmon.conf
ups.conf: pollinterval=10
upsd.conf: LISTEN pfSenseIP 3493 (also tried LISTEN 0.0.0.0 3493)
upsd.users:
[howard]
password=xxxxxxx
upsmon slave

Thank you!

dennypage

@hspindel said in NUT Package (2.8.1 and above):

What is the right way to specify MODE=netserver?

There isn't one. The file nut.conf is unused in pfSense, and most other places. It is intended to be used by generic OS distributions, but I haven't really seen much uptake on it for the systems I work with.

Returning to the attempt to connect remotely... Have you checked the firewall log? Are you able to successfully telnet to port 3493 from the LAN?

hspindel

@dennypage said in NUT Package (2.8.1 and above):

There isn't one. The file nut.conf is unused in pfSense, and most other places. It is intended to be used by generic OS distributions, but I haven't really seen much uptake on it for the systems I work with.

Okay, then NUT on pfSense is automatically configured as remotely accessible? I haven't found a setting to enable/disable it.

Returning to the attempt to connect remotely... Have you checked the firewall log? Are you able to successfully telnet to port 3493 from the LAN?

Nothing in the firewall logs. Yes, I can telnet in. There is no banner message, but if I type Hello I get a response ERR UNKNOWN-COMMAND. Tried to guess at a valid command. "LIST UPS" returned a good looking response. Couldn't guess any other commands.

So perhaps this is more a problem in Home Assistant.