Displaying 20 results from an estimated 6000 matches similar to: "2.8.3 build fail"
2025 May 14
1
UPS configuration issue?
On 5/13/25 21:05, Sam Varshavchik wrote:
> gene heskett via Nut-upsuser writes:
>
>> However debians legendary slowness to update things does test my
>> patience at times. The fact that bookworms default nut is 2.8.0 is an
>> example.
>
> That sounds familiar. Debian's been shipping very old versions of my
> packages, which was ?irritating. I am not being
2025 May 14
2
UPS configuration issue?
This sub-thread is veering off-topic from the original question... but I'll
digress.
>> However debian's legendary slowness to update things does test my
>> patience at times. The fact that bookworms default nut is 2.8.0 is an
>> example.
Per https://www.debian.org/News/2023/20230610 they released the 12th
(bookworm) baseline on June 10, 2023, and `bookworm will be
2023 May 22
2
got nut 2.8.1 but despite reinstall, shows 2.7.4
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
2025 May 13
2
UPS configuration issue?
Hello Gene,
I read and nodded sometimes and caught myself thinking that I used to
propose or agree with some of the points you make, but outgrew those.
> ...makers claim...
I suppose this means asciidoc makers (not e.g. UPS makers)? They are
actually largely non-Windows, especially in the part about rendering books,
presentations, local HTML pages or web sites. These are all
2023 May 22
2
got nut 2.8.1 but despite reinstall, shows 2.7.4
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
2023 May 22
1
got nut 2.8.1 but despite reinstall, shows 2.7.4
>>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
2020 Jun 22
2
Low Battery Problems
On Monday 22 June 2020 15:36:21 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
>
2020 Jun 22
5
Low Battery Problems
On Monday 22 June 2020 09:50:50 Larry Fahnoe wrote:
> On Mon, Jun 22, 2020 at 8:27 AM Gene Heskett <gheskett at shentel.net>
wrote:
> > > On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote:
> > > > pi at rpi4:~ $ upscmd myups *test.battery.start.quick*
> > > > Username (pi):
> > > > Password:
> > > > Unexpected response from upsd:
2020 Jun 22
2
Low Battery Problems
On Monday 22 June 2020 09:18:29 Charles Lepple wrote:
> On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote:
> > pi at rpi4:~ $ upscmd myups test.battery.start.quick
> > Username (pi):
> > Password:
> > Unexpected response from upsd: ERR ACCESS-DENIED
> >
> > Looking at /etc/nut/uspd.users, I (me, pi) should be able to do
> > that. ???
>
> Hi Gene,
2020 Oct 30
2
Can't get CyberPower UPS to work with Raspberry Pi 4
On Thursday 29 October 2020 22:12:00 Charles Lepple wrote:
> On Oct 28, 2020, at 9:56 PM, Gene Heskett <gheskett at shentel.net> wrote:
> > Which looks very incomplete to me. OTOH, its not a very big UPS but
> > neither is the pi. I have tested that, and it shuts off long before
> > it outouts a LB signal.
>
> Which part looks incomplete, the variables or the
2020 Oct 29
2
Can't get CyberPower UPS to work with Raspberry Pi 4
On Wednesday 28 October 2020 21:32:02 Charles Lepple wrote:
> On Oct 26, 2020, at 9:38 AM, Gene Heskett <gheskett at shentel.net> wrote:
> >>> battery.voltage: 24.0
> >>> battery.voltage.nominal: 24
> >>
> >> I don't have the citation handy, but I think another user reported
> >> that the battery.voltage returned by the UPS is a
2020 Oct 31
0
Can't get CyberPower UPS to work with Raspberry Pi 4
On Oct 30, 2020, at 12:22 AM, Gene Heskett <gheskett at shentel.net> wrote:
>
> On Thursday 29 October 2020 22:12:00 Charles Lepple wrote:
>
>> On Oct 28, 2020, at 9:56 PM, Gene Heskett <gheskett at shentel.net> wrote:
>>> Which looks very incomplete to me. OTOH, its not a very big UPS but
>>> neither is the pi. I have tested that, and it shuts off
2019 Dec 09
2
new mobo, ups doesn't connect
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
> >
2023 May 22
1
got nut 2.8.1 but despite reinstall, shows 2.7.4
I think you have just the libraries - also you'd need a *-dev package for
headers. The docs/config-prereqs.txt has the dependencies in more detail.
In quick practice, --with-all=auto can help better if you don't monitor a
netxml device ;)
HTH Jim
On Mon, May 22, 2023, 15:24 gene heskett <gheskett at shentel.net> wrote:
> On 5/22/23 03:10, gene heskett wrote:
> > Which
2020 Jun 22
2
Low Battery Problems
On Monday 22 June 2020 15:26:23 Larry Fahnoe wrote:
> On Mon, Jun 22, 2020 at 12:26 PM Gene Heskett <gheskett at shentel.net>
wrote:
> > So I just edited /etc/nut/upsd.users to add both the commands it
> > claims to have but get this response to either:
> >
> > pi at rpi4:~ $ upscmd myups test.battery.start.quick
> > Username (pi): pi
> > Password:
2023 May 22
2
got nut 2.8.1 but despite reinstall, shows 2.7.4
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
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, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D.
2020 Jan 10
0
nut on armhf, r-pi4b IOW
On Friday 10 January 2020 07:28:13 Charles Lepple wrote:
> On Jan 9, 2020, at 5:51 PM, Gene Heskett wrote:
> > On Thursday 09 January 2020 16:59:12 Charles Lepple wrote:
> >> On Jan 9, 2020, at 4:39 PM, Gene Heskett <gheskett at shentel.net>
wrote:
> >>> So for starters, what's the best ./configure command line?
> >>
> >> There’s this
2019 Dec 08
4
new mobo, ups doesn't connect
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:
2020 Jan 09
0
nut on armhf, r-pi4b IOW
On Thursday 09 January 2020 16:59:12 Charles Lepple wrote:
> On Jan 9, 2020, at 4:39 PM, Gene Heskett <gheskett at shentel.net> wrote:
> > So for starters, what's the best ./configure command line?
>
> There’s this page for matching the layout of an existing Debian
> install:
> https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Ra
2019 Dec 09
0
new mobo, ups doesn't connect
On Sunday 08 December 2019 22:17:39 Gene Heskett wrote:
> 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)
> > >