similar to: NUT messes up UPS after mains power is restored

UPDATE: I think I know what I did wrong. In step 7, I plugged the mains too early causing a power race condition as described by point #51 here<https://networkupstools.org/docs/FAQ.html> . I thought that when APC BR1500GI's display went black (even with the fans still running) it is already in a shutdown state. This was not the case, it waited for a few more seconds until it totally

On 09/04/2018 12:36 PM, Ong, Kevin wrote: > > I think I know what I did wrong. In step 7, I plugged the mains too > early causing a power race condition as described by point #51 here > <https://networkupstools.org/docs/FAQ.html> . I thought that when APC > BR1500GI's display went black (even with the fans still running) it is > already in a shutdown state. This was not

Hi Charles, Are there any logs generated by the WinNUT client? I'm trying to configure it for the first time and I cannot make it to work. Here are my settings: Nut.conf MODE=netclient Upsmon.conf MONITOR ups at pfsense 1 <username> <password> slave MINSUPPLIES 1 SHUTDOWNCMD "C:\\WINDOWS\\system32\\shutdown.exe -s -t 0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME

Kevin, As Matthijs noted, pfSense uses a circular log file. The default size is ~500KB, which can be a bit small. You can increase the log file size by changing the “Log file size” parameter on the Log management page. Look for the wrench symbol on the system log page (Status / System Logs / System / General). Note that you have to clear the log after changing its size. FWIW, I have mine set to

> On Aug 13, 2018, at 06:17, Charles Lepple <clepple at gmail.com> wrote: > > On Aug 12, 2018, at 11:03 PM, Kevin Mychal M. Ong <kevindd992002 at yahoo.com> wrote: >> >> Hi, >> >> I installed apcupsd through pfsense and noticed some discrepancy with the NUT package. I'm not sure if this is a bug regarding the BATTDATE (apcupsd) and battery.date

On Aug 30, 2018, at 10:05 AM, Ong, Kevin wrote: > > The battery.mfr.date is actually the correct value I'm looking for. That is the exact date the battery was last replaced. And yes, it is the correct value displayed in apcupsd. I think we're on the same page for the battery date. What about the date of manufacture for the UPS - does 2012 seem reasonable? > > For the debug

On Fri, 7 Sep 2018, Ong, Kevin wrote: > Any comments here? I am not a WinNUT user, but in general NUT clients do not produce their own log files. If you want more detail, you have to set the debug options and then look in your system logs. Upsmon.conf MONITOR ups at pfsense 1 <username> <password> slave ... POWERDOWNFLAG /usr/local/ups/etc/killpower My

On Aug 30, 2018, at 6:54 AM, Ong, Kevin wrote: > > I'm very sorry for the delay here, I've been very swamped with work. Here's the relevant information you guys need: > > "upsc APC_BR1500GI" output: https://pastebin.com/rH3W0dbz > "upsrw APC_BR1500GI" output: https://pastebin.com/tEWv8a3d > "upscmd -l APC_BR1500GI" output:

I'm very sorry for the delay here, I've been very swamped with work. Here's the relevant information you guys need: "upsc APC_BR1500GI" output: https://pastebin.com/rH3W0dbz "upsrw APC_BR1500GI" output: https://pastebin.com/tEWv8a3d "upscmd -l APC_BR1500GI" output: https://pastebin.com/MraRQnEk "clog /var/log/system.log | grep -i ups" output:

Any comments here? Thank you. Regards, Kevin Mychal M. Ong Sr Infrastructure Engineer, Microsoft Technology Services - Messaging Global Infrastructure Operations Ingram Micro Inc. 4F Three World Square, 22 Upper McKinley Hill, Fort Bonifacio Taguig City, Philippines 1634 Direct +1-716-633-3600 ext. 33996 Mobile +63-917-511-0251 *: kevin.ong at ingrammicro.com<mailto:kevin.ong at

