Displaying 4 results from an estimated 4 matches for "l203".
Did you mean:
203
2015 Aug 13
2
occassional problem wtih upslog and apc ups units via snmp ... [NA] status
Os is redhat enterprise, kernel 2.6.18-164.2.1.e15
NUT is apparently 2.4.1
It was installed by tar.
Monitoring a lot of apc UPS units-mostly Smart-UPS of various flavors, also a Silcon DP380E.
Normally works just fine... "upslog" writes status log every 30 seconds with various parameters..
Every so often, one of the UPS units has a log entry of:
2015 Aug 14
0
occassional problem wtih upslog and apc ups units via snmp ... [NA] status
...00+60.00+1020.00
>
> What does it mean when it puts NA in the log file?
Every log interval, each variable is fetched from the server, and if there is an error retrieving that value at that time, "NA" is logged:
https://github.com/networkupstools/nut/blob/master/clients/upslog.c#L203
Since they are all "NA" at the same time, it is likely that there is a communication problem, either between upslog and upsd, or between upsd and the driver. In either case, there is probably a syslog message describing the problem in more detail.
--
Charles Lepple
clepple at gmail
2015 Aug 14
2
occassional problem wtih upslog and apc ups units via snmp ... [NA] status
...00+60.00+1020.00
>
> What does it mean when it puts NA in the log file?
Every log interval, each variable is fetched from the server, and if there is an error retrieving that value at that time, "NA" is logged:
https://github.com/networkupstools/nut/blob/master/clients/upslog.c#L203
Since they are all "NA" at the same time, it is likely that there is a communication problem, either between upslog and upsd, or between upsd and the driver. In either case, there is probably a syslog message describing the problem in more detail.
--
Charles Lepple
clepple at gmail
2010 Mar 02
3
2.6.33 high cpu usage
With the ATI bug I was hitting earlier fixed, only my btrfs partition
continues to show high cpu usage for some operations.
Rsync, git pull, git checkout and svn up are typicall operations which
trigger the high cpu usage.
As an example, this perf report is from using git checkout to change to
a new branch; the change needed to checkout 208 files out of about 1600
total files. du(1) reports