search for: nxmm

...; > Interestingly, I did some tinkering with openSUSE 15.1 Leap on a physical box and saw the same drops there, but was able to get them to stop after installing NUT and just doing the “standard” configuration. However, I ran into some connection refused messages, e.g.: > > user at linux-nxmm:/dev/bus> sudo upsc -l > Error: Connection failure: Connection refused > I keep meaning to put together a diagram to help with this, but in the mean time: UPS <-- driver <-- upsd <-- clients (upsc, upsmon, NUT Monitor GUI, etc.) "upsc -l" is making a TCP connection to...

...port. Note: Interestingly, I did some tinkering with openSUSE 15.1 Leap on a physical box and saw the same drops there, but was able to get them to stop after installing NUT and just doing the “standard” configuration. However, I ran into some connection refused messages, e.g.: user at linux-nxmm:/dev/bus> sudo upsc -l Error: Connection failure: Connection refused When trying to pull data from the UPS, so I was clearly doing something wrong. But, the UPS stopped dropping (i.e. retained Device # in lsusb and no messages in /var/log/messages) . I did NOT have to make the changes to “42...

...> Interestingly, I did some tinkering with openSUSE 15.1 Leap on a physical box and saw the same drops there, but was able to get them to stop after installing NUT and just doing the “standard” configuration. However, I ran into some connection refused messages, e.g.: > > user at linux-nxmm:/dev/bus> sudo upsc -l > Error: Connection failure: Connection refused > I keep meaning to put together a diagram to help with this, but in the mean time: UPS <-- driver <-- upsd <-- clients (upsc, upsmon, NUT Monitor GUI, etc.) "upsc -l" is making a TCP connect...

...> Interestingly, I did some tinkering with openSUSE 15.1 Leap on a physical box and saw the same drops there, but was able to get them to stop after installing NUT and just doing the “standard” configuration. However, I ran into some connection refused messages, e.g.: > > user at linux-nxmm:/dev/bus> sudo upsc -l > Error: Connection failure: Connection refused > I keep meaning to put together a diagram to help with this, but in the mean time: UPS <-- driver <-- upsd <-- clients (upsc, upsmon, NUT Monitor GUI, etc.) "upsc -l" is making a TCP connect...

Charles and Wolfy, Thanks for the replies. I added some responses below. I think I got the driver debugging right, but let me know if it is off. I should note: The CentOS 7.6 machine I have been testing with is a virtual machine (running on VMware ESXi 7.6). At least 1 customer and I have seen the same issue on VMs and physical boxes, so I don’t think that matters, but if it does let me know.