similar to: odd msg at top of upsc output

On Friday 31 May 2019 01:29:51 am Manuel Wolfshant wrote: > On 5/31/19 6:54 AM, Gene Heskett wrote: > > 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? > > >

On May 31, 2019, at 1:29 AM, Manuel Wolfshant wrote: > > On 5/31/19 6:54 AM, Gene Heskett wrote: >> 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? >> >>

On 5/31/19 6:54 AM, Gene Heskett wrote: > 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 the nut client ( upsc ) is trying to use the NSS-based SSL backend of your OS (in order to

On Friday 31 May 2019 10:08:02 am Charles Lepple wrote: > On May 31, 2019, at 1:29 AM, Manuel Wolfshant wrote: > > On 5/31/19 6:54 AM, Gene Heskett wrote: > >> Greetings all; > >> > >> gene at coyote:~$ upsc myups > >> Init SSL without certificate database > >> battery.charge: 100 > >> battery.charge.low: 30 > >> [yadda

On Mon, 2023-05-22 at 15:54:51 +0200, Matus UHLAR - fantomas wrote: > > > 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 > > > On 5/22/23 07:13, Greg Troxel wrote: > > > It is likely that you have

On 5/22/23 07:13, Greg Troxel wrote: > 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

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

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

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:

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 Jun 22, 2020, at 3:36 PM, Charles Lepple wrote: > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: >> >> So I just edited /etc/nut/upsd.users to add both the commands it claims >> to have but get this response to either: > > In your original example, you had multiple “instcmd =“ lines for one user- I think the allowed commands all need to be listed on one

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,

Greetings all; Back to a thread I started back in May of 2008 I think. I never did get this belkin and nut to talking, so I thought I'd make another run at it. Trying to run the driver as the user gene, I'm getting this: --------------------------- [root at coyote ups]# su gene -c "/sbin/belkin -D -a myups" Network UPS Tools - Belkin Smart protocol driver 0.21 (2.2.2) debug

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

>>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 >On 5/22/23 07:13, Greg Troxel wrote: >>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

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

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 May 31, 2019, at 11:19 AM, Gene Heskett wrote: > > On Friday 31 May 2019 10:08:02 am Charles Lepple wrote: >> >> To be honest, I thought we had fixed this a while ago (NUT 2.7.1), but >> I guess it popped back up again: >> https://github.com/networkupstools/nut/issues/30 > > nut 2.7.2. Built from the tarball. Some option I should have configured > it