search for: retrydelay

...-------- diff -u --recursive openssh-2.3.0p1/ChangeLog openssh-2.3.0p1-new/ChangeLog --- openssh-2.3.0p1/ChangeLog Sun Nov 5 22:17:38 2000 +++ openssh-2.3.0p1-new/ChangeLog Mon Nov 13 11:05:27 2000 @@ -1,3 +1,7 @@ +20001113 + - (spf) Made sleep(1) in sshconnect.c configureable wrt time + ("RetryDelay" option added) + 20001106 - (djm) Use Jim's new 1.0.3 askpass in Redhat RPMs - (djm) Manually fix up missed diff hunks (mainly RCS idents) diff -u --recursive openssh-2.3.0p1/readconf.c openssh-2.3.0p1-new/readconf.c --- openssh-2.3.0p1/readconf.c Sat Oct 14 01:23:12 2000 +++ openssh-...

maybe i have solved this issue, i unplugged APC BackUPS from USB 2.0 and PLUGGED INTO USB 3.0 and now it works prefectly at first time without any side effects, strange, this shoud be working since USB 1.0 so ups driver is configured OK, this config works ok for backups, this looks like there is no problem with detection of UPS but with USB driver or something around so simply if somebody has

...oking for a simulation file named 'eaton1'. The presence of an "@" character enables repeater mode. If you change this to 'port = eaton1 at localhost', things should work as you described. I should also mention a pair of options that were introduced in 2.7.2: maxretry and retrydelay. http://www.networkupstools.org/docs/man/ups.conf.html#_global_directives I haven't used dummy-ups in production (I just use the other mode to simulate an UPS) but I suspect there might be a race condition if upsdrvctl starts dummy-ups before both usbhid-ups instances connect to upsd. Not...

I am running NUT as part of FreeNAS 9.2.0. I have looked through the manuals, but I don't see how to address my issue. The box has 4 NIC's in a LACP LAGG group. It takes a while for LACP to finish, and NUT tries to start before packets are flowing. NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS. If I stop NUT and restart

...ar term) is to see if this is just a startup issue. You can specify one UPS with "upsdrvctl start ups1", and then see if the other drivers still start if you wait until the first driver has completed its SNMPv3 handshake. You can automate this a bit with the "maxretry" and "retrydelay" options in ups.conf: http://networkupstools.org/docs/man/ups.conf.html > -------------- next part -------------- Script started on Mon 04 Dec 2017 09:32:50 AM PST : || nomad at nomaddev ups [1001] ; time -p sudo /usr/sbin/upsdrvctl -D start && exit Network UPS Tools - UPS driver...

On Jan 1, 2015, at 4:57 PM, Jonathan Gammell <jon.gammell at utoronto.ca> wrote: > [ups] > driver = dummy-ups > port = eaton1 > desc = "Dummy UPS" There is a typo in the specification of "port =" in the dummy-ups man page, but your configuration file is effectively looking for a simulation file named 'eaton1'. The presence of

"lsusb" always shows the UPS. It's always there with an ls -al. I can start the thing, and it doesn't load.... wait a minute and try again and it doesn't load.... wait another minute and it loads.... then try to restart a minute later and it doesn't load. > You might also benefit from adjusting these variables:

...ar term) is to see if this is just a startup issue. You can specify one UPS with "upsdrvctl start ups1", and then see if the other drivers still start if you wait until the first driver has completed its SNMPv3 handshake. You can automate this a bit with the "maxretry" and "retrydelay" options in ups.conf: http://networkupstools.org/docs/man/ups.conf.html

...d=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=051d ProdID=0002 Rev=01.06 S: Manufacturer=American Power Conversion S: Product=Back-UPS RS 1500 FW:8.g9 .I USB FW:g9 Also, if you are having intermittent trouble with drivers, you can use the maxrestart and retrydelay options: http://networkupstools.org/docs/man/ups.conf.html We have had some reports of issues with VMware and USB. This can affect systems with APC UPSes, because the driver needs to be able to pull the model number to apply model-specific fixes. Versions after NUT 2.7.2 have a partial fix for thi...

...trying to systemd I see a bunch of zombie processes that used to be snmp-ups for one of ups2-1 or ups3-1 (depending on the run). I'm trying again with /etc/systemd/system/nut-driver.service.d/nut-driver.conf set to: [Service] TimeoutSec=600 and /etc/ups/ups.conf having maxretry = 10 retrydelay = 15 This time ps shows three apparently happy snmp-ups processes but upsdrvctl start is still showing up. ... and then everything vanishes but systemd doesn't complain. journalctl -xe shows a good startup then claims nut-driver.service isn't needed anymore and shuts it down: Dec 04 10:17...

