similar to: NUT USB Delayed Communication

Hello, Yes, "pollonly" is a driver option for certain devices (and relevant to just some drivers). Disconnects are probably relevant, at least to loss of connection (and staying that way, with less agressive retries in NUT v2.7.4 and before). There is a logged issue that "pollonly" mode might have trouble detecting a disconnection/staleness, I'm not sure there's merit

Good evening folks, So I configured NUT on a Raspberry Pi 4 both UPS are connected over USB however the switch from AC Power to Battery seems to be delayed on the NUT communication would anyone have any ideas? The Pi Reports that the UPS is on battery around 30 seconds later I think this delay is long. I have tested it on a physical computer and the detection is around 5 to 6 seconds with

Good afternoon, So been trying to figure out a problem i am encountering with NUT and two APC 1000 UPS's that's connected via USB, First off it somewhat works well kind of, Pull the power to either UPS and it's slow at responding but finally detects it however the other problem is that after a few days NUT just stops reporting that the Power has been off. Here is what I've

tisdagen den 16 december 2014 15.36.29 skrev Frantz de Germain: > Hello, Hi Frantz, > > I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. > I've got the message : > > "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of > this message)" > > I've been looking for "pollonly" in

Hello I currently run a few samba servers one being used as a PDC. Today I added a user to the domain and for some reason I can not get it to connect to any of the shares but "home" on the file server. % smbclient -U gregi //server3/public Password: Domain=[HYDRIX-MALVERN] OS=[Unix] Server=[Samba 3.0.28] tree connect failed: NT_STATUS_ACCESS_DENIED However I can connect with : $

Hi all, Have been using Nut on Linux for over ten years now and find it brilliant. Thanks. Just upgraded to 2.4.2 and have the 5 or 6 models of UPS's that we use (apcsmart, megatec, mge-shut, surgemax, digitus) all working including the MGE Pulsar Evolution 1100 on a USB connection using the usbhid-ups driver. Running on SLES9. Old but we still have a few servers out there running

Hello, I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. I've got the message : "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of this message)" I've been looking for "pollonly" in the usbhid-ups man page, but it didn't help me. Could someone explain me what does this means exactly ? What are

Sergey, I?m no expert on this but I have been reading the driver code, trying to sort out bigger problems with the OpenUPS driver! I can make 2 observations that I can?t check out myself : ?beeper.disable? was previously ?beeper off? - and ?beeper.enable? was ?beeper.on?. Not sure if it?s worth trying the old versions? If your UPS doesn?t wait for LB, could this be because there is another

On Wed, 18 Oct 2017, Drew Plaster wrote: > MASTER SYSTEM > > nut.conf > MODE=netserver > > ups.conf > [TOPAPC] > driver = usbhid-ups > port = auto > pollonly > serial = "IS1309002707" > desc = "TOPAPC" > [MIDAPC] > driver = usbhid-ups > port = auto > pollonly > serial =

Hi Philip, I've updated NUT to 2.7.3 and finally found the root cause for the unexpected shutdown: It is recommended to increase pollinterval to 10 seconds in ups.conf for usbhid-ups driver due to a known issue: http://www.networkupstools.org/docs/man/usbhid-ups.html Default DEADTIME=15 in upsmon.conf was triggering shutdown. Increasing the value to 30 seconds resolved the issue. Now when

STATISTICIAN / DATA ANALYST Centocor, an operating company of Johnson & Johnson, seeks a highly motivated statistician/data analyst to work in its newly formed Nonclinical Statistics group. We support innovative science in the discovery and research of biotechnology therapies, with obligatory emphasis on the application of modern statistical approaches. Primary responsibilities of the

MASTER SYSTEM nut.conf MODE=netserver ups.conf [TOPAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309002707" desc = "TOPAPC" [MIDAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309001233" desc = "MIDAPC" [BOTAPC] driver = usbhid-ups port = auto

Hi all, I have problem with UPS from PowerWalker model VFI 2000 RT LCD over USB (didn't try serial yet). UPS should work via HID driver but ups.status is not rendered properly. Specification of UPS says USB HID compatible. HID driver is the only one which talks with UPS as i try a few from /lib/nut. I use driver usbhid-ups (which communicate with ups), but subdriver resolving is

| Ross Bamford wrote: | | On Tue, 13 Dec 2005 12:50:08 -0000, Thomas Leitner <thomas_leitner at | gmx.at> wrote [in comp.lang.ruby]: | | > I''m currently gathering ideas for new features for the next big | > webgen release (0.4.0). Some of the planned features are: | > | > * RSS feed generation (proposed by Friz Heinrichmeyer) | | That would be very nice -

Roger, The topology is: UPS TOPAPC, Data link to master, Power supply to master, slave1 and slave2 UPS MIDAPC, Data link to master, Power supply to master, slave1 and slave2 UPS BOTAPC, Data link to master, Power supply to master, slave1 and slave2 Shutdown plan: When wall power fails for any of the three UPS units, they continue powering the master and the two slaves. When two of the UPS

Le Tue, 16 Dec 2014 15:36:29 +0100 Frantz de Germain <frantz at info.univ-angers.fr> ?crivait: > Hello, > > I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. I've > got the message : > > "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of this message)" > > I've been looking for

------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14008.870179829.1@erehwon.bmc.com> See attached. Red Hat Linux package mh-6.8.3-13.i386.rpm installs the inc and msgchk programs as follows: -rwsr-sr-x- root mail 72628 Oct 17 16:57 /usr/bin/mh/inc -rwsr-xr-x- root root 52536 Oct 17 16:57 /usr/bin/mh/msgchk Hal -------

Linux-2.4.28 libusb-0.1.8 nut-2.6.5 [+most recent drivers from GIT] - from tarball EATON 3S700DIN [mfr.date 09/28/14] ---------------------------------- ISSUES: I) Too many kernel logs: --- In /var/log/kernel.log usbdevfs: usb_submit_urb returned -28 In /var/log/daemon.log: usbhid-ups[744]: libusb_get_interrupt: No error usbhid-ups[744]: libusb_get_interrupt: error submitting URB: No space left

Hi, I have the following system configuration (probably does not matter, but anyway): Ubuntu Linux x86 VM running under ESXi bare metal hypervisor. UPS is connected to the ESXi host, and VM communicates to the UPS using USB pass through option. Details of elaborated shutdown sequence are out of topic, so I skip them. NUT was installed from the package, I believe it is recent enough. NUT was set

Hi Guys, I'd like to submit a patch to enable NUT to communicate with APC 5G UPSs. The current usbhid-ups driver recognises APC UPSs by the Vendor ID and Product ID of 0x051D and 0x0002. This needs to be amended with the new Product ID of 0x0003. (See attached file: apc-hid.patch) Secondly, when Nut polls the UPS via the interrupt channel, these will time out, resulting in frequent lost