Re: [Nut-upsuser] Tripplite SNMPwebcard communication lost and established randomly

2015-03-31 Thread Jason Gould
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? I'm going to set POLLFREQ=30 and DEADTIME = 90 and see if that has any effect. I'll check

Re: [Nut-upsuser] Tripplite SNMPwebcard communication lost and established randomly

2015-03-31 Thread Jason Gould
So it turns out can't set DEADTIME with snmp-ups. It isn't listed as a supported optional setting on the man page. If you try to set it the connection doesn't work. I'm not sure what this means in regards to setting pollfreq to a higher value like say 60. From: Nut-upsuser

Re: [Nut-upsuser] Tripplite SNMPwebcard communication lost and established randomly

2015-03-31 Thread Charles Lepple
On Mar 31, 2015, at 9:07 AM, Jason Gould jgo...@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

Re: [Nut-upsuser] Tripplite SNMPwebcard communication lost and established randomly

2015-03-31 Thread Jason Gould
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

Re: [Nut-upsuser] Tripplite SNMPwebcard communication lost and established randomly

2015-03-31 Thread Charles Lepple
On Mar 31, 2015, at 9:34 AM, Jason Gould jgo...@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: