System Shuts Down when UPS does a Self Test
-
@Chunks said in System Shuts Down when UPS does a Self Test:
Unfortunately, I'm a little confused by the versioning that's going on here. It seems possible to me, that the PFSense package is using a release from just before this fix? Even though it's labeled as 2.8.2 in the pfsense Package list, I'm not sure if that directly correlates to the underlying NUT version.
From the NUT support thread:
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.
-
FWIW, I am having the same problem as OP. My pfSense is the ONLY device that is randomly shutting down. I have Synology NAS devices also running NUT client (slave) to the same NUT server that is on a Rasp PI and they stay up the entire time. This started a couple of weeks ago and has happened twice now (I think each time was a Friday). I'm fairly certain this started around the time of the pfSense 23.09-1 release.
NUT Server 2.7.4 (on a Rasp Pi)
pfSense+ 23.09-1-Release
NUT 2.8.2 package on pfSenseIs there any way to tell when the NUT server will next run a system test? Maybe I could keep an eye on things and see what occurs.
I'm guessing the resolution to this needs to come in the way of a NUT package update or another pfSense patch or update?
-
@mtk67 with your current configuration, you will need to wait for a NUT update. However if you reverse the situation and run pfSense as the master/primary and Synology as the slave/secondary, it will also solve your issue. FWIW, using Synology as the primary is not best practice--see the NUT support thread for info on this.
-
@dennypage Thanks but I didn't say I was running Synology as the primary. They are configured as slaves/clients just like the pfSense is. The primary is on a raspberry pi.
-
@mtk67 said in System Shuts Down when UPS does a Self Test:
Is there any way to tell when the NUT server will next run a system test? Maybe I could keep an eye on things and see what occurs.
According to APC, most of their UPS's run a self test every 14 days. Other brands, IDK.
-
@mtk67 said in System Shuts Down when UPS does a Self Test:
Thanks but I didn't say I was running Synology as the primary. They are configured as slaves/clients just like the pfSense is. The primary is on a raspberry pi.
My bad. Yes, running NUT on the pi is a good choice.
It's going to take an update to NUT on pfSense to address the issue. I'm working on that. As a temporary workaround until an update is published, you could have pfSense as the primary.
-
@dennypage No worries. Just wanted to clarify. I really appreciate the info and the suggestion for a temporary fix. I was beginning to worry that I was having a problem with the power supply on the device running pfSense with the random issues, but glad I found this thread and have a better understanding of what is likely occurring. I look forward to the fix in NUT. I may take your advice on the workaround too. Cheers and Happy New Year.
-
S SteveITS referenced this topic on
-
N NeVaR referenced this topic on
-
I would like also like to point out that I also experienced the same thing. I'm running Synology as the primary but it is running on DSM 6.2 so nothing change on Synology. In my case the system shuts down twice but gap is more than 30 days. I also check the log on synology and there no power outage. I'm guessing there change to NUT package that it is very sensitive? Also, have truenas and it didn't report any issue and didn't shutdown.
EDIT: for the meantime, I disable the nut services for now.
-
@NeVaR There is an issue in NUT in the current version of nut-devel in pfSense's copy of the FreeBSD repo. It is fixed upstream, and hopefully will be fixed in the pfSense copy soon.
As an aside, I would recommend that you move the primary to pfSense rather than the Synology. As noted above, running the Synology as primary is not best practice.
-
@dennypage said in System Shuts Down when UPS does a Self Test:
@NeVaR There is an issue in NUT in the current version of nut-devel in pfSense's copy of the FreeBSD repo. It is fixed upstream, and hopefully will be fixed in the pfSense copy soon.
As an aside, I would recommend that you move the primary to pfSense rather than the Synology. As noted above, running the Synology as primary is not best practice.
Unfortunately, synology dsm 6.2 has limited support as nut client. I will try with another UPS
-
@NeVaR said in System Shuts Down when UPS does a Self Test:
Unfortunately, synology dsm 6.2 has limited support as nut client. I will try with another UPS
It's been a while, but DSM 6 had support for remote NUT. They don't document anything but connecting to another Synology ("Synology UPS server"), but as long as you use the required values for ups name, user name and user password, it works fine.
-
S SteveITS referenced this topic on
-
I think I am experiencing the same issue, as I outlined here https://forum.netgate.com/topic/185262/sg5100-shutting-down-unexpectedly
I get the following system log entries
I am running pfSense as the primary, with two Synology-s as secondary units (slaves?)
I guess I just have to wait for the package to be updated on pfSense?
-
@pfguy2018 If you look in the NUT support thread, you will find executables you can use in the interim.
-
@dennypage Thanks!
