-
NUT itself doesn't invoke self-tests on a schedule. This is done by the UPS itself.
There are usually configuration parameters that can be viewed and modified in the UPS. The complete list of NUT variables can be found here. Note that a given UPS model will generally only offer a small subset of these variables. Use the upsrw command to discover the list of variables you can modify. For your particular issue, the variable you are looking to modify is ups.test.interval.
Further information on running commands can be found here. Be careful.
-
Thanks Denny!
After using upsrw, and only getting three outlet switch options, a delay shutdown and ups.id as modifiable, I fear a call to TrippLite is in order..
-
Your UPS is a network model, yes? If so, is there anything that is connecting to the UPS that could be initiating the self test?
-
No, it's the non-network model.. I've got two usb cables plugged into it.. One to a (stupid) Windows 7 machine I need for Photography work, and the other goes to the BSD rig.. I've slightly cheated a little here, the cable is plugged into a freenas machine and I have pfsense nut talking to nut on the nas. It's all bsd nuts though and so apparently they can't do anything but report it seems and I know the people here are nicer. =)
Here's a link to the unit I have https://www.tripplite.com/smartpro-120v-2.2kva-1.6kw-line-interactive-ups-tower-snmpwebcard-option-usb-db9-serial~SMART2200VS/
If you know of a way to replace Lightroom on a *Nix/BSD System, I'm all ears!
Thanks Danny!
-
Different story then. NUT doesn't initiate a self-test by default, and the pfSense NUT package doesn't initiate a self-test, but that doesn't mean that the FreeNAS NUT package isn't doing it or that Windows isn't doing it. Before calling Tripplite, I would disconnect all but one USB or RS-232 cable and test each system stand-alone to see if it still happens.
I can't help you with Windows I'm afraid. I stopped running Windows around the XP timeframe. For a nice and cuddly Unix UI environment, I use Mac. As I recall, Lightroom runs a bit better on Mac than Windows. Adobe used to let you turn your Windows license in and get a Mac license in exchange, but I don't know if they still do that.
First time in my life someone has referred to me as one of the nicer people. :)
-Denny
-
It's always a different story when Microcrap is involved, isn't it…. I'd love to drop kick them to next century, but I refuse to give Apple any money. I've never liked how the OS was setup and you're stuck with whatever they let you have. but that's another topic, lol..
I've removed any trace of ups software from wincrap, and I may disable the service on the nas rig for a day and see, seem easier than trying to reach cables.. :/
I would have thought that the NUT service is the same on both PF and FreeNas and thus has the same functionality/or lack thereof. Incorrect presumption?
I've been a light user of *Nix/BSD since Slackware 4ish iirc and FreeBSD 3ish, I've just never been able to drop win as the software wasn't there for *nix/bsd. Now the only holdup is LR, and running LR under a VM just doesn't get it done, tried that recently..
These days, Adobe wants you to pay them monthly for their software, and if you refuse and buy the standalone, they remove features... bastids..
First time for everything! :) Anyone that can take what could be a stupid and/or silly question/issue and reply with helpful info in a concise manner gets my nice vote... 8)
-Scott
-
I would have thought that the NUT service is the same on both PF and FreeNas and thus has the same functionality/or lack thereof. Incorrect presumption?
The NUT distribution itself is the same, but the package that configures and runs it is quite different. If you look at your pfSense system, you will see two packages:
nut-2.7.4_1 Network UPS Tools pfSense-pkg-nut-2.7.4_4 Network UPS ToolsThe first one is the NUT package itself and the second one the the pfSense package for NUT. The pfSense package is what controls the NUT configuration and starts the NUT service.
-
Thanks Denny for some clarification there.
Is it wrong of me to then presume that pfSense has a control package for every add-on service/package?
If that's the case, is it possible to run other freebsd packages separately?
Thanks again! Hope I'm not too ot or anything.
-
The list of supported packages for your pfSense version can be found in System / Package Manager / Available Packages. There are a good number of excellent FreeBSD packages directly supported in pfSense.
There are also many packages that are in FreeBSD that are not directly supported in pfSense. If you are interested in installing FreeBSD packages that are not directly supported by pfSense, you can search the forums for instructions on how to do this. In general, I would recommend against using unsupported packages unless 1) you have a very strong need for the package on your firewall, and 2) you are extremely confident of the security implications of having the package running on your firewall.
-
I indeed know and run many of the great packages in the package manager, a couple don't seem to like me too much, but that's another topic.
I've been very thrilled with how well all the Devs and supporters have made pfSense, it's been great so far the last couple months. I was merely wondering and curious if the standard ports tree was supported considering pfSense having it's own controller packages.
I completely agree with both of your conditions of usage, if it ain't broke don't fix it, and if you don't know wth your doing, don't do it. It's why we have Allow All on the WAN right? ::) :P
Thanks again for all the time and help Denny!
-
Is there any support for graphs like apcupsd has on IPCOP?
See attachments, really like how they make a daily, weekly, monthly & yearly graph for the stats that can be taken from the UPS:temperature and battery voltage min. / max. line voltage remaining runtime supplying voltage load capacity min. /max. battery chargeAttached two example graphs.
 -
