-
@renegade said in NUT package:
I get an message by PfSense that the UPS has been disconnected from pfsense
Can you show the message ?
-
@dennypage Alright, thank you. Understood and good to know that I can stop trying testing different things.
@gertjan I‘ll configured pushover to send me messages:
Firewall: firewall.home
UPS Notification from firewall.home - Mon, 24 Oct 2022 03:47:12 +0200Communications with UPS ups lost
————————————-
Firewall: firewall.home
UPS Notification from firewall.home - Mon, 24 Oct 2022 03:47:17 +0200Communications with UPS ups established
-
-
@gwaitsi said in NUT package:
@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 or @gwaitsi - Did you ever find a way to do this - read the status from multiple UPS units into NUT? I just made a post along similar lines before finding these messages. But that rogerprice.org website seems to be down now, did either of you by chance save that PDF?
-
@occamsrazor no. the more I thought about the problem, I put it on the back burner.
- I have a dumb battery on the J1900
- I have an APC smart UPS on the NAS upstairs
- in between are a couple of switches.
a) if I shut the J1900 down after x minutes due to loss of comms,
I wouldn't be able to restart it because you can't use the netgear switches as a WakeOnLAN for providerb) I am now using ZFS as pfsense the file system and I should get about 30-60min with the battery.
If the outage is longer, the ZFS should provide a more resilient recovery (I think). I can then simply use the PowerOn Restore BIOS option to force the restart.On balance, I decided it was easier to take the risk of a long outage and get the benefit of an autorestart. Of course, it would have been a different story if i could have used the netgear switches to trigger WakeOnLAN for the pfsense box
-
NUT (2.7.4_20) with CyberPower RMCARD205 incorrect decimal point (0.1) vari.: battery.runtime
Problem with CyberPower RMCARD205 + NUT installations, maybe it's time to switch to 2.8
( https://www.freshports.org/sysutils/nut ), as the "snmp-ups" driver does not include this type either.
The problem with this wrong value is that, the shutdown threshold slips by, say, from a few minute (20%) - to a few hour :) and thus, - the UPS protection does not work in real time.
(because it "thinks" there are 5 hours left in the batteries, but in fact there are only 5 minutes left)I repeat, only with this network SNMP card which we use RMCARD205 and unfortunately with the old driver set "driver.list" - snmp-ups...
OLD "snmp-ups" file in pfS inst driver.list NUT.:
RMCARD205 web interface:
pfS NUT console:
According to new compatibility:
-
@daddygo said in NUT package:
maybe it's time to switch to 2.8
Pending pull request and redmine issue.
-
Hi Denny,
Super then we thought of one (2.8) and hope it will happen quickly as we have purchased 10 pcs. 1.5KVA UPS units with RMCARD205.
(I say softly - yeah, my fault for not checking the pfS NUT package and the RMACARD drivers first)Anyway thanks for your sacrificial work with this package, I have been watching it for a while...
-
D dennypage referenced this topic on
-
D dennypage referenced this topic on
-
D dennypage referenced this topic on
-
This post is deleted! -
@Viper_Rus i assume you found the answer to supporting Synology elsewhere in the thread.
-
I‘m having the issue that I get a shutdown loop after the UPS battery is empty.
pfSense shutdown as expected. After power restores the UPD turns on and pfSense boots up. Couple of seconds later the UPS is doing battery check. This seems to trigger pfSense to shutdown again and turns of UPS aswell. This loop continues until I unplug communication to the UPS and wait that battery gets fully charged.
You can see here that the input power is available but the UPS is getting the signal from pfSense to not charge. After couple of seconds pfSense and UPS shutdown.
-
@mrsunfire please post your config. And your UPS model.
-
@dennypage Config is vanilla (no change). UPS is APC Backups Pro 550 via USB.
-
@mrsunfire Hmm... I would have expected there to be some config change, either in the NUT package or in the UPS, as the UPS should not be bringing the load back on that quickly (0%). Nor would I expect it to show "On Line" and "Discharging" like that unless a calibration cycle were underway.
Speaking thereof, have you run a battery calibration recently? Perhaps the battery is dead...
Lastly, can you post the output of upsrw?
-
@dennypage No calibration. I wo der why UPS switches back on battery the moment I connect pfSense.
Whats the command for that output?Netgate 6100 MAX
-
@mrsunfire How old it the UPS and battery?
Please post the output of upsrw. If you aren't familiar with that, you can find examples in this thread.
-
@mrsunfire I was having weird issues in the last and it turned out to be a bad battery not the software.
-
@jonathanlee Yes I already ordered new batteries before continue further testing.
I also did edit upsmon.conf and removed "SHUTDOWNCMD "/sbin/shutdown -h +0"". Unfortunately after reboot this setting is back there. How to proper edit that file? My goal in the first step was to not shutdown the pfSense at all.
Netgate 6100 MAX
-
@mrsunfire said in NUT package:
Unfortunately after reboot this setting is back there. How to proper edit that file? My goal in the first step was to not shutdown the pfSense at all.
Fast answer : you can't.
As the GUI states, this is what gets inserted in that file :
And this is what gets inserted upfront by the GUI interface, even when you leave that bloc empty :
/usr/local/pkg/nut/nut.inc line 250->252
( so, edit that file and do whatever you want ^^ )
-
@mrsunfire said in NUT package:
I also did edit upsmon.conf and removed "SHUTDOWNCMD "/sbin/shutdown -h +0"". Unfortunately after reboot this setting is back there.
You can't. If you want to prevent NUT operation (shutdown and everything else), change the UPS Type to disabled until you replace the battery.