...a simulation file named 'eaton1'. The presence of an "@" character enables repeater mode. If you change this to 'port = eaton1 at localhost', things should work as you described. > > I should also mention a pair of options that were introduced in 2.7.2: maxretry and retrydelay. > > http://www.networkupstools.org/docs/man/ups.conf.html#_global_directives > > I haven't used dummy-ups in production (I just use the other mode to simulate an UPS) but I suspect there might be a race condition if upsdrvctl starts dummy-ups before both usbhid-ups instances co...

Hi, I tried your suggestions on another Proxmox environment with the following ups.conf: # Wait 10 seconds for the driver to finish starting. maxstartdelay = 10 # Try 3 times to start the driver, before giving up. maxretry = 3 # Wait 5 seconds between attempts to start the driver. retrydelay = 5 # Poll the ups every 5 seconds pollinterval = 5 [pve1] # Cyber Power Systems, Inc driver = usbhid-ups port = auto desc = "Cyber Power CP1500 AVR UPS" vendorid = 0764 productid = 0501 # if the charge is less than 75 percent trigger a LB status override.battery.charge...

...mean it starts after reboot and after issuing 'sudo systemctl restart nut-driver' but, as expected, it takes quite a while to finish startup. /etc/systemd/system/nut-driver.service.d/nut-driver.conf [Unit] StopWhenUnneeded=no [Service] TimeoutSec=600 /etc/ups/ups.conf ... maxretry = 10 retrydelay = 15 ... As I said, I suspect the bulk of these are cargo cult "it worked, not messing with it" settings. nomad

...ion directives # ------------------------ # # These directives are used by upsdrvctl only and should be specified outside # of a driver definition: # # maxretry: OPTIONAL. Specify the number of attempts to start the driver(s), # in case of failure, before giving up. A delay of 'retrydelay' is # inserted between each attempt. Caution should be taken when using # this option, since it can impact the time taken by your system to # start. # # The built-in default is 1 attempt. # # retrydelay: OPTIONAL. Specify the delay between e...

Hi, I have a NUT client that requires the UPS it monitors to be named "ups". The client (a Synology NAS) does not provide a method to change this configuration. My setup consists of multiple UPSes monitored by a single master and I'd rather not have 1/4 UPSes named `ups` while the other 3/4 are named something descriptive and helpful for administration. I think I should be able

...system, with a dependency on the network interfaces being fully started. (I haven't looked at the FreeNAS init system much.) If the comms errors are from the SNMP driver, then we should be able to tweak the retry settings in the driver itself, or get the driver to fail and rely on the maxretry/retrydelay that I mentioned earlier. Then, the question becomes "where is the driver getting stuck?" -- Charles Lepple clepple at gmail

New NUT install dealing with three APC Smart-UPS 5000s, two of which have AP9617 and the third has a AP9619 card. The SNMPv3 configurations on all three are exactly the same. This is confirmed by snmpget calls that work just fine: snmpget -Cf -v3 -u [...] -l authPriv -A '[...]' -X '[...]' -a MD5 -x DES [upsname] .1.3.6.1.4.1.318.1.1.1.1.1.1.0 snmp-ups can query all three

...s store (before the chain closed-down) as a second UPS for my home/office - the first being an old Zigor Ebro650 - a long story for another post... NUT v2.7.4_7 is running as a package on pfSense 2.2.4 (based on FreeBSD 11.2-RELEASE-p10) with the following ups.conf: pollinterval=10 maxretry=10 retrydelay=20 maxstartdelay=120 [ups] driver=blazer_usb port=auto protocol=mustek bus=/dev/usb desc=Sweex PP200 novendor This model has USB productid/vendorid of 5161/0665. The following output from upsc shows the available status from the Sweex, including Load and Charge stats, which do appear to be vali...

...) { - - argv[arg++] = (char *)"-x"; - sprintf(argv[arg++],"serial=%s",ups->serial); - } - } - /* stick on the chroot / user args if given to us */ if (pt_root) { argv[arg++] = (char *)"-r"; /* FIXME: cast away const */ @@ -330,8 +312,6 @@ sleep (retrydelay); } } - - if (tval) free(tval); } static void help(const char *progname)