similar to: CentOS 6 spontaneous reboots

Hi Bill, On 2016-05-30, Bill Gee <bgee at campercaver.net> wrote: > > By luck I saw the beginning of a reboot on the server console. Normally I have > other systems up on the KVM switch. It appears to have dumped core. I don't > know where to look for the core dump files. They are not in /root. One place you might check is under /var/lib. I think there may be a

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

Look in the startup logs and see where itnis starting. I'm not at a RH system at the moment, but at work, I have had to do this, so can look there,mor perhaps put Nut on the test RH8 VM I spun up for other rrasons on Friday and work out the syntax. Not sure if the systemd file you are using came in the RPM or not, but if it did, it's almost a crime that this critical detail was overlooked.

On Tue, Dec 30, 2014 at 9:58 AM, Marcelo Roccasalva < marcelo-centos at irrigacion.gov.ar> wrote: > On Tue, Dec 30, 2014 at 11:46 AM, Bill Gee <bgee at campercaver.net> wrote: > > > Hello everyone - > > > > I am trying to use virt-viewer to connect to KVM virtual machines running > > on a > > CentOS7 host. It works great when running directly on

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 =

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

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]

On Tue, Dec 30, 2014 at 4:08 PM, Bill Gee <bgee at campercaver.net> wrote: > > Thanks! I changed the qemu.conf file to listen on 0.0.0.0. That works - > I can > connect to the virtual machines using a VNC client. > Listening on 0.0.0.0 listens on all network interfaces. Mark's comment is not a major concern unless your KVM host is directly connected to the Internet (no

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

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

Hello everyone - I am trying to use virt-viewer to connect to KVM virtual machines running on a CentOS7 host. It works great when running directly on the host, but I have not been able to figure out the magic connection string to make it work from another computer. On the host, I set selinux to "permissive" and stopped the firewalld service. No change, so it is not related to

On 06/28/2013 04:07 PM, Gene Cumm wrote: > On Fri, Jun 28, 2013 at 12:53 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Fri, Jun 28, 2013 at 10:13 AM, Ady <ady-sf at hotmail.com> wrote: >> >>> But, in Syslinux 4.06, there is linux.c32, which is a sort of >>> introduction to Syslinux 5.xx (please allow me to be not strictly >>> accurate in

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

I have two suggestions about how to keep - for a while - the 388 kernel. First - Use DNF to remove the bad kernels. Then when a new one comes in it will take one of those slots. Second - Increase the number of installed kernels. That change is in yum.conf. https://linuxconfig.org/how-to-remove-old-unused-kernels-on-centos-linux If the number is too high, you may run out of room in /boot

Ha! The secret sauce! Thanks, Tim - This last bit has got my system working. I had nut-server.service enabled and nut.target disabled. I cannot tell you how they got to that state. It might be the RPM, or more likely my messing around several months ago. I do not remember ... In any event, I added the network stuff to the Wants and After lines in the nut.target file, then disabled

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 with all the latest Fedora packages. Now NUT will not run. Chasing the issue through the layers, I come to this: ===================== [root at mythtv rules.d]# upsc cyberpower Error: Driver not connected [root at mythtv rules.d]#

I agree with earlier posters, such documentation can help future tinkerers. There is probably more than just one to hold the hand and walk through the ordeals :) Perhaps a new page at https://github.com/networkupstools/nut/wiki can be a good location... Jim On Thu, May 16, 2024 at 1:29?PM Bill Gee <bgee at campercaver.net> wrote: > Hi Kelly - > > As an Arduino nerd, I am

Hello, FYI. This problem looks similar to the problem I reported in Februari http://www.syslinux.org/archives/2013-February/019517.html Kind regards, Wim. On 06/28/2013 10:02 AM, Matt Fleming wrote: > On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: >> Hi guys! >> I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and >> i have issues to boot it with

> Am 05.03.2018 um 15:34 schrieb Bill Gee <bgee at campercaver.net>: > > > On Monday, March 5, 2018 7:23:53 AM CST Leon Fauster wrote: >> Am 05.03.2018 um 13:04 schrieb Nicolas Kovacs <info at microlinux.fr>: >>> Le 28/02/2018 ? 22:23, Nicolas Kovacs a ?crit : >>>> So far, I've only been able to filter HTTP. >>>>

On Thu, Feb 20, 2020 at 11:06:52AM -0600, Bill Gee wrote: > On Thursday, February 20, 2020 10:54:02 AM CST Fred Smith wrote: > > Hi! > > > > totally OT... > > > > Hoping there is a mailing list or wiki (or other help forum) > > for GWC, but haven't found one yet. > > > > I'm working on converting a bunch of my LPs to CDs, and am using