On Sun, 2 Jun 2024, chrib...@duck.com wrote:
# if the charge is less than 75 percent trigger a LB status
override.battery.charge.low = 75
# if the remaining charge is less than 1200s (20 minutes) trigger a low
battery status
override.battery.runtime.low = 1200
# wait 5 minutes for
On Sat, 1 Jun 2024, Alan via Nut-upsuser wrote:
root@proxmox-01:~# cat nano /etc/nut/ups.conf
If you send us hundreds of lines of comments it makes your post difficult to
understand. Could you trim out the comments with for example
cat /etc/nut/ups.conf | grep -v "#"
which would show us
On Sat, 1 Jun 2024, chrib...@duck.com wrote:
Yes. I received both the email and the update from the console.
>From your email, I understand that the expected behaviour should have been
that the os should have started the shutdown process.
NUT requires that 3 os services be running. If you
On Sat, 1 Jun 2024, Alan via Nut-upsuser wrote:
I modified ./etc/nut/upssched-cmd and modified the script to send an email
(happy to share).
NUT wrote a message to the console and I received an email to inform me that
the UPS was on battery.
Have you also specified an e-mail when power is
On Fri, 29 Mar 2024, Dan Grostick wrote:
It is consistently happening 14-15 minutes after starting. Please see attached
upssched-cmd and upssched.conf. I don't have a upssched.cmd. The binary
upssched is used.
After the heartbeat failure, is upsd still running? Does the command "upsc -L"
On Fri, 29 Mar 2024, Dan Grostick wrote:
It is consistently happening 14-15 minutes after starting. Please see attached
upssched-cmd and upssched.conf. I don't have a upssched.cmd. The binary
upssched is used.
If you speed up the heartbeat by reducing the timers in heartbeat.conf from 300
On Thu, 28 Mar 2024, Dan Grostick via Nut-upsuser wrote:
All three systems have a heartbeat-timer failure approximately 15 minutes
after starting NUT. No subsequent failures. Any ideas on what is happening?
I've seen the timers: heartbeat.conf has two 300 sec timers, upssched.cmd looks
like
On Sun, 10 Mar 2024, Alan via Nut-upsuser wrote:
Very good point. I hope to write a beginners guide -- more like adopting my
notes --on NUT.
I did the same thing, 131 pages, at
https://rogerprice.org/NUT/ConfigExamples.A5.pdf
Roger___
On Mon, 4 Mar 2024, Alan C. Bonnici via Nut-upsuser wrote:
Platform: Proxmox VE 8.1.4
NUT version: Network UPS Tools upsstats 2.8.0
I configured Proxmox and I can pull up the UPS stats.
Typing in `upsrw -l cyberpower@localhost` I get the following:
[battery.charge.low]
Remaining battery level
On Tue, 27 Feb 2024, Giacomo Tognetti via Nut-upsuser wrote:
Home Assistant at https://www.home-assistant.io/integrations/nut/ doesn't give
any examples of how it thinks NUT is configured, and I don't have an
installation to try. Is this an acceptable format for HA ?, because it's not a
NUT
On Sat, 17 Feb 2024, Harlan Stenn via Nut-upsuser wrote:
I'd bet the following is news to nobody.
Some of us Dislike setting Reply-To: at all.
Debian doesn't do it. Why should we?
If it exists, there's an expectation that it should be followed.
That's the problem for me - it exists and
I recently wrote to the list. The distributed message had the following
headers:
Date: Fri, 16 Feb 2024 19:22:59 +0100 (CET)
From: Roger Price via Nut-upsuser
Reply-To: Roger Price
To: nut-upsuser Mailing List
Subject: ...
Note that the Reply-To goes back to the original poster
On Fri, 16 Feb 2024, Dan Grostick wrote:
[heartbeat]
driver=dummy-ups
port=heartbeat.conf
mode=dummy-once
desc= "Heart beat verfication of NUT"
I would be interesting to see the file heartbeat.conf and the NOTIFYFLAG
declarations in upsmon.conf .
See also
On Fri, 16 Feb 2024, Roger Price via Nut-upsuser wrote:
On Fri, 16 Feb 2024, Dan Grostick via Nut-upsuser wrote:
Is there any way to stop dummy ups from continuously broadcasting status?
(onbatt) I want to keep the broadcasts from the ups itself.
Could you show us your entry in ups.conf
On Fri, 16 Feb 2024, Dan Grostick via Nut-upsuser wrote:
Is there any way to stop dummy ups from continuously broadcasting status?
(onbatt) I want to keep the broadcasts from the ups itself.
Could you show us your entry in ups.conf for the dummy ups ?
If you have an entry "port = file" in
On Thu, Dec 21, 2023, 13:11 Tim Reimers KA4LFP via Nut-upsuser
wrote:
- I have a RasPI (hereafter referred to as Pi1) running Bullseye in which
this all WORKS FINE
- I have a SECOND RasPI (hereafter referred to as Pi2) running Bullseye in
which ONLY the CGI scripts do not work.
I have
I would like to suggest that we merge the two mailing lists Nut-upsuser
and Nut-upsdev.
1. Users increasingly post simultaneously to both lists. One list is
sufficient.
2. The very detailed technical discussions which previously justified a second
Nut-upsdev list now take place on
On Sun, 6 Aug 2023, Jim Klimov via Nut-upsdev wrote:
While looking at https://github.com/networkupstools/nut/issues/2014 I
understood that I am
not sure if currently NUT has a standard way of triggering a shutdown based on
remaining charge
or runtime, if a device/driver lacks a
On Fri, 16 Jun 2023, Dan Grostick via Nut-upsuser wrote:
Now that upsstats.cgi works, I've noticed that dummy-ups changes state every 5
minutes between OL and OB (probably when the 300 second timer expires). The
UPS state stays online.
This is a part of the heartbeat intended to assure that
Hello Dan, If I were faced with this problem, I would replace your current NUT
configuration with a well understood "classic" involving MODE=standalone and
upssched. I would not specify RUN_AS_USER root in upsmon.conf, and I would
use the built-in techniques for not running as root.
If this
On Tue, 16 May 2023, Carsten Aulbert wrote:
... I'm still struggling how to shut down servers fed by two independent UPS
systems.
* Keep nut unpatched but use our own NOTIFYCMD or CMDSCRIPT to pull the values
from the server and implement our logic there?
Hello Carsten, That's what I did
On Sat, 29 Apr 2023, Willcox David via Nut-upsuser wrote:
Content of upsmon.conf: (I probably should have called it something other than
“usbhid,” but that’s working for now.)
> RUN_AS_USER upsmon
> MONITOR usbhid@localhost 1 upsmon_master master
> MINSUPPLIES 1
> SHUTDOWNCMD "/sbin/shutdown
On Sun, 23 Apr 2023, Prometheus via Nut-upsuser wrote:
I am trying to configure a graceful shutdown on my TrippLite UPS what would i
need to configure to achieve this keeping in mind I’m using a USBHID driver by
default
Perhaps one of the chapters in this collection of configuration examples
On Sun, 19 Mar 2023, Elton Jhon via Nut-upsuser wrote:
hello I found the Nut project by chance and I wanted to know if it will serve
my purpose.
work with several brands of UPS (Eaton, CM, APC, Vertiv (Emerson)).
I want to know if I could change parameters, update UPS battery and firmware,
On Sat, 28 Jan 2023, John Fowler wrote:
We are getting "Init SSL without certificate database” in response to all
requests.
pi@cyva:~ $ upsc ups@cyva
Init SSL without certificate database
battery.charge: 100
If you don't like the warning, then a command such as upsc ups@cyva 2>/dev/null
On Mon, 9 Jan 2023, Greg Troxel wrote:
Specifically, I find all of this to be noise:
upsmon startup:
Network UPS Tools upsmon 2.8.0.1
again, all knowable statically from config.
upsd:
Network UPS Tools upsd 2.8.0.1
listening on 127.0.0.1 port 3493
listening on ::1 port 3493
Connected to
On Mon, 2 Jan 2023, Jim Klimov wrote:
> Surely if the password is say "!@#"!@*&" then all 10 characters are part of
the password. It is not for NUT to guess.
So I've run some experiments... and it seems to work as I OTOH-described
earlier.
In the new NIT tests, there are methods for
On Thu, 29 Dec 2022, Jim Klimov via Nut-upsuser wrote:
> Ah, dropping the ""s seems to have resolved it.
I think parser should ignore quotes (not take them as content -
just treat the insides as one token) unless escaped, in both config file
contexts.
Surely if the password is say
On Thu, 22 Dec 2022, Rafael Reinoso via Nut-upsuser wrote:
Some systems I have take some time to shut down, so I would like them to shut
down if the UPS have been on battery for 2 minutes.
Have a look at chapter 7 of the NUT Configuration Examples at
On Thu, 1 Dec 2022, Sam Varshavchik wrote:
Simon Wilson via Nut-upsuser writes:
I'm just looking forward to a set of RH/Fedora packages which are not
borked out of the box.
I'm not sure what's going on with that. Looking through that package, it was
built back in September, long before
On Sun, 27 Nov 2022, Simon Wilson via Nut-upsuser wrote:
Per https://networkupstools.org/docs/user-manual.chunked/ar01s06.html 6.3, am
I right in thinking, for my single server running NUT (in standalone mode)
with connected USB UPS:
- when battery.charge reaches battery.charge.low:
On Tue, 11 Oct 2022, Andrea Venturoli via Nut-upsuser wrote:
On 10/11/22 16:02, Roger Price wrote:
On Tue, 11 Oct 2022, Andrea Venturoli via Nut-upsuser wrote:
On 10/11/22 15:17, Greg Troxel wrote:
I suggest an experiment:
Thanks.
This is planned, but I can't be at this site before some
On Tue, 11 Oct 2022, Andrea Venturoli via Nut-upsuser wrote:
On 10/11/22 15:17, Greg Troxel wrote:
I suggest an experiment:
Thanks.
This is planned, but I can't be at this site before some weeks.
When you get to the site, you might be able to speed up testing by setting
battery.charge.low
On Tue, 11 Oct 2022, Andrea Venturoli via Nut-upsuser wrote:
I've got an APC SmartUPS 1500: it's connected via USB and I'm using the
usbhid-ups driver. This used to work properly until recently.
Now, when power goes out it keeps on going on battery potentially for several
minutes, but, the
On Fri, 16 Sep 2022, Joshua Quesenberry via Nut-upsuser wrote:
I’m part of team that’s been tasked with building an embedded system that does,
among other things, battery management, including behaving
like a UPS. We’d like to take full advantage of integrating with NUT and
hopefully also it
On Fri, 16 Sep 2022, Jim Klimov via Nut-upsuser wrote:
Hello all,
Here's a PR I want to ask community about: should NUT clients like upsc
report (log!) or hide the infamous 'Init SSL without certificate
database' message?
How should upsc be used in order to get SSL/TLS protection? There
RFC 9271 is now available in Japanese as 無停電電源（UPS）管理プロトコル -
コマンドと応答 https://tex2e.github.io/rfc-translater/html/rfc9271.html
Roger___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
I have updated the Configuration Examples to cover NUT 2.8.0 and TLS 1.3.
Part 1 provides detailed descriptions of basic configurations.
Part 2 describes TLS support for releases 2.7.4, 2.8.0 and mixes of the two.
Part 3 provides technical appendices, e.g. for systemd and notifications.
On Fri, 2 Sep 2022, Pavel Hofman wrote:
blazer_usb reports:
ups.model: WPHVT2K0
ups.productid: 5161
Clearly a bug in blazer_usb
If battery.charge.low is not available, perhaps it is possible to get the
same effect by watching the voltage drop to a critical value. This needs
upssched and
On Mon, 29 Aug 2022, Pavel Hofman wrote:
blazer_usb reports:
ups.model: WPHVT2K0
ups.productid: 5161
The Fortron site https://energy.fsp-europe.com/uninterruptible-power-supply/ has
no mention of these references. I wonder where blazer_usb found them?
ups.status: OL
If you unplug the
On Fri, 26 Aug 2022, Jim Klimov via Nut-upsuser wrote:
I'd expect upsmon service to only begin stopping when something like
multi-user target has finished stopping, but not sure quickly if packaging
covers that, and/or if VMs are part of that target. Maybe a "drop-in" file for
e.g. nut-client
On Wed, 24 Aug 2022, Jim Klimov wrote:
Sorry, forgot to update the News entries. And stumbled on terminology: since
this I-D is "from community" and "not an imternet standard", how should I
correctly refer to it? :) Is the following OK?
NUT protocol RFC published at
The command "systemctl status nut-driver-enumerator" in my 2.7.4 installation
returns:
● nut-driver-enumerator.service - Network UPS Tools - enumeration of
configure-file devices into systemd unit instances
Loaded: loaded (/lib/systemd/system/nut-driver-enumerator.service;
disabled;
I would like to test the new TLS support in nut 2.8.0, but Debian 11 only
provides nut 2.7.4. So I downloaded nut-2.8.0.tar.gz , unpacked and read the
instructions: "Briefly, the shell command './configure && make && make install'
should configure, build, and install this package."
I tried
It is a pleasure to report that RFC 9271 is now available at
https://www.rfc-editor.org/info/rfc9271
My thanks to everyone who contributed the documentation on which the RFC is
based. I hope that RFC 9271 will help give the NUT Project the visibility that
it deserves. The IANA port number
On Tue, 26 Jul 2022, Harlan Stenn wrote:
Perhaps you could move the Implementation Status section to a new,
informational RFC, and simply cite that new RFC in the base document?
Generating a whole new RFC just for a couple of paragraphs is a lot of work,
which editors try to avoid.
Is
The Internet Draft has progressed to the final stage known as AUTH48. The
technical contents are ok, and the reviewers are working on my british spelling,
lack of commas and other sins. The document is now known as an RFC-to-be.
Among the reviewers' comments is the following:
8)
On Tue, 19 Jul 2022, po...@elettronica.it wrote:
Hi all for more than 30 years I have been working in the ups sector I would
like to insert my ups in the nut ups tool platform
Hi Alessio, To include you in the Nut Project Hardware Compatibility List,
On Tue, 12 Jul 2022, Tyler Montney via Nut-upsuser wrote:
The only way I can get "load %" to update is by unplugging the power. 'upsc'
shows the same values. Perhaps this is because the UPS is
only sending load on this event?
Nut is latest (as of a week ago), not sure how to check the
On Wed, 13 Jul 2022, gene heskett wrote:
Question for Roger: Your alert about TLSstorm does not apply to apc's using
the usbhid-ups driver?
Hello Gene, It's currently independent of the NUT driver used. The APC
Smart-UPS feature called "SmartConnect" has its own RJ45 port on the back of the
An online newspaper for IT professionals, "The Register", reports that APC
Smart-UPS devices are vulnerable to an attack known as "TLStorm".
https://www.theregister.com/2022/03/09/tlstorm_apc_ups_critical_zero_days/
These UPS units have Internet ports, and if connected to the Internet will
On Sat, 25 Jun 2022, PeReZ via Nut-upsuser wrote:
Hi,I create a script to build a file for the dummy-ups to simulate an UPS from
other two in redundant mode for devices that allows monitoring only one UPS.
The diagram: https://imgur.com/a/z4ZUuNw
I tried this with three different browsers,
On Fri, 17 Jun 2022, gene heskett wrote:
So, since there are no man pages installed, where can I find the
docs that will guide me in configuring it from a blank slate?
A reminder that the NUT man pages are on line at
https://networkupstools.org/docs/man/index.html#User_man with the User
On Fri, 17 Jun 2022, gene heskett wrote:
So, since there are no man pages installed, where can I find the
docs that will guide me in configuring it from a blank slate?
Hello Gene, I put up some pages on NUT configurations at
http://rogerprice.org/NUT/ConfigExamples.A5.pdf
They don't cover
On Fri, 17 Jun 2022, PeReZ via Nut-upsuser wrote:
I need to manage two UPSes but my host can set and monitor only one.
How are they connected? What software are you using?
So I thinked to install NUT UPS ...
NUT in itself is not a UPS. It is a software package.
... on a Raspberry to
IANA have updated their registry for port 3493/TCP to reference the Future RFC
(no longer an I-D).
https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=3493
It uses the e-mail address i...@networkupstools.org for
the port assignee. Is this
On Tue, May 17, 2022, 06:41 Roger Price wrote:
The IESG [1] has approved the NUT I-D.
The Independent Submissions Editor tells me that the NUT I-D is now in the RFC
Editors queue for publication. Independent submissions have no special priority
and may wait one to two months.
Roger
The IESG [1] has approved the NUT I-D.
Backgound: The Internet Engineering Steering Group (IESG) is a body composed of
the Internet Engineering Task Force (IETF) chair and area directors. It provides
the final technical review of Internet standards and is responsible for
day-to-day management
On Tue, 10 May 2022, gene heskett wrote:
On Tuesday, 10 May 2022 03:13:34 EDT Roger Price wrote:
A personal comment: I am surprised by the way the IETF have handled our
text. We are being treated as if we were a formal standards group
which alone has the authority to produce a Standards Track
The discussions with IANA concluded that the following sentence should be added
to chapter 7 IANA Considerations:
This document will be added to the registration's reference field.
This is good for NUT since it makes official and permanent the relationship
between port 3493/TCP (nut) and
I am trying to understand the new 2.8.0 dummy-ups man page. I see that the old
2.7.4 behaviour of looping on the operations specified in the file named by port
= file.dev in ups.conf has changed. The ".dev" in "file.dev" now means
once-only. The user may specify the old looping behaviour by
It is a pleasure to report to you that the I-D has reached the final review
stages. The next review is the IESG (Internet Engineering Steering Group)
conflict review. This takes 5-6 weeks.
The version under review is 13: you will find the HTML at
On Tue, 19 Apr 2022, Jim Klimov wrote:
I think I committed one recently; should be possible anyhow.
On Tue, Apr 19, 2022, 14:38 Roger Price wrote:
Jim, Is this change to PROTVER possible for 2.8.0?, or should I keep
NETVER?
Ok, I will specify PROTVER in the I-D, with a note saying
On Tue, 19 Apr 2022, Greg Troxel wrote:
Roger Price writes:
On Tue, 19 Apr 2022, Matus UHLAR - fantomas wrote:
On 19.04.22 08:56, Roger Price wrote:
The problem: the I-D uses PROTVER rather than NETVER, however 2.8.0
only supports NETVER.
The argument in favour of PROTVER
On Tue, 19 Apr 2022, Matus UHLAR - fantomas wrote:
On 19.04.22 08:56, Roger Price wrote:
The problem: the I-D uses PROTVER rather than NETVER, however 2.8.0 only
supports NETVER.
The argument in favour of PROTVER is that the command is not asking for the
version of the _network_
I have received comments from the ISE (Independent Submissions Editor) on
NETVER/PROTVER and I would would like to get the list's consensus on how to
proceed.
NETVER vs PROTVER
-
The problem: the I-D uses PROTVER rather than NETVER, however 2.8.0 only
supports NETVER.
The
I tried the command SET VAR "" for containing
other than ASCII, e.g. àéïôũ. The accented characters were dropped.
Should the user expect to be able to use Unicode beyond ASCII?
If this is not possible with 2.8.0, then I propose removing all mention of
Unicode in the I-D, and saying that
On Sun, 10 Apr 2022, Manuel Wolfshant wrote:
On 4/10/22 20:45, Jim Klimov via Nut-upsuser wrote:
I believe the code only deals with '\n' character for line-breaks, in
protocol and probably configs.
I've just thrown in a quick test: I converted upsmon.conf to dos format and
restarted
The IETF requires that the I-D contain an ABNF (Augmented Backus-Naur Form)
grammar of the NUT commands and responses. At the end of each command, there is
a NEWLINE character sequence. The IETF in RFC 5234 say that NEWLINE is CRLF,
carriage return + line feed, hex 0D0A.
Is this true for
On Thu, 7 Apr 2022, Manuel Wolfshant wrote:
It is a bit stupid but nut uses a different port for so long that, to be
honest, I do not think that it matters any more.
It was not too bright of IANA to assign 401/TCP (ups) when 3493/TCP (nut) was
already available, but the problem was probably
I have received the following disappointing reply from IANA. It was precisely
the IETF review/IESG approval that I was asking for.
Meantime it seems to me to be an anomaly that the Network UPS Tools project is
not able to use port ups intended for UPS management.
I will discuss the matter
On Wed, 6 Apr 2022, gene heskett wrote:
On Wednesday, 6 April 2022 03:39:19 EDT Roger Price wrote:
Is there a maximum length for a password in NUT? Should I specify 15
or 31 characters in the grammmar?
I would be far more concerned with the minimum size, make 'em work to find it
if its
On Wed, 6 Apr 2022, Jim Klimov wrote:
Also does not seem dictated in docs nor comments. De-facto it is a string
pointer, in some code constrained by a SMALLBUF sized character array, where
SMALLBUF is a macro currently defined to 512.
I decided to fix arbitrary limits in the grammar based on
Is there a maximum length for a password in NUT? Should I specify 15 or 31
characters in the grammmar?
The IETF are wedded to US ASCII, where character = byte, so I will ignore the
question of multibyte characters.
Roger
___
Nut-upsuser mailing
Thanks for your comments. I think it's best for the formal grammar that I am
obliged to write to take a restrictive view of what is permitted, and I will
call for a leading letter A-Z or a-z.
Roger
___
Nut-upsuser mailing list
On Tue, 5 Apr 2022, Roger Price wrote:
Do we have a formal definition of a UPS name?
Should a system administrator be able to name a UPS "Bébé" or "罗杰-1" ?
Roger___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debia
On Tue, 5 Apr 2022, Roger Price wrote:
Do we have a formal definition of a UPS name? For example:
upsname = "A-Ca-c-_"+ with a minimum of 1 and a maximum of 15 characters
I should have written
upsname = "A-Ca-c0-9-_"+ with a minimum of 1 and a maximum of 15 character
Do we have a formal definition of a UPS name? For example:
upsname = "A-Ca-c-_"+ with a minimum of 1 and a maximum of 15 characters
This means that a UPS may be called "_"
Is that acceptable? Must the initial character always be a letter? Roger
The IETF review of the I-D continues, and we have reached version 09 which you
will find at
https://datatracker.ietf.org/doc/draft-rprice-ups-management-protocol/
I think the proposed text is much better following the IETF review of the
previous sections.
The next big subject in the IETF
informed of progress. Roger
-- Forwarded message --
Date: Mon, 04 Apr 2022 14:55:15 +0200
From: i...@rogerprice.org
To: i...@iana.org
Subject: Request for Assignment
Contact Name:
Roger PRICE
Contact Email:
i...@rogerprice.org
Type of Assignment:
A de-assignment of 401/TCP (ups
On Sun, 27 Mar 2022, Manuel Wolfshant wrote:
On March 27, 2022 6:57:23 PM GMT+03:00, Greg Troxel wrote:
Roger Price writes:
The IETF Independent Submissions Editor (ISE) has asked for more
detail on the command STARTTLS, in particular the use of certificates.
That's interesting, given
The IETF Independent Submissions Editor (ISE) has asked for more detail on the
command STARTTLS, in particular the use of certificates.
I propose saying that NUT 2.8.0 supports the encryption of communications
between Attachment Daemon upsd and Management Daemon upsmon using TLS 1.3
[RFC8446]
On 20.03.22 16:02, Roger Price wrote:
I received the following comment from the Independent Submissions Editor (ISE):
The command VER is hazardous because it encourages exploiting of
implementation peculiarities that are not well documented in a
protocol. The best example of such a failure
I received the following comment from the Independent Submissions Editor (ISE):
The command VER is hazardous because it encourages exploiting of
implementation peculiarities that are not well documented in a
protocol. The best example of such a failure is the browser version
field in HTTP.
The proposed RFC (known as an I-D) is now under review by the Independent
Submissions Editor. One of his comments is:
I think the entire document could benefit from a complete ABNF
grammar. Have a look at RFCs 5234 and 7405.
RFC5234 specifies a case insensitive ABNF (Augmented
On Tue, 1 Mar 2022, Arno de Kok wrote:
The NOTIFYCMD only works when I run upsmon -D.
If I run upsmon normally then I get NOTIFY message’s:
Broadcast message from nut@raspberrypi (somewhere) (Tue Mar 1 20:33:41 2022):
UPS servers@localhost on battery
But only with upsmon -D I also get the
This new version addresses comments from IETF reviewers. The changes are listed
in appendix D.7.
Roger
-- Forwarded message --
Date: Sat, 26 Feb 2022 06:32:08 -0800
From: internet-dra...@ietf.org
To: Roger Price
Subject: New Version Notification for
draft-rprice-ups
On Fri, 18 Feb 2022, Manuel Wolfshant wrote:
On February 18, 2022 12:41:39 AM GMT+02:00, Philip Taylor
wrote:
I’m wanting to run a bash script after upsmon starts. I can see it’s easy to
run a script on any notification AFTER upsmon has started using NOTIFYFLAG; but
I’m struggling to find
On Wed, 16 Feb 2022, William Cole via Nut-upsuser wrote:
I ran telnet on both machines:
First from the server [235] to the client [236]
Then from the client [236] to the server [235]
The result in both cases:
Trying 192.168.1.xxx
telnet: Unable to connect to remote host: Connection
On Mon, 14 Feb 2022, William Cole via Nut-upsuser wrote:
Here;'s the result of running upsc 1:
Init SSL without certificate database
Error: Unknown UPS
I'm trying to find out if TCP/IP based communication is possible between your
machines. Can you ssh from one to another?
Roger
On Sun, 13 Feb 2022, William Cole via Nut-upsuser wrote:
I ran both:
upsc 1LRES850@196.168.1.235
upsc 2UCES750@192.168.1.236
from the server's terminal - which is 192.168.1.235. In both cases the outcome
was:
Error: Connection failure: No route to host.
What does "upsc 1LRES850" do?
On Wed, 9 Feb 2022, William Cole via Nut-upsuser wrote:
In your last post you had suggested that I run the NUT-report bash script that
you had posted to your web site.
### /etc/nut/ups.conf ###
maxretry = 3
[1LRES850]
driver=usbhid-ups
On Fri, 4 Feb 2022, William Cole via Nut-upsuser wrote:
The entry for nut-server.service on my machine was the same as the one that you
listed.
It took me a while to locate nut-server.service, hence the delay. Here's the result of
running script -a -c"/sbin/upsd" NUT.script. Before running
On Thu, 3 Feb 2022, William Cole via Nut-upsuser wrote:
I guess I'm not understanding what "your server setup command" should be. I
looked at the manpage for script - I'm still learning all this - and
understand what the script command is to do in capturing terminal activity.
The -c
On Wed, 2 Feb 2022, William Cole via Nut-upsuser wrote:
My upsd.conf [located on the server] is set to listen as follows:
LISTEN 192.168.1.100 3493
LISTEN 192.168.1.101 3493
LISTEN 0.0.0.0 3493
LISTEN 127.0.0.1 3493
After making these changes I shut both the server and client down [sudo
On Tue, 25 Jan 2022, William Cole via Nut-upsuser wrote:
I hope that this is an appropriate post for this group. Please let me know if
it should go elsewhere.
This is the right place.
I am running NUT on RaspberryPi 3B+ [RPi] units using Buster. The NUT version
is 2.7.4.
I have two
On Wed, 19 Jan 2022, Phil Stracchino via Nut-upsuser wrote:
On 1/19/22 06:10, Roger Price wrote:
The man page for upsmon.conf explains the HOSTSYNC directive:
The explanation is clear. but the name "HOSTSYNC" is not. It seems to me
that if the directive is to provide a ma
The man page for upsmon.conf explains the HOSTSYNC directive:
HOSTSYNC seconds
upsmon will wait up to this many seconds in master mode for the
slaves to disconnect during a shutdown situation. By default, this is
15 seconds.
When a UPS goes critical (on battery + low battery, or
: Sun, 16 Jan 2022 05:53:12 -0800
From: internet-dra...@ietf.org
To: Roger Price
Subject: New Version Notification for
draft-rprice-ups-management-protocol-06.txt
A new version of I-D, draft-rprice-ups-management-protocol-06.txt
has been successfully submitted by Roger Price and posted
On Tue, 11 Jan 2022, Manuel Wolfshant wrote:
On 1/11/22 11:46, Eyal Lebedinsky wrote:
Jan 11 19:29:19 e7.eyal.emu.id.au upsdrvctl[1610]: Driver failed to start
(exit status=1)
Here is your culprit, the UPS is not seen in the moment the driver tries to
talk with it. Use a monotonic timer to
1 - 100 of 274 matches
Mail list logo
