Nut upsuser - Mar 2015 - Tripplite SNMPwebcard communication lost and established randomly

On Mar 31, 2015, at 9:07 AM, Jason Gould <jgould at cddiagnostics.com>
wrote:
> I missed that snmp-ups set pollfreq to 30 by default. I?d hope that it
would set deadtime to an appropriate value as well than, no? Is there a way to
query what the settings are or what the defaults are?
There is a TODO comment in snmp-ups that mentions doing something similar to
usbhid-ups: just poll the important status OIDs every two seconds
(pollinterval), and fill in the rest every 30 (pollfreq).

The configuration files have the default values listed in the comments:
https://github.com/networkupstools/nut/tree/master/conf
> I?m going to set POLLFREQ=30 and DEADTIME = 90 and see if that has any
effect. I?ll check for the logs. And if that doesn?t get my anywhere I?ll look
at trying to simulate with snmpwalk like you mentioned.
 
DEADTIME is a setting in upsmon.conf, versus the driver.

-- 
Charles Lepple
clepple at gmail



-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150331/0b62aa0f/attachment.html>

Thanks.

As mentioned, deadtime can't be set for snmp-ups. You see this in the logs.

Mar 31 09:08:30 freenas notifier: Fatal error: 'DEADTIME' is not a valid
variable name for this driver.
Mar 31 09:08:30 freenas notifier: Look in the man page or call this driver with
-h for a list of valid variable names and flags.


While looking at /var/log/messages I also see this when starting NUT;

Mar 31 09:11:15 freenas notifier: No matching MIB found for sysOID
'.1.3.6.1.4.1.850.1'!
Mar 31 09:11:15 freenas notifier: Please report it to NUT developers, with an
'upsc' output for your device.
Mar 31 09:11:15 freenas notifier: Going back to the classic MIB detection
method.
Mar 31 09:11:15 freenas kernel: <118>Mar 31 09:11:15 freenas upsd[94201]:
mainloop: Interrupted system call
Mar 31 09:11:15 freenas kernel: <118>Mar 31 09:11:15 freenas
upsmon[94217]: upsmon parent: read
Mar 31 09:11:15 freenas notifier: Detected SU6000RT4UHVPM on host 192.168.0.24
(mib: ietf 1.4)
Mar 31 09:11:17 freenas notifier: [tripplite] unhandled ASN 0x81 received from
1.3.6.1.2.1.33.1.2.6.0
Mar 31 09:11:17 freenas notifier: [tripplite] unhandled ASN 0x81 received from
1.3.6.1.2.1.33.1.3.3.1.4.1
Mar 31 09:11:17 freenas notifier: [tripplite] unhandled ASN 0x81 received from
1.3.6.1.2.1.33.1.3.3.1.5.1
Mar 31 09:11:19 freenas notifier: [tripplite] unhandled ASN 0x81 received from
1.3.6.1.2.1.33.1.5.3.1.3.1
Mar 31 09:11:19 freenas notifier: [tripplite] unhandled ASN 0x81 received from
1.3.6.1.2.1.33.1.5.3.1.4.1
Mar 31 09:11:19 freenas notifier: [tripplite] unhandled ASN 0x80 received from
1.3.6.1.2.1.33.1.6.3.8
Mar 31 09:11:19 freenas notifier: [tripplite] unhandled ASN 0x80 received from
1.3.6.1.2.1.33.1.7.1.0
Mar 31 09:11:19 freenas notifier: [tripplite] unhandled ASN 0x81 received from
1.3.6.1.2.1.33.1.9.2.0
Mar 31 09:11:19 freenas notifier: [tripplite] unhandled ASN 0x81 received from
1.3.6.1.2.1.33.1.9.3.0
Mar 31 09:11:19 freenas notifier: [tripplite] unhandled ASN 0x81 received from
1.3.6.1.2.1.33.1.9.4.0
Mar 31 09:11:19 freenas notifier: [tripplite] unhandled ASN 0x80 received from
1.3.6.1.2.1.33.1.9.5.0
Mar 31 09:11:19 freenas notifier: [tripplite] unhandled ASN 0x80 received from
1.3.6.1.2.1.33.1.9.6.0
Mar 31 09:11:19 freenas notifier: [tripplite] unhandled ASN 0x80 received from
1.3.6.1.2.1.33.1.9.7.0
Mar 31 09:11:23 freenas notifier: Network UPS Tools - UPS driver controller
2.7.2
Mar 31 09:11:23 freenas notifier: Starting nut.
Mar 31 09:11:23 freenas notifier: fopen /var/db/nut/upsd.pid: No such file or
directory
Mar 31 09:11:23 freenas notifier: listening on 127.0.0.1 port 3493
Mar 31 09:11:23 freenas notifier: Connected to UPS [tripplite]:
snmp-ups-tripplite
Mar 31 09:11:23 freenas notifier: /usr/local/etc/nut/cmdvartab not found -
disabling descriptions

I assume I should post this info to the developers mailing list as stated in the
log?

From: Charles Lepple [mailto:clepple at gmail.com]
Sent: Tuesday, March 31, 2015 9:24 AM
To: Jason Gould
Cc: NUT Users
Subject: Re: [Nut-upsuser] Tripplite SNMPwebcard communication lost and
established randomly

On Mar 31, 2015, at 9:07 AM, Jason Gould <jgould at
cddiagnostics.com<mailto:jgould at cddiagnostics.com>> wrote:


I missed that snmp-ups set pollfreq to 30 by default. I'd hope that it would
set deadtime to an appropriate value as well than, no? Is there a way to query
what the settings are or what the defaults are?

There is a TODO comment in snmp-ups that mentions doing something similar to
usbhid-ups: just poll the important status OIDs every two seconds
(pollinterval), and fill in the rest every 30 (pollfreq).

The configuration files have the default values listed in the comments:
https://github.com/networkupstools/nut/tree/master/conf

I'm going to set POLLFREQ=30 and DEADTIME = 90 and see if that has any
effect. I'll check for the logs. And if that doesn't get my anywhere
I'll look at trying to simulate with snmpwalk like you mentioned.

DEADTIME is a setting in upsmon.conf, versus the driver.

--
Charles Lepple
clepple at gmail



-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150331/5e6ed1bf/attachment-0001.html>

On Mar 31, 2015, at 9:34 AM, Jason Gould <jgould at cddiagnostics.com>
wrote:
> As mentioned, deadtime can?t be set for snmp-ups. You see this in the logs.
>  
> Mar 31 09:08:30 freenas notifier: Fatal error: 'DEADTIME' is not a
valid variable name for this driver.
> Mar 31 09:08:30 freenas notifier: Look in the man page or call this driver
with -h for a list of valid variable names and flags.
Right, I mentioned it is a setting in upsmon.conf, which is separate from
ups.conf that the driver reads.

-- 
Charles Lepple
clepple at gmail



-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150331/d3c09692/attachment.html>