Not at this time.
-
Ok, would be awsome if it could be added!
Still run an old IPCOP box just for that reason, would be nice to switch it to pfSense :) -
@Per:
Ok, would be awsome if it could be added!
Still run an old IPCOP box just for that reason, would be nice to switch it to pfSense :)Yes, it would be nice to have. However, I wouldn't view this is a sufficient reason to stay with IPCop as the IPCop distribution really isn't being kept up to date. Security is more important that voltage monitoring.
-
… Security is more important that voltage monitoring.
Like this :
pfSense is handling my network flux.
My UPS is monitoring all the 'electric' stuff - and exposing its finding by snmp. I use NUT just for the 'shutdown properly' when power goes to zero … -
I'm having issues with NUT shutting down the pfSense, but it is NOT shutting down the UPS after the pfSesnse shuts down.
I am using a CyberPower UPS, with all default settings of the NUT package in pfSense. I am using the driver of 'usbhid-ups'. It is able to monitor the UPS without any issue.
From an ssh console of pfSense, if i issue 'upsdrvctl shutdown' it will shut down the UPS, so at least I know the driver works properly. But how do I get it so that it will shutdown the pfSense physical server, and then shutdown the UPS immediately after? It seems like it should just "work" based on what I've read about NUT, but perhaps I am missing a setting.
The reason I need it to behave this way is that if the UPS battery is good for 30 minutes, pfSense shuts down after 20 minutes. Then there is 10 minutes battery remaining - and if power resumes before the UPS is fully depleted, there is no way for the pfSense server to know that power was restored, and it will stay in an off situation, requiring human intervention.
Thanks!
-
bdf0506, can you please confirm that you haven't modified any of the system or nut scripts by hand? I will have a look at this, but it will be about a week before I can.
-
Thanks for the reply. I've added a LISTEN section into upsd.conf for another device to query NUT, but that is all. Everything else should be the default.
I'm not convinced this is an issue with the pfsense port of NUT, but perhaps its a NUT configuration setting all together that I am missing. I have noticed that some of the files - especially upsmon.conf are missing a lot of values vs the sample file, but maybe some of those fields are just the default fields.
Here's the config files that I have:
[2.3.4-RELEASE][root@pfSense.home]/root: cat /usr/local/etc/nut/ups.conf [ups] driver=usbhid-ups port=auto[2.3.4-RELEASE][root@pfSense.home]/root: cat /usr/local/etc/nut/upsd.conf LISTEN 127.0.0.1 LISTEN ::1 LISTEN 192.168.10.1 3493[2.3.4-RELEASE][root@pfSense.home]/root: cat /usr/local/etc/nut/upsmon.conf MONITOR ups 1 monuser 615fdd64b1d37893a33d master SHUTDOWNCMD "/sbin/shutdown -p +0" POWERDOWNFLAG /etc/killpower NOTIFYCMD /usr/local/pkg/nut/nut_email.php NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC NOTIFYFLAG FSD SYSLOG+WALL+EXEC NOTIFYFLAG COMMOK SYSLOG+WALL+EXEC NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC NOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXEC NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC NOTIFYFLAG NOCOMM SYSLOG+WALL+EXEC NOTIFYFLAG NOPARENT SYSLOG+WALL+EXEC[2.3.4-RELEASE][root@pfSense.home]/root: cat /usr/local/etc/nut/upsd.users [admin] password=ca21ff457d2db2f4d776 actions=set instcmds=all [monuser] password=615fdd64b1d37893a33d upsmon masterAnd here is an output of my actual ups device, showing that NUT is working and can connect to it.
[2.3.4-RELEASE][root@pfSense.home]/root: upsc ups@localhost battery.charge: 28 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 714 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 12.9 battery.voltage.nominal: 12 device.mfr: CPS device.model: EC650LCD device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: CyberPower HID 0.4 driver.version.internal: 0.41 input.transfer.high: 142 input.transfer.low: 100 input.voltage: 123.0 input.voltage.nominal: 120 output.voltage: 123.0 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 16 ups.mfr: CPS ups.model: EC650LCD ups.productid: 0501 ups.realpower.nominal: 390 ups.status: OL CHRG ups.test.result: No test initiated ups.timer.shutdown: -60 ups.timer.start: 0 ups.vendorid: 0764[2.3.4-RELEASE][root@pfSense.home]/root: upsdrvctl -t shutdown Network UPS Tools - UPS driver controller 2.7.4 *** Testing mode: not calling exec/kill 0.000000 If you're not a NUT core developer, chances are that you're told to enable debugging to see why a driver isn't working for you. We're sorry for the confusion, but this is the 'upsdrvctl' wrapper, not the driver you're interested in. Below you'll find one or more lines starting with 'exec:' followed by an absolute path to the driver binary and some command line option. This is what the driver starts and you need to copy and paste that line and append the debug flags to that line (less the 'exec:' prefix). 0.000219 Shutdown UPS: ups 0.000240 exec: /usr/local/libexec/nut/usbhid-ups -a ups -k -
In package manager, I can see nut is installed, but there is an orange warning "Newer version available", followed by a "Package is configured but not (fully) installed". No update button exists. See attached screenshot.
Something I must do here?
-
There is nothing you need to do. What you are seeing below the blue line is actually the legend for the entire package list. I.E. what the icons and colors mean. If you only have one package installed, it can be visually confusing.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.