search for: maxstartdelay

...ore:~ # diff -u /root/upsdrvctl.c nut-2.7.4/drivers/upsdrvctl.c --- /root/upsdrvctl.c 2019-07-16 15:23:36.496587000 +0200 +++ nut-2.7.4/drivers/upsdrvctl.c 2015-12-29 13:08:34.000000000 +0100 @@ -33,7 +33,6 @@ char *upsname; char *driver; char *port; - char *serial; int sdorder; int maxstartdelay; void *next; @@ -95,9 +94,6 @@ if (!strcmp(var, "port")) tmp->port = xstrdup(val); - if (!strcmp(var, "serial")) - tmp->serial = xstrdup(val); - if (!strcmp(var, "maxstartdelay")) tmp->maxstartdelay = atoi(val); @@ -119,7 +115,6...

...e driver works perfectly - almost. I have some problems with it. I hope you can help me or enlight me to cure, at least. * First: the megatec_usb driver takes sooo long to detect the UPS - almost 70 seconds to say "yes, this UPS talks megatec_usb protocol", so I needed to raise the maxstartdelay to 80. It's possible to reduce this time? * Second: variables detected. Look at the listing: battery.charge: 87.5 ^^^^ Nut states battery is at 87,5% but Winpower says 100%. In fact, with nut, the battery doesn't charge above 95%. Using megatec_ups -DDDDDD gave me t...

Hello, I had to increase slightly the maxstartdelay value to 60 instead of 45 as a work around, otherwise upsdrv and upsdrvctl are unable to start megatec_usb daemon at all. The strange thing is /lib64/nut/megatec_usb -DDDDDD -u nut -a mgeups runs without any problem and will recognize the value coming from the ups faster. Anyway, I don't...

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...

...]: Poll UPS [eaton_2 at localhost] failed - Driver not connected Apr 4 00:44:10 mail blazer_usb[10804]: Got disconnected by another driver: Device or resource busy Apr 4 00:44:10 mail kernel: [83496.177686] usb 4-2: usbfs: process 10804 (blazer_usb) did not claim interface 0 before use ups.conf: maxstartdelay = 70 norating novendor subdriver = cypress [eaton_1] driver = blazer_usb port = "002" desc = "Eaton NV 2000H" vendorid = 0665 productid = 5161 bus = "003" [eaton_2] driver = blazer_usb port = &qu...

...e 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 valid and well-calib...

...ess critical # parameters are polled. See respective driver man pages. # # Set maxretry to 3 by default, this should mitigate race with slow devices: maxretry = 3 # These directives can be set outside and inside a driver definition, with # slightly different meanings per context: # # maxstartdelay: OPTIONAL. This can be set as a global variable # above your first UPS definition and it can also be # set in a UPS section. This value controls how long # upsdrvctl will wait for the driver to finish starting. # This keeps your system f...