How do you setup the debug options in WinNUT? Correct, it sets the POWERDOWNFLAG when it receives an FSD but only if it acts as a NUT MASTER (since the UPS is connected locally to the NUT MASTER and can issue a killpower). This is the default value and I did not care to change it because it won't be use on my Windows machine anyway as it is working as a NUT SLAVE. Thank you. Regards, Kevin

Hi All, hoping someone might have some insights to what is going wrong with my NUT setup and my APC Back - UPS RS 1500 (specifically a BR1500GI) using the usbhid driver. https://download.schneider-electric.com/files?p_File_Name=AHUG-9JU4RH_R0_EN.pdf&p_Doc_Ref=SPD_AHUG-9JU4RH_EN&p_enDocType=User%20guide Main issue: NUT successfully shuts down my server when it goes on battery but when

Hi, I installed apcupsd through pfsense and noticed some discrepancy with the NUT package. I'm not sure if this is a bug regarding the BATTDATE (apcupsd) and battery.date (NUT) but BATTDATE shows the correct date of 2016/05/11. While NUT shows the battery.date as 2001/09/25 which doesn't make sense. Any ideas? Pfsense 2.4.3-RELEASE-p1 (amd64) NUT 2.7.4_6 NUT installed through

Denny, The first three commands had outputs but the "clog /var/log/system.log | grep -i ups” didn't output any. Did I do anything wrong? This is the output without the grep: can't allocate llinfo for <Public IP> on igb0 Aug 14 18:14:59 pfSense kernel: arpresolve: can't allocate llinfo for <Public IP> on igb0 Aug 14 18:15:00 pfSense kernel: arpresolve: can't

Oh, and I forgot to mention that "echo $SHELL" returns /bin/sh for me. Thank you. Regards, Kevin Mychal M. Ong Sr Infrastructure Engineer, Microsoft Technology Services - Messaging Global Infrastructure Operations Ingram Micro Inc. 4F Three World Square, 22 Upper McKinley Hill, Fort Bonifacio Taguig City, Philippines 1634 Direct +1-716-633-3600 ext. 33996 Mobile

I don't think the UPS mfr date is accurate also but I'm not a 100% sure. APC replaced my old BR1500GI unit with a brand new one (the one I have now) back in 2015 and this model was one of the newer models back then. So I'd say 2014 to 2015 is more reasonable for the UPS mfr date. Sorry, I'm more of a PowerShell guy so I don't know much with Linux commands. I tried removing the

Hi Charles, The battery.mfr.date is actually the correct value I'm looking for. That is the exact date the battery was last replaced. And yes, it is the correct value displayed in apcupsd. For the debug commands, is there a line break between "upsdrvctl stop" and "/usr/local/libexec/nut/usbhid-ups -a APC_BR1500GI -DDDDD 2>&1 | tee /tmp/APC_BR1500GI.debug.txt"?

Thanks for the quick response! On Sat, Jun 27, 2020, at 22:17, Manuel Wolfshant wrote: > On 6/28/20 4:25 AM, Scott Colby wrote: > > Hello, > > > > I am having difficulty using NUT to shut down my Netgate SG-1100 > > (a pfSense router) when the power level of the UPS gets critically > > low. > > > > Here is some relevant information: > > - OS:

Hello, I am having difficulty using NUT to shut down my Netgate SG-1100 (a pfSense router) when the power level of the UPS gets critically low. Here is some relevant information: - OS: pfSense 2.4.5-RELEASE-p1 (FreeBSD 11.3-STABLE) - NUT version: 2.7.4 - Installed from: pfSense package 2.7.4_7 - UPS: AVR750U (Device release number 2) - I have included my config files, output from `upsc`, and

I have implemented a small local network. I use pfSense as Firewall and Gateway, I have all my servers inside a DMZ, except the domain controllers that are on the LAN. LAN: 10.10.20.0/24 DMZ: 10.10.30.0/24 DC1: 10.10.20.2 DC2: 10.10.20.3 pfSense: LAN: 10.10.20.1 WAN: x.x.x.x DMZ: 10.10.30.1 In my local network, I have 2 domain controllers with SAMBA4, I would like to find