similar to: WinNUT Client Logs

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

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

Hi Charles, Ok. I'm testing NUT now with only pfsense running as the master and no slaves. I'm noticing a very strange behavior that totally doesn't make sense to me. So here's what I did (in chronological order): 1. Set override.battery.charge.warning to 55 and override.battery.charge.low to 50. 2. I started with a full charge battery and unplugged the UPS from the mains.

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 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

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 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:

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

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

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'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:

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"?

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

Hi All! This time I'm using Nut 2.2.0, Debian etch and kernel v. 2.6.23.9. My hardware config is quite simple. There are 2 PCs connected to my PowerMust 600VA. One is mensioned above the other is a Windows PC using Winnut 2.0.0b. The Linux PC is connected to the UPS via a serial cable and acts as the server. The problem is that both upsmon and winnut disconnect regularly but in random

Hello All links I can find for winnut are not responding.. Anyone got a working link or maybe can send the package to me privately? /Martin -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20060410/717c77a2/attachment.html

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, 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

Hi, I have an Eaton 5SC UPS with only 1 USB communication port, but... I need 3 devices to safely switch off in case of power failure, 2 Synology NAS and 1 PC under Windows 7 (soon 10)! So I've decided to connect the UPS to the main NAS (via the USB cable), enabled the "Network UPS server" on the NAS, entered the other NAS and PC IP addresses to let them receive NUT messages in case

Hi, Another beginner question. I spend hours trying to find the solution for how to configure winnut properly but I' struggling to make it work. I want my QNAP NAS TS-231 to work as a master and send signal to the PC to shut it down during power outage. I configured QNAP properly (like this: http://geekbeat.tv/qnap-adding-external-devices-qnap), but I don't know what to do next. I work