similar to: nut vs ups fail

On Tuesday 07 May 2019 08:38:44 am Charles Lepple wrote: > On May 7, 2019, at 5:06 AM, Gene Heskett wrote: > > New testing install(stretch) > > pulled in nut stuff from repo. > > copied old wheezy configs to /etc/nut, overwriting the resident > > files can't talk to ups, missing usbhid-ups file > > Gene, > > What do you have in /etc/nut/ups.conf? (There

On Tuesday 07 May 2019 09:49:47 am Charles Lepple wrote: > On May 7, 2019, at 9:09 AM, Gene Heskett wrote: > > On Tuesday 07 May 2019 08:38:44 am Charles Lepple wrote: > >> On May 7, 2019, at 5:06 AM, Gene Heskett wrote: > >>> New testing install(stretch) > >>> pulled in nut stuff from repo. > >>> copied old wheezy configs to /etc/nut,

On Sunday 12 May 2019 02:41:02 pm Charles Lepple wrote: > /lib/nut/usbhid-ups -a myups -DD gene at coyote:~$ /lib/nut/usbhid-ups -a myups -DD Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 Can't open /etc/nut/ups.conf: Can't open /etc/nut/ups.conf: Permission denied lemme see who owns that. huh? amandabackup:nut what the h? Who is supposed to own

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:

Greetings; I found pdf user manual which explains a few things that might help. However, for a ubuntu flavor, the various .conf etc files seem to be in /etc/nut. But this pdf says they are in /usr/local/ups/etc, and yes indeed there are some there, with the .sample files being owned by root, and the rest are user 503, whoever he may be. Are these just a sample storage in case one needs to

On Sunday 12 May 2019 12:07:13 pm Charles Lepple wrote: > systemctl status nut-driver ● nut-driver.service - Network UPS Tools - power device driver controller Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2019-05-10 02:35:09 EDT; 2 days ago Ok, I'll byte, the only usnhid-ups on the system is on

Hi Gene, On Oct 18, 2014, at 7:35 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Greetings; > > I found pdf user manual which explains a few things that might help. > > However, for a ubuntu flavor, the various .conf etc files seem to be in > /etc/nut. We have an open ticket about that[*]; basically, the official NUT documentation needs to be a bit more explicit

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 > >

Greetings; Its unk because whats plugged in seems to be blocking the rear name plate. About all I can recall is that its big, 3 battery unit, rated somewhere north ob 1250 VA. Its an 050D:0751 Belkin. What driver should I use, and what file is that set in? The nut version presently and freshly installed is from the Ubuntu 10.04.4 LTS repo's. Probably old, but IIRC it also worked with

On Wednesday 08 May 2019 05:39:22 pm Stuart D. Gathman wrote: > On Tue, 7 May 2019, Gene Heskett wrote: > > May 07 10:40:21 coyote upsd[12110]: fopen /var/run/nut/upsd.pid: No > > such file or directory > > Some time ago, Fedora made /var/run a symlink to /run which is a tmpfs > filesystem. Thus, any subdirectories must be created afresh each > boot. The packager for

Greetings all; Is it possible to set a logging option in one of the config files so that when we have a 1 second power bump, the date is included, both in the log, and in the -wall broadcast? We apparently have a substation regulator in the process of failing, and the recycle isn't normally slow enough to reset the clocks, but it killing one of my computers w/o actually causing a reboot.

Greetings people; The section of drakeconf that pclos uses has two problems. First is several screens full of complaints about deprecated syntax in "/etc/udev/rules.d/70-nut-usbups.rules" at each reboot. So I pulled the current 2.5 svn trunk, then found I was missing quite a few build tools needed here that aren't used when building a kernel, currently running a 32 bit

Hi Charles; I hope this finds you well. Here is dmesg output: gene at coyote:~$ dmesg |grep Belkin [ 3.315667] usb 2-3: Product: Belkin UPS [ 3.315669] usb 2-3: Manufacturer: Belkin [ 4.084258] generic-usb 0003:050D:0751.0009: hiddev0,hidraw4: USB HID v1.11 Device [Belkin Belkin UPS] on usb-0000:00:02.0-3/input I have configured it to use this generic-usb, and probably made it less

Greetings all; gene at coyote:~$ upsc myups Init SSL without certificate database battery.charge: 100 battery.charge.low: 30 [yadda yadda] Is there a certificate package I should install? 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) Genes Web page

Greetings Charles; I hope you had a nice Christmas, and will have a happy and prosperous new year in 2016. You mentioned upsrw in a message earlier, so I ran it, and found the shutdown timeout was only 20 seconds. gene at coyote:~$ upsrw myups [input.transfer.high] High voltage transfer point (V) Type: STRING Value: 140 [input.transfer.low] Low voltage transfer point (V) Type: STRING Value:

On Sunday 12 May 2019 03:10:13 pm Charles Lepple wrote: > On May 12, 2019, at 2:51 PM, Gene Heskett wrote: > > On Sunday 12 May 2019 02:41:02 pm Charles Lepple wrote: > >> /lib/nut/usbhid-ups -a myups -DD > > > > gene at coyote:~$ /lib/nut/usbhid-ups -a myups -DD > > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > > USB communication driver 0.33

Greetings; I have the newest nut (nut-2.2.2-4.fc10.i386) from fedora 10 repos) installed and this ups (from lsusb -vv): Bus 001 Device 006: ID 050d:0751 Belkin Components Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0

gene heskett <gheskett at shentel.net> writes: > Which file in the nut I pulled a month ago, should I start with to get > the new version actually running? I still get - -V=2.7.4 It is likely that you have built new nut but old nut is still on your system. I do a 'sudo make install' to write over the distribution nut (on NetBSD/pkgsrc, surely not what you are using).

Hi Charles; I had nut working from before, but managed to lock up something and had to reboot. Nut is in the stuff to start at boot time, but is not now capable to being restarted with the nut script in /etc/init.d, claiming it is disabled: gene at coyote:/usr/src/nut-2.7.2/docs/man$ sudo service nut start * nut disabled, please adjust the configuration to your needs * Then set MODE to a

On Sep 5, 2020, at 5:23 AM, Roger Price wrote: > > On Sat, 5 Sep 2020, Gene Heskett wrote: > >> But runs normally if started. On a rpi4 running an uptodate raspbian buster, how do I set it to auto start at boot time? > > Hello Gene, By "auto start" I assume you mean the automatic power on of a box when wall power returns after a power failure. For this to work,