search for: 90enumerator

...conflict with a > generated `nut-driver at cyberpower.service` instance (although this is not > the only problem, as the unit seems to fail starting for you too), more > details about such units at: > > * https://github.com/networkupstools/nut/wiki/ > nut%E2%80%90driver%E2%80%90enumerator-(NDE) <https://github.com/ > networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE)> > > Jim > > > On Sun, Nov 10, 2024 at 4:47?PM Bill Gee <bgee at campercaver.net > <mailto:bgee at campercaver.net>> wrote: > > I also am wonderin...

...riven attempts, you may also be in conflict with a generated `nut-driver at cyberpower.service` instance (although this is not the only problem, as the unit seems to fail starting for you too), more details about such units at: * https://github.com/networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE) Jim On Sun, Nov 10, 2024 at 4:47?PM Bill Gee <bgee at campercaver.net> wrote: > I also am wondering if the message about libusb driver missing might be > the real problem. > > Checking my system, I see this: > > =================== > [root at mythtv dev]# ll /de...

...rated `nut-driver at cyberpower.service` instance (although this is > not > > the only problem, as the unit seems to fail starting for you too), more > > details about such units at: > > > > * https://github.com/networkupstools/nut/wiki/ > > nut%E2%80%90driver%E2%80%90enumerator-(NDE) <https://github.com/ > > networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE)> > > > > Jim > > > > > > On Sun, Nov 10, 2024 at 4:47?PM Bill Gee <bgee at campercaver.net > > <mailto:bgee at campercaver.net>> wrote: &gt...

...A systemd unit may have been started without a PID file, so the copy started from command line does not see that one to kill off (as NUT drivers usually do since the dawn of time, assuming a frozen older copy). More details here: https://github.com/networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE) Newer NUT versions should be more informative in the log about such situations, as well as capable of communicating with the older copy (if it is not frozen) over Unix sockets "intelligently" instead of sending bare-bone signals to reload or exit with no feedback. Jim On Fri,...

I also am wondering if the message about libusb driver missing might be the real problem. Checking my system, I see this: =================== [root at mythtv dev]# ll /dev/bus/usb/001 total 0 crw-rw-r--+ 1 root root 189, 0 Nov 9 08:21 001 crw-rw-r--+ 1 root root 189, 1 Nov 9 08:21 002 crw-rw-r--+ 1 root root 189, 2 Nov 9 08:21 003 crw-rw-r--+ 1 root dialout 189, 3 Nov 10 09:43 004

...unit may have been started without a PID file, so the copy started from command line does not see that one to kill off (as NUT drivers usually do since the dawn of time, assuming a frozen older copy). > > More details here: https://github.com/networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE) > > Newer NUT versions should be more informative in the log about such situations, as well as capable of communicating with the older copy (if it is not frozen) over Unix sockets "intelligently" instead of sending bare-bone signals to reload or exit with no feedback. > &gt...

Hi folks, I'm having an issue with getting nut-server to start at boot on a freshly installed Fedora 40 desktop. Seems once the machine is up, I can manually start with systemctl start nut-server and everythings fine. dnf info nut Last metadata expiration check: 2:08:11 ago on Sat 27 Jul 2024 03:48:13 PM EDT. Installed Packages Name : nut Version : 2.8.2 Release : 1.fc40

Hello Initial Disclaimer: I used this tutorial. I know its in german but the entries to be made in the configuration files are marked and should be able to identify if there are any errors. https://techbotch.org/blog/ups-setup/index.html After several power failures and damaged fuses I decided to give Eaton & Nut another try. Eaton because the model I bought seems to be the one on the

...UT versions already do not default to offering them in `nut-scanner` output, to minimize run-time surprises. 4) See if you already have a service instance `nut-driver at apcupskelder.service` defined and running, since NUT v2.8.0 https://github.com/networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE) could have created it - but the older blogs/videos do not reflect this facility. The "terminating other driver" seems to be a clue in that direction. Maybe that other copy of the driver is what holds the USB port. Also avoid `upsdrvctl` in that case. Notably, if the driver already r...

...ot default to offering them in `nut-scanner` > output, to minimize run-time surprises. > > 4) See if you already have a service instance > `nut-driver at apcupskelder.service` defined and running, since NUT v2.8.0 > https://github.com/networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE) > could have created it - but the older blogs/videos do not reflect this > facility. The "terminating other driver" seems to be a clue in that > direction. Maybe that other copy of the driver is what holds the USB port. > Also avoid `upsdrvctl` in that case. > Notably...

I installed a new UPS today and after several failed attempts with other software, installed Nut version 2.8 on my Centos 7 server using yum nut. Several issues followed: 1. When I started nut-server it failed because /run/nut did not exist so I created it by hand. 2. nut-server then started but gave he following in /var/log/messages: May 11 13:33:00 mustang systemd: Started Network UPS Tools -