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 anything else.

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

 : [email protected]


-----Original Message-----
From: Denny Page <[email protected]>
Sent: Wednesday, August 15, 2018 11:54 PM
To: Kevin Mychal Ong <[email protected]>
Cc: Charles Lepple <[email protected]>; [email protected]
Subject: Re: [Nut-upsuser] Wrong battery.date variable value

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 10MB.

If you want complete information on UPS discovery, the best time to capture 
complete information about the UPS would be after a reboot. If you are not able 
to reboot, then restarting the UPS service (Status / Services) will get suffice 
to get all the messages originating from NUT itself. It will not include the 
kernel discovery messages, but I don’t see a need for that here.

Denny


> On Aug 15, 2018, at 00:00, Kevin Mychal Ong <[email protected]> wrote:
>
> 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 allocate llinfo for
> <Public IP> on igb0 Aug 14 18:15:26 pfSense kernel: arpresolve: can't
> allocate llinfo for <Public IP> on igb0 Aug 14 18:15:27 pfSense
> kernel: arpresolve: can't allocate llinfo for <Public IP> on igb0 Aug
> 14 18:15:53 pfSense kernel: arpresolve: can't allocate llinfo for
> <Public IP> on igb0 Aug 14 18:15:54 pfSense kernel: arpresolve: can't
> allocate llinfo for <Public IP> on igb0 Aug 14 18:16:20 pfSense
> kernel: arpresolve: can't allocate llinfo for <Public IP> on igb0 Aug
> 14 18:16:21 pfSense kernel: arpresolve: can't allocate llinfo for
> <Public IP> on igb0 Aug 14 18:16:47 pfSense kernel: arpresolve: can't
> allocate llinfo for <Public IP> on igb0 Aug 14 18:16:48 pfSense
> kernel: arpresolve: can't allocate llinfo for <Public IP> on igb0 Aug
> 14 18:17:14 pfSense kernel: arpresolve: can't allocate llinfo for
> <Public IP> on igb0 Aug 14 18:17:15 pfSense kernel: arpresolve: can't
> allocate llinfo for <Public IP> on igb0 Aug 14 18:17:41 pfSense
> kernel: arpresolve: can't allocate llinfo for <Public IP> on igb0
>
> Thank you.
>
> Regards,
>
> Kevin Mychal M. Ong
> 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
>
>  : [email protected]


This email may contain material that is confidential, and proprietary to Ingram 
Micro, for the sole use of the intended recipient. Any review, reliance or 
distribution by others or forwarding without express permission is strictly 
prohibited. If you are not the intended recipient, please contact the sender 
and delete all copies.
[Ingram_2818e5de]
_______________________________________________
Nut-upsuser mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Reply via email to