similar to: Wait for network delay

On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: > NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS Hmm, at first glance, I read the "complain endlessly" part as a figure of speech, and figured SNMP would get there eventually since it's UDP. But if you have to stop and restart NUT, that is a different story. What

On 2/5/2014 8:24 AM, Charles Lepple wrote: > On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: > >> NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS > Hmm, at first glance, I read the "complain endlessly" part as a figure of speech, and figured SNMP would get there eventually since it's UDP. But if you have

I am using NUT 2.6.5 as part of FreeNAS 9.2.0. I am using an APC Smart-UPS 5000 RM DL4 with a AP9619 network management card. NUT properly detects when the UPS goes on battery and initiates a shutdown after the configured time. The problem I have is that I am using a 208V unit on a 240V circuit. That means the normal state for the UPS is "TRIM". NUT doesn't treat that as an on line

On Jan 10, 2014, at 12:58 PM, Elliot Dierksen wrote: > I am using NUT 2.6.5 as part of FreeNAS 9.2.0. I am using an APC Smart-UPS > 5000 RM DL4 with a AP9619 network management card. NUT properly detects > when the UPS goes on battery and initiates a shutdown after the configured > time. The problem I have is that I am using a 208V unit on a 240V circuit. > That means the normal

Greetings all, Anyone have a clue on this behavior (see below) on this behavior with FreeNAS-8.3.0-RELEASE-x64 (r12701M) on a TrippLite 1500LCD UPS? NUT version is 2.6.5 Using the following profile: Tripp-Lite ups 2 Smart1500LCD USB (usbhid-ups) I get the following: Dec 10 21:40:12 nas6 kernel: uhid0: <Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.02, addr 2> on usbus1 Dec 10 21:40:12

On Apr 3, 2014, at 7:24 AM, Daniele Borghesi wrote: > nothing appens. The output is exactly the same as below (attached screen with freenas config) > What happens without the leading "-x"? (just "productid=0004") The "-x" is what you would add if you were running the driver from the command line. -- Charles Lepple clepple at gmail

nothing appens. The output is exactly the same as below (attached screen with freenas config) [image: Immagine in linea 2] 2014-04-03 13:16 GMT+02:00 Charles Lepple <clepple at gmail.com>: > please reply to the list. thanks! > > See below. > > On Apr 3, 2014, at 3:10 AM, Daniele Borghesi wrote: > > thanks for your reply.* I'm running the latest version of

Nice! it seems to works. Later this evening when I'll be back to my home I'll try to unplug the power chord from my ups. Apr 3 14:08:11 archivio notifier: nut not running? (check > /var/db/nut/upsd.pid). > Apr 3 14:08:11 archivio notifier: nut_upsmon not running? (check > /var/db/nut/upsmon.pid). > Apr 3 14:08:11 archivio notifier: nut_upslog not running? (check >

Hello, I need help configuring my USB connected UPS "Emerson Power Liebert PowerSure PSI 1440" to my freebsd machine, using NUT. here's the manufacturer's product page http://www.emersonnetworkpower.com/en-US/Products/ACPower/Pages/LiebertPowerSurePSILineInteractiveUPS10003000VA.aspx I'm not a BSD expert, so please ask me for any information you need. regards Daniele

please reply to the list. thanks! See below. On Apr 3, 2014, at 3:10 AM, Daniele Borghesi wrote: > thanks for your reply. I'm running the latest version of FreeNAS based on 9.2 with NUT 2.7.1 > > [root at archivio ~]# uname -a > FreeBSD archivio.dannyb78.home 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #0 r262572+ > 38751c8: Thu

> On Jan 10, 2014, at 12:58 PM, Elliot Dierksen wrote: >> I am using NUT 2.6.5 as part of FreeNAS 9.2.0. I am using an APC >> Smart-UPS >> 5000 RM DL4 with a AP9619 network management card. NUT properly detects >> when the UPS goes on battery and initiates a shutdown after the >> configured >> time. The problem I have is that I am using a 208V unit on a 240V

[please use Reply-All to keep the list CC'd, thanks] On Mar 30, 2015, at 11:04 PM, Jason Gould <jgould at cddiagnostics.com> wrote: > Thanks. I should also mention the freenas server is setup with an lacp lagg. > > I will also mention that even when not setting pollfreq (leave as default) the issue still occurs. > It looks like the default for pollfreq is actually 30 on

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 for the logs. And if that doesn't get my anywhere I'll look at trying to simulate

Hello, I have the following hardware configuration. Tyan 2466N motherboard, 1.03 BIOS, 2 Athlon-MP 1800+ CPUs, 512MB registered ECC DRAM, Onboard 3Com NIC (xl type) Radeon 8500 AGP video card Adaptec 3210S SCSI RAID controller Comtrol RocketPort 8 port PCI serial card I have started to experience some odd system lockups in the past couple months, and it seems to be getting worse. I particular,

On 2014-02-16 16:36, Elliot Dierksen wrote: > On 2/5/2014 8:24 AM, Charles Lepple wrote: >> On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: >> >>> NUT will complain endlessly about communication errors and never >>> establish SNMP communication with my APC UPS >> Hmm, at first glance, I read the "complain endlessly" part as a figure >> of

Greetings- I'd like to configure multiple copper NICs on a server running CentOS 6.2 in a LAGG configuration for better throughput to the core switch. After quite a bit of searching, I'm not seeing anything of the sort. Is LAGG specific to the BSD world and the HP switches I'm running? Or, does it go by a different name? Bonding perhaps? If so, is bonding compatible with LAGG? --Tim

On Jun 2, 2014, at 7:27 AM, elliot smith wrote: > For example I am using FreeNAS. Rather than supporting my unorthodox UPS > signaling scheme by installing it as a script in FreeNAS, (and me probably > messing something up in the process) this scheme could be supported > instead by NUT. Bear in mind that all of the NUT drivers have authors who are expected to be maintainers of that

Hi Ted, Thanks for the reply. I didn't realize that tapping into the serial port could be that simple. I might do that - for my application all I would need would be the first relay. I can simply set the timer in the FreeNAS GUI to wait a few minutes to see if the UPS comes back up before it does a system shut down, so I can be okay without the low battery signal. I respectfully disagree

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

On Nov 18, 2015, at 12:16 PM, Chris Adams <linux at cmadams.net> wrote: > > Once upon a time, Warren Young <wyml at etr-usa.com> said: >> - They?re serious server-grade machines, not borderline flimsy boxes competing largely on price. Built in and supported from Silicon Valley, not China. :) > > iXsystems sells rebadged SuperMicro stuff, nothing special (not made