search for: apc_br1500gi

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: https://pastebin.com/MraRQnEk > "clog /var/log/system.log | grep -i ups" output: https://pastebin.com/QxXLqEcH Hi Kevin...

...y.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"? Well, I tried both ways and I come up with an "Ambiguous output redirect." error message. Thank you. Regards, Kevin Mychal M. Ong Sr Infrastructure Engineer, Microsoft Technology Services - Messaging Global Infrastructure Oper...

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

...lue 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 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"? Well, I tried both ways and I come up with an "Ambiguous output redirect." error message. > yes, line break, and each of the commands you put in quotes should all be on one line. What does "echo $SHELL" say? (I'...

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: https://pastebin.com/QxXLqEcH Let me know if you need...

...alue 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 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"? Well, I tried both ways and I come up with an "Ambiguous output redirect." error message. > yes, line break, and each of the commands you put in quotes should all be on one line. What does "echo $SHELL" say? (I'...

...alue 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 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"? Well, I tried both ways and I come up with an "Ambiguous output redirect." error message. > yes, line break, and each of the commands you put in quotes should all be on one line. What does "echo $SHELL" say? (I'...