similar to: NUT stopped working after an upgrade

Did the upgrade by chance install/alter any udev rules causing the UPS devices to now have incorrect permissions? And what user is nut running as? On November 9, 2024 9:58:57 AM EST, Bill Gee <bgee at campercaver.net> wrote: >Running NUT version 2.8.2 on Fedora 40. NUT installed from the Fedora package. CyberPower CP1000AVRLCD connected by USB. > >I updated the system yesterday

Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS seeing the UPS at a low level. I looked through /dev/ but did not see a device that jumps out as the UPS. ===================== [root at mythtv rules.d]# dmesg | grep -i 0764 [ 2.021485] usb 1-1.8: New USB device found, idVendor=0764, idProduct=0501, bcdDevice= 0.01 [ 2.049515]

Check /dev/hidraw6, as noted in your dmesg output (and any other *hid* devices under /dev). User nut has almost zero privs to devices unless a udev rule changes the perms on the dev for nut . . . On November 9, 2024 1:25:29 PM EST, Bill Gee <bgee at campercaver.net> wrote: >Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS

I've had fun with nut on RH systems, these are my notes to get it working: Create /usr/lib/tmpfiles.d/nut-client.conf:D? ? /run/nut 0770 root nut - ...the file did not exist, and so the PID folder/file was not getting generated. Then the driver would start. Also had to setup enabled services (still not 100% confident that this is totally correct):[root at emp80 ups]# systemctl list-unit-files

Great! Regarding libusb and nut-scanner, I think the *.so (exact) symlinks are part of *-devel packages. This was solved in NUT recently (maybe after 2.8.2 release already) by detecting and stashing the basename of realpath of the library present during build, so the exact *.so.X.Y.Z would be also tried. Also, nut-scanner now (in 2.8.2 IIRC) should not suggest the volatile bus/busport/device

Thanks for the tip, Jim. I just figured out what is going on. The system is now working. ==> This one is on me. <== The root cause was the specification of the bus number in the ups.conf file. Here is what it looks like now: ============ [cyberpower] driver = "usbhid-ups" port = "auto" vendorid = "0764" productid =

Can you try starting the driver with higher debug verbosity to see more details, e.g. add `debug_min = 6` to the `ups.conf` section, or stop the auto-starting driver attempts and run the driver program with CLI options? * https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity With `upsdrvctl` driven attempts, you may also be in conflict with a generated `nut-driver at

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

I keep getting errors in my logs about can not bind to address *.*.*.*:53 address in use.. what did i do wrong in the setup of my server or domain? attached logs and smb.conf along with the output from my provision command. Jeffrey D. Means meaje at meanspc.com Owner / CIO for MeansPC http://www.meanspc.com/ Custom Web Development For Your Needs. (970)308-1298 - The

Dear Alexander Morozov, From the output of the command "ps -ef | grep wine", we can observe that the native Windows USB driver ICDUSB2.sys for the Sony IC Recorder gets loaded with winedevice.exe. enming 18814 18781 0 16:15 ? 00:00:00 C:\windows\system32\winedevice.exe ICDUSB2 However, Digital Voice Editor 3 (under Wine) simply would not detect the Sony IC Recorder. The

I'm still digging into this but thought I'd post what I have so far in case there's a known issue that's easily fixed. I'm using the version of NUT that's in the ports tree (see the info at the bottom). Using the SNMP drivers to talk with two ACP SmartUPSs. NUT is functional about monitoring and initiating host shutdown. However, when it comes time to shut down the UPSs

can anyone advise on where to find the mythtv repo? I have dag but a yum install mythtv-suite yields nothing thanks

Hello, Thanks for the report and sorry about any complications. A few first questions: * is this setup known to have been working with earlier NUT releases (e.g. same OS and devices, older NUT - can try with a custom build of older tags)? Is this a regression, or we never knew the correct mappings for timeouts and/or shutdown commands used by this model? * is there the `select` error when

I'm starting a project to build a MythTV box for my living room. Anyone else currently working with MythTV on CentOS 4? Here are some of the gotcha's I've worked through so far: - I was originally planning on using KnoppMyth. But their CD appears to be only for i386. Without realizing it, the P4 CPU I picked is one of the newer ones with the x86_64 extensions. It won't boot

I have several machines, same hardware and config, but one tiny little change.. the hostname. Each one of these diskless machines needs its own hostname. Presently my pxelinux.cfg is setup like: prompt 1 default Gentoo timeout 10 label Gentoo kernel boot/kernel-3.16.5-gentoo APPEND root=/dev/nfs rw ip=dhcp nfsroot=192.168.1.10:/RAID/diskless/XXXXX-mythtv-0.27-fixes,tcp,rsize=131072

This is on EL9 with 2.8.2: nut-monitor[150988]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it I have no idea what this really means. I think it has something to do about systemd startup notification, but I'm not really sure. Can someone enlighten me? Is this something that anyone should care about? -- Orion Poplawski he/him/his -

Hi, After upgrading to 1.2 I started getting fchown errors in the log. They look like: Jul 12 18:32:54 jukebox dovecot: deliver(kim): fchown(/data/mail/kim/.lists.mythtv-users/tmp/1247416373.M857540P19162.jukebox.alleroedderne.adsl.dk, -1, 500(k im)) failed: Operation not permitted (egid=12(mail), group based on /data/mail/kim/.lists.mythtv-users) I have tried to get rid of the by changing

On 5/25/2015 12:12 PM, Jonathan Billings wrote: > On May 25, 2015, at 10:48 AM, Kirk Bocek <t004 at kbocek.com> wrote: >> It usually happens when I've wanted to change versions of the same software between repos and that software has been compiled differently. Usually audio-visual software. Yum install triggers a conflict and yum uninstall on the older package cascades a bunch

On 11/15/24 15:57, Orion Poplawski wrote: > This is on EL9 with 2.8.2: > > nut-monitor[150988]: upsnotify: failed to notify about state 2: no > notification tech defined, will not spam more about it > > I have no idea what this really means. I think it has something to do about > systemd startup notification, but I'm not really sure. Can someone enlighten me? >

I have a network server running FC5, with a hardware raid 3 card using 5 drives, as one large (1.2TB) partition in JFS. I chose JFS because of a recommendation for performance from a MythTV tutorial, but I don't really know much about file systems and am suspecting JFS to be causing my problems. I run samba, apache and MythTV on this machine, and there is essentially only one problem as far