Displaying 20 results from an estimated 80000 matches similar to: "Solaris ?"
2024 Mar 06
2
Upssched 100% CPU
Thanks for the tip.
I had downloaded a prerelease source version of NUT 2.8.1, built and installed it. Evidently there was an issue with upssched consuming 100% CPU.
I downloaded the current release and the issue has been resolved. Updating all 3 systems.
Dan
________________________________
From: Nut-upsuser <nut-upsuser-bounces+danpower2023=outlook.com at alioth-lists.debian.net> on
2024 Mar 06
1
Upssched 100% CPU
Am i the only user who has no glue about how to build a new version for my
system?
I?m running on Raspberry GNU/Linux (bullseye) v 11, which might be similar
to your system?
Sounds as if it is not a big issue to download the version and build it and
install it.
Is there anybody out there who might be able to give me a kickoff, how to do
that?
Have found various built versions here at Binary
2024 Mar 29
1
Heartbeat timer failure 15 minutes after startup
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.
Dan
________________________________
From: Nut-upsuser <nut-upsuser-bounces+danpower2023=outlook.com at alioth-lists.debian.net> on behalf of Roger Price via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>
2024 Mar 08
1
NUT 2.8.1 (source build) Pi OS bookworm 32 bit - nut-monitor trying to connect to UPS - Connection Refused
On Mar 8, 2024, at 8:22?AM, Dan Grostick via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote:
>
> I've installed 2.8.1 on a Raspberry PI 5 using Pi OS bookworm 64 bit (Debian 12) with success.
>
> When I take that same configuration to a PI 3B running bookworm 32 bit, compile from source, use the same files from /etc/nut, I get a 'nut-monitor ups at
2024 Mar 03
2
NUT 2.8.1 build from source - upssched missing
PI OS - Debian12 - Raspberry PI 5 NUT 2.8.1
I'm building from source just downloaded from GITHUB.
The error when starting NUT:
nut-monitor: /usr/sbin/upssched not found
I did a 'find / ' and upssched is not in the filesystem.
I've done a make clean, make uninstall.
then autogen.sh, make, make install
1. is there an option to make that completely removes everything? In
2024 Mar 28
2
Heartbeat timer failure 15 minutes after startup
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 what is often called upssched.conf and has a 660 sec timer. So it looks as
if the
2024 Mar 05
1
Upssched 100% CPU
Hi,
On Tue, Mar 05, 2024 at 08:37:32AM +0000, Dan Grostick via Nut-upsuser wrote:
> My Raspberry PI 3B was overheating - 70 degrees C. I used Top and
> it turns out that upssched is taking 100% CPU. Debian 11 (PI Os).
> I have two others running the same configuration, 2.8.1 with no
> problems.
I have no first hand knowledge of this issue, but in the change log
for the 2.8.1
2024 Feb 19
1
msmtp not running in upssched-cmd
On 19.02.24 14:48, Dan Grostick via Nut-upsuser wrote:
>Msmtp is not sending messages when invoked from upssched-cmd.
>I can manually invoke it from the command line.
where is its config file?
>There is a 's' instead of an 'x' in the ls -l. Might this be some sort of
>permission problem?
Should not be the case.
>upsmon.conf has run user as root.
msmtp may use
2024 Mar 29
2
Heartbeat timer failure 15 minutes after startup
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"
report the UPS's? If you use systemd, what does the command
2024 Feb 23
0
Getting two notifications of nocomm-timer expired when USB cable is pulled from the UPS
NUT 2.8.01
When I pull the USB cable from the UPS, I get two notifications of the nocomm-timer expired. The first notification is in the proper sequence, the second notification occurs after 'commok' occurs. Seems somehow that upssched-cmd is getting a second nocomm-timer expired delayed.
Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2024 Sep 06
0
Nut-upsuser Digest, Vol 231, Issue 1
As fast as I know, the standard NUT package will not command your power
supply off unless customizations are made. Devices like Synology have an
option to command the UPS off. What is acting as your NUT server? Your
server PC?
On Fri, Sep 6, 2024, 11:10 AM <nut-upsuser-request at alioth-lists.debian.net>
wrote:
> Send Nut-upsuser mailing list submissions to
> nut-upsuser at
2024 Mar 28
1
Heartbeat timer failure 15 minutes after startup
I have 3 Raspberry Pi NUT 2.8.1 systems running PI OS. (Debian 11 and 12)
All three systems have a heartbeat-timer failure approximately 15 minutes after starting NUT. No subsequent failures. Any ideas on what is happening?
Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2023 Jun 16
1
Dummy-ups cycles between online and onbatt every 5 minutes. (Nut 2.8.0)
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.
Also "online" and "onbatt" are broadcast to the console probably via WALL. (The state changes don't seem to be form the ups as upsshed-cmd doesn't run). Upssched-cmd does run when the UPS
2023 Jun 14
1
Accessing: upsstats.cgi Error: no hosts to monitor (check hosts.conf)
Not fully true about example configs in docs: man pages for CGI bits have
some :)
https://github.com/networkupstools/nut/blob/master/docs/man/upsset.conf.txt
https://github.com/networkupstools/nut/blob/master/docs/man/upsstats.cgi.txt
https://github.com/networkupstools/nut/blob/master/docs/man/hosts.conf.txt
etc.
Other than that, check permissions - e.g. OTOH if Apache user may read your
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
That is terminology from Computer Science. (Decades ago?) It is familiar. Not invented by Cisco. As in, producer-consumer, from the same time. Those were all different paradigms for client-server relationships. There must be Wikipedia citations that can be consulted. As I recall, there were distinctions, such as, producer-consumer were tightly bound, where the producer had no purpose
2024 Sep 07
2
Nut-upsuser Digest, Vol 231, Issue 2
THIS IS systemctl list-units | grep UPS
nut-driver at back-ups.service
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
I didn't go there due to its use by Cisco.
On Fri, Mar 12, 2021, 10:03 PM Baker, Lawrence M via Nut-upsuser <
nut-upsuser at alioth-lists.debian.net> wrote:
> Jim,
>
> The terminology I recall for that one-to-many relationship is
> publisher-subscriber.
>
> Larry Baker
> US Geological Survey
> 650-329-5608
> baker at usgs.gov
>
>
>
> On Mar 12
2023 Jun 14
1
Accessing: upsstats.cgi Error: no hosts to monitor (check hosts.conf)
Dan Grostick via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>
writes:
> When Apache starts is complains about not finding the fully qualified domain name.
That seems normal
> In the past, upsstats.cgi would just load. I didn?t have to do any Apache2 configuration. I don?t know what has changed.
in general this does need configuration. read the apache config file.
read the
2021 Apr 01
0
On retiring some terminology
Hello all,
As some people watching GitHub closely might have noticed, the majority
of proposed changes (for primary/secondary in the end) were merged around
weekend. This impacts text documentation and keyword support for upsmon
configuration, testing welcome :)
Some work remains for image files in documentation, and the protocol/ABI
were not touched so far.
Following the recent eminent
2021 Mar 13
1
[EXTERNAL] Re: On retiring some terminology
Jim,
The terminology I recall for that one-to-many relationship is publisher-subscriber.
Larry Baker
US Geological Survey
650-329-5608
baker at usgs.gov<mailto:baker at usgs.gov>
On Mar 12 2021, at 6:24:38 PM, Phil Stracchino via Nut-upsuser <nut-upsuser at alioth-lists.debian.net<mailto:nut-upsuser at alioth-lists.debian.net>> wrote:
This email has been received from