> 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
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
I have no idea. I would search the internet for "pfSense kernel: arpresolve: can't allocate llinfo for <Public IP> on igb0". On August 15, 2018 3:34:22 AM Kevin Mychal Ong <kevindd992002 at yahoo.com> 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 > > : 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 > > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
The kernel log is a circular log with a limited size. In your situation, it appears that that igb0 message from arpresolve (which has probably nothing to do with the real problem you are trying to solve) occurred so many times, that it has completely filled the message log, thereby overwriting any older messages (for example those from nut). In order to get sensible information from the logs, you either should solve that igb0 message, watch the logs before they are full (for example immediately after a reboot), or append the log messages to some file, so that they don't get lost. Regards, Matthijs -----Original Message----- From: Kevin Mychal Ong [mailto:kevindd992002 at yahoo.com] Sent: woensdag 15 augustus 2018 9:01 To: Denny Page <denny at cococafe.com>; Charles Lepple <clepple at gmail.com> Cc: nut-upsuser at alioth-lists.debian.net Subject: Re: [Nut-upsuser] Wrong battery.date variable value 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 DISCLAIMER: For our full disclaimer, please visit www.awl.nl/en/about-us/disclaimer
On Aug 13, 2018, at 11:54 AM, Denny Page <denny at cococafe.com> wrote:> > 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”.Kevin, Before we go into the system logs, I want to make sure we're looking at the right driver. As Denny mentioned, what is the output of "upsc UPSNAME" (where UPSNAME is the name from the GUI, or from "upsc -l")? The other logs I mentioned are debug logs that are somewhat specific to the driver, and are not collected by default. I'd like to mention this again:> One last thing: we have had some issues in the past with messages from yahoo.com ending up in spam/junk folders due to Yahoo's SPF/DKIM rules (or worse yet, unsubscribing other users from the mailing list). I would recommend using a different email address, or create an issue here: https://github.com/networkupstools/nut/issuesIf you can post from another email address (e.g. the ingrammicro.com one), please do.
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 <kevindd992002 at yahoo.com> 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 > > : kevin.ong at ingrammicro.com