APCupsd package status for pfSense
-
Same here…
we also have the issue that pfsense is halted with message "press any key to reboot" instead of shutting down the power.
Power on USB isn't availiable for our supermicro mainboard.regards
-
On the FreeBSD OS, there is no known way for a user program to get control when all the disks are synced. This is needed for apcupsd to be able to issue the killpower command to the UPS so that the UPS shuts off the power. To accomplish the same thing on FreeBSD systems, make sure you have a SmartUPS and that your UPS shutdown grace period is set sufficiently long so that you system will power down (usually 2 minutes), the use the –kill-on-powerfail option on the apcupsd command line.
http://www.apcupsd.com/manual/manual.html#freebsd
This means kill power doesn't work for pfsense?!
-
Thanks for raising that issue. I was just testing this the other day and although I'm using NUT to control my pfsense and FreeNAS boxes, my UPS didn't shutdown either so I suspect this is correct.
-
Will this package be updated for the new version of pfsense?
-
Will this package be updated for the new version of pfsense?
Doesn't look likely. https://doc.pfsense.org/index.php/2.3_Removed_Packages
If there is no maintainer, then there is no one to convert it unless the pfSense guys themselves do it (and if they were planning to, it would have said so in the link).
-
Will this package be updated for the new version of pfsense?
Doesn't look likely. https://doc.pfsense.org/index.php/2.3_Removed_Packages
If there is no maintainer, then there is no one to convert it unless the pfSense guys themselves do it (and if they were planning to, it would have said so in the link).
Doh!! I upgraded to 2.3 today, and this is the only package I actually really need :-
During the upgrade it seemed to have removed the package.My fault for not reading or preparing for the update, anyway can I manually install this package outside the supported pfSense package management?
I have a USB attached UPS (CyberPower 550VA) and need this so that my home lab can gracefully shutdown when I have a power outage.
My neighborhood powergrid sucks, we get about half a dozen power blips a year.I'm not too adverse in the BSD package management, I noticed this https://www.freshports.org/sysutils/apcupsd/ not sure if there is a pre-built binary that will work for pfSense. Also tried downloading source of apcupsd-3.14.13 but ran into ./configure failures
-
but the 'nut' package should re-appear.
the link says: nut - not yet converted.
-
Will this package be updated for the new version of pfsense?
On the way.
I've sent a PR for adding apcupsd on pfSense 2.3.
-
Will this package be updated for the new version of pfsense?
On the way.
I've sent a PR for adding apcupsd on pfSense 2.3.
Hi Danilo!
Any news? -
-
Is there a way to give some donations for this? Right now I have only bandaid method to shutdown pfsense from another server hosting apcupsd using custom script. It's not as robust but it's better than nothing. If there is power outage, people without custom solutions will have pfsense just shutoff without shutting down gracefully…
-
Is there a way to give some donations for this? Right now I have only bandaid method to shutdown pfsense from another server hosting apcupsd using custom script. It's not as robust but it's better than nothing. If there is power outage, people without custom solutions will have pfsense just shutoff without shutting down gracefully…
I would be willing to donate to the cause as well, to support this package with functional email alrerts
-
Still nothing here? Is there anyway to get NUT working with an APC UPS that's running apcupsd driver rather than directly USB to pfsense box?
-
I'm not sure why the apcupsd was pulled, but according to the application site, there seems to be a design issue with FreeBSD in how it can shutdown the UPS
http://www.apcupsd.org/manual/manual.html#freebsd
Not sure if that has been resolved, or is part of the reason it isn't considered supported for FreeBSD.
I too would be willing to make a donation to get this package back in -
So is there any chance for this to ever be approved ?
-
NUT itself supports talking with a remote apcupsd instance, although the existing NUT package does not support the configuration. I am working on a new version of the NUT package which will support have support for this configuration. I do not have an eta, but in the interim you could hand edit the files in /usr/local/etc/nut.
Is there anyway to get NUT working with an APC UPS that's running apcupsd driver rather than directly USB to pfsense box?
-
I fixed it for now with configuring NUT the following way:
- Choose Local UPS
- Local UPS Name: <insert name="" here="">- Local UPS model: APC SmartUPS USB
- Local UPS Port: Auto
Save these settings.
Then go to diagnostics > Edit file.
load the folloing file: /usr/local/etc/nut/ups.conf
change the driver and port settings to the following:
driver=apcupsd-ups
port= <hostname of="" your="" system="" where="" apcupsd="" runs="">Save the file.
Start the NUT service.This works for me.
</hostname></insert> -
The new NUT package is available for testing if you are interested:
