[Nut-upsuser] Wrong battery.date variable value

[Kevin Mychal Ong]

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

 : kevin.ong at ingrammicro.com


-----Original Message-----
From: Denny Page <denny at cococafe.com> 
Sent: Monday, August 13, 2018 11:55 PM
To: Charles Lepple <clepple at gmail.com>; Kevin Mychal M. Ong <kevindd992002 at yahoo.com>
Cc: nut-upsuser at alioth-lists.debian.net
Subject: Re: [Nut-upsuser] Wrong battery.date variable value



> 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 (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 pfsense package manager Pfsense installed on PC 
>> Engines APU2C4 board
>> 
>> I’m not sure how to get the logs for this issue. Can you please direct me on how to do this in pfsense?
> 
> I am not familiar with pfsense, but as I recall, it is FreeBSD using the ports tree, so I'll give this a shot. I would welcome any corrections from those more knowledgeable.

Yes, it is nut-2.7.4_6 from the FreeBSD ports tree.


> One handy aspect of the DDL is that it shows what the driver returns, bugs and all. Hopefully, it will allow us to fix the issue you are seeing without causing a regression for others.
> 
> Instructions to gather info for HCL/DDL here: 
> https://networkupstools.org/stable-hcl.html#footnotes
> 
> When it mentions 'upsc', 'upsrw' and 'upscmd', those all need to be 
> run from a shell on pfsense. (They do not require any special 
> permissions, and if upsd is listening on a network interface other 
> than localhost, they could be run from another system with NUT 
> installed.)
> 
> We might also need some lower-level logs, but the exact procedure will depend on the driver you are using (apcsmart or usbhid-ups).

Kevin, to collect the command outputs, you will need to either be logged into pfSense (ssh) or use the command prompt in the GUI (Diagnostics / Command Prompt). The command he is asking you to run is “upsc UPSNAME” where UPSNAME is the name you gave the UPS in the GUI. The others would be “upsrw UPSNAME” and “upscmd -l UPSNAME”.

To get the relevant system logs, you would execute "clog /var/log/system.log | grep -i ups”.

Denny