Hi Charles; Had a fire on the mobo of my old server, replaced it all with about 10x the hardware. dmesg now says this: 71068.842780] usb 1-9: new full-speed USB device number 10 using xhci_hcd [71069.012577] usb 1-9: New USB device found, idVendor=051d, idProduct=0003 [71069.012579] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [71069.012579] usb 1-9: Product: Smart-UPS_1500 FW:UPS 03.5 / ID=1015 [71069.012580] usb 1-9: Manufacturer: American Power Conversion [71069.012581] usb 1-9: SerialNumber: 3S1906X11389 [71069.126796] hid-generic 0003:051D:0003.0003: hiddev0,hidraw2: USB HID v1.11 Device [American Power Conversion Smart-UPS_1500 FW:UPS 03.5 / ID=1015] on usb-0000:00:14.0-9/input0 What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't seem to want to talk to it, and the original name _(usbhid-ups) doesn't work from new mobo. Oh wait, I can't spell. But that didn't help, and a restart gets this error: Dec 07 18:49:46 coyote systemd[1]: Starting Network UPS Tools - power devices information server... Dec 07 18:49:46 coyote upsd[3259]: fopen /var/run/nut/upsd.pid: No such file or directory Dec 07 18:49:46 coyote upsd[3259]: listening on 127.0.0.1 port 3493 Dec 07 18:49:46 coyote upsd[3259]: listening on 127.0.0.1 port 3493 Dec 07 18:49:46 coyote upsd[3259]: Can't connect to UPS [myups] (hidraw-myups): No such file or directory /var/run/nut/upsd.pid does exist, but root is being bounced and for some reason I can't su nut from root. By now I've probably got it AFU from playing one of that famous 10k monkeys. :( Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
On Sat, 7 Dec 2019, Gene Heskett wrote:> /var/run/nut/upsd.pid does exist, but root is being bounced and for some > reason I can't su nut from root.Just a thought - what does ls -lF /var/run/nut/upsd.pid report when run as root? Roger
On Sunday 08 December 2019 09:25:29 Roger Price wrote: ls -lF /var/run/nut/ total 8 -rw-r--r-- 1 nut nut 5 Dec 7 18:49 upsd.pid -rw-r--r-- 1 root root 5 Dec 7 18:52 upsmon.pid No permission if I look as gene(me) Now, I do have a /home/nut ls -l /home root at coyote:Daily$ ls -l /home total 16 drwx------ 53 amanda backup 4096 Jul 8 12:22 amanda drwxr-xr-x 72 gene gene 4096 Dec 8 12:17 gene drwxr-xr-x 15 nut nut 4096 Dec 14 2016 nut drwx------ 16 nut nut 4096 Jun 17 2012 ups Something back in time forced me to give amanda a passwd, so as root "su amanda -c "command works" but nut is empty so that doesn't work now: nut:x:121:125::/var/lib/nut:/bin/false Is this where I need to fix it? With a passwd nut as root? Thanks Roger. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
On Dec 7, 2019, at 7:01 PM, Gene Heskett <gheskett at shentel.net> wrote:> > What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't seem > to want to talk to it, and the original name _(usbhid-ups) doesn't work > from new mobo. Oh wait, I can't spell. But that didn't help, and a > restart gets this error:...> Dec 07 18:49:46 coyote upsd[3259]: Can't connect to UPS [myups] > (hidraw-myups): No such file or directoryHi Gene, Might be simpler to start with the contents of your /etc/nut/ups.conf file? Mine looks like this: [apc] driver = usbhid-ups port = auto # USB Yours should probably look similar: [myups] driver = usbhid-ups port = auto # USB Are you using Debian? I think they split things out a bit in recent versions, so the exact NUT restart command might depend on whether you are using stretch, or later. Roger is also onto something with the contents of /var/run/nut. If the driver is running, you should see a socket (3rd entry): $ sudo ls -l /run/nut total 12 -rw-r--r-- 1 nut nut 5 Aug 23 09:40 upsd.pid -rw-r--r-- 1 root root 5 Aug 23 09:40 upsmon.pid srw-rw---- 1 nut nut 0 Aug 23 09:40 usbhid-ups-apc -rw-r--r-- 1 nut nut 5 Aug 23 09:40 usbhid-ups-apc.pid If that socket isn't showing up, then we need to figure out why the driver isn't starting. - Charles
On Sunday 08 December 2019 21:48:03 Charles Lepple wrote:> On Dec 7, 2019, at 7:01 PM, Gene Heskett <gheskett at shentel.net> wrote: > > What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't > > seem to want to talk to it, and the original name _(usbhid-ups) > > doesn't work from new mobo. Oh wait, I can't spell. But that didn't > > help, and a restart gets this error: > > ... > > > Dec 07 18:49:46 coyote upsd[3259]: Can't connect to UPS [myups] > > (hidraw-myups): No such file or directory > > Hi Gene, > > Might be simpler to start with the contents of your /etc/nut/ups.conf > file? > > Mine looks like this: > > [apc] > driver = usbhid-ups > port = auto # USB > > Yours should probably look similar: > > [myups] > driver = usbhid-ups > port = auto # USB > > Are you using Debian? I think they split things out a bit in recent > versions, so the exact NUT restart command might depend on whether you > are using stretch, or later. > > Roger is also onto something with the contents of /var/run/nut. If the > driver is running, you should see a socket (3rd entry): > > $ sudo ls -l /run/nut > total 12 > -rw-r--r-- 1 nut nut 5 Aug 23 09:40 upsd.pid > -rw-r--r-- 1 root root 5 Aug 23 09:40 upsmon.pid > srw-rw---- 1 nut nut 0 Aug 23 09:40 usbhid-ups-apc > -rw-r--r-- 1 nut nut 5 Aug 23 09:40 usbhid-ups-apc.pid > > If that socket isn't showing up, then we need to figure out why the > driver isn't starting. > > - CharlesThe working part: [myups] driver=hidraw #driver=usbhid-ups #driver=belkin #driver=belkinunv #driver=genericups port=auto offdelay=120 ondelay=0 The previous belkin used the next commented line down. This is an even bigger APC. Thanks Charles Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>